Summary of what happened:
Hi! I have been testing out using rapidtide for delay mapping in my data, and was trying out different search ranges. (I’m working with older adult scans so am deciding whether to use the default -10 to 30s or something else.) I noticed occasionally a lag time that appeared outside of the specified range. You can see below that I set the search range to -15 to 15, but in the tidepool screenshot at the selected voxel the lag is 16.66 (I’ve observed similar in other voxels/subjects). When I press “Full Range” for this subject, the range is auto set to approx. -20 to 21.
Is this expected behavior and I’m misunderstanding how the search range works? Or should there be no voxels outside for which the lag should be outside of the set range?
Thank you!
Command used (and if a helper script was used, a link to the helper script or the command generated):
singularity exec -e rapidtide.sif rapidtide \
fmriprep_dir/*_desc-preproc_bold.nii.gz \
output_dir/prefix \
--motionfile fmriprep_dir/*_desc-confounds_timeseries.tsv \
--brainmask fmriprep_dir/*_desc-brain_mask.nii.gz \
--globalmean --globalmeaninclude fmriprep_dir/*_desc-brain_GM_mask.nii.gz \
--offsetinclude fmriprep_dir/*_desc-brain_GM_mask.nii.gz \
--nprocs -1 --reservecpu \
--delaymapping \
--searchrange -15 15
Version:
rapidtide v3.1.10
Environment (Docker, Singularity / Apptainer, custom installation):
Singularity
Data formatted according to a validatable standard? Please provide the output of the validator:
PASTE VALIDATOR OUTPUT HERE
Relevant log outputs (up to 20 lines):
"lag_extrema":[
-15.0,
15.0
],
"lag_extrema_nondefault":true,
"laghist_centerofmass.txt":-0.17854423129153407,
"laghist_peak.txt":0.2716595335356278,
"lagmaskside":"both",
"lagmax":15.0,
"lagmax_nondefault":true,
"lagmaxthresh":3.0,
"lagmin":-15.0,
