matplotlib-users Mailing List for matplotlib

I've been in touch with the Travis-CI guys about this a little bit. 
They restrict each project to a single OS partly to reduce resource 
consumption, but they said they might reconsider for paying customers 
(which we may want to become).
Mike
On 08/16/2013 04:17 PM, Matt Terry wrote:
>
> I was looking into the TravisCI Mac testing environment. Right now, 
> you can only run tests on a single os. You also trigger a Mac build by 
> declaring your language to be objective-c. There are probably more q 
> quirks, but that's what I've found thus far.
>
> -matt
>
> On Aug 16, 2013 12:45 PM, "Matthew Brett" <mat...@gm... 
> <mailto:mat...@gm...>> wrote:
>
> Hi,
>
> On Fri, Aug 16, 2013 at 10:36 AM, Kevin Hunter Kesling
> <kmh...@nc... <mailto:kmh...@nc...>> wrote:
> > At 12:11pm -0400 2013年8月16日, Matthew Brett wrote:
> >>
> >> We've got 5 macs running OSX 10.4 through 10.8 for us, you'd be
> >> welcome to remote access to those, and we'd be happy to run builds
> >> for you. Paul Ivanov has or will have access to the buildbot master
> >> and all the slaves. We also have an XP and Windows 7 64 bit machine
> >> you are welcome to use.
> >
> >
> > Bless you for supporting OS X prior to 10.6! My family still
> has a quite
> > functional OS X 10.5 machine that we should update but can't for
> various
> > (less than stellar, but unfortunately real) reasons. I'm
> chagrined that
> > Apple et al. no longer supports 10.5. I'm sure others feel
> similarly about
> > their 10.4- machines.
> >
> > On the other hand, no one would blame a development team that
> decided not to
> > support what even Apple does not support.
>
> :) - we just happened to have them lying around. Actually, the 10.5
> machine is PPC and catches endian errors fairly often, but I'm sure
> we'll retire the 10.4 machine fairly soon.
>
> Cheers,
>
> Matthew
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I was looking into the TravisCI Mac testing environment. Right now, you can
only run tests on a single os. You also trigger a Mac build by declaring
your language to be objective-c. There are probably more q quirks, but
that's what I've found thus far.
-matt
On Aug 16, 2013 12:45 PM, "Matthew Brett" <mat...@gm...> wrote:
> Hi,
>
> On Fri, Aug 16, 2013 at 10:36 AM, Kevin Hunter Kesling
> <kmh...@nc...> wrote:
> > At 12:11pm -0400 2013年8月16日, Matthew Brett wrote:
> >>
> >> We've got 5 macs running OSX 10.4 through 10.8 for us, you'd be
> >> welcome to remote access to those, and we'd be happy to run builds
> >> for you. Paul Ivanov has or will have access to the buildbot master
> >> and all the slaves. We also have an XP and Windows 7 64 bit machine
> >> you are welcome to use.
> >
> >
> > Bless you for supporting OS X prior to 10.6! My family still has a quite
> > functional OS X 10.5 machine that we should update but can't for various
> > (less than stellar, but unfortunately real) reasons. I'm chagrined that
> > Apple et al. no longer supports 10.5. I'm sure others feel similarly
> about
> > their 10.4- machines.
> >
> > On the other hand, no one would blame a development team that decided
> not to
> > support what even Apple does not support.
>
> :) - we just happened to have them lying around. Actually, the 10.5
> machine is PPC and catches endian errors fairly often, but I'm sure
> we'll retire the 10.4 machine fairly soon.
>
> Cheers,
>
> Matthew
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi,
On Fri, Aug 16, 2013 at 10:36 AM, Kevin Hunter Kesling
<kmh...@nc...> wrote:
> At 12:11pm -0400 2013年8月16日, Matthew Brett wrote:
>>
>> We've got 5 macs running OSX 10.4 through 10.8 for us, you'd be
>> welcome to remote access to those, and we'd be happy to run builds
>> for you. Paul Ivanov has or will have access to the buildbot master
>> and all the slaves. We also have an XP and Windows 7 64 bit machine
>> you are welcome to use.
>
>
> Bless you for supporting OS X prior to 10.6! My family still has a quite
> functional OS X 10.5 machine that we should update but can't for various
> (less than stellar, but unfortunately real) reasons. I'm chagrined that
> Apple et al. no longer supports 10.5. I'm sure others feel similarly about
> their 10.4- machines.
>
> On the other hand, no one would blame a development team that decided not to
> support what even Apple does not support.
:) - we just happened to have them lying around. Actually, the 10.5
machine is PPC and catches endian errors fairly often, but I'm sure
we'll retire the 10.4 machine fairly soon.
Cheers,
Matthew

At 12:11pm -0400 2013年8月16日, Matthew Brett wrote:
> We've got 5 macs running OSX 10.4 through 10.8 for us, you'd be
> welcome to remote access to those, and we'd be happy to run builds
> for you. Paul Ivanov has or will have access to the buildbot master
> and all the slaves. We also have an XP and Windows 7 64 bit machine
> you are welcome to use.
Bless you for supporting OS X prior to 10.6! My family still has a 
quite functional OS X 10.5 machine that we should update but can't for 
various (less than stellar, but unfortunately real) reasons. I'm 
chagrined that Apple et al. no longer supports 10.5. I'm sure others 
feel similarly about their 10.4- machines.
On the other hand, no one would blame a development team that decided 
not to support what even Apple does not support.
Cheers,
Kevin

Hi,
On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <md...@st...> wrote:
> We actually discussed this very issue yesterday in our Google hangout about
> continuous integration. We're probably going to need to script a full setup
> from a clean Mac + XCode to a working matplotlib development environment in
> order to make that happen, and obviously that will be shared with the world.
> Things are even more complex on Windows, and I'd like to do that there, too.
> So stay tuned.
We've got 5 macs running builds on OSX 10.4 through 10.8 for us, you'd be
welcome to remote access to those, and we'd be happy to run builds for
you. Paul Ivanov has or will have access to the buildbot master and
all the slaves. We also have an XP and Windows 7 64 bit machine you
are welcome to use.
Cheers,
Matthew

Hi,
On Fri, Aug 16, 2013 at 7:32 AM, Michael Droettboom <md...@st...> wrote:
> We actually discussed this very issue yesterday in our Google hangout about
> continuous integration. We're probably going to need to script a full setup
> from a clean Mac + XCode to a working matplotlib development environment in
> order to make that happen, and obviously that will be shared with the world.
> Things are even more complex on Windows, and I'd like to do that there, too.
> So stay tuned.
We've got 5 macs running OSX 10.4 through 10.8 for us, you'd be
welcome to remote access to those, and we'd be happy to run builds for
you. Paul Ivanov has or will have access to the buildbot master and
all the slaves. We also have an XP and Windows 7 64 bit machine you
are welcome to use.
Cheers,
Matthew

We actually discussed this very issue yesterday in our Google hangout 
about continuous integration. We're probably going to need to script a 
full setup from a clean Mac + XCode to a working matplotlib development 
environment in order to make that happen, and obviously that will be 
shared with the world. Things are even more complex on Windows, and I'd 
like to do that there, too. So stay tuned.
Mike
On 08/16/2013 10:02 AM, Paul Hobson wrote:
> Mike,
>
> That's great news. Is there any chance we can look forward to 
> "official" instructions for setting up a Mac to develop matplotlib?
>
> I gave up a long time ago and started piecing to together my meager 
> PRs in a linux VM.
> -paul
>
>
> On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st... 
> <mailto:md...@st...>> wrote:
>
> Thanks to the gracious donation from Hans Petter Langtangen and the
> Center for Biomedical Computing at Simula
> (http://home.simula.no/~hpl <http://home.simula.no/%7Ehpl>),
> I now have a new Mac Mini sitting at my desk. This should allow me to
> keep on top of changes that affect the Mac builds and to better track
> down Mac-only issues.
>
> Stay tuned over the next few weeks and months as we will most
> likely be
> using some more of these funds to pay for hosted continuous
> integration
> services (as discussed yesterday in our MEP19 Google Hangout).
>
> Cheers,
> Mike
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> <mailto:Mat...@li...>
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>

Mike,
That's great news. Is there any chance we can look forward to "official"
instructions for setting up a Mac to develop matplotlib?
I gave up a long time ago and started piecing to together my meager PRs in
a linux VM.
-paul
On Fri, Aug 16, 2013 at 6:52 AM, Michael Droettboom <md...@st...> wrote:
> Thanks to the gracious donation from Hans Petter Langtangen and the
> Center for Biomedical Computing at Simula (http://home.simula.no/~hpl),
> I now have a new Mac Mini sitting at my desk. This should allow me to
> keep on top of changes that affect the Mac builds and to better track
> down Mac-only issues.
>
> Stay tuned over the next few weeks and months as we will most likely be
> using some more of these funds to pay for hosted continuous integration
> services (as discussed yesterday in our MEP19 Google Hangout).
>
> Cheers,
> Mike
>
>
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

Thanks to the gracious donation from Hans Petter Langtangen and the 
Center for Biomedical Computing at Simula (http://home.simula.no/~hpl), 
I now have a new Mac Mini sitting at my desk. This should allow me to 
keep on top of changes that affect the Mac builds and to better track 
down Mac-only issues.
Stay tuned over the next few weeks and months as we will most likely be 
using some more of these funds to pay for hosted continuous integration 
services (as discussed yesterday in our MEP19 Google Hangout).
Cheers,
Mike

On Thu, Aug 15, 2013 at 09:06:02PM +0200, vwf wrote:
[...]
> On stackoverflow I found:
> widths = np.linspace(0, 2, X.size)
> plt.quiver(X, Y, cos(deg), sin(deg), linewidths=widths)
[...]
I kind of found out how it works. quiver has width and linewidth.
width takes a scalar, linewidth can take a vector. 
width sets the width of the shaft, linewidth sets the width of the edge...
How it works precisely I do not know yet, but this works for me:
plt.quiver(x_vector,y_vector,u_vector,v_vector,
 linewidth=w_vector, width=0.001, headwidth=3,
 color=mycolor, edgecolors=mycolor)
Cheers

On Aug 15, 2013 3:07 PM, "vwf" <vw...@vu...> wrote:
>
> After some struggling I got my first plots with quiver working.
> A simple plot is very simple, but a complicated one is very different.
> Right now I have a 80x80 grid with multiple plots and I plan to go up.
> For this I need full control of the arrow dimensions.
>
> The only way I can get narrow arrow is by setting width:
> plt.quiver(x,y,u,v, width=0.001, headwidth=3, scale=0.07,...
> works fine for me. But I would like to set the linewidth per arrow.
>
> On stackoverflow I found:
> widths = np.linspace(0, 2, X.size)
> plt.quiver(X, Y, cos(deg), sin(deg), linewidths=widths)
>
> This did not work for me: the minimum width was too large.
> I there a way to create narrow arrows with varying width?
>
The point of the example was to show that one can assign an array of widths
to a quiver plot. The array can have whatever values you want. Note that
there is likely a subtle difference between "width" and "linewidth" as
keyword arguments that you might want to experiment with.
Cheers!
Ben Root

On Aug 15, 2013 1:31 PM, "vwf" <vw...@vu...> wrote:
>
> Got it working!
It would be nice to post your solution here in case others are interested.
>
> (new problems in the making...)
>
>
Good, can't wait to hear them!
Cheers!
Ben Root