-
Notifications
You must be signed in to change notification settings - Fork 437
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
[ENH] Asymmetric peak_directions #2751
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #2751 +/- ##
=======================================
Coverage 83.90% 83.90%
=======================================
Files 132 132
Lines 18468 18471 +3
Branches 3018 3017 -1
=======================================
+ Hits 15496 15499 +3
Misses 2227 2227
Partials 745 745
|
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.
Thanks @CHrlS98. Looks good to me. Just a few minor suggestions.
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.
Apart from the small comment below, all good to me.
Does someone else want to look at it before merging ???
Thanks @CHrlS98, merging! |
Hello,
Add a
is_symmetric
flag todipy.direction.peaks.peak_directions
to enable peak extraction on asymmetric ODFs.is_symmetric
isTrue
by default, so that the default behaviour does not change. When set toFalse
, the sphere directionsv
and-v
are considered distinct, such that it is possible to find a maxima alongv
but not along-v
.I simply removed the absolute value in
remove_similar_vertices
so that opposite sphere directions are not considered close to each other.Have a good one!