New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🐛 Nuisance regression strategies might not be forking properly when despiking is also forking #1370
Comments
Here is the regressor selection from the user who reported this issue:
|
At completion with the above
|
The specific user issue here is this forking in concert with forking from runDespike: [0,1] which should generate the 8 outputs above with and without despiking but only one set of 8 outputs is generated |
Bingo, so then this is really this: |
Just merged #1372 to develop; can try again. |
Success! In the output directory, a subdirectory with despiking and one without:
|
Describe the bug
User reports that not every nuisance regression strategy showed up in the output directory. Note the strategies fork via Nipype iterables (instead of the C-PAC pipeline fork points) and show up as multiple sub-directories under the nuisance-regressed functional outputs.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
There should be a sub-directory for each nuisance regression strategy under the nuisance-regressed functional outputs in the output directory.
functional_nuisance_residuals
is a good directory to check.Versions
The text was updated successfully, but these errors were encountered: