-
-
Notifications
You must be signed in to change notification settings - Fork 481
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
Warnings in plot_slope_field
#12277
Comments
comment:1
It seems like I remember that this was fixed in the new matplotlib 1.1.0 release (an spkg is up on trac somewhere). |
comment:2
Ah yes, #11915. Do you still see the problem after applying that spkg? |
comment:3
Replying to @jasongrout:
Yes, the same issue both in 4.7.2 and 4.8.alpha6 with #11915 applied. Are these warnings coming from matplotlib? Also, what would be an appropriate doctest for this bug? |
This comment has been minimized.
This comment has been minimized.
comment:5
Yes, strange I couldn't find it, I tried to search... My current workaround is that I have redefined |
comment:7
Am I supposed to do anything with author/reviewer fields? |
comment:8
One puts the reviewers only to those who realized, it, at least in the usage lately. If I misspelled your name, just fix it. |
Reviewer: Karl-Dieter Crisman, Andrey Novoseltsev |
Duplicate of #11208
If I do (in Sage 4.7.2 or 4.8.alpha6)
(or anything else that I have tried), then in front of the plot, which looks as expected, I get
My investigation so far shows: this function is a little wrapper for
plot_vector_field
which sets new defaults for three options. Ifheadlength
is set to 0, there are warnings.A possible workaround is to set it to something small: 0.001 seems to work on the screen. However, since with
headaxislength=0
andheadlength=0.2
I definitely see "a hair on the end", it does not seem to be satisfactory from a perfectionist point of view (and producing vector formats that may be scaled or printed with high resolution).Besides, current settings do produce the accurate plot, it just shows warnings that should not be there, and I have no idea how to fix it.
CC: @jasongrout
Component: graphics
Reviewer: Karl-Dieter Crisman, Andrey Novoseltsev
Issue created by migration from https://trac.sagemath.org/ticket/12277
The text was updated successfully, but these errors were encountered: