-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Investigate extreme data in all trace types #2061
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
Comments
There's #551 for |
Here's an example of https://codepen.io/cpsievert/pen/KQNRWN |
I have found that extremes in error bars on scatter plots cause the whole trace not to display (in both markers and lines mode). It seems to me to be a combination of a large value with a large error bar of a similar scale. An example can be seen here: |
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson |
#2060 fixes display of scatter lines containing extreme-out-of-view data (#403). We should investigate whether other trace types that exist in an infinite plane / space can handle data like that. I suspect the others will all or nearly all be substantially easier to clean up than scatter lines, likely just by limiting the data-to-pixel conversions (which we can't do with scatter lines because we need to preserve angles).
The text was updated successfully, but these errors were encountered: