You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What would you like to see added in fMRIPost-AROMA?
Hi, for one of my projects I had in mind to feed the outputs of fMRIPost-AROMA to XCP-D in the CIFTI file format, so I was interested in having the data denoised in the fsLR 91k template instead of MNI152 if possible.
However, the --output-spaces flag doesn't seem to be available so I can't specify it (I'm using the latest version of your tool with Docker and I get an 'unrecognized arguments' error related to that).
I thought I would report this assuming it's something you were planning to implement anyway at some point given it's in the documentation (https://fmripost-aroma.readthedocs.io/latest/spaces.html). But please let me know if you can confirm this first..
Thank you for your work!
Marco
Do you have any interest in helping implement the feature?
Yes, but I would need guidance
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered:
What would you like to see added in fMRIPost-AROMA?
Hi, for one of my projects I had in mind to feed the outputs of fMRIPost-AROMA to XCP-D in the CIFTI file format, so I was interested in having the data denoised in the fsLR 91k template instead of MNI152 if possible.
However, the --output-spaces flag doesn't seem to be available so I can't specify it (I'm using the latest version of your tool with Docker and I get an 'unrecognized arguments' error related to that).
I thought I would report this assuming it's something you were planning to implement anyway at some point given it's in the documentation (https://fmripost-aroma.readthedocs.io/latest/spaces.html). But please let me know if you can confirm this first..
Thank you for your work!
Marco
Do you have any interest in helping implement the feature?
Yes, but I would need guidance
Additional information / screenshots
No response
The text was updated successfully, but these errors were encountered: