Fix autoscale in Feature Color Mode Preferences #299
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* The test shows that the DefaultFeatureRangeCalculator does not return the expected min and max values for Features that contain NaN values
…tures contain NaN values
tinevez
approved these changes
Mar 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR contains a change so that the function
autoscaleinPreferences > Feature Color Modesalso works for Features that containNaNvalues.The current situation is that pressing
autoscalefor such features results in non usuable (and even non manually changeable) values, cf.:This PR lets the
DefaultFeatureRangeCalculatorignoreNaNvalues so that the expected min and max values are returned.The PR contains a unit test to demonstrate the behaviour of
DefaultFeatureRangeCalculator