Christopher Barker wrote:
> Christopher Barker wrote:
>>> If you are not running from svn, a workaround may be to specify the
>>> angles as an ndarray or masked array with the shape set to (N,1) where N
>>> is the number of arrows.
>> Yes, that seems to work. Thanks!
>
> However, I'm a bit confu
Christopher Barker wrote:
>> If you are not running from svn, a workaround may be to specify the
>> angles as an ndarray or masked array with the shape set to (N,1) where N
>> is the number of arrows.
>
> Yes, that seems to work. Thanks!
However, I'm a bit confused now -- if I specify the angle
Eric Firing wrote:
> No, you hit a bug. Thanks for the report and test script. It is fixed
> in r7103.
>
> If you are not running from svn, a workaround may be to specify the
> angles as an ndarray or masked array with the shape set to (N,1) where N
> is the number of arrows.
Yes, that seems
Christopher Barker wrote:
> Christopher Barker wrote:
>> Hi all,
>>
>> I've been messing with quiver a bit, and have some confusions:
>
> one more issue with quiver -- autoscaling fails if there is a NaN in the
> data:
>
I just committed a change to ensure that nans and infs are treated as
mas
Christopher Barker wrote:
> Hi all,
>
> I've been messing with quiver a bit, and have some confusions:
No, you hit a bug. Thanks for the report and test script. It is fixed
in r7103.
If you are not running from svn, a workaround may be to specify the
angles as an ndarray or masked array with
Christopher Barker wrote:
> Hi all,
>
> I've been messing with quiver a bit, and have some confusions:
one more issue with quiver -- autoscaling fails if there is a NaN in the
data:
x = (1,2)
y = (1,2)
u = (2,2)
v = (-2,2)
fig = plt.figure(1)
fig.clear()
ax = fig.add_subplot(2,2,3)
# fail
Hi all,
I've been messing with quiver a bit, and have some confusions:
according to the docs:
"""
units: [‘width’ | ‘height’ | ‘dots’ | ‘inches’ | ‘x’ | ‘y’ ]
arrow units; the arrow dimensions except for length are in
multiples of this unit.
"""
and yes, when I change units from 'do
