-
Notifications
You must be signed in to change notification settings - Fork 39
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
DOCKER: Include 3T18yoSchwartzReactN32 FreeSurfer atlas in image #357
DOCKER: Include 3T18yoSchwartzReactN32 FreeSurfer atlas in image #357
Conversation
The failures seem to be related to a weird issue we had in fmriprep about |
Oh I see -- thanks for clarifying |
Here's the commit, if you want to try replicating it here: nipreps/fmriprep@6fd7c54 |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## master #357 +/- ##
===========================================
+ Coverage 31.08% 54.07% +22.99%
===========================================
Files 20 22 +2
Lines 1454 1459 +5
Branches 206 206
===========================================
+ Hits 452 789 +337
+ Misses 987 614 -373
- Partials 15 56 +41
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Here's hoping "here" meant in this pull request 😅 Let me know if I should break off that last commit into another pull request or issue |
Perfect. Thanks! |
0.12.2 (August 16, 2023) Bug-fix release in the 0.12.x series. In rare cases where Freesurfer is unable to align to its default atlas in Talairach registration, it was unable to fall back to the Schwartz atlas because we were not including it in the Docker image. This release exists to provide an updated Docker image, and no upgrade is needed for users not encountering this issue. * DOCKER: Include 3T18yoSchwartzReactN32 FreeSurfer atlas in image (#357)
Closes #356