Re: [Matplotlib-users] Quiver 3D ValueError

You need 1.4.0 as the 3D quiver code is not in 1.3.1. On Fri, Oct 10, 2014 at 5:02 PM, Thomas Proctor wrote: > I'm trying to generate a 3D quiver plot. When I try running the sample > available at > http://matplotlib.org/mpl_examples/mplot3d/quiver3d_demo.py > I get a "ValueError: too many value

Re: [Matplotlib-users] Quiver 3D ValueError

chances are, something is wonky with the inputs that is causing the broadcasting not to work correctly. Could you post a simple, self-contained code example? Ben Root On Fri, Oct 10, 2014 at 5:02 PM, Thomas Proctor wrote: > I'm trying to generate a 3D quiver plot. When I try running the sample

Re: [Matplotlib-users] Quiver 3D ValueError

I'm trying to generate a 3D quiver plot. When I try running the sample available at http://matplotlib.org/mpl_examples/mplot3d/quiver3d_demo.py I get a "ValueError: too many values to unpack" error. I'm using matplotlib 1.3.1 (the vers

Re: [Matplotlib-users] twinx cla problem

Yes, I did. Same result as with cla(). Thanks, Charlie -Original Message- From: Sterling Smith [mailto:smit...@fusion.gat.com] Sent: Friday, October 10, 2014 11:30 AM To: Duke, Charles Cc: matplotlib-users@lists.sourceforge.net Subject: Re: [Matplotlib-users] twinx cla problem This is no

Re: [Matplotlib-users] twinx cla problem

On 2014/10/10, 4:45 AM, Duke, Charles wrote: > With matplotlib 1.4.0 the cla() method for the twinx axes also clears > the primary axes. With matplotlib 1.3.1 the method only clears the > twinx axes as expected. I have a much longer program where the twinx > axes must be cleared while retaining t

Re: [Matplotlib-users] FW: traceback when import matplotlib.pyplot twice

Something is going really sideways on your system as `Gcf` is the class that the static method is a member of. If you have the method to call it, then you have the class defined. My guess is there is some race condition is the cleanup-at-exit code where the system is cleaning up the class object

Re: [Matplotlib-users] FW: traceback when import matplotlib.pyplot twice

Thanks for pointer on the None…. Just got the future warning in my code when comparing a numpy array param in a class of mine that defaults to None. That should be solved differently… but I have plenty of other params that default to None and I will change them accordingly…. Back to the traceb

Re: [Matplotlib-users] twinx cla problem

This is not tested, but did you try ax2.clear() instead? -Sterling On Oct 10, 2014, at 7:45AM, Duke, Charles wrote: > With matplotlib 1.4.0 the cla() method for the twinx axes also clears the > primary axes. With matplotlib 1.3.1 the method only clears the twinx axes as > expected. I have a

[Matplotlib-users] twinx cla problem

With matplotlib 1.4.0 the cla() method for the twinx axes also clears the primary axes. With matplotlib 1.3.1 the method only clears the twinx axes as expected. I have a much longer program where the twinx axes must be cleared while retaining the primary axis plot. I would prefer not to replo