On Sat, Jul 19, 2008 at 9:48 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Ok, thanks for the vote of confidence. My (newly created) ID is: ryanmay
Alright, you're now set up for commits. Keep working closely with
Eric and Jeff and the rest of us on the functionality you are adding.
Welcome aboard!
John Hunter wrote:
> On Sat, Jul 19, 2008 at 9:30 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>> Take this one instead. I missed some imports on the last one (oops).
>
> Hey Ryan -- the code you have been contributing is certainly high
> quality, and I am happy to give you commit rights if you send m
On Sat, Jul 19, 2008 at 9:30 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Take this one instead. I missed some imports on the last one (oops).
Hey Ryan -- the code you have been contributing is certainly high
quality, and I am happy to give you commit rights if you send me your
sf id. You should st
On Sat, Jul 19, 2008 at 8:02 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> We might want to consider, however, whether such extensive changes
> should be made immediately *before* a "bugfix" release. I think John is
> trying to get one out. I am already a little nervous about other recent
> and i
John Hunter wrote:
On Sat, Jul 19, 2008 at 8:58 PM, Ryan May <[EMAIL PROTECTED]> wrote:
Hi,
In integrating my barbs work, I'm having trouble that causes a circular
import. I used delete_masked_points from axes. The problem here is that
axes imports quiver (where I put barbs) which then has to
John Hunter wrote:
On Sat, Jul 19, 2008 at 8:58 PM, Ryan May <[EMAIL PROTECTED]> wrote:
Hi,
In integrating my barbs work, I'm having trouble that causes a circular
import. I used delete_masked_points from axes. The problem here is that
axes imports quiver (where I put barbs) which then has to
John Hunter wrote:
> On Sat, Jul 19, 2008 at 8:58 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>> Hi,
>>
>> In integrating my barbs work, I'm having trouble that causes a circular
>> import. I used delete_masked_points from axes. The problem here is that
>> axes imports quiver (where I put barbs) which
On Sat, Jul 19, 2008 at 8:58 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Hi,
>
> In integrating my barbs work, I'm having trouble that causes a circular
> import. I used delete_masked_points from axes. The problem here is that
> axes imports quiver (where I put barbs) which then has to (in some form
Hi,
In integrating my barbs work, I'm having trouble that causes a circular
import. I used delete_masked_points from axes. The problem here is that
axes imports quiver (where I put barbs) which then has to (in some form)
import axes to get delete_masked_points. Anyone have something I'm
miss
David,
I am reverting your changes to contour.py; that is, I am taking it back
to 5689. The problem is that running contour_demo.py, below, fails.
Some index accounting somewhere is getting fouled up. I don't have time
to investigate.
When you have it straightened out you can put the changes
Eric Firing wrote:
> Ryan May wrote:
>
>> Eric Firing wrote:
>>
>>> Ryan May wrote:
>>>
Hi,
In looking over trying to support masked arrays in wind barbs, I noticed
a problem. I had originally copied the model of quiver, wherein masked
arrays are supported f
Thanks for the help, Ryan and Eric.
On Sat, Jul 19, 2008 at 7:27 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> Ryan,
>
> Thanks. I will take care of this one way or another, but I want to see
> whether we really need both _uniform_offsets and _offsets.
>
> Eric
>
> Ryan May wrote:
>> John Hunter w
Eric Firing wrote:
>>> Quiver and windbarb could use the axes.delete_masked_points function
>>> right at the start, and this might be a good change to make, except
>>> that it is inconsistent with using the present set_UVC method to
>>> update arrows at constant locations.
>>
>> delete_masked_
Ryan May wrote:
> Eric Firing wrote:
>> Ryan May wrote:
>>> Hi,
>>>
>>> In looking over trying to support masked arrays in wind barbs, I noticed
>>> a problem. I had originally copied the model of quiver, wherein masked
>>> arrays are supported for U,V, and color, but not for X,Y. This stems
>>>
Ryan,
Thanks. I will take care of this one way or another, but I want to see
whether we really need both _uniform_offsets and _offsets.
Eric
Ryan May wrote:
> John Hunter wrote:
>> On Thu, Jul 17, 2008 at 10:28 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> I helped Eric out with this offline,
John Hunter wrote:
On Thu, Jul 17, 2008 at 10:28 PM, Ryan May <[EMAIL PROTECTED]> wrote:
I helped Eric out with this offline, and obviously set_array is for the
colors, but the only solution we could come up with was to directly
reset the PolyCollection._offsets member. This seems a little hac
Jeff Whitaker wrote:
> John: Well, I hit one snag. One file in natgrid has this comment in it.
>
> /*
> * The code in this file is based on code written and
> * copyrighted (C) by Dave Watson. Dr. Watson retains the
> * copyright to his original code. Augmentations and changes
> * to
Eric Firing wrote:
> Ryan May wrote:
>> Hi,
>>
>> In looking over trying to support masked arrays in wind barbs, I noticed
>> a problem. I had originally copied the model of quiver, wherein masked
>> arrays are supported for U,V, and color, but not for X,Y. This stems
>> from the seemingly nonsen
Ryan May wrote:
> John Hunter wrote:
>> Fernando and Gael proposed supporting a backend fallback option so the
>> user could express the intention: use my default backend unless I
>> happen to be in an incompatible user interface environment and then
>> just choose the most sensible thing. Users w
Ryan May wrote:
> Hi,
>
> In trying to add a symbol for an empty wind barb, I ran into problem.
> Traditionally, a smaller, non-filled circle is used for low wind speeds
> when doing a barb plot. I can draw the circle easily as a polygon,
> using CirclePolygon from patches, but unfortunately,
Ryan May wrote:
> Hi,
>
> In looking over trying to support masked arrays in wind barbs, I noticed
> a problem. I had originally copied the model of quiver, wherein masked
> arrays are supported for U,V, and color, but not for X,Y. This stems
> from the seemingly nonsensical nature of masking a
Hi,
As promised, here's a short patch to add get_offsets() and set_offsets()
to the Collections() base class. I tried to make it do the right thing
with regard to _offsets vs. _uniform_offsets, depending on whether
_uniform_offsets is None. I also had tried to make __init__ use
set_offsets,
John Hunter wrote:
> Fernando and Gael proposed supporting a backend fallback option so the
> user could express the intention: use my default backend unless I
> happen to be in an incompatible user interface environment and then
> just choose the most sensible thing. Users who do not want this ma
Hi,
In trying to add a symbol for an empty wind barb, I ran into problem.
Traditionally, a smaller, non-filled circle is used for low wind speeds
when doing a barb plot. I can draw the circle easily as a polygon,
using CirclePolygon from patches, but unfortunately, the fill color for
this pol
On Sat, Jul 19, 2008 at 1:05 AM, Gael Varoquaux
<[EMAIL PROTECTED]> wrote:
> It turns out it was only in the GTK backend, and quite trivial to
> correct. Attached is a new patch, including this correction.
Hey Gael, this is starting to look reasonable. I know implementing
these checks, such as d
Hi,
In looking over trying to support masked arrays in wind barbs, I noticed
a problem. I had originally copied the model of quiver, wherein masked
arrays are supported for U,V, and color, but not for X,Y. This stems
from the seemingly nonsensical nature of masking a location. However,
if noth
if (hasattr(x, 'get_compressed_copy')):
compressed_x = x.get_compressed_copy(mask)
John,
You added the snippet above to axes.delete_masked_points as part of one
of your massive "units" patches. It needs at least a comment in the
code--which I would be happy to add
Hi,
On Fri, 2008-07-18 at 15:47 -0400, Paul Kienzle wrote:
> The cases I'm thinking about (e.g., select fit range) have a specific
> number of points. Other cases (e.g., select shape outline) have an
> indefinite number of points. I can't think of case off hand where
> I would want e.g., six or
28 matches
Mail list logo
