You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Scattergl markers are not rendered but you can hover over them #3751
The behavior here is similar to a previous bug I hit (issue 2999) but that bug's reproducing case no longer reproduces for me so I think this might be the same behavior from a different issue.
If I plot a large number of markers with scattergl, it works fine. If I then plot a subset, it does not. The transition point seems to be ~100k markers. That is, once I plot more than ~100k, plotting below ~100k shows the issue.
If I use 'scatter' instead of 'scattergl' it works fine, but our actual use case is much larger than 100k points so scatter doesn't work.
The browser generates hundreds of these warnings:
[.WebGL-00000080DCBEE1F0]GL ERROR :GL_INVALID_OPERATION : glDrawArrays: attempt to access out of range vertices in attribute 0
I'm using chrome Version 73.0.3683.103 (Official Build) (64-bit). This specific sample code does not show the issue in firefox, but I do hit the issue in firefox with our actual code and I'm not sure why.
Scanning through that...if I understood correctly, newPlot will not show this issue? I tried it out in that codepen I included and the issue goes away. Is that a valid stopgap?
This issue appears to be (going to be) fixed (in the next release v.1.49.0) after bumping regl-scatter@3.1.5 which uses point-cluster@3.1.5 in #3904. Codepen
Activity
archmoj commentedon Apr 9, 2019
rhamner commentedon Apr 9, 2019
@archmoj on the order of 1M. The actual one where I noticed this originally was ~300k points dropping down to ~15k points.
etpinard commentedon Apr 9, 2019
Right the cross-over should be at 1e5 pts. Something must be up with
point-cluster. Note that we never cluster x/y scattergl data below 1e5 pts.plotly.js/src/traces/scattergl/index.js
Lines 77 to 85 in 636a356
etpinard commentedon Apr 9, 2019
More info -> gl-vis/regl-scatter2d#19
rhamner commentedon Apr 9, 2019
Scanning through that...if I understood correctly, newPlot will not show this issue? I tried it out in that codepen I included and the issue goes away. Is that a valid stopgap?
wweitzel commentedon Apr 9, 2019
etpinard commentedon Apr 9, 2019
wweitzel commentedon Apr 9, 2019
etpinard commentedon Apr 9, 2019
wweitzel commentedon Apr 9, 2019
etpinard commentedon May 22, 2019
cc #2334
etpinard commentedon May 22, 2019
cc #3405
archmoj commentedon Jul 3, 2019
This issue appears to be (going to be) fixed (in the next release v.1.49.0) after bumping
regl-scatter@3.1.5which usespoint-cluster@3.1.5in #3904.Codepen
etpinard commentedon Jul 3, 2019
I doubt it. We shouldn't be calling
point-clusterfromregl-scatter. Our call topoint-clusteris here:plotly.js/src/traces/scattergl/calc.js
Line 67 in d75e956
archmoj commentedon Jul 3, 2019
But that line is not called in the codepen demonstrating the issue.
etpinard commentedon Jul 3, 2019
Right, because your https://codepen.io/MojtabaSamimi/pen/VJddPx has (only) 1e4 points. See https://codepen.io/etpinard/pen/EBRpqz which has 1e5 points - and appears buggy still.
archmoj commentedon Oct 30, 2019
@rhamner
A candidate fix illustrated in this demo.
archmoj commentedon Oct 31, 2019
Closed by #4323 .
rhamner commentedon Nov 1, 2019
Thanks