-
-
Notifications
You must be signed in to change notification settings - Fork 358
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
Errorbars/Ribbons #143
Comments
It would be great to have this for both axis (x and y) and supporting symmetric and asymmetric errors. |
So I don't forget... it would be good to use the existing |
Yes it's easy, but need to decide on the right API. Could pass a tuple, or have a separate |
I was looking at the code... At the moment only symmetric errors are supported, aren't they? Maybe tuples can be used for asymmetric errors (lower and upper limits), and add |
Yeah that's a good idea. Alias error to yerror and add xerror. Then I could remove the need for orientation, and keep access to asymmetric errors. I'll do this next.
|
Thanks for the API suggestions. I haven't implemented asymmetric errors yet but it should be an easy extension.
|
Awesome! You're welcome :D |
In case someone is looking here for single scatter points and asymmetric error bars (inputs to xerr and yerr need to be arrays): x = 10
y = 4
xe = (2,3)
ye= (2,1)
scatter((x,y), yerr=([ye[1]],ye[2]), xerr=([xe[1]],xe[2]) ) |
Hi there! After reading all this, I still do not understand. Is it possible to represent the xerror as a ribbon as well somehow? I would really like to do this! |
I am planning to add a new keyword argument:
:errorbars
. Some notes:err
,error
,errorbar
.ribbon
should be its own keyword arg, or if I can somehow useerrorbars
for both.fillrange
overlaps here. Should one pass the numerical values intofillrange
, thenerrorbars
could be the "style", for example:plot(y, fillrange=std(y), errorbars = :ribbon)
If anyone has good ideas and/or opinions on how they'd like the interface to look, please post here.
The text was updated successfully, but these errors were encountered: