matplotlib-users Mailing List for matplotlib (Page 2)

Hi,

> Try getting your system set up to use the xpdf distiller, that has always 
> given me excellent results.

Thanks alot! Using xpdf gives perfect results!
http://www.staff.uni-mainz.de/wuertz/matplotlib/xpdf_tof_spectrum_bec_500ns.eps
http://www.staff.uni-mainz.de/wuertz/matplotlib/xpdf_tof_spectrum_bec_500ns.pdf

> There have been many problems reported on this mailing list that concern latex 
> markup. Most often, people have difficulty getting usetex to work because 
> matplotlib depends on latex, dvipng, ghostscript, and optionally xpdf (more 
> precisely, xpdf's pdftops utility).

The problem is, the whole plot/ps/eps/dvi/ghostscript/pdf/xpdf/distiller
process is totally obscure to a normal user. For example, i don't have
xpdf installed... but choosing the xpdf setting gives me perfect results
now. If I understand you correctly, I just need the "pdftops" utility
included in "poppler-utils".

Well, thanks again!

-
Peter

On Tuesday 24 July 2007 9:50:46 am Peter W=FCrtz wrote:
> Hi,
>
> I ran into some troubles when trying to do the following with
> matplotlib:
> 	- plotting a figure
> 	- using latex for axis labels
> 	- (getting acceptable fonts)
> 	- getting a pdf in the end
> I've not been able to solve this.
>
> In the documentation I found 2 ways to do this. First, when a string is
> enclosed in $ signs, matplotlib has its own way of rendering latex code.
> Thats ok for mathematical expressions, but I can't print normal text at
> all. The documentation says that \rm{} should be used, but
>
> "$\rm{some label text} (\mu V)$" becomes "somelabeltext\muV"

I think you need to use raw strings so your \'s are interpretted as \'s and=
=20
not as special characters (like \n is newline). We know it is inconvenient=
=20
that you cant do something like r'This example: $a=3De^{i\pi}$' with the=20
existing mathtext, but it is a difficult problem and remains unsolved.

> so I searched again and found another documentation, telling me to
> enable 'text.usetex' so all text is handled by latex. This way, the text
> is rendered correctly, but then the font used for the tick numbers
> switches to some ugly looking font.

=46or starters, see http://www.scipy.org/Cookbook/Matplotlib/UsingTex. I su=
ggest=20
changing your serif rc settings to use the PSNFSS fonts described in that=20
link. Also, try deleting your ~/.matplotlib/tex.cache.

> Because Latex mode does not seem to work with the pdf output,=20

It doesn't, not yet.

> I saved=20
> these figures as EPS, using epstopdf in oder to get a pdf. Normally this
> process gives me perfect results, but the ugly-font-ticks problem is
> getting even worse, because in the pdf some of them are just missing.

Try getting your system set up to use the xpdf distiller, that has always=20
given me excellent results.

> I upped the eps and pdf files here:
> http://www.staff.uni-mainz.de/wuertz/matplotlib/
> There is also a png file with a screenshot from the "ugly" and missing
> ticks.
>
> Plotting a reasonable figure seems to be hard, is there any chance of
> solving this problem?

There have been many problems reported on this mailing list that concern la=
tex=20
markup. Most often, people have difficulty getting usetex to work because=20
matplotlib depends on latex, dvipng, ghostscript, and optionally xpdf (more=
=20
precisely, xpdf's pdftops utility). If those dependencies are not working=20
properly, or if you are missing latex packages or fonts, then it shows up i=
n=20
mpl's output.

Darren

On Tue, 24 Jul 2007, Jouni K. Seppänen wrote:

> Peter Würtz <pw...@st...>
> writes:

>> The documentation says that \rm{} should be used, but

>> "$\rm{some label text} (\mu V)$" becomes "somelabeltext\muV"

> This is similar to what you would get in TeX, so strictly taken it is
> not a bug. However, in TeX you could write "some label text ($\mu V$)"
> instead, which unfortunately does not work with matplotlib. A workaround
> is to type r"$\rm{some\ label\ text}\ (\mu V)$", (as Christian Meesters
> already wrote).

Shouldn't
r"some label text ($\mu V$)"
work?

BTW, my EPS issues went away when I started starting my scripts with

from pylab import *
text.usetex = True
from matplotlib import rc
rc('text', usetex=True)

-- 
======================================================================
Office: 0.17 (Golm)                     Dr. John T. Whelan
Phone: +49 331 567 7117                 MPI for Gravitational Physics
FAX:   +49 331 567 7298                 (Albert-Einstein Institute)
http://www.aei.mpg.de/~whelan/          D-14424 Potsdam
joh...@li...                    joh...@ae...
======================================================================

Peter Würtz <pw...@st...>
writes:

> The documentation says that \rm{} should be used, but
>
> "$\rm{some label text} (\mu V)$" becomes "somelabeltext\muV"

This is similar to what you would get in TeX, so strictly taken it is
not a bug. However, in TeX you could write "some label text ($\mu V$)"
instead, which unfortunately does not work with matplotlib. A workaround
is to type r"$\rm{some\ label\ text}\ (\mu V)$", (as Christian Meesters
already wrote).

Even if this solves your immediate problem, it would be interesting to
debug it further to find the reason that usetex is not working right.

> This way, the text is rendered correctly, but then the font used for
> the tick numbers switches to some ugly looking font.

I could not find the font in your eps file. I think the ghostscript
"distilling" step may have converted the original font to pure drawing
commands. Could you repeat the test with ps.usedistiller set to None and
upload the resulting file? It may also be interesting to set
ps.usedistiller to xpdf, if you do have the required programs.

> Because Latex mode does not seem to work with the pdf output, 

Correct: the usetex option is not yet supported by the pdf backend.

-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hoi Peter,

> "$\rm{some label text} (\mu V)$" becomes "somelabeltext\muV"
You could try
r"$\rm{some\ label\ text} (\mu V)$"
instead. (Note the backslashes and the 'raw' r in front of the string.)
This way the string should be interpreted fine. You can use the '\ ' to
force a space, but whether it's necessary depends on the string you want
to display, of course.

Possible statements in the head of your programs might be:
from matplotlib import rcParams
rcParams['text.fontname'] = 'cmr10'
rcParams['lines.markerfacecolor'] = None
from matplotlib import rc
rc('text', usetex=True)
rc('axes', hold=True)

(From a current program of mine. Of course, some statements have nothing
to do with your problem, but they might illustrate some options you
have.)

The wiki/Cookbook has some info (on pitfalls, too):
http://www.scipy.org/Cookbook/Matplotlib/UsingTex
http://www.scipy.org/Cookbook/Matplotlib/LaTeX_Examples

You probably know the mathtex module:
http://matplotlib.sourceforge.net/matplotlib.mathtext.html
the wheeler_demo:
http://matplotlib.sourceforge.net/screenshots/wheeler_demo.py
and the tex_demo:
http://matplotlib.sourceforge.net/screenshots/tex_demo.py
?

As for your eps2pdf-problem:
I don't know any straightforward solution (one that always gives a
pleasant output) for it, but had a similar problem lately. It seems that
MPLs eps-output is not well read in by many viewers / converters (that
statement correct?). Correcting the eps with eps2eps or trying to
convert the eps with some other software did not work well for me. My
solution was:
Producing plots in formats other then eps/ps (e. g. png), with
sufficient resolution and converting to the format the publisher wanted
with other software (e.g. gimp or see what's on our terminal
server ;-) ).
Currently I'm only using eps figures for import into LaTeX - works fine.

HTH
Christian

Hi,

I ran into some troubles when trying to do the following with
matplotlib:
	- plotting a figure
	- using latex for axis labels
	- (getting acceptable fonts)
	- getting a pdf in the end
I've not been able to solve this.

In the documentation I found 2 ways to do this. First, when a string is
enclosed in $ signs, matplotlib has its own way of rendering latex code.
Thats ok for mathematical expressions, but I can't print normal text at
all. The documentation says that \rm{} should be used, but

"$\rm{some label text} (\mu V)$" becomes "somelabeltext\muV"

so I searched again and found another documentation, telling me to
enable 'text.usetex' so all text is handled by latex. This way, the text
is rendered correctly, but then the font used for the tick numbers
switches to some ugly looking font.

Because Latex mode does not seem to work with the pdf output, I saved
these figures as EPS, using epstopdf in oder to get a pdf. Normally this
process gives me perfect results, but the ugly-font-ticks problem is
getting even worse, because in the pdf some of them are just missing.

I upped the eps and pdf files here:
http://www.staff.uni-mainz.de/wuertz/matplotlib/
There is also a png file with a screenshot from the "ugly" and missing
ticks.

Plotting a reasonable figure seems to be hard, is there any chance of
solving this problem?

Thanks in advance,
Peter

Hi Anthony,
=20
> legend to be at the same height as the top of the axis.  How=20
> do I go about moving the legend once I've created it?

myLegend._loc=3D(x,y)
myFigure.draw()

There doesn't seem to be a .moveLegend() or equivalent method, so I
always update the semi-private ._loc and on redraw.  After the draw, the
legend appears where you want it (in 0..1 figure coords, not data
coords).

HTH,
Anthony.

Hi list,

how can I position major xticklabels on top of my axes an minor 
xticklabels on bottom?

Example:

Datetimes on xaxis, minors = hours, labels as usual below xaxis, majors 
= days, labels on top of my axes:



	23.07	24.07	25.07	26.07	27.07	28.07	
--------------------------------------------------------------
|         x
| x	x  x x    x
|  x   x      x  x x
|    x          x   x
|                    x
|                     x
|                       x
|                        x
|                         x
|                          x
|
|
---------------------------------------------------------------
   0 6 9 12 18 0 6 9 12 18 ........


Regards
Simon

I've been using matplotlib on OSX a bit and was wondering if anyone  
had code out there for a polar half-space plot?  I created one for  
matlab a while back and if there is not one for matplotlib, I would  
be happy to offer up my code as a good beginning.  It has a good bit  
of logic in it to make the plot look good.  My python is not the best  
so I wanted to see if anyone wanted to take a crack at it before I  
did a messy python hack of it.


--Chad Kidder

If numpy provide us with a distutils version that *works* IMHO 
matplotlib should just be shipped with.
If it is overkill, it could be possible to detect the compiler version 
and to remove this option if and only if g++ is used.
It looks not so clean but cleaner than compiling this an extra option 
and waiting for the next g++ version which may move from a warning to an 
error...
Maybe we should also ask on the python ML.

 From http://docs.python.org/ext/building.html "distutils users should 
trust that distutils gets the invocations right." : ha ha ha!

Xavier

> This is a long standing Python (distutils) bug, IMHO.
>
> Numpy, for instance, ships with a heavily patched version of distutils 
> that has a workaround for this.  Maybe now that mpl requires Numpy, 
> there may be some advantage to using its distutils rather than the stock 
> one.  (I say having not looked into it very deeply).
>
> I've always got the impression that Python with C++ is sort of an 
> afterthought -- I don't think C++ extensions are part of the regular 
> testing procedure for distutils.
>
> Cheers,
> Mike
>
> Matthieu Brucher wrote:
>   
>> Hi,
>>
>> Matplotlib uses the distutils facilities to build the extension code. 
>> Unfortunately, it is not possible to add or remove compiler flags, 
>> distutils uses the same flags as Python when it was built. So this 
>> should probably be sent to the Python users ML.
>>
>> Matthieu
>>
>> 2007/7/23, Xavier Gnata <gn...@ob... 
>> <mailto:gn...@ob...>>:
>>
>>     Hi,
>>
>>     It would be great to be able to compile matplotlib without a
>>     warning :)
>>     Unfortunately, I was not able to fix this warning performing a simple
>>     grep into the sources:
>>     "cc1plus: warning: command line option "-Wstrict-prototypes" is valid
>>     for Ada/C/ObjC but not for C++"
>>     It looks like this option is automagically added by the build
>>     script in
>>     a way I fail to understand reading quickly the sources.
>>     Anyway, there should be a simple solution to avoid this warning (gcc
>>     version 4.1.3)...
>>     Any comments?
>>
>>     Xavier
>>
>>     --
>>     ############################################
>>     Xavier Gnata
>>     CRAL - Observatoire de Lyon
>>     9, avenue Charles André
>>     69561 Saint Genis Laval cedex
>>     Phone: +33 4 78 86 85 28
>>     Fax: +33 4 78 86 83 86
>>     E-mail: gn...@ob... <mailto:gn...@ob...>
>>     ############################################
>>
>>
>>     -------------------------------------------------------------------------
>>
>>     This SF.net email is sponsored by: Splunk Inc.
>>     Still grepping through log files to find problems?  Stop.
>>     Now Search log events and configuration files using AJAX and a
>>     browser.
>>     Download your FREE copy of Splunk now >>   http://get.splunk.com/
>>     _______________________________________________
>>     Matplotlib-users mailing list
>>     Mat...@li...
>>     <mailto:Mat...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>   
>>     
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>   


-- 
############################################
Xavier Gnata
CRAL - Observatoire de Lyon
9, avenue Charles André
69561 Saint Genis Laval cedex
Phone: +33 4 78 86 85 28
Fax: +33 4 78 86 83 86
E-mail: gn...@ob...
############################################ 

Yes, Python is written in C, but it is responsible for providing the good
flags so that extensions are compatible with the interpreter (there is an
option is Python steup for the C++ compiler for instance).
The exemple you give is valid for GCC, but is not for other compilers that
will crash with this kind of options. In fact, it would be far better if
Python provided out of the box a correct set of flags for g++ (and for the
other C++ compilers). I have to say that with ICC, there are far more
warning than for gcc.

Matthieu

2007/7/23, Xavier Gnata <gn...@ob...>:
>
> http://deluge-torrent.org/svn/tags/deluge-0.5.0/setup.py seems to
> provide us with a clean?? way to do that.
>
> > Hi,
> >
> > Well the point is that matplotlib in writtenin C++ and python is writte=
n
> > in C.
> > The valid gcc options are not the same in C and in C++ so it looks
> > strange (and it is a pity) if distutils do not provide the user with a
> > way to modify these flag in this case.
> > XAvier
> >
> >
> >> Hi,
> >>
> >> Matplotlib uses the distutils facilities to build the extension code.
> >> Unfortunately, it is not possible to add or remove compiler flags,
> >> distutils uses the same flags as Python when it was built. So this
> >> should probably be sent to the Python users ML.
> >>
> >> Matthieu
> >>
> >> 2007/7/23, Xavier Gnata <gn...@ob...
> >> <mailto:gn...@ob...>>:
> >>
> >>     Hi,
> >>
> >>     It would be great to be able to compile matplotlib without a
> >>     warning :)
> >>     Unfortunately, I was not able to fix this warning performing a
> simple
> >>     grep into the sources:
> >>     "cc1plus: warning: command line option "-Wstrict-prototypes" is
> valid
> >>     for Ada/C/ObjC but not for C++"
> >>     It looks like this option is automagically added by the build
> >>     script in
> >>     a way I fail to understand reading quickly the sources.
> >>     Anyway, there should be a simple solution to avoid this warning
> (gcc
> >>     version 4.1.3)...
> >>     Any comments?
> >>
> >>     Xavier
> >>
> >>     --
> >>     ############################################
> >>     Xavier Gnata
> >>     CRAL - Observatoire de Lyon
> >>     9, avenue Charles Andr=E9
> >>     69561 Saint Genis Laval cedex
> >>     Phone: +33 4 78 86 85 28
> >>     Fax: +33 4 78 86 83 86
> >>     E-mail: gn...@ob... <mailto:gn...@ob...>
> >>     ############################################
> >>
> >>
> >>
> -------------------------------------------------------------------------
> >>
> >>     This SF.net email is sponsored by: Splunk Inc.
> >>     Still grepping through log files to find problems?  Stop.
> >>     Now Search log events and configuration files using AJAX and a
> >>     browser.
> >>     Download your FREE copy of Splunk now >>   http://get.splunk.com/
> >>     _______________________________________________
> >>     Matplotlib-users mailing list
> >>     Mat...@li...
> >>     <mailto:Mat...@li...>
> >>     https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >>
> >>
> >>
> ------------------------------------------------------------------------
> >>
> >>
> -------------------------------------------------------------------------
> >> This SF.net email is sponsored by: Splunk Inc.
> >> Still grepping through log files to find problems?  Stop.
> >> Now Search log events and configuration files using AJAX and a browser=
.
> >> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> >>
> ------------------------------------------------------------------------
> >>
> >> _______________________________________________
> >> Matplotlib-users mailing list
> >> Mat...@li...
> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >>
> >>
> >
> >
> >
>
>
> --
> ############################################
> Xavier Gnata
> CRAL - Observatoire de Lyon
> 9, avenue Charles Andr=E9
> 69561 Saint Genis Laval cedex
> Phone: +33 4 78 86 85 28
> Fax: +33 4 78 86 83 86
> E-mail: gn...@ob...
> ############################################
>
>

This is a long standing Python (distutils) bug, IMHO.

Numpy, for instance, ships with a heavily patched version of distutils 
that has a workaround for this.  Maybe now that mpl requires Numpy, 
there may be some advantage to using its distutils rather than the stock 
one.  (I say having not looked into it very deeply).

I've always got the impression that Python with C++ is sort of an 
afterthought -- I don't think C++ extensions are part of the regular 
testing procedure for distutils.

Cheers,
Mike

Matthieu Brucher wrote:
> Hi,
>
> Matplotlib uses the distutils facilities to build the extension code. 
> Unfortunately, it is not possible to add or remove compiler flags, 
> distutils uses the same flags as Python when it was built. So this 
> should probably be sent to the Python users ML.
>
> Matthieu
>
> 2007/7/23, Xavier Gnata <gn...@ob... 
> <mailto:gn...@ob...>>:
>
>     Hi,
>
>     It would be great to be able to compile matplotlib without a
>     warning :)
>     Unfortunately, I was not able to fix this warning performing a simple
>     grep into the sources:
>     "cc1plus: warning: command line option "-Wstrict-prototypes" is valid
>     for Ada/C/ObjC but not for C++"
>     It looks like this option is automagically added by the build
>     script in
>     a way I fail to understand reading quickly the sources.
>     Anyway, there should be a simple solution to avoid this warning (gcc
>     version 4.1.3)...
>     Any comments?
>
>     Xavier
>
>     --
>     ############################################
>     Xavier Gnata
>     CRAL - Observatoire de Lyon
>     9, avenue Charles André
>     69561 Saint Genis Laval cedex
>     Phone: +33 4 78 86 85 28
>     Fax: +33 4 78 86 83 86
>     E-mail: gn...@ob... <mailto:gn...@ob...>
>     ############################################
>
>
>     -------------------------------------------------------------------------
>
>     This SF.net email is sponsored by: Splunk Inc.
>     Still grepping through log files to find problems?  Stop.
>     Now Search log events and configuration files using AJAX and a
>     browser.
>     Download your FREE copy of Splunk now >>   http://get.splunk.com/
>     _______________________________________________
>     Matplotlib-users mailing list
>     Mat...@li...
>     <mailto:Mat...@li...>
>     https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>   

http://deluge-torrent.org/svn/tags/deluge-0.5.0/setup.py seems to 
provide us with a clean?? way to do that.

> Hi,
>
> Well the point is that matplotlib in writtenin C++ and python is written 
> in C.
> The valid gcc options are not the same in C and in C++ so it looks 
> strange (and it is a pity) if distutils do not provide the user with a 
> way to modify these flag in this case.
> XAvier
>
>   
>> Hi,
>>
>> Matplotlib uses the distutils facilities to build the extension code. 
>> Unfortunately, it is not possible to add or remove compiler flags, 
>> distutils uses the same flags as Python when it was built. So this 
>> should probably be sent to the Python users ML.
>>
>> Matthieu
>>
>> 2007/7/23, Xavier Gnata <gn...@ob... 
>> <mailto:gn...@ob...>>:
>>
>>     Hi,
>>
>>     It would be great to be able to compile matplotlib without a
>>     warning :)
>>     Unfortunately, I was not able to fix this warning performing a simple
>>     grep into the sources:
>>     "cc1plus: warning: command line option "-Wstrict-prototypes" is valid
>>     for Ada/C/ObjC but not for C++"
>>     It looks like this option is automagically added by the build
>>     script in
>>     a way I fail to understand reading quickly the sources.
>>     Anyway, there should be a simple solution to avoid this warning (gcc
>>     version 4.1.3)...
>>     Any comments?
>>
>>     Xavier
>>
>>     --
>>     ############################################
>>     Xavier Gnata
>>     CRAL - Observatoire de Lyon
>>     9, avenue Charles André
>>     69561 Saint Genis Laval cedex
>>     Phone: +33 4 78 86 85 28
>>     Fax: +33 4 78 86 83 86
>>     E-mail: gn...@ob... <mailto:gn...@ob...>
>>     ############################################
>>
>>
>>     -------------------------------------------------------------------------
>>
>>     This SF.net email is sponsored by: Splunk Inc.
>>     Still grepping through log files to find problems?  Stop.
>>     Now Search log events and configuration files using AJAX and a
>>     browser.
>>     Download your FREE copy of Splunk now >>   http://get.splunk.com/
>>     _______________________________________________
>>     Matplotlib-users mailing list
>>     Mat...@li...
>>     <mailto:Mat...@li...>
>>     https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
>> ------------------------------------------------------------------------
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Splunk Inc.
>> Still grepping through log files to find problems?  Stop.
>> Now Search log events and configuration files using AJAX and a browser.
>> Download your FREE copy of Splunk now >>  http://get.splunk.com/
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>   
>>     
>
>
>   


-- 
############################################
Xavier Gnata
CRAL - Observatoire de Lyon
9, avenue Charles André
69561 Saint Genis Laval cedex
Phone: +33 4 78 86 85 28
Fax: +33 4 78 86 83 86
E-mail: gn...@ob...
############################################ 

Hi,

Well the point is that matplotlib in writtenin C++ and python is written 
in C.
The valid gcc options are not the same in C and in C++ so it looks 
strange (and it is a pity) if distutils do not provide the user with a 
way to modify these flag in this case.
XAvier

> Hi,
>
> Matplotlib uses the distutils facilities to build the extension code. 
> Unfortunately, it is not possible to add or remove compiler flags, 
> distutils uses the same flags as Python when it was built. So this 
> should probably be sent to the Python users ML.
>
> Matthieu
>
> 2007/7/23, Xavier Gnata <gn...@ob... 
> <mailto:gn...@ob...>>:
>
>     Hi,
>
>     It would be great to be able to compile matplotlib without a
>     warning :)
>     Unfortunately, I was not able to fix this warning performing a simple
>     grep into the sources:
>     "cc1plus: warning: command line option "-Wstrict-prototypes" is valid
>     for Ada/C/ObjC but not for C++"
>     It looks like this option is automagically added by the build
>     script in
>     a way I fail to understand reading quickly the sources.
>     Anyway, there should be a simple solution to avoid this warning (gcc
>     version 4.1.3)...
>     Any comments?
>
>     Xavier
>
>     --
>     ############################################
>     Xavier Gnata
>     CRAL - Observatoire de Lyon
>     9, avenue Charles André
>     69561 Saint Genis Laval cedex
>     Phone: +33 4 78 86 85 28
>     Fax: +33 4 78 86 83 86
>     E-mail: gn...@ob... <mailto:gn...@ob...>
>     ############################################
>
>
>     -------------------------------------------------------------------------
>
>     This SF.net email is sponsored by: Splunk Inc.
>     Still grepping through log files to find problems?  Stop.
>     Now Search log events and configuration files using AJAX and a
>     browser.
>     Download your FREE copy of Splunk now >>   http://get.splunk.com/
>     _______________________________________________
>     Matplotlib-users mailing list
>     Mat...@li...
>     <mailto:Mat...@li...>
>     https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>   


-- 
############################################
Xavier Gnata
CRAL - Observatoire de Lyon
9, avenue Charles André
69561 Saint Genis Laval cedex
Phone: +33 4 78 86 85 28
Fax: +33 4 78 86 83 86
E-mail: gn...@ob...
############################################ 

Hi,

Matplotlib uses the distutils facilities to build the extension code.
Unfortunately, it is not possible to add or remove compiler flags, distutil=
s
uses the same flags as Python when it was built. So this should probably be
sent to the Python users ML.

Matthieu

2007/7/23, Xavier Gnata <gn...@ob...>:
>
> Hi,
>
> It would be great to be able to compile matplotlib without a warning :)
> Unfortunately, I was not able to fix this warning performing a simple
> grep into the sources:
> "cc1plus: warning: command line option "-Wstrict-prototypes" is valid
> for Ada/C/ObjC but not for C++"
> It looks like this option is automagically added by the build script in
> a way I fail to understand reading quickly the sources.
> Anyway, there should be a simple solution to avoid this warning (gcc
> version 4.1.3)...
> Any comments?
>
> Xavier
>
> --
> ############################################
> Xavier Gnata
> CRAL - Observatoire de Lyon
> 9, avenue Charles Andr=E9
> 69561 Saint Genis Laval cedex
> Phone: +33 4 78 86 85 28
> Fax: +33 4 78 86 83 86
> E-mail: gn...@ob...
> ############################################
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi,

It would be great to be able to compile matplotlib without a warning :)
Unfortunately, I was not able to fix this warning performing a simple 
grep into the sources:
"cc1plus: warning: command line option "-Wstrict-prototypes" is valid 
for Ada/C/ObjC but not for C++"
It looks like this option is automagically added by the build script in 
a way I fail to understand reading quickly the sources.
Anyway, there should be a simple solution to avoid this warning (gcc 
version 4.1.3)...
Any comments?

Xavier

-- 
############################################
Xavier Gnata
CRAL - Observatoire de Lyon
9, avenue Charles André
69561 Saint Genis Laval cedex
Phone: +33 4 78 86 85 28
Fax: +33 4 78 86 83 86
E-mail: gn...@ob...
############################################ 

Hi All,

Been reading this mail-list for a long time, I came to a conclusion,
that principal structure of the program is not well thought.

Look at the ton of mails where is asking how to change one or another parameter
in the given Plot. People just don't remember all functions or variables which
provide needed functionality.

It means that Matplotlib is cumbersome and not easy to overview.

>From other point of view most people use often the same plot format
they've chosen
some times ago. So they don't need to change the elements format for every Plot.

Looking at matplotlibrc file we'll see, that it has to much parameters
defined by default.
Either you keep they as is, or you'll have to change most of them to produce
Plot you want. The problem hidden here is non compatibility. You can't
send script to
another machine and produce the same plot.

Having the same matplotlibrc file for all is not possible. Cause
everyone has his own view
how it should look like.

That means, to make the script compatible you have to change all
parameters you want
within the script. It's only one working solution for now.

But, it looks ugly and makes code way too long it could be.

What is the solution of all this issues?

First, we have to understand that every Plot could be described with a
markup language,
cause it's nothing else as a vector graph.
And building of such a plot is differ from the solution of
mathematical equation.
In the last case only the result is important, but for the plot even
the part of them is the vector graph.
And every part of it could be rendered separately. Almost separately...

Understanding of this can push the development of matplotlib further.
We don't need matplotlibrc anymore, but just a template file for every plot.
It could be the base template file, where main parameters described and also
custom template where maybe some partial parameters defined, like
Legend, size of the plot, scale etc.
The matplotlib in that case should produce the plot from known
parameters leaving not known
parameters not visible. Just imaging the Plot without any graphic curve on it.
It could be processed without knowing how the curve looks like.
Rendering it and saving
into the svg file or meta svg file for example you may drastically
improve the time needed for the
rendering the finished plot with certain curve on it. Taking some
coordinates from the template
you need to calculate only the curve from the given data table.
And moreover user don't have to care about format of many elements
like  text size distance between elements, alignment etc...

Generating the similar plot can be improved. But even the keeping of
the same style
of different plot for a publication is easy possible.

>From the developing point of view using tons of function to adjust one
or another parameters from a million is not really a nice solution.
Even the object paradigm doesn't help here.

Actually what we have to do is just _to describe_ how our plot should look like.
So why to program anything if it's easier to describe?

For that such languages like json or yaml could be utilized. And the
matplotlib have to
parse the code and generate kind of template where you can put your data.

Then one can really produce 3 lines code to plot his data in any way he wants.

It will also help to integrate the matplotlib with any software which
produces vector drawings.



Please, answer what do you think about it.
Thanks for comments.

Alex

In the legend command, the location keyword accepts a tuple giving x, y in
axes coords, so I guess it will also work similarly with the figlegend
command (which I assume you are using). Also you could try using legend
(instead of figlegend) with coords out of the [0,1] range. See:

http://matplotlib.sourceforge.net/matplotlib.pylab.html#-figlegend
and
http://matplotlib.sourceforge.net/matplotlib.pylab.html#-legend

Armando.

On 7/21/07, Anthony <bag...@gm...> wrote:
>
> So I've figured out how to move the graph data out from underneath my
> legend using draw() methods and calculating where the axis should be
> but now I'd also like the top of the legend to be at the same height
> as the top of the axis.  How do I go about moving the legend once I've
> created it?
>
> This is a legend that is created on the figure, obviously. :)
>
> Thanks,
>
> Anthony
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Sorry to bother -- The answer to my question was at:
http://www.scipy.org/Cookbook/Matplotlib/Using_MatPlotLib_in_a_CGI_script
John

--- JJ <jos...@ya...> wrote:

> Hello all:
> I am developing a website, initially on my local
> machine using the apache httpd server.  My linux box
> has scipy/numpy/pylab installed, and they work fine
> from a terminal.  However, I need to use the
> programs
> in a cgi script and am having problems getting them
> to
> import.  When I try to import pylab I get the
> following error:
> 
> File
>
"/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
> line 64, in _init  _gtk.init_check()
> RuntimeError: could not open display
> 
> Im sure this is easy to fix, but how would I go
> about
> doing it?  I want to save jpg files from computed
> data
> and then serve them up to a web page.
> 
> Thanks, John
> 
> 
>        
>
____________________________________________________________________________________
> Need a vacation? Get great deals
> to amazing places on Yahoo! Travel.
> http://travel.yahoo.com/
> 



       
____________________________________________________________________________________
Moody friends. Drama queens. Your life? Nope! - their life, your story. Play Sims Stories at Yahoo! Games.
http://sims.yahoo.com/  

On 7/22/07, JJ <jos...@ya...> wrote:
> Hello all:
> I am developing a website, initially on my local
> machine using the apache httpd server.  My linux box
> has scipy/numpy/pylab installed, and they work fine
> from a terminal.  However, I need to use the programs
> in a cgi script and am having problems getting them to
> import.  When I try to import pylab I get the
> following error:

> File
> "/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
> line 64, in _init  _gtk.init_check()
> RuntimeError: could not open display

You need to set your graphics "backend" to a pure image backend.  Eg,
at the start of your script, before importing pylab, do

import matplotlib
matplotlib.use('Agg')

pylab may not be your best choice for a web app server, you may want
to consider using the matplotlib API directly because it gives you a
bit more control

http://matplotlib.sourceforge.net/faq.html#OO


>
> Im sure this is easy to fix, but how would I go about
> doing it?  I want to save jpg files from computed data
> and then serve them up to a web page.

JPG is usually not a good choice for line graphs and text, PNG is
better for this, and agg will make these.  If you need JPG, you can
either convert the agg output, or use a different backend, eg I
suspect cairo supports JPG output.

JDH

Hello all:
I am developing a website, initially on my local
machine using the apache httpd server.  My linux box
has scipy/numpy/pylab installed, and they work fine
from a terminal.  However, I need to use the programs
in a cgi script and am having problems getting them to
import.  When I try to import pylab I get the
following error:

File
"/usr/lib64/python2.4/site-packages/gtk-2.0/gtk/__init__.py",
line 64, in _init  _gtk.init_check()
RuntimeError: could not open display

Im sure this is easy to fix, but how would I go about
doing it?  I want to save jpg files from computed data
and then serve them up to a web page.

Thanks, John


       
____________________________________________________________________________________
Need a vacation? Get great deals
to amazing places on Yahoo! Travel.
http://travel.yahoo.com/

So I've figured out how to move the graph data out from underneath my
legend using draw() methods and calculating where the axis should be
but now I'd also like the top of the legend to be at the same height
as the top of the axis.  How do I go about moving the legend once I've
created it?

This is a legend that is created on the figure, obviously. :)

Thanks,

Anthony

The automatic docstring generation for this command is badly fouled up, 
and I can't straighten it out right now.  In the meantime, look at the 
docstring for FancyArrow.__init__ in patches.py.  There is also a 
horrendously complicated example in examples/arrow_demo.py.

Depending on what you want to do, you might find the annotate command to 
be what you want.  I think its docstring is in better shape, as its 
example: examples/annotate_demo.py.

Eric

Jessica Lu wrote:
> I usually use the following to make single arrows:
> 
> plot([0,1], 'k.')
> arr1 = pylab.Arrow(0.5, 0.5, 0.1, 0.0, width=0.02)
> fig = pylab.gca()
> fig.add_patch(arr1)
> 
> 
> If in "ipython -pylab" you need to savefig or send another command (e.g. 
> xlabel) or reload/refresh the plot (I can't remember the command) for 
> the new patch to display. I use this rather than arrow() because I can 
> control the arrow width and other properties. There is also the quiver 
> command which lets you draw many arrows:
> 
> quiver([[0, 1, 2]], [[0, 1, 2]], [[0.0, 0.0, 0.0]], [[0.1, 0.1, 0.1]], 0.2)
> 
> Cheers,
> Jessica
> 
> On Jul 20, 2007, at 6:32 AM, Alexander Dietz wrote:
> 
>> Hi,
>>
>> How is the syntax for the matplotlib command 'arrow'? There is not 
>> very much to take from the help (see below). An example would be nice.
>>
>> Thanks
>>   Alex
>>  
>> In [46]: arrow?
>> Type:           function
>> Base Class:     <type 'function'>
>> String Form:    <function arrow at 0xb77f8a3c>
>> Namespace:      Interactive
>> File:           /usr/lib/python2.4/site-packages/matplotlib/pylab.py
>> Definition:     arrow(*args, **kwargs)
>> Docstring:
>>     Draws arrow on specified axis from (x,y) to (x+dx,y+dy).
>>     Optional kwargs control the arrow properties:
>>             alpha: float
>>             animated: [True | False]
>>             antialiased or aa: [True | False]
>>             axes: an axes instance
>>             clip_box: a matplotlib.transform.Bbox instance
>>             clip_on: [True | False]
>>             clip_path: an agg.path_storage instance
>>             edgecolor or ec: any matplotlib color
>>             facecolor or fc: any matplotlib color
>>             figure: a matplotlib.figure.Figure instance
>>             fill: [True | False]
>>             hatch: unknown
>>             label: any string
>>             linewidth or lw: float
>>             lod: [True | False]
>>             picker: [None|float|boolean|callable]
>>             transform: a matplotlib.transform transformation instance
>>             visible: [True | False]
>>             zorder: any number
>>
>>     Addition kwargs: hold = [True|False] overrides default hold state
>>
>> -------------------------------------------------------------------------
>> This SF.net email is sponsored by: Microsoft
>> Defy all challenges. Microsoft(R) Visual Studio 2005.
>> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/_______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li... 
>> <mailto:Mat...@li...>
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
> ------------------------------------------------------------------------
> 
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I usually use the following to make single arrows:

plot([0,1], 'k.')
arr1 = pylab.Arrow(0.5, 0.5, 0.1, 0.0, width=0.02)
fig = pylab.gca()
fig.add_patch(arr1)


If in "ipython -pylab" you need to savefig or send another command  
(e.g. xlabel) or reload/refresh the plot (I can't remember the  
command) for the new patch to display. I use this rather than arrow()  
because I can control the arrow width and other properties. There is  
also the quiver command which lets you draw many arrows:

quiver([[0, 1, 2]], [[0, 1, 2]], [[0.0, 0.0, 0.0]], [[0.1, 0.1,  
0.1]], 0.2)

Cheers,
Jessica

On Jul 20, 2007, at 6:32 AM, Alexander Dietz wrote:

> Hi,
>
> How is the syntax for the matplotlib command 'arrow'? There is not  
> very much to take from the help (see below). An example would be nice.
>
> Thanks
>   Alex
>
> In [46]: arrow?
> Type:           function
> Base Class:     <type 'function'>
> String Form:    <function arrow at 0xb77f8a3c>
> Namespace:      Interactive
> File:           /usr/lib/python2.4/site-packages/matplotlib/pylab.py
> Definition:     arrow(*args, **kwargs)
> Docstring:
>     Draws arrow on specified axis from (x,y) to (x+dx,y+dy).
>     Optional kwargs control the arrow properties:
>             alpha: float
>             animated: [True | False]
>             antialiased or aa: [True | False]
>             axes: an axes instance
>             clip_box: a matplotlib.transform.Bbox instance
>             clip_on: [True | False]
>             clip_path: an agg.path_storage instance
>             edgecolor or ec: any matplotlib color
>             facecolor or fc: any matplotlib color
>             figure: a matplotlib.figure.Figure instance
>             fill: [True | False]
>             hatch: unknown
>             label: any string
>             linewidth or lw: float
>             lod: [True | False]
>             picker: [None|float|boolean|callable]
>             transform: a matplotlib.transform transformation instance
>             visible: [True | False]
>             zorder: any number
>
>     Addition kwargs: hold = [True|False] overrides default hold state
>
> ---------------------------------------------------------------------- 
> ---
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi,
   I wanted to plot a graph with a grid background and an x axis ranging =
from  0 -16 and a y axis ranging from 0 -16. I used the following code:

from pylab import*
xlabel('time (s)')
ylabel('voltage (mV)')
title('About as simple as it gets, folks')
grid(True)
axis([-16,16,-16,16])
show()

However, both axes were scaled in intervals of 5 automatically, ranging =
from -15 - 15. Although the axes began and end at -16 & 16 respectively, =
the number 16 or -16 is not shown. How do I resacle the axis to ensure =
16 & -16 are shown and the grid is not cut off at each axes? How do I =
control the interval size on each scale to change it from an interval =
size of 5 to lets say 2? Is it possible to control grid size?

Jonathan.