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
If you make this plot, the range gets corrupted and nothing shows:
vartrace1={x: [1,2,3,4,5],y: [30.326883631078317,31.130257299167397,1.7976931348623157e+303,1.6976931348623157e+304,// 1.79... does not fail, just disappears1.7976931348623157e+308// this one always disappears],mode: 'markers',type: 'scatter'};vardata=[trace1];Plotly.newPlot('myDiv',data);
make sure that no input numbers can corrupt the range calculations (or anything else about the plot)
perhaps it would be better to clip out-of-range numbers, rather than discarding them? I'm imagining cases where some program generates Number.MAX_VALUE as some sort of error condition or infinity value.
see if we can increase FP_SAFE closer to Number.MAX_VALUE without breaking plotting or interactions (pay attention to log axes too in this whole thing)
@alexcjohnson
Additional part: since plotly.js version 1.21.0, when mode:'lines' the entire line is not rendered when a value of ~1.79e+308 is present. See codepens:
Hi - this issue has been sitting for a while, so as part of our effort to tidy up our public repositories I'm going to close it. If it's still a concern, we'd be grateful if you could open a new issue (with a short reproducible example if appropriate) so that we can add it to our stack. Cheers - @gvwilson
If you make this plot, the range gets corrupted and nothing shows:
The cutoff comes from
FP_SAFE: Number.MAX_VALUE / 10000
so this issue has several parts:Number.MAX_VALUE
as some sort of error condition or infinity value.FP_SAFE
closer toNumber.MAX_VALUE
without breaking plotting or interactions (pay attention to log axes too in this whole thing)cc @cldougl
The text was updated successfully, but these errors were encountered: