Configuration options

When using the programmatic interface of this package, the configuration options used by the different parts of the sending operation are given as objects. See SenderConfig, MeasurementSetDataSourceConfig, HardcodedDataSourceConfig, SdpConfigDbConfig, Config and Spead2TransmissionConfig for details.

From nested dictionaries

When using the command-line interface, options can be specified either in a YAML configuration file, or individually via the emu-send -o option. In both cases options live within a group or category, and have a name and a value, and thus the overall configuration can be specified as a top-level dictionary with group names as keys, and group dictionaries as values. To preserve backwards compatibility, the programmatic entry points still accept this dictionary-based configuration approach too.

These options are used to populate a SenderConfig object as follows:

• Within each group, the key names are directly mapped to the corresponding configuration object member.

• The sender group is used to populate the options in the top-level SenderConfig object.

• The ms (previously reader) group is used to populate the options in the MeasurementSetDataSourceConfig object under ska_sdp_cbf_emulator.packetiser.SenderConfig.ms.

• The hardcoded group is used to populate the options in the HardcodedDataSourceConfig object under ska_sdp_cbf_emulator.packetiser.SenderConfig.ms.

• The sdp_config_db group is used to populate the options in the SdpConfigDbConfig object under ska_sdp_cbf_emulator.packetiser.SenderConfig.sdp_config_db.

• The transmission group is used to populate the options in the Config (or subclass) object under ska_sdp_cbf_emulator.packetiser.SenderConfig.transmission.