-
Notifications
You must be signed in to change notification settings - Fork 1
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
Comments
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 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?
|
@jcohenadad the key/value pairs for magnetization transfer are now The One other thing worth noting is that BEP001 also deprecates the suffix Hope that helps! |
Awesome! That does help. Thank you so much.
Ah! I'm glad about this change. I always found it confusing to have T1"w" and T2"w" but not PD"w". Thanks! |
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
The text was updated successfully, but these errors were encountered: