Skip to content

Bug - heatmap renders with wrong colors when using zsmooth #2275

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
LarryMartell opened this issue Jan 21, 2018 · 3 comments
Closed

Bug - heatmap renders with wrong colors when using zsmooth #2275

LarryMartell opened this issue Jan 21, 2018 · 3 comments

Comments

@LarryMartell
Copy link

Here are 2 codepens showing the issue. They both have the same data, one with zsmooth, one without - the one without zsmooth shows the correct colors, the with shows the wrong colors.

zsmooth, wrong colors: https://codepen.io/LarryMartell/pen/aEPxbZ?editors=0010
no zsmooth correct colors: https://codepen.io/LarryMartell/pen/GyzrGE?editors=0010

You have to zoom in to see the data points. Attached are 2 screen shots showing the correct and incorrect colors.

I contend that no matter what, zsmooth or not, shouldn't it be that the color for a given value shows the same and
screen shot 2018-01-20 at 10 19 56 am
screen shot 2018-01-20 at 10 20 04 am

proper color?

@alexcjohnson
Copy link
Collaborator

Thanks @LarryMartell - I believe this is another manifestation of #2233 - see specifically #2233 (comment) - we're confusing the brick center and the data point, when bricks are nonuniform sizes.

@LarryMartell
Copy link
Author

I submitted this bug report because I was asked to by Chelsea Douglas from your support group. I reported this issue to support and she said “As far as I can tell this is the expected outcome, but you're always welcome to open an issue in the plotly.js repo: https://github.com/plotly/plotly.js/issues with a reproducible example“ so that is what I did.

@alexcjohnson
Copy link
Collaborator

Oh sure - please don't take my closing the issue as an indication you were wrong to open it, just that it has the same cause as another issue so I combined them. This is a tricky one, so I'm glad @cldougl steered you here.

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

2 participants