-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Integrating discrete-heatmap2d #4924
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
Thaks @ordiology. Would you mind opening a PR from your |
Right now there are conflicts between @ordiology 's |
Thank you @archmoj , I have resolved the conflict (it was the package-lock.json). However, I'm not sure you want to just pull in my branch at this point. The version of the heatmap-gl that I have made is to link with our scientists' platform. I chose to make as minimal changes to the plotly source code as possible to get a discretised heatmap to work for our scientists. I considered renaming my version of the gl-heatmap2d code and creating a new npm package that could be sourced using a separate trace tree in plotly, but I wasn't sure this would be a productive way to implement the option. So, instead, I kept the linking to the gl-heatmap2d through plotly.js exactly the same and changed the manner in which the gl-heatmap2d code operated on the data and simply linked to a local version of my edited gl-heatmap2d rather than the default npm package. This wouldn't work for proper implementation purposes as a zsmooth switch is required to choose between each implementation. If there's a better way to communicate rather than in github messages, I can send you more information about how I approached the issue and further discuss what would be the simplest way to effect integration of my solution. I'm happy to help any way that I can. |
@ordiology thanks for the quick fixup. |
@ordiology has patched
gl-heatmap2d
to implementing discretization, which could be used to resolve #2924 by implementingzsmooth
onheatmapgl
(i.e. enabling it to be set tofalse
)... Let's help them prepare a PR to get this functionality exposed in Plotly.js.The text was updated successfully, but these errors were encountered: