-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
--datalad option : Can it aggregate-metadata by individual subject/session to be used by datalad metadata search? #235
Comments
For DICOMs, you would need to have dicoms around and enable 'dicom' extractor. With current heudiconv approach to DICOMS (storing them in the tarballs), there is no way to "extract" it (see related datalad/datalad-neuroimaging#32). So you would want to either add dicoms manually extracted from those tarballs, or just add another (sub?)dataset with the original dicoms, where you actually extract metadata. For bids, you need to enable bids extractor (and probably you would want nifti1 as well)
in the dataset where you want to enable those. Note that you would need datalad-neuroimaging extension installed |
Ok I have:
|
It is just an empty list since all of them moved into the main set of dependencies, but this would allow external tools which demanded it before still function without fixups, see e.g nipy/heudiconv#235 (comment)
Let's see if pybids authorities return back analysis or we just drop it ;-) |
I have converted a collection of dicoms to BIDS using heudiconv, with the datalad option, and passing multiple dicoms by subject option
-s
.Dicom metadata have been transferred into .heudiconv metadata files, e.g.
.heudiconv/DICOM-NAME/info/dicominfo.tsv
, I would like to make that available todatalad search
. Runningdatalad aggregate-metadata
only seems to capture top-level contents, and ignores lower level BIDS metadata files.Is there a way to convince datalad to ingest BIDS json and tsv metadata so it will be available to datalad searches?
The text was updated successfully, but these errors were encountered: