-
Notifications
You must be signed in to change notification settings - Fork 29
FIX: Re-enable priors respecting sd_priors
argument
#488
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
7e34769
to
6b55a28
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes sense to me.
@mgxd Note that sd_prior
is removed from the syn_sdc_wf
. It never did anything, but you should stop passing it before we remove **kwargs
(if we do). It does still do something on the syn_preprocessing_wf
.
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #488 +/- ##
==========================================
+ Coverage 83.86% 83.98% +0.11%
==========================================
Files 30 30
Lines 2826 2828 +2
Branches 367 367
==========================================
+ Hits 2370 2375 +5
+ Misses 385 384 -1
+ Partials 71 69 -2 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
and the atlas pun? 😅 EDIT: I see your emoji reaction now :D |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Have not tested it, but feels cleaner removing the priors logic within init_syn_sdc_wf
.
004ed5e
to
1cc6a7e
Compare
0b43ccc
to
67ea545
Compare
2.13.0 (May 15, 2025) Feature release in the 2.13.x series. This release addresses some longstanding issues with the SyN-SDC workflow, improving the registration quality in adult humans by utilizing a spatial prior, as well as allowing Laplacians to be up- or down-weighted in the cost function, making it more usable across species. Additionally, this release allows for the use of ``EstimatedTotalReadoutTime`` or ``EstimatedEchoSpacing``, or a manually provided fallback ``TotalReadoutTime`` value, permitting the use of SDCFlows on datasets that do not have reliable timing information without introducing incorrect metadata into the datasets. * fix(syn): Re-enable priors respecting ``sd_priors`` argument (#488) * feat: Add workflow arguments for metadata estimates and fallback TRT (#479) * feat(syn): Update totalFieldVarianceInVoxel space based on voxel resolution (#487) * feat(syn): Allow changing laplacians weights in SyN registration metric (#484) * test(syn): Add a test to exercise SyN workflow creation and check parameters (#486)
2.13.0 (May 15, 2025) Feature release in the 2.13.x series. This release addresses some longstanding issues with the SyN-SDC workflow, improving the registration quality in adult humans by utilizing a spatial prior, as well as allowing Laplacians to be up- or down-weighted in the cost function, making it more usable across species. Additionally, this release allows for the use of ``EstimatedTotalReadoutTime`` or ``EstimatedEchoSpacing``, or a manually provided fallback ``TotalReadoutTime`` value, permitting the use of SDCFlows on datasets that do not have reliable timing information without introducing incorrect metadata into the datasets. * fix(syn): Re-enable priors respecting ``sd_priors`` argument (#488) * feat: Add workflow arguments for metadata estimates and fallback TRT (#479) * feat(syn): Update totalFieldVarianceInVoxel space based on voxel resolution (#487) * feat(syn): Allow changing laplacians weights in SyN registration metric (#484) * test(syn): Add a test to exercise SyN workflow creation and check parameters (#486)
Re-enables the inclusion of a prior mask, but moving the logic into the preprocessing (which is more readable).
If
sd_priors
is set toFalse
on the preprocessing, then thesd_prior
output is populated with another brain mask (which is equivalent to the behavior after #480).EDIT: Pun intended for @effigies. As you'll see, I've refrained from changing the argument name
atlas_threshold
, however, I fixed the node name because—to me—a displacements field is not an atlas :D