Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Eric Firing
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread John Hunter
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread John Hunter
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Eric Firing
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Eric Firing
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread John Hunter
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-25 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-24 Thread Eric Firing
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-24 Thread John Hunter
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 >

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-24 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-24 Thread Eric Firing
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-24 Thread John Hunter
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-23 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-22 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-21 Thread Ryan May
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,

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-21 Thread Michael Droettboom
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-21 Thread Eric Firing
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-20 Thread Ryan May
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

Re: [matplotlib-devel] Wind Barbs Full Patch

2008-07-20 Thread John Hunter
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