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
Background: In the v4.0.0 HCPpipelines version of ICAFIX/hcp_fix, we added the capability to control whether the motion parameters were regressed out of the data as part of the fix-cleaning (via the do_motion_regression argument). [Prior to that (e.g., v3.27.0 and earlier), regression of the motion parameters was always applied].
FIX was originally written for volume (NIFTI) data, with the assumption that any high-pass filtering was applied prior to FIX itself. Thus, FIX originally only needed to worry about applying the same hp filter to the motion regressors, and thus in the fix script, the -h argument (to specify the filter) was made a subargument to the -m flag (that instructs fix to apply motion regression).
When the CIFTI format came along, the hp filtering of the CIFTI dtseries data was implemented in the context of fix_3_clean (called by the fix script to implement the actual cleaning of the data). But the -h argument in fix stayed a subargument to the -m flag.
Problem: While fix_3_clean has the capability to independently apply motion regression and an hp filter to the CIFTI dtseries, the fix script itself does not support that -- unless one requests motion regression, there is no mechanism in fix itself for filtering the dtseries.
Consequently, if running the v4.0.0 version of hcp_fix with something like the following hcp_fix <data> 2000 FALSE
the volume (NIFTI) data will be filtered by the requested hp=2000 filter (since that is done in hcp_fix script itself), but the CIFTI dtseries data will not get filtered at all (due to the setting of FALSE for the do_motion_regression argument). Insidiously in this situation, a cleaned CIFTI file will still be generated, and the file name will in fact be labeled hp2000_clean.dtseries.nii, even though an hp=2000 filter wasn't actually applied to it!!
Suggested solution: Split -m and -h into independent arguments in the fix script. (Ideally, in the FIX distribution itself).
The text was updated successfully, but these errors were encountered:
Restarted from #107.
Background: In the v4.0.0 HCPpipelines version of
ICAFIX/hcp_fix
, we added the capability to control whether the motion parameters were regressed out of the data as part of the fix-cleaning (via thedo_motion_regression
argument). [Prior to that (e.g., v3.27.0 and earlier), regression of the motion parameters was always applied].FIX was originally written for volume (NIFTI) data, with the assumption that any high-pass filtering was applied prior to FIX itself. Thus, FIX originally only needed to worry about applying the same hp filter to the motion regressors, and thus in the
fix
script, the-h
argument (to specify the filter) was made a subargument to the-m
flag (that instructsfix
to apply motion regression).When the CIFTI format came along, the hp filtering of the CIFTI dtseries data was implemented in the context of
fix_3_clean
(called by thefix
script to implement the actual cleaning of the data). But the-h
argument infix
stayed a subargument to the-m
flag.Problem: While
fix_3_clean
has the capability to independently apply motion regression and an hp filter to the CIFTI dtseries, thefix
script itself does not support that -- unless one requests motion regression, there is no mechanism infix
itself for filtering the dtseries.Consequently, if running the v4.0.0 version of
hcp_fix
with something like the followinghcp_fix <data> 2000 FALSE
the volume (NIFTI) data will be filtered by the requested hp=2000 filter (since that is done in
hcp_fix
script itself), but the CIFTI dtseries data will not get filtered at all (due to the setting ofFALSE
for thedo_motion_regression
argument). Insidiously in this situation, a cleaned CIFTI file will still be generated, and the file name will in fact be labeledhp2000_clean.dtseries.nii
, even though an hp=2000 filter wasn't actually applied to it!!Suggested solution: Split
-m
and-h
into independent arguments in thefix
script. (Ideally, in the FIX distribution itself).The text was updated successfully, but these errors were encountered: