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

Motion-BIDS for MRI #1847

Open
JuliusWelzel opened this issue Jun 5, 2024 · 4 comments
Open

Motion-BIDS for MRI #1847

JuliusWelzel opened this issue Jun 5, 2024 · 4 comments

Comments

@JuliusWelzel
Copy link
Collaborator

Your idea

Hi,

Many MRI researchers have approached me about the Motion-BIDS specifications. They would like to know if the motion from a subject could also be expressed as motion data in BIDS. As I have not worked with an MRI before, I could not tell, but I wanted to know if some MRI people could help us include this in the specifications.

@Remi-Gau
Copy link
Collaborator

@Remi-Gau
Copy link
Collaborator

Also note that if the motion data was computed after acquisition it goes into deiratives:
https://bids-specification--519.org.readthedocs.build/en/519/derivatives/functional-derivatives.html#motion-related-time-series

@Remi-Gau
Copy link
Collaborator

Not sure if we should care about anything related to storing motion computed for prospective motion correction in MRI scanner. I think those are mostly used for structural MRI AFAIK.

@JuliusWelzel
Copy link
Collaborator Author

Maybe worth adding a note and a link to this in the motion page ?

That is a good point, thanks. Do you know the leads for the MRI or would the maintainers review such a PR for the website?

Regarding storing it as derivatives, would it be stored in an extra directory but using the same layout as raw motion data?

    sub-<label>/
        derivatives/
           motion/
            <source_entities>[_desc-<label>]_motion.tsv
            <source_entities>[_desc-<label>]_motion.json

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

2 participants