Fix all_scalars
usage in threshold
#2670
Merged
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.
Overview
In the tests, it is shown that
all_scalars=True
does not use all the scalars but rather all the points in a cell for the threshold filter. This can also be seen when using cell data where there is only 1 value per cell thereforeall_scalars=True
does not have an effect even when having multiple cell data scalars.Details
There was a discussion of this in #1488 (comment), where @adeak wished to have
all_scalars
to mean 'all points' match rather than 'all scalars' match. In my testing, this is indeed what this argument does.I'm not sure if this would suggest a name change from
all_scalars
toall_points
.