Open luigibrancati opened 1 year ago
One possible solution to this is to add a fictitious data point as a first row, like the 0 I added here
We could probably do something better here in the log case, but fundamentally the issue is image / heatmap data has bricks with some implied extent if you specify one coordinate value per brick, and this is particularly awkward when those coordinate values are not distributed linearly. If you give us a coordinate array (y
in this case) that's one longer than the corresponding dimension of the img
array (or z
if you use heatmap directly) we'll treat those as the brick edges rather than centers, and then there's no ambiguity - although then there's ambiguity in where we should draw the text and what values we should display on hover!
Plotly version: 5.15.0
I'm passing some values to the yaxis of
px.imshow
. If I just plot it as-is it's fineBut if I change the yaxis type to
log
usingfig.update_yaxis
, the first row of data disappearsPlaying around with the yaxis values doesn't seem to affect this behaviour
Note: It seems to depend only on the closeness of the first and second yaxis values
VS