You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should we save the options passed to the converter? I guess some of them are intrinsically stored in the zarr (all the chunking options and stuff), but maybe the full command should be also stored nonethless?
The text was updated successfully, but these errors were encountered:
dcm2niix (a widely used software to convert DICOM data to BIDS) saves itself in the sidecar json file of the converted file, using keys "ConversionSoftware" and "ConversionSoftwareVersion". We should do the same. We could also add "ConversionSoftwareOptions" and save the arguments as a JSON.
This makes me think that we should write BIDS-compatible sidecar JSON's for most of these files. But we need data-generating sites to provide us with proper metadata. I'll open another issue for this.
Should we save the options passed to the converter? I guess some of them are intrinsically stored in the zarr (all the chunking options and stuff), but maybe the full command should be also stored nonethless?
The text was updated successfully, but these errors were encountered: