Override Curve's count aggregator default to self_intersect=False
#6030
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.
fixes #5975
This PR disables the self-intersect option for a Datashader count aggregator, which controls whether pixel-crossings of the same line contribute toward a pixel's count.
Why? In some cases, showing self-intersection counts (showing where a line crosses through the same pixel multiple times) is preferred, as it provides information about how the signal varies even when the variations involved are smaller than the pixels on the screen. However, in order to be more consistent with how a non-Datashader curve would appear, it was decided that a more reasonable default behavior would be to disable self-intersect for individual (non-categorical) curves.
As this PR is currently composed, not providing any
aggregator
argument for hvPlot will adopt the new default. One issue is that setting a count aggregator without any kwargs will revert to adopting Datashader's default (self_intersect=True
), is this acceptable?Code