-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
🐛 pipeline does not produce with/without ICAAROMA or two nuisance pipelines specified. #2149
Comments
If this is an issue with my yaml, apologies, but I'll confess, I'm pretty frustrated. |
Hi @nimzodisaster, thanks for reaching out! It looks like the run is forking at the ICA-AROMA fork point, but there’s a naming collision bug when getting the outputs from the working directory to the output directory - only one of the forks is making it to the output directory. If you still have the working directory, you can look for pairs of directories with the same name. For example, in our team's test runs, we have The attached pipeline config only has one nuisance regression strategy:
so there’s nothing to fork over there. When we tried adding a second:
we did see outputs generated for both nuisance forks - e.g.:
Please let me know if that helps and if there are any additional questions I can answer for you! |
Thanks for getting back to me. Unfortunately I do not have the working directories anymore as I was working on a workstation with limited disk space, and was auto removing the work directory. I have moved my processing to another workstation with lots of disk space and so will be keeping the working directory in the future. I noticed a few other things about outputs: OUTPUTS AND DERIVATIVES-----------------------post_processing: z-scoring: I think my default will be to make each config as direct as possible and to keep the working directory. I do hope this is only an issue with the outputting process, and not mixing them up in the working directory. |
Hi @nimzodisaster, It’s pretty likely that the naming collision is also source of the error with these outputs. To alleviate your concerns about mixing up the configs in the working directory, when C-PAC forks, each fork is unaware of the other forks until copying over to the output directory at the end, so there’s no chance of an internal mix-up. |
Describe the bug
My pipeline YAML: yml_orig.txt
The minimized YAML inthe log directory: yml_min.txt
Expected Outputs:
`anat:
func:
To reproduce
No response
Preconfig
Custom pipeline configuration
No response
Run command
No response
Expected behavior
produce the full set of derivatives.
Acceptance criteria
Produce full set of outputs
Screenshots
No response
C-PAC version
i.8.7.dev1
Container platform
No response
Docker and/or Singularity version(s)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: