We expect the use pattern for a NCD created by sigmf.fromfile() to be that you open your wav/bluefile/etc and then save a .sigmf-meta adjacent to that file with meta.tofile('whatever.sigmf-meta').
Now if you instead decide to do meta.tofile('whatever.sigmf') then it will create a tar with the metadata and no data file. This creates an unreadable .sigmf archive.
Options
- Disallow writing archives from NCD datasets
- Write the original
whatever.bluefile into the whatever.sigmf archive along with the NCD whatever.sigmf-meta. This technically complies with the SigMF spec (archives MAY contain other files), but something reading a .sigmf file might be confused by NCD files.
- Convert the NCD to a "normal" file before writing it into an archive. This may be complex due to multiple captures and multiple
header-bytes and trailing-bytes fields that can exist in NCDs.
We expect the use pattern for a NCD created by
sigmf.fromfile()to be that you open yourwav/bluefile/etcand then save a.sigmf-metaadjacent to that file withmeta.tofile('whatever.sigmf-meta').Now if you instead decide to do
meta.tofile('whatever.sigmf')then it will create atarwith the metadata and no data file. This creates an unreadable.sigmfarchive.Options
whatever.bluefileinto thewhatever.sigmfarchive along with the NCDwhatever.sigmf-meta. This technically complies with the SigMF spec (archives MAY contain other files), but something reading a .sigmf file might be confused by NCD files.header-bytesandtrailing-bytesfields that can exist in NCDs.