John Hunter wrote:
> On Fri, Jul 25, 2008 at 6:42 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> This is the kind of thing I would want to look at and test *very* carefully,
>> or know that someone like John or Mike has done so--which perhaps one of
>> them can do quickly. I have looked at this
John Hunter wrote:
> On Fri, Jul 25, 2008 at 6:42 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
>
>> This is the kind of thing I would want to look at and test *very* carefully,
>> or know that someone like John or Mike has done so--which perhaps one of
>> them can do quickly. I have looked at this
On Fri, Jul 25, 2008 at 7:11 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> try:
>from hashlib import md5
> except ImportError:
>from md5 import md5
Looks good to me -- thanks for the offer to fix this. In general, we
only actively want to be supporting 2 python versions at a time, but
if the
John Hunter wrote:
> On Fri, Jul 25, 2008 at 5:47 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> Ok, I think I found our problem, at line 859 of backend_ps.py (inside
>> _print_ps()):
>>
>>self.figure.set_dpi(72) # Override the dpi kwarg
>>dpi = kwargs.get("dpi", 72)
>>
>> The proble
On Fri, Jul 25, 2008 at 6:42 PM, Eric Firing <[EMAIL PROTECTED]> wrote:
> This is the kind of thing I would want to look at and test *very* carefully,
> or know that someone like John or Mike has done so--which perhaps one of
> them can do quickly. I have looked at this dpi business with puzzleme
John Hunter wrote:
> On Fri, Jul 25, 2008 at 5:47 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> Ok, I think I found our problem, at line 859 of backend_ps.py (inside
>> _print_ps()):
>>
>>self.figure.set_dpi(72) # Override the dpi kwarg
>>dpi = kwargs.get("dpi", 72)
>>
>> The proble
Ryan May wrote:
> John Hunter wrote:
>> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> What else is confusing is how that relates to DPI. When I change the
>>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger*
>>> barbs.
>>> To me, if I'm actually
On Fri, Jul 25, 2008 at 5:47 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Ok, I think I found our problem, at line 859 of backend_ps.py (inside
> _print_ps()):
>
>self.figure.set_dpi(72) # Override the dpi kwarg
>dpi = kwargs.get("dpi", 72)
>
> The problem here is that while it sets t
John Hunter wrote:
> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> What else is confusing is how that relates to DPI. When I change the
>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger* barbs.
>> To me, if I'm actually specifying pixels, there's
Eric Firing wrote:
> John Hunter wrote:
>> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> What else is confusing is how that relates to DPI. When I change the
>>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger*
>>> barbs.
>>> To me, if I'm actua
John Hunter wrote:
> On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> What else is confusing is how that relates to DPI. When I change the
>> figure's dpi, using set_dpi, (and redraw), I get physically *bigger* barbs.
>> To me, if I'm actually specifying pixels, there's
On Thu, Jul 24, 2008 at 10:00 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> What else is confusing is how that relates to DPI. When I change the
> figure's dpi, using set_dpi, (and redraw), I get physically *bigger* barbs.
> To me, if I'm actually specifying pixels, there's no way that they should
>
Eric Firing wrote:
> John Hunter wrote:
>> On Wed, Jul 23, 2008 at 10:05 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> Ok, it fixes the problem if I pass dpi=72 to savefig().
>>> Curiously,
>>> passing dpi=72 to Figure() does not have the same effect. So now how
>>> do I
>>
>> That is because
John Hunter wrote:
> On Wed, Jul 23, 2008 at 10:05 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> Ok, it fixes the problem if I pass dpi=72 to savefig(). Curiously,
>> passing dpi=72 to Figure() does not have the same effect. So now how do I
>
> That is because "savefig" has its own dpi, which ov
On Wed, Jul 23, 2008 at 10:05 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> Ok, it fixes the problem if I pass dpi=72 to savefig(). Curiously,
> passing dpi=72 to Figure() does not have the same effect. So now how do I
That is because "savefig" has its own dpi, which overrides the figure
dpi. Tee
John Hunter wrote:
> On Sat, Jul 19, 2008 at 11:09 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> The only issue I've seen is that scaling with PS is way too big. I've
>> attached ps and pdf files from the same run to show the problem.
>
> The only thing I can think of is since you are using a ide
Eric Firing wrote:
> Ryan May wrote:
>> Ok,
>>
>> I've committed my wind barbs stuff in SVN. Anyone interested, go
>> ahead an hammer on it.
>
> Very nice!
>
> Comments on the example, barb_demo.py:
>
> 1) In your third panel, you put the args after the kwargs. I had no
> idea this was even
Eric Firing wrote:
> Ryan May wrote:
>> Ok,
>>
>> I've committed my wind barbs stuff in SVN. Anyone interested, go
>> ahead an hammer on it.
>
> Very nice!
>
> Comments on the example, barb_demo.py:
>
> 1) In your third panel, you put the args after the kwargs. I had no
> idea this was even
Ryan May wrote:
> Ok,
>
> I've committed my wind barbs stuff in SVN. Anyone interested, go ahead
> an hammer on it.
Very nice!
Comments on the example, barb_demo.py:
1) In your third panel, you put the args after the kwargs. I had no
idea this was even legal--it's the first time I have seen
Ryan May wrote:
> Ok,
>
> I've committed my wind barbs stuff in SVN. Anyone interested, go ahead
> an hammer on it.
>
> Should I post this over on matplotlib-users, or does experience show
> that the SVN crowd all read here? (This is what you get for having a
> n00b developer :) )
We routi
How do you guys manage committing only parts of your working copy,
especially when you want to commit part of a file? I figure there's
got to
be a better way than multiple SVN checkouts and manually editing diffs.
>>> svn should do this automagically; it only commits the diff
Michael Droettboom wrote:
> Ryan May wrote:
>> 5) I added an empty circle marker for low wind speeds (vector
>> magnitudes). Accomplishing having the unfilled circle while having
>> the barbs filled involved a bit of a "elegant hack". Using the set of
>> vertices that draws the CirclePolygon,
Ryan May wrote:
> 5) I added an empty circle marker for low wind speeds (vector
> magnitudes). Accomplishing having the unfilled circle while having
> the barbs filled involved a bit of a "elegant hack". Using the set of
> vertices that draws the CirclePolygon, I add an additional copy of
> t
Ryan May wrote:
> John Hunter wrote:
>> On Sat, Jul 19, 2008 at 11:09 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> The only issue I've seen is that scaling with PS is way too big. I've
>>> attached ps and pdf files from the same run to show the problem.
>> The only thing I can think of is since
John Hunter wrote:
> On Sat, Jul 19, 2008 at 11:09 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> The only issue I've seen is that scaling with PS is way too big. I've
>> attached ps and pdf files from the same run to show the problem.
>
> The only thing I can think of is since you are using a ide
On Sat, Jul 19, 2008 at 11:09 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> The only issue I've seen is that scaling with PS is way too big. I've
> attached ps and pdf files from the same run to show the problem.
The only thing I can think of is since you are using a identity
transform and drawing i
Ryan May wrote:
> John Hunter wrote:
>> On Tue, Jul 15, 2008 at 5:37 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>>
>>> I welcome any comments/criticism to help improve this.
>> Hey Ryan,
>>
>> I have looked at this code briefly and have a few minor comments. I
>> think Eric, who did the bulk of the c
Jeff Whitaker wrote:
> Ryan May wrote:
>> Hi,
>>
>> I've got (what seems to me) a nice clean, self-contained
>> implementation of wind barbs plots. I'd like to see if I can get this
>> into matplotlib, as it would be very useful to the meteorology
>> community. I've borrowed heavily from Quive
John Hunter wrote:
> On Tue, Jul 15, 2008 at 5:37 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>> I welcome any comments/criticism to help improve this.
>
> Hey Ryan,
>
> I have looked at this code briefly and have a few minor comments. I
> think Eric, who did the bulk of the current quiver implem
Ryan May wrote:
Hi,
I've got (what seems to me) a nice clean, self-contained
implementation of wind barbs plots. I'd like to see if I can get this
into matplotlib, as it would be very useful to the meteorology
community. I've borrowed heavily from Quiver for rounding out rough
edges (like
John Hunter wrote:
> On Tue, Jul 15, 2008 at 5:37 PM, Ryan May <[EMAIL PROTECTED]> wrote:
>
>
> The 2nd alternative, which I haven't
> explored, is to set the edgecolor equal to the facecolor and support
> colormapping of the edgecolors.
>
FWIW, pcolor and pcolormesh have also needed this fun
On Tue, Jul 15, 2008 at 5:37 PM, Ryan May <[EMAIL PROTECTED]> wrote:
> I welcome any comments/criticism to help improve this.
Hey Ryan,
I have looked at this code briefly and have a few minor comments. I
think Eric, who did the bulk of the current quiver implementation, and
as an oceanographer
32 matches
Mail list logo
