[bug] wrong range values for boxplot of layout type category
See original GitHub issueWhen I inspect the range returned after the ‘plotly_selected’ callback in a boxplot with a categorical axis. I get the string values which is fine
But, if I want to get the pixel values or better yet the range that the selection translates to, I get strange results.
I tried d2p
and d2c
(c2p
and c2r
didnt produce any results)
and the results dont seem right. I believe there is a bug here unless I’m wrong
See the screen shot below
Here is the codepen: https://codepen.io/destrada/pen/EzKeMb
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
BUG: Bad axis limits when using DataFrame.boxplot ... - GitHub
I meant fixing this issue by reducing number of axes causes an API change (It makes impossible to return array which has the...
Read more >seaborn boxplot x-axis as numbers, not labels - Stack Overflow
What I would like is to generate the set of boxplots that are spaced out as if the x-axis values are treated as...
Read more >BOXPLOT in R [boxplot by GROUP, MULTIPLE box plot, ...]
A box and whisker plot in base R can be plotted with the boxplot function. You can plot this type of graph from...
Read more >Chapter 12 Single Boxplot | Basic R Guide for NSC Statistics
This is an R guide for statistics course at NSC.
Read more >Box Plot (Box and Whiskers): How to Read One & How to ...
Select the “Layout” tab again, then click “Error Bars” and then click “More Error Bar Options.” Click “Mins” and then type the difference...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Good question, @etpinard ? The only place I’m aware of is buried deep in the code:
https://github.com/plotly/plotly.js/blob/e26f8f4c9c75a0381e75dd4a56035f7fbf07fe73/src/plots/cartesian/set_convert.js#L40-L55
That describes what the letters
d/c/l/p/r
mean, so you can extrapolate to thex2y
functions. Perhaps we were trying to keep our options open, thinking if we don’t document these functions we can change them without considering it a breaking change? 🙈 But obviously people like yourself have found them and depend on them so at this point we really should document them publicly.and the range values (of the selection box) too?