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

Add magnetization transfer #6

Closed
tsalo opened this issue Aug 3, 2020 · 5 comments
Closed

Add magnetization transfer #6

tsalo opened this issue Aug 3, 2020 · 5 comments
Labels
1.0-compatible These can be proposed for the specification in its current form.

Comments

@tsalo
Copy link
Member

tsalo commented Aug 3, 2020

Also find a way to organize data for MT-related protocols (e.g. mt0+mt1 to compute MTR, mt0+mt1+t1w to compute MTsat, etc.). B1 mapping should also be accounted for in case researchers acquire it (but then, B1 map could be used for other purposes than MT protocol, so maybe not put it in the mt folder).

Original authors: @jcohenadad

@tsalo
Copy link
Member Author

tsalo commented Aug 3, 2020

I believe that MT (both as an entity and as multiple suffixes) was rolled into BEP-001 (see bids-standard/bids-specification#508), so I'm going to label this as 1.0-compatible, but I'll hold off on closing it until BEP-001 has been merged.

@tsalo tsalo added the 1.0-compatible These can be proposed for the specification in its current form. label Aug 3, 2020
@tsalo
Copy link
Member Author

tsalo commented Dec 27, 2020

mt was added to the specification in bids-standard/bids-specification#681, so I'm closing now.

@tsalo tsalo closed this as completed Dec 27, 2020
@jcohenadad
Copy link

@tsalo this is awesome! thank you so much for this new feature. I can see the new MT-related fields were added to the latest doc, however I am not sure how file should be named. Should it be something like this?

sub-01_acq-MTState1_PD.nii.gz

@tsalo
Copy link
Member Author

tsalo commented Dec 27, 2020

@jcohenadad the key/value pairs for magnetization transfer are now mt-on or mt-off, and the entity goes between the new inv and part entities in filenames. In your case, I believe you'd want sub-01_mt-on_PD.nii.gz (for the file with the metadata field MTState set to True, I think) and sub-01_mt-off_PD.nii.gz (when MTState is False).

The mt entity has been accepted, so it will become officially supported in the next release (1.5.0), but currently it's not supported in pybids, bids-matlab, or bids-validator, although those are all on our to-do list.

One other thing worth noting is that BEP001 also deprecates the suffix PD in favor of PDw (for arbitrarily-scaled maps) and PDmap (for quantitative maps). The associated PR (bids-standard/bids-specification#690) is not yet merged, but I think now's a good opportunity to adopt the new naming convention.

Hope that helps!

@jcohenadad
Copy link

@jcohenadad the key/value pairs for magnetization transfer are now mt-on or mt-off, and the entity goes between the new inv and part entities in filenames. In your case, I believe you'd want sub-01_mt-on_PD.nii.gz (for the file with the metadata field MTState set to True, I think) and sub-01_mt-off_PD.nii.gz (when MTState is False).

Awesome! That does help. Thank you so much.

One other thing worth noting is that BEP001 also deprecates the suffix PD in favor of PDw

Ah! I'm glad about this change. I always found it confusing to have T1"w" and T2"w" but not PD"w". Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.0-compatible These can be proposed for the specification in its current form.
Projects
None yet
Development

No branches or pull requests

2 participants