DigitalDownConverter — Services

The pipeline runs as a single Docker container managed by the EDD Master Controller. It does not start automatically at provision time; the Master Controller starts it on demand when an observation requires it.

Container

Property	Value
Container name	`ddc_processor`
Docker image	`edd_dbbc`
Start command	`edd_ddc_processor --host=<edd_subnet> --port=<bind_port>`
Registered with Master Controller	Yes (`register_as_pipeline: True`)
Restart policy	Controlled by Master Controller

Sidecar Services

Sidecar	Purpose
Redis	Stores pipeline index assignment across multiple pipeline instances
InfluxDB	Receives time-series metrics from the pipeline

Grafana Dashboards

The following dashboard panels are installed at provision time:

Panel	Contents
`pipeline_status.json`	KATCP state machine state, error indicators
`mkrecv_status.json`	SPEAD2 capture statistics (heap rates, drop rates)
`dada_monitor.json`	PSRDADA ring buffer fill levels

Ports

Port	Protocol	Direction	Description
`bind_port` (default 0)	TCP	inbound	KATCP control
configured via `input_data_streams`	UDP multicast	inbound	SPEAD2 input
configured via `output_data_streams`	UDP multicast	outbound	SPEAD2 output