matplotlib-users Mailing List for matplotlib (Page 4)

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

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?
Thanks

Got it working!
(new problems in the making...)

Hello,
I would like to have a set of quiver plots on top of each other: the x/y
positions remain the same but the arrows have different directions. The
arrays are largely empty so the multiple-arrow problem is not that bad
(and very interesting). Can this be done? Right now only the last quiver
plot is visible, the others are gone after plotting.
The objective is multiple arrows on one x/y location, in different
colors. If this can be done in another way please share it.
If it is of any importance: I have arrays with x/y/u/v data, and for
all arrays the x/y positions are the same.
Thanks!

Hi gsal,
Would you mind sharing a simple example how did you manage to that? I am
trying to freeze a simple code with matplotlib for the past two days with no
success, every time I get the "No module backend_tkagg" message... ;(
Many thanks for help in advance!
gsal wrote
> oh, I got it...needed to include backend package in the cf_freeze setup
> script.
> 
> thanks,
--
View this message in context: http://matplotlib.1069221.n5.nabble.com/cx-freeze-ing-tp41780p41808.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Forgot to mention. I normally use epstopdf to convert eps files to pdf
files and the color information is stripped from the pdf file when embedded
with the color or xcolor packages from within matplotlib. But if you use,
epspdf or epspdftk on linux you can retain color information when
converting eps files to pdf files so can try that as an option.
On Wed, Aug 14, 2013 at 8:50 PM, Xiha <xi...@la...> wrote:
> Thanks Jeffrey. That clarifies why \mathcal works everywhere: it's handled
> by matplotlib's own parser. In contrast, for \textcolor, a call to TeX via
> the lines
>
> from matplotlib import rc
> rc('text', usetex=True)
> rc('text.latex', preamble='\usepackage{color}')
>
> is necessary.
>
> I still don't get \texcolor to work for anything other than ps. This is
> inconvenient as I'm not used to PostScript; for one thing, when I need the
> plot to be 'big' [using plt.figure(figsize=(13.0, 13.0))], the ps file
> created seems to be an A4 format with the plot not fitting onto it: it is
> shown only partially. In contrast, for pdf or svg output, the page size is
> adapted to the figure size -- but in those cases \textcolor does not work...
>
>
> On Wed 14 Aug 2013 03:34:13 CEST, Jeffrey Spencer wrote:
>
>> Have a look here why Mathcal works in all backends:
>>
>> http://matplotlib.org/users/**mathtext.html<http://matplotlib.org/users/mathtext.html>
>>
>> They give an example for an interactive backend which means it would
>> work with any output format in the link you provided. Could also use
>> \textcolor for .pdf output as well since the text rendering would use
>> TeX as well but this wouldn't get you SVG.
>>
>> On Tue, Aug 13, 2013 at 9:00 PM, Xiha <xi...@la...
>> <mailto:xi...@la...>> wrote:
>>
>> Hello,
>>
>> I am trying to color-highlight parts of a figure title. I got it
>> to work via the second ('non-interactive') solution given here
>> <http://stackoverflow.com/**questions/9169052/partial-**
>> coloring-of-text-in-matplotlib<http://stackoverflow.com/questions/9169052/partial-coloring-of-text-in-matplotlib>
>> **>,
>>
>> using TeX's \textcolor. It has the advantage (over the first
>> solution) that you can use .xlabel(), .title() etc. as usual.
>>
>> However the limitation stated is that it only works when saving
>> the plot as a PostScript file. I'm finding this to be true: the
>> coloring does not appear when plotting to the screen rather than
>> to a file (as with .show()), nor when using matplotlib.use('SVG')
>> or matplotlib.use('AGG') to get svg or png output (which I would
>> prefer). This is so even though other 'fancy' TeX commands like
>> \mathcal do seem to work in all output options.
>>
>> I am only minimally acquainted with (La)TeX, and fairly new to
>> Python and matplotlib too, so I don't quite grasp what is going on
>> here, and whether it is worth digging deeper to try and make it
>> work. So: why is there a difference in success between using
>> (e.g.) \mathcal versus \textcolor over different output options?
>>
>> Many thanks!
>> ||
>>
>> ------------------------------**------------------------------**
>> ------------------
>> 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<http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk>
>> ______________________________**_________________
>> Matplotlib-users mailing list
>> Matplotlib-users@lists.**sourceforge.net<Mat...@li...>
>> <mailto:Matplotlib-users@**lists.sourceforge.net<Mat...@li...>
>> >
>> https://lists.sourceforge.net/**lists/listinfo/matplotlib-**users<https://lists.sourceforge.net/lists/listinfo/matplotlib-users>
>>
>>
>>
>
>

The .tex parser for matplotlib uses dvi files that when converted to be
used in a pdf or other backends lose their color information is my guess.
If you output a ps file (or an eps file which you might want to do so you
don't have to set the page size). Then run epstopdf or pstopdf the color is
striped from the file as well. I don't know enough about the actual
mechanisms to provide much more information then this but hope that helps.
On Wed, Aug 14, 2013 at 8:50 PM, Xiha <xi...@la...> wrote:
> Thanks Jeffrey. That clarifies why \mathcal works everywhere: it's handled
> by matplotlib's own parser. In contrast, for \textcolor, a call to TeX via
> the lines
>
> from matplotlib import rc
> rc('text', usetex=True)
> rc('text.latex', preamble='\usepackage{color}')
>
> is necessary.
>
> I still don't get \texcolor to work for anything other than ps. This is
> inconvenient as I'm not used to PostScript; for one thing, when I need the
> plot to be 'big' [using plt.figure(figsize=(13.0, 13.0))], the ps file
> created seems to be an A4 format with the plot not fitting onto it: it is
> shown only partially. In contrast, for pdf or svg output, the page size is
> adapted to the figure size -- but in those cases \textcolor does not work...
>
>
> On Wed 14 Aug 2013 03:34:13 CEST, Jeffrey Spencer wrote:
>
>> Have a look here why Mathcal works in all backends:
>>
>> http://matplotlib.org/users/**mathtext.html<http://matplotlib.org/users/mathtext.html>
>>
>> They give an example for an interactive backend which means it would
>> work with any output format in the link you provided. Could also use
>> \textcolor for .pdf output as well since the text rendering would use
>> TeX as well but this wouldn't get you SVG.
>>
>> On Tue, Aug 13, 2013 at 9:00 PM, Xiha <xi...@la...
>> <mailto:xi...@la...>> wrote:
>>
>> Hello,
>>
>> I am trying to color-highlight parts of a figure title. I got it
>> to work via the second ('non-interactive') solution given here
>> <http://stackoverflow.com/**questions/9169052/partial-**
>> coloring-of-text-in-matplotlib<http://stackoverflow.com/questions/9169052/partial-coloring-of-text-in-matplotlib>
>> **>,
>>
>> using TeX's \textcolor. It has the advantage (over the first
>> solution) that you can use .xlabel(), .title() etc. as usual.
>>
>> However the limitation stated is that it only works when saving
>> the plot as a PostScript file. I'm finding this to be true: the
>> coloring does not appear when plotting to the screen rather than
>> to a file (as with .show()), nor when using matplotlib.use('SVG')
>> or matplotlib.use('AGG') to get svg or png output (which I would
>> prefer). This is so even though other 'fancy' TeX commands like
>> \mathcal do seem to work in all output options.
>>
>> I am only minimally acquainted with (La)TeX, and fairly new to
>> Python and matplotlib too, so I don't quite grasp what is going on
>> here, and whether it is worth digging deeper to try and make it
>> work. So: why is there a difference in success between using
>> (e.g.) \mathcal versus \textcolor over different output options?
>>
>> Many thanks!
>> ||
>>
>> ------------------------------**------------------------------**
>> ------------------
>> 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<http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk>
>> ______________________________**_________________
>> Matplotlib-users mailing list
>> Matplotlib-users@lists.**sourceforge.net<Mat...@li...>
>> <mailto:Matplotlib-users@**lists.sourceforge.net<Mat...@li...>
>> >
>> https://lists.sourceforge.net/**lists/listinfo/matplotlib-**users<https://lists.sourceforge.net/lists/listinfo/matplotlib-users>
>>
>>
>>
>
>

