Basic EVAM Configuration

EVAM exposes multiple application related fields in the config file. The configuration file is expected to be created at [EVAM_WORKDIR]/configs/default/config.json on your host machine.

Here is a sample of basic config file.

{
    "config": {
        "pipelines": [
            {
                "name": "pallet_defect_detection",
                "source": "gstreamer",
                "pipeline": "{auto_source} name=source  ! decodebin ! videoconvert ! gvadetect name=detection model-instance-id=inst0 ! queue ! gvawatermark ! gvafpscounter ! gvametaconvert add-empty-results=true name=metaconvert ! gvametapublish name=destination ! appsink name=appsink",
                "parameters": {
                    "type": "object",
                    "properties": {
                        "detection-properties": {
                             "element": {
                                "name": "detection",
                                "format": "element-properties"
                              }
                        }
                    }
                },
                "auto_start": false
            }
        ]
    }
}

The following table describes the essential attributes that are supported in the config section.

Parameter	Description
logging	Set log level for "C_LOG_LEVEL", "PY_LOG_LEVEL". Default is INFO.
pipelines	List of DLStreamer pipelines.

The parameters applicable for each pipeline are described below.

Parameter	Description
name	Name of the pipeline. This is used to differentiate pipeline URL in CURL command e.g. [SERVER-IP]/pipelines/user_defined_pipelines/[NAME]
pipeline	DLStreamer pipeline description.
source	Source of the frames. This should be "gstreamer" or "image-ingestor".
parameters	Optional JSON object specifying pipeline parameters that can be customized when the pipeline is launched
auto_start	The Boolean flag for whether to start the pipeline on EVAM start up.
queue_maxsize	Optional queue size to limit the output buffer from appsink element.
udfs	UDF config parameters

Refer this tutorial to update config file and deploy EVAM with updated configs.

EVAM pipelines are executed by GStreamer, hence to realize any usecase users will have to create their pipeline using GStreamer. Refer GStreamer Documentation and GStreamer Plugins for detailed guidelines on constructing pipelines.