Skip to content
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

quiver is not plotting only 1 vector #3817

Closed
moghimis opened this issue Nov 19, 2014 · 9 comments
Closed

quiver is not plotting only 1 vector #3817

moghimis opened this issue Nov 19, 2014 · 9 comments

Comments

@moghimis
Copy link

For some reason my old script which was plotting correctly is not reproducing the same figure.
Here is the line of the code:

axq.quiver([xtexth],[ytexth],[uwnd,],[vwnd,],units=units,scale=scalew,width=0.03,color='b')

However if I add 1 element to vector it will plot as before:

axq.quiver([0,xtexth],[0,ytexth],[0,uwnd,],[0,vwnd,],units=units,scale=scalew,width=0.03,color='b')

It seems the first element is ommited.

Saeed.

In [178]: import matplotlib as mpl
In [179]: print mpl.__version__
1.4.2

[TAC edited to add formatting markup]

@tacaswell
Copy link
Member

I can not reproduce this on master, but I had to guess at the values of all of the inputs.

Can you provide a complete minimal example of code that does not work (including values, it should be copy-paste runnable).

@tacaswell tacaswell added status: needs confirmation status: needs clarification Issues that need more information to resolve. labels Nov 20, 2014
@tacaswell tacaswell added this to the unassigned milestone Nov 20, 2014
@moghimis
Copy link
Author

Here is my example:

worked

f=figure(1)
axq=f.add_subplot(111)
axq.quiver([5,],[5,],[5,],[5,],pivot='left',color='k')
axq.set_xlim(0,10)
axq.set_ylim(0,10)
plt.show()

works now

f=figure(2)
axq=f.add_subplot(111)
axq.quiver([0,5,],[0,5,],[0,5,],[0,5,],pivot='left',color='k')
axq.set_xlim(0,10)
axq.set_ylim(0,10)
plt.show()

In older version both are working but the scale are differrent.

On Wed, Nov 19, 2014 at 7:00 PM, Thomas A Caswell notifications@github.com
wrote:

I can not reproduce this on master, but I had to guess at the values of
all of the inputs.

Can you provide a complete minimal example of code that does not work
(including values, it should be copy-paste runnable).


Reply to this email directly or view it on GitHub
#3817 (comment)
.


Saeed Moghimi
College of Earth, Ocean, and Atmospheric Sciences,
Oregon State University,
Corvallis, OR 97331-5503
Office: Burt 104
Email: moghimi@coas.oregonstate.edu
Home page: http://ceoas.oregonstate.edu/profile/moghimi/ (or My personal
homepage https://sites.google.com/site/moghimis/)
Telephone: +1 (541) 737-3402.


@tacaswell tacaswell modified the milestones: v1.4.3, unassigned Nov 21, 2014
@tacaswell tacaswell added status: confirmed bug and removed status: needs confirmation status: needs clarification Issues that need more information to resolve. labels Nov 21, 2014
@tacaswell
Copy link
Member

@efiring Thoughts on this?

@efiring
Copy link
Member

efiring commented Jan 13, 2015

It works on 1.4.0, but not on 1.4.2. Strange.

@efiring
Copy link
Member

efiring commented Jan 17, 2015

Bisecting shows 350413c as the first bad commit. @mdboom would you look at this, please? It's deep in agg.

@efiring
Copy link
Member

efiring commented Jan 23, 2015

I don't understand why, but this seems to be fixed by #4025. It must be the elimination of the conditional in the draw method. How that would be related to my bisecting result, I don't know.

efiring added a commit to efiring/matplotlib that referenced this issue Jan 24, 2015
…tplotlib#3709, matplotlib#3817

The reason why the unconditional recalculation now seems to be
needed, but was not in v1.4.0, is unknown.
tacaswell added a commit that referenced this issue Jan 25, 2015
BUG :  fixes for quiver
 - always recalculate verts
 - improve docstring;

closes #3709 closes #3817
@rsignell-usgs
Copy link

@tacaswell, this bug was killing me all morning -- my student's notebook was working for him, but not for me. We (with help from @ocefpaf) eventually tracked this down to this bug, due to my newer matplotlib (1.4.2) vs his older one (1.4.0). Any chance of releasing 1.4.3 with this bugfix?

@tacaswell
Copy link
Member

@rsignell-usgs Target date for 1.4.3 is Feb 1, but we still have a few out-standing blockers (mostly #3095 ) so with in the next few weeks.

@rsignell-usgs
Copy link

@tacaswell. Okay, thanks for this information and thank you also for all the great work you do for the community!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants