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

--use-syn-sdc no longer respected when --ignore fieldmaps is passed #1941

Closed
effigies opened this issue Jan 21, 2020 · 4 comments · Fixed by #1942 or #2101
Closed

--use-syn-sdc no longer respected when --ignore fieldmaps is passed #1941

effigies opened this issue Jan 21, 2020 · 4 comments · Fixed by #1942 or #2101
Labels

Comments

@effigies
Copy link
Member

Prior to 1.5.3, --use-syn-sdc --ignore fieldmaps would ignore fieldmaps, and use SyN-SDC.

As of 9e23203 (#1886), access to any SDC algorithm is restricted by --ignore fieldmaps.

This leaves users who would prefer to use SyN over fieldmaps stranded.

Ref: https://neurostars.org/t/syn-sdc-not-working-with-more-recent-fmriprep-version/5824

@effigies
Copy link
Member Author

This appears to still occur in 20.1.0rc1.

@effigies effigies reopened this Apr 24, 2020
@effigies
Copy link
Member Author

From the reports:

Functional

Reports for: task repeatchange, run 1.

Summary

  • Repetition time (TR): 3.38s
  • Phase-encoding (PE) direction: Anterior-Posterior
  • Slice timing correction: Not applied
  • Susceptibility distortion correction: None

...

About

fMRIPrep version: 20.1.0rc1
fMRIPrep command: /usr/local/miniconda/bin/fmriprep sourcedata/ . participant --participant-label 02 --output-spaces anat fsnative --cifti-output --ignore fieldmaps --use-syn-sdc -vv --fs-license-file /projectnb/bohland/repeat_change/worktrees/02/tokens/freesurfer_license.txt --nthreads 16 --omp-nthreads 8 --mem-mb 48000
Date preprocessed: 2020-04-09 21:45:06 -0400

@effigies
Copy link
Member Author

@mgxd
Copy link
Collaborator

mgxd commented Apr 24, 2020

@effigies that seems like the case - I'll double check the config options to see if there are any other deviations from the parser

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
2 participants