SDS Utilities - Observations

[ReinhardKeil]

This are a list of observations and small issues that might be addressed over time.

1. Consistency of parameters

• most utilities use -i to specify an SDS input file. However some are using -s
• there could be also useful defaults for output files names (derived from input filename), so that the option could be optional

2. sds-convert

• simple_csv should be actually csv (as it is a plain CSV file)
• qeexo_v2_csv should be revisited (it's powerful, but needs perhaps more explanation)

3. in YML metadata files frequency could be optional, for cases where the frequency does not matter.

• utilities react differently to a missing frequency. Some have a clear error message, while others just output some Python script.

4. Control Interface

• consider to use the SDSIO-Server as control interface channel. This would remove the need for another UART or push button channel. In general the Control Interface should be more generic and perhaps support also user commands.
  See also: https://arm-software.github.io/SDS-Framework/main/theory.html#sdsio-server-protocol
  • More detailed proposal: Add sdsFlags and Firmware status: exchange between SDS firmware and SDS host (server) #207

[MiloradCvjetkovic]

For item 3. in YML metadata files frequency could be optional, for cases where the frequency does not matter.
maybe the frequency could be derived from the timestamp data in the SDS files.