Skip to content
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

adding BIDS EchoTime1, EchoTime2 metadata for fieldmaps? #139

Closed
kjamison opened this issue Oct 24, 2017 · 5 comments
Closed

adding BIDS EchoTime1, EchoTime2 metadata for fieldmaps? #139

kjamison opened this issue Oct 24, 2017 · 5 comments

Comments

@kjamison
Copy link

This might not be within the scope of dcm2niix, but for multi-TE B0 fieldmaps, BIDS metadata expects something like "EchoTime1" "EchoTime2", so that you can extract a delta-TE for preprocessing. Is it possible to automatically add something like that to the BIDS json when appropriate?

@neurolabusc
Copy link
Collaborator

I do not think this is required, as dcm2niix should save each echo as a separate NIfTI volume with its own json file - so both the NIfTI descrip field and BIDS files should report the echo time for the volume. Images from multiple TRs (e.g. fMRI data) and data with different B-vectors (DTI) are stacked as 4D data, where different echo times and different coils are segmented in different files. I think this is convenient for most tools, which expect data segmented this way. For example it is possible to create fMRI runs with multiple echoes, but the software expects two 4D files with X/Y/Z/T rather than a single volume with X/Y/Z/T/E. As ever, I leave @chrisfilo as the final say for BIDS information, but I think the current solution is consistent and simple. If you have any data that is not segmented like this, I would be interested in seeing a sample.

@chrisgorgo
Copy link
Collaborator

EchoTime1 and EchoTime2 fields are only required when the scanner outputs phase difference volume instead of two phase volumes (see https://docs.google.com/document/d/1HFUkAEE-pB-angVcYe6pf_-fVf4sCpOHKesUvfb8Grc/edit#heading=h.fexn37cr2yum).

In case of two separate volumes each should have it's own sidecar file with EchoTime field (which is what I think dcm2niix is producing).

@kjamison
Copy link
Author

kjamison commented Oct 25, 2017 via email

@chrisgorgo
Copy link
Collaborator

I see - in this case it would be optimal if dcm2niix produced 14_FIeldMap_e2.json that includes EchoTime1 and EchoTime2 fields.

@mharms
Copy link
Collaborator

mharms commented Oct 25, 2017 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants