-
Notifications
You must be signed in to change notification settings - Fork 52
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
Filter out phase, real, and imaginary data in collect_data #591
Comments
Perhaps this could be done simply at the following location. niworkflows/niworkflows/utils/bids.py Lines 168 to 176 in 6488ef7
The change could be the following, although I'm not 100% sure. Thanks to @effigies for the recommendation! queries = {
"fmap": {"datatype": "fmap", "part": ["mag", None]},
"bold": {"datatype": "func", "suffix": "bold", "part": ["mag", None]},
"sbref": {"datatype": "func", "suffix": "sbref", "part": ["mag", None]},
"flair": {"datatype": "anat", "suffix": "FLAIR", "part": ["mag", None]},
"t2w": {"datatype": "anat", "suffix": "T2w", "part": ["mag", None]},
"t1w": {"datatype": "anat", "suffix": "T1w", "part": ["mag", None]},
"roi": {"datatype": "anat", "suffix": "roi"},
} |
I think #594 should have closed this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
BIDS has recently added a new entity,
part
, to indicate the part of the complex signal an MRI file corresponds to (see bids-standard/bids-specification#424). The default is magnitude, so files without the entity can be assumed to be useable (along withpart-mag
), but files with values ofpart-imag
,part-real
, andpart-phase
should be filtered out at data collection.This new change also deprecated the
phase
suffix for phase fMRI data, and instead recommends usingpart-phase
with thebold
suffix, so this has the possibility of causing problems for both single-band reference images and BOLD files.A minor note: The specification has not had a release since the part entity was added, but that will likely happen within the next month or so, so I thought it would be best to raise an issue here earlier rather than later.
The text was updated successfully, but these errors were encountered: