PipelineElement

PipelineElement inheritance diagram
- class savant.config.schema.PipelineElement(element='???', element_type=None, version='v1', name=None, properties=<factory>)
Base pipeline element configuration template. Validates entries in a module config file under
pipeline.source,pipeline.elementsandpipeline.sink.Look for examples in
elementdocumentation.- element: str = '???'
Either a Gstreamer element name (gst factory name) or a short notation string to define
element,element_typeandversionat the same time.Short notation string format is
<element>@<element_type>:<version>Note
Version is
v1by default.Examples.
The following three element definitions are equivalent:
- element: nvinfer element_type: attribute_model version: v1 ... - element: nvinfer@attribute_model:v1 ... - element: nvinfer@attribute_model
Some elements might not have subtypes, in this case
versionin the short notation can be defined immediately after theelement:- element: drawbin:v1 location: /data/frames/image_%06d.jpg
Warning
Mixing short notation and full definition is not supported.
Examples of unsupported notation mixing:
- element: nvinfer@attribute_model version: v1 ... - element: nvinfer:v1 element_type: attribute_model ... - element: nvinfer element_type: attribute_model:v1
- element_type: str | None = None
Element type/subtype, can be defined as a substring of the
element.For example,
detectorin- element: nvinfer@detector
- version: str = 'v1'
Element version, can be defined as a substring of the
element.For example,
v1in- element: nvinfer@detector:v1
- name: str | None = None
GstElement instance name. Arbitrary string, useful for identifying pipeline elements.
- property full_name
Full element name.