-
Notifications
You must be signed in to change notification settings - Fork 24
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
fix statistics bug and rename resolution methods to coarsest and finest #7355
Conversation
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.
Fixes the bug for me and LGTM. Thanks for looking into this so quickly!
I added one comment on naming. While this was not introduced in this PR, I think it should be changed to avoid future confusion.
Also, please add a changelog entry mentioning the bugfix :) |
thank you for the very fast review! |
4336555
to
c31737b
Compare
c31737b
to
5f2174f
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.
Nice! 😎
Could you adapt the PR description and changelog to briefly mention the faulty computation that this fixes?
Then this is good to go from my side
I missed to places where
lowest
andhighest
resolution were mixed in the segment statistics modal. I fixed that and renamed the methods.It also occured to us that the conversion from voxel to nm^3 was faulty, so this is also fixed for all segment stats.
Steps to test:
(Please delete unneeded items, merge only when none are left open)