Skip to content

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

Closed
7 tasks
alexcjohnson opened this issue Oct 4, 2017 · 4 comments
Closed
7 tasks

Investigate extreme data in all trace types #2061

alexcjohnson opened this issue Oct 4, 2017 · 4 comments

Comments

@alexcjohnson
Copy link
Collaborator

#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).

@etpinard
Copy link
Contributor

etpinard commented Oct 4, 2017

There's #551 for scatter3d.

@cpsievert
Copy link

cpsievert commented Feb 7, 2018

Here's an example of box's jitter not working as intended when just one outlier exists (perhaps we could just ignore jitter in that case?)

https://codepen.io/cpsievert/pen/KQNRWN
From plotly/plotly.R#1189

@madeleinemf
Copy link

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:
https://codepen.io/madeleinens/pen/JLjPWE

@gvwilson
Copy link
Contributor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants