-
-
Notifications
You must be signed in to change notification settings - Fork 7.9k
pyplot.errorbar attempts to plot 0 on a log axis in SVGs #6563
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
Comments
Do pngs render correctly? |
Yes. SVGs even render correctly when viewed in chrome or IPython notebook. On Thu, Jun 9, 2016, 9:49 PM Thomas A Caswell notifications@github.com
|
Can you try the 2.0.0b1 or 1.5.1rc2 release ( |
I used your command to install maptlotlib 2.0.0b1. This appeared to address this issue. I could no longer find the extreme value in the SVG xml and the svg functioned correctly when loaded into illustrator suggesting that the problem was fixed. Thanks for the support! Feel free to close the issue. |
Closed by #5911 . |
@BrianLandry Thank you for reporting this bug and following up to check if it was already fixed. We really do greatly appreciate both of those things! |
pyplot.errorbar will attempt to plot a 0 point errorbar on a log axis when saving as a SVG, despite 0 not existing on a log axis. Although the SVG will be visualized correctly by chrome ect., it will crash inkscape, and be unable to be moved in illustrator. This can be accomplished with the following code
This will generate a SVG with the following line:
Where I think the " -116021015.957275" value is an attempt to plot at the 0 point on the log axis, which does not exist. Removing the zero point alleviates the reported problems
This was done in Windows 10, Python 2.7.11, Matplotlib 1.5.1, installed via Anaconda 4.0.0
Edit: This also appears to be an issue with pyplot.plot. However, for some pyplot.plot plots I do not get errors when working with some of them in illustrator, but regardless, they all still contain the highly negative location value in their XML.
The text was updated successfully, but these errors were encountered: