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

Clarifications on input structure for most functions #38

Open
gdevenyi opened this issue Mar 20, 2024 · 3 comments
Open

Clarifications on input structure for most functions #38

gdevenyi opened this issue Mar 20, 2024 · 3 comments

Comments

@gdevenyi
Copy link

When working with our various quantitative imaging components, we follow a BIDSified format where all our inputs are separate files. It appears various functions in QUIT require images with stacked-dimensionality of some kind to store multiple image inputs for processing (ex #37)

Could you please provide some additional documentation on the expected input format for the various functions? Thanks!

@spinicist
Copy link
Owner

All the QUIT commands require the main inputs to be "stacked" along the 4th / time dimension in the input nifti file. My own qMRI sequences on GE write out DICOMs that will convert to the corresponding niftis, and I find the format to be far more convenient to work with than separate files. For instance, CEST experiments usually have >20 offset frequencies, it's much easier to have one file than 20 separate ones. It's also the convention for diffusion imaging.

This is one of several reasons I have ignored BIDS as much as possible.

@gdevenyi
Copy link
Author

gdevenyi commented May 1, 2024

Can you please enhance the documentation regarding the expected order of these stacked 4D files where possible? Thanks.

@spinicist
Copy link
Owner

What documentation do you want to see and where do you want it to go?

I do not mean to be obtuse - as I started working with fsl, and this is the way all the fsl tools work, I've taken this format to be self-evident.

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