matplotlib-devel Mailing List for matplotlib

I just downloaded 0.99.1 and ran into some problems using it in Sage. 
Basically, in the tar.gz file, there was a setup.cfg file, which had the 
following:
Note that some options are already uncommented, forcing a build of 
tkagg, wxagg, and macosx backends, and forcing the default backend to be 
tkagg. This is in direct contradiction to the text just above these 
commands, which say the default is an "auto" option.
# You can uncomment any the following lines if you know you do
# not want to use the GUI toolkit. Acceptible values are:
# True: build the extension. Exits with a warning if the
# required dependencies are not available
# False: do not build the extension
# auto: build if the required dependencies are available,
# otherwise skip silently. This is the default
# behavior
#
#gtk = False
#gtkagg = False
tkagg = True
wxagg = True
macosx = True
[rc_options]
# User-configurable options
#
# Default backend, one of: Agg, Cairo, CocoaAgg, GTK, GTKAgg, GTKCairo,
# FltkAgg, MacOSX, Pdf, Ps, QtAgg, Qt4Agg, SVG, TkAgg, WX, WXAgg.
#
# The Agg, Ps, Pdf and SVG backends do not require external
# dependencies. Do not choose GTK, GTKAgg, GTKCairo, MacOSX, TkAgg or WXAgg
# if you have disabled the relevent extension modules. Agg will be used
# by default.
#
backend = TkAgg
Should I just delete the setup.cfg file? It looks like it shouldn't be 
in the release, since there is a template file there.
Thanks,
Jason

Michael Droettboom wrote:
> Jouni K. Seppänen wrote:
> 
>> I am thinking about adding pdf comparison ability to compare_images. One
>> simple way to do this would be to convert pdf files to pngs using
>> Ghostscript: if we store reference pdf files, and both the reference
>> file and the result of the test are converted using with exactly the
>> same version of gs, there should be no font-rendering or antialiasing
>> mismatches.
>>
>> Can we assume that all test computers will have some version of
>> Ghostscript installed and callable as "gs"?
>> 
>> 
> We can probably standardize the version of gs on the buildbot machines, 
> but it's been very useful up to now to have tests that can run on a 
> variety of developer machines as well. 
>
> I don't know how different the output will be from different versions of 
> gs -- maybe we should just try it and see. I have a pretty old version 
> of gs on my RHEL4 box (7.07). If you want me to send you a png of a 
> particular pdf to directly compare with yours before you even start with 
> the test infrastructure, I'm happy to do that.
> 
I understood Jouni's idea to be to save the .pdfs as baseline images --
then the same version of gs would be used to generated the rasterized
images for the baseline and test result -- the version on your computer.
I think this is the way to go (either that or compare the PDFs directly
somehow).
Anyhow, allowing the test infrastructure to support testing multiple
backends is why I removed file extensions from the test image name in
the first place, so anything along these lines should hopefully be quite
doable. We could add a keyword arg to the image comparison decorator
that specified which image formats to test. Alternatively, it could
perform comparisons based on the presence baseline images of known
extensions.
-Andrew

Jouni K. Seppänen wrote:
> I am thinking about adding pdf comparison ability to compare_images. One
> simple way to do this would be to convert pdf files to pngs using
> Ghostscript: if we store reference pdf files, and both the reference
> file and the result of the test are converted using with exactly the
> same version of gs, there should be no font-rendering or antialiasing
> mismatches.
>
> Can we assume that all test computers will have some version of
> Ghostscript installed and callable as "gs"?
> 
We can probably standardize the version of gs on the buildbot machines, 
but it's been very useful up to now to have tests that can run on a 
variety of developer machines as well. 
I don't know how different the output will be from different versions of 
gs -- maybe we should just try it and see. I have a pretty old version 
of gs on my RHEL4 box (7.07). If you want me to send you a png of a 
particular pdf to directly compare with yours before you even start with 
the test infrastructure, I'm happy to do that.
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

I am thinking about adding pdf comparison ability to compare_images. One
simple way to do this would be to convert pdf files to pngs using
Ghostscript: if we store reference pdf files, and both the reference
file and the result of the test are converted using with exactly the
same version of gs, there should be no font-rendering or antialiasing
mismatches.
Can we assume that all test computers will have some version of
Ghostscript installed and callable as "gs"?
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On second look, I think it's the "--small" commandline option that 
breaks this. I hadn't tested my recent changes to the plot directive 
with that flag. The new version of make.py in SVN r7815 should fix this.
Mike
Sandro Tosi wrote:
> Hi all,
> I'm a bit unsure if this is really a problem in the code or it's my
> machine that has problem (I didn't manage to test it in a clean
> chroot).
>
> When building the doc (after having built mpl with python setup.py
> build) I got the attached traceback.
>
> The strange fact is that 'formats' is indeed defined as a 2D list (At
> the bottom of plot_directive.py).
>
> Thanks for considering,
> 
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