Thanks Jeffrey. That clarifies why \mathcal works everywhere: it's 
handled by matplotlib's own parser. In contrast, for \textcolor, a call 
to TeX via the lines
from matplotlib import rc
rc('text', usetex=True)
rc('text.latex', preamble='\usepackage{color}')
is necessary.
I still don't get \texcolor to work for anything other than ps. This is 
inconvenient as I'm not used to PostScript; for one thing, when I need 
the plot to be 'big' [using plt.figure(figsize=(13.0, 13.0))], the ps 
file created seems to be an A4 format with the plot not fitting onto 
it: it is shown only partially. In contrast, for pdf or svg output, the 
page size is adapted to the figure size -- but in those cases 
\textcolor does not work...
On Wed 14 Aug 2013 03:34:13 CEST, Jeffrey Spencer wrote:
> Have a look here why Mathcal works in all backends:
>
> http://matplotlib.org/users/mathtext.html
>
> They give an example for an interactive backend which means it would
> work with any output format in the link you provided. Could also use
> \textcolor for .pdf output as well since the text rendering would use
> TeX as well but this wouldn't get you SVG.
>
> On Tue, Aug 13, 2013 at 9:00 PM, Xiha <xi...@la...
> <mailto:xi...@la...>> wrote:
>
> Hello,
>
> I am trying to color-highlight parts of a figure title. I got it
> to work via the second ('non-interactive') solution given here
> <http://stackoverflow.com/questions/9169052/partial-coloring-of-text-in-matplotlib>,
> using TeX's \textcolor. It has the advantage (over the first
> solution) that you can use .xlabel(), .title() etc. as usual.
>
> However the limitation stated is that it only works when saving
> the plot as a PostScript file. I'm finding this to be true: the
> coloring does not appear when plotting to the screen rather than
> to a file (as with .show()), nor when using matplotlib.use('SVG')
> or matplotlib.use('AGG') to get svg or png output (which I would
> prefer). This is so even though other 'fancy' TeX commands like
> \mathcal do seem to work in all output options.
>
> I am only minimally acquainted with (La)TeX, and fairly new to
> Python and matplotlib too, so I don't quite grasp what is going on
> here, and whether it is worth digging deeper to try and make it
> work. So: why is there a difference in success between using
> (e.g.) \mathcal versus \textcolor over different output options?
>
> Many thanks!
> ||
>
> ------------------------------------------------------------------------------
> 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
>
>

Have a look here why Mathcal works in all backends:
http://matplotlib.org/users/mathtext.html
They give an example for an interactive backend which means it would work
with any output format in the link you provided. Could also use \textcolor
for .pdf output as well since the text rendering would use TeX as well but
this wouldn't get you SVG.
On Tue, Aug 13, 2013 at 9:00 PM, Xiha <xi...@la...> wrote:
> Hello,
>
> I am trying to color-highlight parts of a figure title. I got it to work
> via the second ('non-interactive') solution given here<http://stackoverflow.com/questions/9169052/partial-coloring-of-text-in-matplotlib>,
> using TeX's \textcolor. It has the advantage (over the first solution) that
> you can use .xlabel(), .title() etc. as usual.
>
> However the limitation stated is that it only works when saving the plot
> as a PostScript file. I'm finding this to be true: the coloring does not
> appear when plotting to the screen rather than to a file (as with .show()),
> nor when using matplotlib.use('SVG') or matplotlib.use('AGG') to get svg or
> png output (which I would prefer). This is so even though other 'fancy' TeX
> commands like \mathcal do seem to work in all output options.
>
> I am only minimally acquainted with (La)TeX, and fairly new to Python and
> matplotlib too, so I don't quite grasp what is going on here, and whether
> it is worth digging deeper to try and make it work. So: why is there a
> difference in success between using (e.g.) \mathcal versus \textcolor over
> different output options?
>
> Many thanks!
>
>
> ------------------------------------------------------------------------------
> 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
>
>

