Summary
--sd-export-csv requires an explicit --sd-parse <path> and is rejected when the parse source is supplied via --sd-capture-parse:
$ ... --sd-capture-parse capture.bin --sd-export-csv capture.csv ...
--sd-export-csv requires --sd-parse <path>.
This is surprising because --sd-capture-parse internally sets SdParsePath and runs the same parse path (RunSdCardParseAsync) that already honors SdExportCsvPath — the arg validation just runs before that assignment. Users must run two separate commands (capture, then parse+export) to go from a live capture to a CSV.
Suggested fix
Allow --sd-export-csv when either --sd-parse or --sd-capture-parse is present, so a live capture can be exported to CSV in one invocation.
Minor UX only. Found during daqifi-core v1.2.0 pre-release hardware testing.
Summary
--sd-export-csvrequires an explicit--sd-parse <path>and is rejected when the parse source is supplied via--sd-capture-parse:This is surprising because
--sd-capture-parseinternally setsSdParsePathand runs the same parse path (RunSdCardParseAsync) that already honorsSdExportCsvPath— the arg validation just runs before that assignment. Users must run two separate commands (capture, then parse+export) to go from a live capture to a CSV.Suggested fix
Allow
--sd-export-csvwhen either--sd-parseor--sd-capture-parseis present, so a live capture can be exported to CSV in one invocation.Minor UX only. Found during daqifi-core v1.2.0 pre-release hardware testing.