Skip to content

This bubble charts isn't working #1397

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
suribabu39 opened this issue Feb 20, 2017 · 5 comments
Closed

This bubble charts isn't working #1397

suribabu39 opened this issue Feb 20, 2017 · 5 comments
Labels
bug something broken

Comments

@suribabu39
Copy link

Hi,
For certain range of values(x, y, size in trace) bubble chart is not plotting, Maybe it is plotting but clearly not visible. For most of range it is working but for certain range of values it is not working. Is there any constraint on the value ranges or should I maintain a ratio?
One such example where it doesn't plot any chart is here (http://codepen.io/suribabu_95/pen/egwPrG?editors=0010)

Thank You

@etpinard etpinard changed the title Bubble charts are not working This bubble charts isn't working Feb 20, 2017
@etpinard
Copy link
Contributor

etpinard commented Feb 20, 2017

Strange.

Back in v1.7.0, your bubble chart would've looked like http://codepen.io/etpinard/pen/mRZozR

At first glance, it looks like very large bubbles are throwing off the marker sizing routine.

Is there any constraint on the value ranges or should I maintain a ratio?

Yes. Try using marker.sizeref as in http://codepen.io/etpinard/pen/VPJVyv

@etpinard etpinard added the bug something broken label Feb 20, 2017
@etpinard
Copy link
Contributor

This bug is a side-effect of (the very controversial) #353

@etpinard
Copy link
Contributor

More closely, the problem lies inside the autorange routine: where very large bubbles make

dp = ax._length - minpt.pad - maxpt.pad;

always be negative and hence excluded from the the autorange computation. Perhaps dp should be constrained?

@etpinard
Copy link
Contributor

etpinard commented Feb 20, 2017

Referencing #1352 which also highlights a getAutoRange issue.

@etpinard
Copy link
Contributor

Fixed as best we can in 1f4898c

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

No branches or pull requests

2 participants