services.yaml
services.yaml defines the available services in the system.
Each service includes its unique ID, name, description, input and output data types, and a reference to its specific
configuration file.
These pre-defined services can be orchestrated in the DAG Orchestration page of frontend UI to build complex applications after running system.
# A list of services available in the system.
# Each services will be decorated in a processor container in the upper layer system.
- id: car-detection # Unique identifier for the service.
service: car-detection # Real invoking service related to images in "https://hub.docker.com/u/dayuhub" or code in "dependency/core/applications"
name: car detection # Human-readable name of the service.
description: car detection (detection + tracking) # Description of the service.
input: [frame] # Input data forms for the service.
output: [bbox] # Output data forms for the service.
yaml: car-detection.yaml # YAML defining the service, included in 'processor/' directory
- id: license-plate-recognition
service: license-plate-recognition
name: license plate recognition
description: license plate recognition
input: [bbox]
output: [text]
yaml: license-plate-recognition.yaml
- id: traffic-detection
service: traffic-detection
name: traffic detection
description: traffic detection for vehicles, pedestrians, cyclists, lights, and signs
input: [frame]
output: [bbox]
yaml: traffic-detection.yaml
- id: risk-graph-generation
service: risk-graph-generation
name: risk graph generation
description: traffic risk and violation event graph generation
input: [segmentation, text, trajectory]
output: [graph]
yaml: risk-graph-generation.yaml
# ......
input and output must be YAML lists, even when the service has only one input or output form. The labels describe
payload form rather than business meaning. Common labels include frame, bbox, text, segmentation, track,
attribute, trajectory, pose, and graph.
The input/output forms defined in services must be compatible when orchestrating DAG-structured applications. For
example, a service that outputs [bbox] can feed a downstream service that requires [bbox].
For the built-in structured traffic service catalog, see Application Service Layer. Implementation-specific backend and recommended DAG details are maintained in the Structured Traffic Services reference.