Skip to content
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

🐛 Freesurfer-based pipeline options cause a hang in a specific use case #2104

Open
1 of 15 tasks
sgiavasis opened this issue May 6, 2024 · 0 comments
Open
1 of 15 tasks
Labels

Comments

@sgiavasis
Copy link
Collaborator

Describe the bug

When running both recon-all within C-PAC via Nipype and the ABCD surface post-processing workflow, the pipeline tends to hang roughly around the timeseries warp-to-template part of the pipeline, although the warp-to-template portion seems unrelated to the stall (which really confounded the debugging efforts).

This most notably impacts the abcd-options preconfig and/or the options commonly associated with it.

This error will not happen if:

  • recon-all is run outside of C-PAC first, then the results ingressed into C-PAC and surface post-processing run afterwards.
  • If recon-all is run inside C-PAC but surface post-processing is not enabled.

If this error occurs, it can also be bypassed by:

  • Cancelling the stalled pipeline, and then re-starting it as-is via warm restart (if the Nipype working directory remains).

I suspect it is the combination of recon-all and its outputs' Nipype pointer connections to the surface post-processing nodes, in some way. Fortunately, we are moving away from recon-all being run within C-PAC in the near future.

To reproduce

  1. Simply run the abcd-options preconfig with recon-all enabled within C-PAC, instead of ingressing Freesurfer results from a previous Freesurfer run.

Preconfig

  • default
  • abcd-options
  • anat-only
  • blank
  • ccs-options
  • fmriprep-options
  • fx-options
  • monkey
  • monkey-ABCD
  • ndmg
  • nhp-macaque
  • preproc
  • rbc-options
  • rodent

Custom pipeline configuration

No response

Run command

No response

Expected behavior

The pipeline should simply complete.

Acceptance criteria

  • An abcd-options pipeline run with Freesurfer recon-all run as part of the pipeline, and then the pipeline completes successfully with no intervention.

Screenshots

No response

C-PAC version

v1.8.7

Container platform

No response

Docker and/or Singularity version(s)

No response

Additional context

No response

@sgiavasis sgiavasis added the bug label May 6, 2024
@sgiavasis sgiavasis changed the title 🐛 Freesurfer-based pipeline options causes a hang in a specific use case 🐛 Freesurfer-based pipeline options cause a hang in a specific use case May 6, 2024
shnizzedy added a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 7, 2024
Co-authored-by: Steve Giavasis <[email protected]>
shnizzedy pushed a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 7, 2024
shnizzedy pushed a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 7, 2024
shnizzedy added a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 8, 2024
Co-authored-by: Steve Giavasis <[email protected]>
shnizzedy pushed a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 8, 2024
shnizzedy added a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 8, 2024
Co-authored-by: Steve Giavasis <[email protected]>
shnizzedy pushed a commit to shnizzedy/fcp-indi.github.io that referenced this issue May 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: No status
Development

No branches or pull requests

1 participant