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
I think it would be nice if the confounds JSON file included the units of motion-related columns.
This could be done for all motion-related confounds, but I think it's most important for the rotation columns.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
This stems from PennLINC/xcp_d#1053. Basically, a user wants me to include metadata for the motion parameters in XCP-D. I'm happy to do that, but I thought it would make more sense to inherit the metadata from the preprocessing pipeline (i.e., fMRIPrep).
The text was updated successfully, but these errors were encountered:
I know that the units of the motion parameters (mm for translations and radians for rotations) is enforced in BEP012 (Functional Derivatives) (see here) and the units are documented in the init_bold_confs_wf docstring, but neither location is particularly obvious to users.
Closes#3231.
## Changes proposed in this pull request
- Add metadata, including Units, for motion parameters (6 basic
parameters and FD).
- I included FD because it might be good to log the head radius that is
used to calculate it at some point (e.g., if
nipreps/nibabies#198 moves forward)
## Documentation that should be reviewed
none
---------
Co-authored-by: Chris Markiewicz <effigies@gmail.com>
What would you like to see added in fMRIPrep?
I think it would be nice if the confounds JSON file included the units of motion-related columns.
This could be done for all motion-related confounds, but I think it's most important for the rotation columns.
Do you have any interest in helping implement the feature?
Yes
Additional information / screenshots
This stems from PennLINC/xcp_d#1053. Basically, a user wants me to include metadata for the motion parameters in XCP-D. I'm happy to do that, but I thought it would make more sense to inherit the metadata from the preprocessing pipeline (i.e., fMRIPrep).
The text was updated successfully, but these errors were encountered: