-
Notifications
You must be signed in to change notification settings - Fork 318
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
horizontal shift when show error bars #1187
Comments
I would like to work on this issue. |
@sainmas Great. I've assigned you the issue. Please let me know if you need anything. |
The issue is hard to see due to including the Electric Utility group. It is hard to see but there are a few values graphed on the far, right edge of the graphic because they span only a few, very different dates than the Cos 23 meter. Here is what I see if I only graph that meter: and this what it looks like after you add error bars: Hopefully this is easier to see the shift of the original graph to the left and right when error bars are shown. Let me know if this is not clear or you need anything else. |
Hello @huss , |
@sainmas This code is involved when error bars are shown. I believe that it is calculating the amount above and below the reading value that the error line should, i.e., the height above and below the point that the error bar will display. To be specific, the first line is taking each point in the yMaxData array and taking the max value minus the value which is how far above the reading (average value or |
Describe the bug
When error bars are selected, the dates on the x-axis expand so the graphic is compress somewhat toward the center of the graphic. Normalizing by area does not do this.
To Reproduce
Any meter/group on a line graphic that supports error bars should show this.
Expected behavior
The shift is visually unappealing. It is unclear if the width of the horizontal error bar is causing Plotly to automatically do this. If so, the fix may be difficult. If so, we can reconsider what to do.
Additional context
None
The text was updated successfully, but these errors were encountered: