Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This contains more fixes for LabelGeometryMeasures.
The median was only added relatively recently, when switching out the deprecated ITK filter. But it is approximated and derived from a histogram, the default is to use 255 bins over the whole range of the image. This can get really imprecise when there are outliers or a large dynamic range, eg, t-statistic maps - this is how the problem was brought to my attention.
I experimented with using a mask of all the labels to define the histogram range for intensity voxels inside the mask. I also increased the number of histogram bins. It works better, but still, I'm not sure it's a good idea to include imprecise information, and I expect most users who really want median would rather compute it exactly with numpy or similar.
Mean, Min, Max, and Sum (called "IntegratedIntensity" for backwards compatibility) are computed exactly and remain in this version.