-
Notifications
You must be signed in to change notification settings - Fork 307
fix: Default to grid-constant interpolation mode #3516
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
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #3516 +/- ##
=======================================
Coverage 73.64% 73.64%
=======================================
Files 60 60
Lines 4759 4759
Branches 616 616
=======================================
Hits 3505 3505
Misses 1111 1111
Partials 143 143 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
Thanks for the heads-up! @claraElk and I are happy to have a look, but we likely need a week or two to re-run the analysis and get results |
|
Sounds good. Will check in in two weeks. |
1e8d7b8 to
bc5c33f
Compare
|
@HippocampusGirl @claraElk Just checking in for results / an updated time estimate. |
|
For what it's worth, I reran my notebook from #3452:
I'm reasonably confident that this fixes the issue. |
25.2.0 (October 01, 2025) New feature release in the 25.2.x series. This release is an *fMRIPrep Long-Term Support (LTS)* release. The planned support window is 4 years, until October 2029. This release is an incremental improvement over 25.1.x, but includes some fixes and improvements that do not fit within our `bug-fix policy <https://www.nipreps.org/devs/releases/#bug-fix-releases>`__. Importantly, the change in interpolation in 25.1.0 introduced artifacts for some datasets. This release changes the default interpolation mode to ``grid-constant``, which resolves those problems while not reintroducing the issue the previous release sought to fix. This release also (finally) introduces per-session processing. The ``--session-label`` flag selects the sessions to process, and the ``--subject-anatomical-reference`` flag indicates whether and how to combine across sessions. Existing filters passed via ``--bids-filter-file`` may need to be updated or removed in favor of using these flags to achieve the desired behavior. We would like to thank the AMP-SCZ and ENIGMA consortia for testing out and providing feedback on this release. * FIX: Clean up output report language (#3529) * FIX: Default to grid-constant interpolation mode (#3516) * FIX: Adapt to transposed ndcoords in nitransforms (#3517) * FIX: Write out Freesurfer-derived outputs (#3512) * FIX: Add kwargs to _warnings.py (#3483) * ENH: Resample BOLD data to any surface template space using the Connectome Workbench (#3461) * ENH: Add boldref / sbref to source metadata (#3532) * ENH: Add dedicated session filtering, alternative anatomical template options (#3495) * ENH: Write out goodvoxels mask (#3513) * ENH: Add registration metadata to boldref-to-anat transforms (#3500) * ENH: Write out cortex mask GIFTIs (#3491) * ENH: Update transforms.py according to new transform chain of nitransforms (#3494) * RF/DOC: Improve and document command-line parser defaults (#3487) * DOC: Explain better SDC and B0FieldSource requirement (#2768) * DOC: Document `freesurfer` parameter in BOLD confound workflow init (#3504) * DOC: Add myself to contributor list (#3506) * DOC: Fix non-standard Input/Output docstring section management (#3505) * MNT: Split Dockerfile into base and pixi layers (#3521) * MNT: Replace conda with pixi and lock (#3503) * MNT: Update license metadata using SPDX expression (#3486) * MNT: no need to re-run `ruff check` after `ruff format` (#3480) * MNT: Update pre-commit ruff legacy alias (#3479)
|
Hi @effigies ! Sorry for the late reply. I extracted connectivity matrices using HALFpipe with fMRIPrep 20.2.7 and compared them with those obtained using HALFpipe with fMRIPrep 25.2.3, which includes the modifications mentioned above. The results below show the average correlations across subjects for different motion confound parameters extracted by the two fMRIPrep versions (dataset ds000228, ~155 participants). I also examined the average correlations between the resulting connectivity matrices, which were above 0.9 (depending on the confound removal strategy).
So, it looks like these changes did not reintroduce the problem, which is great news! |


This is a potential fix to #3475 and #3508. To test:
@claraElk @HippocampusGirl Could you verify that this does not re-introduce the problems we were trying to fix in #3453?