Hello,
I am trying to color-highlight parts of a figure title. I got it to work 
via the second ('non-interactive') solution given here 
<http://stackoverflow.com/questions/9169052/partial-coloring-of-text-in-matplotlib>, 
using TeX's \textcolor. It has the advantage (over the first solution) 
that you can use .xlabel(), .title() etc. as usual.
However the limitation stated is that it only works when saving the plot 
as a PostScript file. I'm finding this to be true: the coloring does not 
appear when plotting to the screen rather than to a file (as with 
.show()), nor when using matplotlib.use('SVG') or matplotlib.use('AGG') 
to get svg or png output (which I would prefer). This is so even though 
other 'fancy' TeX commands like \mathcal do seem to work in all output 
options.
I am only minimally acquainted with (La)TeX, and fairly new to Python 
and matplotlib too, so I don't quite grasp what is going on here, and 
whether it is worth digging deeper to try and make it work. So: why is 
there a difference in success between using (e.g.) \mathcal versus 
\textcolor over different output options?
Many thanks!
||

As I'm researching what we may want to do for better continuous 
integration, I'm remembering that at least one person, Thomas Kluyver, 
is producing daily automated builds (for Ubuntu) here:
https://launchpad.net/~takluyver/+archive/matplotlib-daily 
<https://launchpad.net/%7Etakluyver/+archive/matplotlib-daily>
Is anyone else out there doing anything similar for other Linux distros 
or other platforms? a) I'd like to list these things on the main 
website, and b) I'd like to look at how these kinds of things might make 
sense as part of a broader CI strategy.
Cheers,
Mike

On Tue, Aug 13, 2013 at 04:43:19PM +1000, Stephen Gibson wrote:
> Call 'figure()' for each plot.
Like this you mean?
import matplotlib.pyplot as plt
a=plt.figure()
a=plt.plot([1, 2], [1, 2])
plt.savefig('1.png', dpi=100)
a=plt.figure()
a=plt.plot([1, 2], [2,1])
plt.savefig('2.png', dpi=100)
Thank you!

On 2013年08月12日 8:35 PM, vwf wrote:
> Thank you for you reply. I tried to create one after the other but when
> I did this my second plot was on top of the first one. The old plot
> needs to be "flushed" before starting the second one.
>
> This doesn't work:
> import matplotlib.pyplot as plt
> a=plt.plot([1, 2], [1, 2])
> plt.savefig('1.png', dpi=100)
plt.close()
> b=plt.plot([1, 2], [2,1])
> plt.savefig('2.png', dpi=100)
>
> In 2.png, a and b are on top of each other
>

Call 'figure()' for each plot.
see: http://matplotlib.org/api/pyplot_api.html
matplotlib.pyplot.figure(/num=None/, /figsize=None/, /dpi=None/, 
/facecolor=None/, /edgecolor=None/, /frameon=True/, /FigureClass=<class 
'matplotlib.figure.Figure'>/, /**kwargs/)
 Creates a new figure.
 Parameters : 	
 *num* : integer or string, optional, default: none
 If not provided, a new figure will be created, and a the figure
 number will be increamted. The figure objects holds this number
 in a number attribute. If num is provided, and a figure with
 this id already exists, make it active, and returns a reference
 to it. If this figure does not exists, create it and returns it.
 If num is a string, the window title will be set to this
 figure's num.
Steve.

Thank you for you reply. I tried to create one after the other but when
I did this my second plot was on top of the first one. The old plot
needs to be "flushed" before starting the second one.
This doesn't work:
import matplotlib.pyplot as plt
a=plt.plot([1, 2], [1, 2])
plt.savefig('1.png', dpi=100)
b=plt.plot([1, 2], [2,1])
plt.savefig('2.png', dpi=100)
In 2.png, a and b are on top of each other
On Tue, Aug 13, 2013 at 12:10:32AM -0600, Joseph Hardin wrote:
> Can you provide us with more information? You can create one plot, save it,
> and then create the second, or is there something more specific you are
> looking for?
> 
> 
> On Mon, Aug 12, 2013 at 11:58 PM, vwf <vw...@vu...> wrote:
> 
> > Hello,
> >
> > I need to create two plots (png files) in one go, two unrelated views of
> > the same dataset. There is good documentation about subplots but I
> > cannot locate documentation about two plots. Can someone tell me how it
> > is done?
> >
> >
> > ------------------------------------------------------------------------------
> > 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
> >
> 
> 
> 
> -- 
> Joseph Hardin, MSEE
> Colorado State University
> Radar and Communications Laboratory
> One must do not violence to nature, nor model it in conformity to any
> blindly formed chimaera.
> -Janos Boylai