Description
What version of fMRIPrep are you using?
Tested with all releases from 20.1.1 to 20.2.0-LTS
What kind of installation are you using? Containers (Singularity, Docker), or "bare-metal"?
Singularity containers
What is the exact command-line you used?
singularity run --cleanenv -B /path:/path fmriprep-singularity-<version> bids_dataset output_<version> participant --fs-no-reconall --fs-license-file license.txt --participant_label 1003 --output-spaces MNI152NLin2009cAsym:res-native --anat-only -w tmp/work<version> --nprocs 4 > tmp/<version> 2> tmp/<version>
Where <version>
ranged from 20.1.1 to 20.2.0 LTS including the release candidates
Have you checked that your inputs are BIDS valid?
Yes, with bids-validator
v1.5.3
Did fMRIPrep generate the visual report for this particular subject? If yes, could you share it?
Yes, I'm sending the reports to nipreps@gmail.com and put at the bottom of this issue screenshots of the issue.
Can you find some traces of the error reported in the visual report (at the bottom) or in crashfiles?
No errors are reported by fmriprep in the reports or in crashfiles
Are you reusing previously computed results (e.g., FreeSurfer, Anatomical derivatives, work directory of previous run)?
Everything started from a clean work
and output
folder
fMRIPrep log
I saved the logs, they were sent to nipreps@gmail.com
Encountered bug
The normalization of the anatomical files used to work with 20.1.1, but were horribly distorted with 20.2.0-LTS. I tried all versions available as singularity containers in between to find out what happened and summarize what I found below:
Version | Anat normalization | Details shared by email |
---|---|---|
20.1.1 | ✅ | no |
20.1.2 | ✅ | no |
20.1.3 | ✅ | yes |
20.2.0rc0 | ❓ | no |
20.2.0rc1 | ❓ | yes |
20.2.0rc2 | ❌ | no |
20.2.0-LTS | ❌ | yes |
Below, a screenshot of the expected result (taken from 20.1.3), a screenshot from the intermediate result (taken from 20.2.0rc1)
and one from the 20.2.0-LTS version:
20.1.3, seems OK
20.2.rc0, forgot some prefrontal areas?
20.2.0-LTS not OK
Summary of the report (identical for all reports except 20.1.2 that doesn't print the "Anatomical Conformation"):
Summary
- Subject ID: 1003
- Structural images: 1 T1-weighted
- Functional series: [...]
- Standard output spaces: MNI152NLin2009cAsym
- Non-standard output spaces:
- FreeSurfer reconstruction: Not run
Anatomical
Anatomical Conformation
- Input T1w images: 1
- Output orientation: RAS
- Output dimensions: 240x320x320
- Output voxel size: 0.65mm x 0.65mm x 0.65mm
- Discarded images: 0
I'm happy to help in debugging this, however I can only run singularity versions so I could not bissect more to find the relevant commit(s).
EDIT for additional information.
I'm showing the output when starting from defaced images (with pydeface
), but the same bug occurs without defacing. It also occurs when I remove the --fs-no-reconall
flag, and it is similarly distorted for four out of my five subjects so far, with possible issues that I didn't investigate in the fifth.