diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 000000000..e69de29bb diff --git a/404.html b/404.html new file mode 100644 index 000000000..5b9fd0f6c --- /dev/null +++ b/404.html @@ -0,0 +1,1413 @@ + + + +
+ + + + + + + + + + + + + + + + +paz.abstract.loader.Loader(path, split, class_names, name)
+
Abstract class for loading a dataset.
+Arguments
+Properties
+Methods
+load_data()
+load_data()
+
Abstract method for loading dataset.
+Returns
+dictionary containing absolute image paths as keys, and +ground truth vectors as values.
+ + + + + + + + + + + + + +paz.abstract.messages.Box2D(coordinates, score, class_name=None)
+
Bounding box 2D coordinates with class label and score.
+Properties
+[x_min, y_min, x_max, y_max]
coordinates.Methods
+contains()
+contains(point)
+
Checks if point is inside bounding box.
+Arguments
+Returns
+Boolean. 'True' if 'point' is inside bounding box. + 'False' otherwise.
+paz.abstract.messages.Pose6D(quaternion, translation, class_name=None)
+
Pose estimation results with 6D coordinates.
+Properties
+None
indicating the class label name of
+ the object.Class Methods
+Pose6D
object using a
+ rotation and a translation vector.paz.abstract.processor.Processor(name=None)
+
Abstract class for creating a processor unit.
+Arguments
+Methods
+call()
+Example
+class NormalizeImage(Processor):
+def __init__(self):
+ super(NormalizeImage, self).__init__()
+
+def call(self, image):
+ return image / 255.0
+
Why this name?
+Originally PAZ was only meant for pre-processing pipelines that
+included data-augmentation, normalization, etc. However, I found
+out that we could use the same API for post-processing; therefore,
+I thought at the time that Processor
would be adequate to describe
+the capacity of both pre-processing and post-processing.
+Names that I also thought could have worked were: Function
,
+Functor
but I didn't want to use those since I thought they could
+also cause confusion. Similarly, in Keras this abstraction is
+interpreted as a Layer
but here I don't think that abstraction
+is adequate. A layer of computation maybe? So after having this
+thoughts swirling around I decided to go with Processor
+and try to be explicit about my mental jugglery hoping the name
+doesn't cause much mental overhead.
call(X)
+
Custom user's logic should be implemented here.
+paz.abstract.processor.SequentialProcessor(processors=None, name=None)
+
Abstract class for creating a sequential pipeline of processors.
+Arguments
+Processor
+ classes.Methods
+add() +remove() +pop() +insert() +get_processor()
+Example
+AugmentImage = SequentialProcessor()
+AugmentImage.add(pr.RandomContrast())
+AugmentImage.add(pr.RandomBrightness())
+augment_image = AugmentImage()
+
+transformed_image = augment_image(image)
+
add(processor)
+
Adds a process to the sequence of processes to be applied to input.
+Arguments
+Processor
.remove(name)
+
Removes processor from sequence
+Arguments
+pop(index=-1)
+
Pops processor in given index from sequence
+Arguments
+insert(index, processor)
+
Inserts processor
to self.processors queue at index
Argument
+Processor
.get_processor(name)
+
Gets processor from sequencer
+Arguments
+paz.abstract.sequence.ProcessingSequence(processor, batch_size, data, as_list=False)
+
Sequence generator used for processing samples given in data
.
Arguments
+data
.processor
.inputs
and labels
are dispatched as
+ lists. If false inputs
and labels
are dispatched as
+ dictionaries.paz.abstract.sequence.GeneratingSequence(processor, batch_size, num_steps, as_list=False)
+
Sequence generator used for generating samples.
+Arguments
+samples
.inputs
and labels
are dispatched as
+ lists. If false inputs
and labels
are dispatched as
+ dictionaries.{"use strict";/*!
+ * escape-html
+ * Copyright(c) 2012-2013 TJ Holowaychuk
+ * Copyright(c) 2015 Andreas Lubbe
+ * Copyright(c) 2015 Tiancheng "Timothy" Gu
+ * MIT Licensed
+ */var Va=/["'&<>]/;qn.exports=za;function za(e){var t=""+e,r=Va.exec(t);if(!r)return t;var o,n="",i=0,a=0;for(i=r.index;i