Repository navigation
[Bug]: Errorbars separated from markers with negative errors #21101
Description
Activity
So I see why it is doing this ('we draw the error bar from (val - lower_error, val + upper_error)), but I agree, if we document that negative errors should not work, we should do the validation and raise ValueError
The tasks here are:
- add validator to at at least the errorbar method
- investigate how much work it would be to add validation to updating the errorbars after-the-fact (I think in that case the user has to do the offsets them selves so there may be nothing we can do)
- add a test
I will try to work on this near future.
- added a commit that references this issue on Oct 5, 2021
- added a commit that references this issue on Oct 20, 2021
Bug summary
If unique upper and lower errors are specified, and one of them is negative, then the errorbar will appear separate from the marker. It looks like this was mentioned ages ago in #2717 but I could not find a follow up to that issue.
Code for reproduction
Actual outcome
1
2
3
Expected outcome
I understand the documentation states that the error inputs should be positive values, but I would expect some error like ValueError when there is a negative value provided, rather than it trying to make the plot. I would prefer an error being thrown and the plot not being made.
Operating system
CentOS Linux release 7.9.2009 (Core)
Matplotlib Version
3.4.3
Matplotlib Backend
module://matplotlib_inline.backend_inline
Python version
3.9.6
Jupyter version
3.1.9
Other libraries
No response
Installation
conda
Conda channel
No response