Taylor Salo

What stage in preprocessing should `rapidtide` be run on? If we break it down into fMRIPrep's basic stages: 1. Motion correction 2. Slice timing correction 3. Susceptibility distortion correction 4....

If `rapidtide` can be run post-fMRIPrep (i.e., on standard space data with no denoising and no smoothing), then I think it would make sense to ensure that there is good...

To clarify, should rapidtide then be considered more a post-fMRIPrep workflow, or is it crucial to integrate it into fMRIPrep? I am concerned about feature creep, but on the other...

That's a good point. One issue, though, is the sheer number of parameters that can be set for rapidtide. Would you recommend hardcoding those parameters in the fMRIPrep calls? The...

That definitely makes integration easier!

@bbfrederick What rapidtide-generated files would you like to retain in the fMRIPrep outputs?

I think that produces six new files for each functional run. I don't know if that number of additional derivatives is an issue the fMRIPrep devs would want to avoid,...

Given that rapidtide can be run on fMRIPrep outputs, it seems like the best solution is to build a rapidtide postprocessing BIDS App, like [`fmripost-aroma`](https://github.com/nipreps/fmripost-aroma) will do for ICA-AROMA and...

I haven't looked at the source code for `fmripost-aroma`, but if it's fairly mature then you could adapt that and just swap out the AROMA-specific elements with rapidtide ones. I'm...

The minimal --> full test _seems_ to work, but it's running much more quickly than the full-on-its-own test, which is weird, and the output check is failing.