It's also an overridable parameter in conf.py. Of course, it works with 
the conf.py in SVN, but do you perhaps have any local changes to it?
Mike
Sandro Tosi wrote:
> Hi all,
> I'm a bit unsure if this is really a problem in the code or it's my
> machine that has problem (I didn't manage to test it in a clean
> chroot).
>
> When building the doc (after having built mpl with python setup.py
> build) I got the attached traceback.
>
> The strange fact is that 'formats' is indeed defined as a 2D list (At
> the bottom of plot_directive.py).
>
> Thanks for considering,
> 
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> Come build with us! The BlackBerry® Developer Conference in SF, CA
> is the only developer event you need to attend this year. Jumpstart your
> developing skills, take BlackBerry mobile applications to market and stay 
> ahead of the curve. Join us from November 9-12, 2009. Register now!
> http://p.sf.net/sfu/devconf
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Thanks Fernando for the quick response.
Today this is the 3rd time I am hitting an unsupported feature in the Python
lands.
1-) No attribute docstrings
2-) Look this question:
http://stackoverflow.com/questions/1458203/reading-a-float-from-string
and 3rd is this.
However I think I influenced to guys in our campus to take a look Python.
One using Matlab-Simulink and C on collision-detection system design, the
latter uses C to design a small scale embedded acquisition system for UAV
platforms. He uses an ARM Cortex A8 processor powered Gumstix
board<http://www.gumstix.com/store/catalog/product_info.php?cPath=31&products_id=228>.
Xubuntu 9.04 runs on it. I saw Python 2.6.2 installed, however not sure how
easy would that be to bring rest of the scipy stack into that machine.
Besides, tomorrow there is going to be a Matlab seminar here
http://www.mathworks.com/company/events/seminars/seminar39323.html
It is about a SciPy advanced tutorial long.
Many similar subjects I see there:
*Speeding Up MATLAB Applications:Tips and Tricks for Writing Efficient Code
*Topics include:
• Understanding preallocation and vectorization
• Addressing bottlenecks
• Efficient indexing and manipulations
• JIT
• Interpreter
• Mex
*Brief Introduction to Parallel Computing with MATLAB
*• Task parallel applications for faster processing
• Data parallel applications for handling large data sets
• Scheduling your programs to run
I hope I will not kick out from the session by keep commenting oh that is
possible in Python, oh this is too :)
On Tue, Sep 22, 2009 at 12:18 AM, Fernando Perez <fpe...@gm...>wrote:
> 2009年9月21日 Gökhan Sever <gok...@gm...>:
> >
> > It's a very late reply but I am wondering how to make these appear in the
> Ipy dev loaded into the session but not visible to a whos listing?
> >
>
> I don't think that's supported quite right now. IPython does one
> special thing to support a clean %whos listing: right before opening
> up the user mainloop, it checks all keys in the user namespace, and
> later on when %whos is run, those variables that were initially
> present are not displayed. So for now if you do this interactively,
> you will unfortunately pollute %whos.
>
> This is one thing we'll need to make sure works nicely again when the
> dust settles.
>
> Cheers,
>
> f
>
-- 
Gökhan

Hi all,
I'm a bit unsure if this is really a problem in the code or it's my
machine that has problem (I didn't manage to test it in a clean
chroot).
When building the doc (after having built mpl with python setup.py
build) I got the attached traceback.
The strange fact is that 'formats' is indeed defined as a 2D list (At
the bottom of plot_directive.py).
Thanks for considering,
-- 
Sandro Tosi (aka morph, morpheus, matrixhasu)
My website: http://matrixhasu.altervista.org/
Me at Debian: http://wiki.debian.org/SandroTosi

2009年9月21日 Gökhan Sever <gok...@gm...>:
>
> It's a very late reply but I am wondering how to make these appear in the Ipy dev loaded into the session but not visible to a whos listing?
>
I don't think that's supported quite right now. IPython does one
special thing to support a clean %whos listing: right before opening
up the user mainloop, it checks all keys in the user namespace, and
later on when %whos is run, those variables that were initially
present are not displayed. So for now if you do this interactively,
you will unfortunately pollute %whos.
This is one thing we'll need to make sure works nicely again when the
dust settles.
Cheers,
f

On Tue, Sep 8, 2009 at 3:45 PM, Fernando Perez <fpe...@gm...> wrote:
> Hey Gokhan,
>
> thanks for the summary.
>
> On Tue, Sep 8, 2009 at 12:45 PM, Gökhan Sever <gok...@gm...>
> wrote:
> > ### In a new IPython, these lines work --no locking after plt.show() "-a"
> > makes the difference.
> >
> > I[1]: import matplotlib.pyplot as plt
> >
> > I[2]: %gui -a qt
> > O[2]: <PyQt4.QtGui.QApplication object at 0x8fdceac>
> >
> > I[3]: plt.plot(range(10))
> > O[3]: [<matplotlib.lines.Line2D object at 0x9a2c84c>]
> >
> > I[4]: plt.show()
>
> If you do
>
> plt.ion()
>
> right after you import it, then you don't need to do 'show'
> explicitely anymore. Basically what today's '-pylab' does is:
>
> - a bunch of imports
> - the equivalent of %gui, but uglier and at startup
> - do plt.ion() for you
> - patch %run a little so it does ioff() before starting up and ion() at the
> end.
>
> As you can see, even now with trunk in the state of upheaval it is,
> you can get almost all of this back with this snippet. This is pretty
> much what we'll make available built-in when the dust settles (with
> the 'import *' being optional, as they are today):
>
>
It's a very late reply but I am wondering how to make these appear in the
Ipy dev loaded into the session but not visible to a whos listing?
Thanks.
> %gui -a qt
>
> import numpy as np
> import matplotlib.pyplot as plt
> import matplotlib.pylab as pylab
> import matplotlib.mlab as mlab
>
> from numpy import *
> from matplotlib.pyplot import *
>
> plt.ion()
>
>
> ### END CODE
>
> Cheers,
>
> f
>
-- 
Gökhan