Skip to content

Stacked Histogram not rendering correctly when sample sizes are different #1864

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.

Sign up for GitHub

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

Jump to bottom
Closed
cldougl opened this issue Jul 7, 2017 · 2 comments
Closed

Stacked Histogram not rendering correctly when sample sizes are different #1864

cldougl opened this issue Jul 7, 2017 · 2 comments
Labels
bug something broken

Comments

@cldougl
Copy link
Member

cldougl commented Jul 7, 2017 •
edited
Loading

It seems that stacked hists aren't stacking correctly when the traces have different sample sizes.

screen shot 2017-07-07 at 3 09 29 pm

Example: https://codepen.io/plotly/pen/owPQqg
Working Example: https://codepen.io/plotly/pen/BzqwbE

(noticed this recently in the python doc example and I think it worked at some point despite different sample sizes).
@etpinard etpinard added the bug something broken label Jul 7, 2017
@etpinard etpinard added the regression this used to work label Jul 24, 2017
@alexcjohnson
Copy link
Collaborator

haha @cldougl when I open your working example I sometimes get it "working"
screen shot 2017-08-07 at 11 33 16 am

And sometimes it automatically offsets one of the traces (presumably via the edge-avoidance algo though I'm a bit surprised that this would be so unstable):
screen shot 2017-08-07 at 11 33 01 am

And in fact sometimes your non-working example does this and "sort of works":
screen shot 2017-08-07 at 11 36 12 am

I say "sort of works" because this is still not the outcome we want. Yes, the orange trace gets stacked on the blue, but the bin width used for the orange trace is not what's displayed as the bar widths.

I think in the end this may be the same as #50 - currently our oldest open bug! 🏆 So I'm pretty sure this is not a regression, just a hazard of using random in a bug report!

@etpinard etpinard removed the regression this used to work label Aug 7, 2017
@alexcjohnson alexcjohnson mentioned this issue Aug 10, 2017
Merged
@alexcjohnson
Copy link
Collaborator

closed by #1944

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

No branches or pull requests
3 participants
@alexcjohnson @cldougl @etpinard