matplotlib-users Mailing List for matplotlib (Page 7)

"Jae-Joon Lee" <lee...@gm...> writes:
> So, Lebostein and j, if you know how to check out using svn, can you
> give a try either the svn trunk or the maintenance branch? I'm
> attaching the patch just in case.
On the svn trunk, the demo examples/api/legend_demo.py now fails at
"leg.get_texts()" with "AttributeError: 'Legend' object has no attribute
'texts'". Calling show() seems to fix the legend so that get_texts
works, so I suspect that the bug is related to the _init_legend_box call
that your patch removes.
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

On Tue, Dec 16, 2008 at 2:17 PM, Christopher Barker
<Chr...@no...> wrote:
> However, once installed, I tried to run it, and got libpng issues --
> aaarrgg!:
Could you also test the mpkg zip file -- I am curious if that shows
the same png problems for you.
JDH

On Tue, Dec 16, 2008 at 2:20 PM, Michael Oevermann
<mic...@tu...> wrote:
> That's exactly what I was looking for! But how do I get the new feature
> into my
> matplotlib version?
Either wait for the next release and use the workaround for now, or
install from svn. See
 http://matplotlib.sourceforge.net/faq/installing_faq.html#install-from-svn
Nightly builds are on the list of things to do, but we have bigger
fish to fry at the moment. What platform are you on?

On Tue, Dec 16, 2008 at 2:17 PM, Christopher Barker
<Chr...@no...> wrote:
> "/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/image.py",
> line 19, in <module>
> from matplotlib import _png
> ImportError:
> dlopen(/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/_png.so,
> 2): Symbol not found: _png_destroy_read_struct
> Referenced from:
Well, at least we have a *different* bug to focus on. I'll try and
reproduce this somewhere.... I wonder if this is backend dependent
(eg you are using a backend that also links png and something is
getting confused). Could you try running ::
 import matplotlib.pyplot as plt
 plt.plot([1,2,3])
 plt.show()
with
 > python myfile.py -dAgg
 > python myfile.py -dTkAgg
 > python myfile.py -dWXAgg
 > python myfile.py -dPS
and let me know what you find.
JDH
HDG

On Tue, Dec 16, 2008 at 2:13 PM, Michael Hearne <mh...@us...> wrote:
> John - I get the same error at the end. I've been able to build the package
> from the tarball successfully. Output follows:
No, this is not the same. In the original post you had
 error: lib/matplotlib/mpl-data/matplotlib.conf.template
which was breaking the install (I think). This is the bug I fixed.
The CleanUpFile exceptions are annoying but mostly harmless, and I
have a post to distutils.sig about them.
Let me know if you have information otherwise.
JDH

That's exactly what I was looking for! But how do I get the new feature 
into my
matplotlib version?
Michael
John Hunter schrieb:
> On Tue, Dec 16, 2008 at 10:30 AM, John Hunter <jd...@gm...> wrote:
>
> 
>>> using in favour of matplotlib). Plotting the data twice- the first time
>>> without
>>> symbol showing every data point and the second time onlywith the symbol
>>> and some skip in the data - doesn't help as I now get two entities in
>>> the legend.
>>> 
>> There is a way to do this, but it is not terribly elegant. The tricky
>> part is to get the legend right::
>> 
>
> I just added a new line property called "markevery" to support
> subsampling markers. Included below is the docstring and nosetest
> which should clearly indicate usage:
>
> def set_markevery(self, every):
> """
> Set the markevery property to subsample the plot when using
> markers. Eg if ``markevery=5``, every 5-th marker will be
> plotted. *every* can be
>
> None
> Every point will be plotted
>
> an integer N
> Every N-th marker will be plotted starting with marker 0
>
> A length-2 tuple of integers
> every=(start, N) will start at point start and plot every
> N-th marker
>
>
> ACCEPTS: None | integer | (startind, stride)
>
> """
>
>
> def test_markevery():
> x, y = np.random.rand(2, 100)
>
> # check marker only plot
> fig = plt.figure()
> ax = fig.add_subplot(111)
> ax.plot(x, y, 'o')
> ax.plot(x, y, 'd', markevery=None)
> ax.plot(x, y, 's', markevery=10)
> ax.plot(x, y, '+', markevery=(5, 20))
> fig.canvas.draw()
> plt.close(fig)
>
> # check line/marker combos
> fig = plt.figure()
> ax = fig.add_subplot(111)
> ax.plot(x, y, '-o')
> ax.plot(x, y, '-d', markevery=None)
> ax.plot(x, y, '-s', markevery=10)
> ax.plot(x, y, '-+', markevery=(5, 20))
> fig.canvas.draw()
> plt.close(fig)
>
> 

John Hunter wrote:
> I've posted new eggs and a binary mpkg installer for OS X and a new
> tarball. I've tried your egg renaming trick. Let me know how it
> goes.
well, when I tried:
easy_install matplotlib-0.98.5.1-py2.5-macosx.egg
it again did the sillyness of installing it, then going and downloading 
the source.
However, I took the "macosx" off the name, and it worked fine:
easy_install matplotlib-0.98.5.1-py2.5.egg
But then it's a bit hard for users to know that it's an OS-X egg! Maybe 
it could be put on the download site as:
easy_install matplotlib-0.98.5.1-py2.5-macosx.egg.zip
and unpack it to one with the shorter name. (even though *.egg files are 
already zipped!
Perhaps we need to figure out what the heck is wrong with easy_install 
instead! (Not I want to dig into that code!)
However, once installed, I tried to run it, and got libpng issues -- 
aaarrgg!:
 >>> import matplotlib
 >>> matplotlib.__version__
'0.98.5.1'
 >>> import pylab
Traceback (most recent call last):
 File "<stdin>", line 1, in <module>
 File 
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/pylab.py", 
line 1, in <module>
 from matplotlib.pylab import *
 File 
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/pylab.py", 
line 206, in <module>
 from matplotlib import mpl # pulls in most modules
 File 
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/mpl.py", 
line 3, in <module>
 from matplotlib import axes
 File 
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/axes.py", 
line 18, in <module>
 import matplotlib.image as mimage
 File 
"/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/image.py", 
line 19, in <module>
 from matplotlib import _png
ImportError: 
dlopen(/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/_png.so, 
2): Symbol not found: _png_destroy_read_struct
 Referenced from: 
/Library/Frameworks/Python.framework/Versions/2.5/lib/python2.5/site-packages/matplotlib-0.98.5.1-py2.5.egg/matplotlib/_png.so
 Expected in: dynamic lookup
I'm running python 2.5.2 universal framework build, on a PPC running 
OS-X 10.4
Here is the otool ouput on _png.so:
otool -L _png.so
_png.so:
 /usr/lib/libz.1.dylib (compatibility version 1.0.0, current 
version 1.2.3)
 /usr/lib/libstdc++.6.dylib (compatibility version 7.0.0, 
current version 7.4.0)
 /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, 
current version 88.3.10)
 /usr/local/lib/libgcc_s.1.dylib (compatibility version 1.0.0, 
current version 1.0.0)
 /usr/lib/libmx.A.dylib (compatibility version 1.0.0, current 
version 47.1.0)
so it's not linked to the dynamic libpng -- hmmm.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

John - I get the same error at the end. I've been able to build the 
package from the tarball successfully. Output follows:
sudo easy_install matplotlib-0.98.5.1-py2.5-macosx.egg
Processing matplotlib-0.98.5.1-py2.5-macosx.egg
removing 
'/Library/Python/2.5/site-packages/matplotlib-0.98.5.1-py2.5-macosx.egg' 
(and everything under it)
creating 
/Library/Python/2.5/site-packages/matplotlib-0.98.5.1-py2.5-macosx.egg
Extracting matplotlib-0.98.5.1-py2.5-macosx.egg to 
/Library/Python/2.5/site-packages
matplotlib 0.98.5.1 is already the active version in easy-install.pth
Installed 
/Library/Python/2.5/site-packages/matplotlib-0.98.5.1-py2.5-macosx.egg
Processing dependencies for matplotlib==0.98.5.1
Searching for matplotlib==0.98.5.1
Reading http://pypi.python.org/simple/matplotlib/
Reading http://matplotlib.sourceforge.net
Reading http://sourceforge.net/project/showfiles.php?group_id=80706
Reading 
https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=278194
Reading 
https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=82474
Best match: matplotlib 0.98.5.1
Downloading 
http://downloads.sourceforge.net/matplotlib/matplotlib-0.98.5.1.tar.gz?modtime=1229456199&big_mirror=0
Processing matplotlib-0.98.5.1.tar.gz
Running matplotlib-0.98.5.1/setup.py -q bdist_egg --dist-dir 
/var/folders/GK/GKdPFArAGq0lmR1STz+kR++++TQ/-Tmp-/easy_install-RxTUy6/matplotlib-0.98.5.1/egg-dist-tmp-9hZznV
============================================================================
BUILDING MATPLOTLIB
matplotlib: 0.98.5.1
python: 2.5.1 (r251:54863, Jan 17 2008, 19:35:17) [GCC
4.0.1 (Apple Inc. build 5465)]
platform: darwin
REQUIRED DEPENDENCIES
numpy: 1.1.0.dev5077
freetype2: 9.17.3
OPTIONAL BACKEND DEPENDENCIES
libpng: 1.2.18
Tkinter: Tkinter: 50704, Tk: 8.4, Tcl: 8.4
wxPython: 2.8.4.0
* WxAgg extension not required for wxPython >= 2.8
Gtk+: no
* Building for Gtk+ requires pygtk; you must be able
* to "import gtk" in your build/install environment
Mac OS X native: yes
Qt: no
Qt4: no
Cairo: no
OPTIONAL DATE/TIMEZONE DEPENDENCIES
datetime: present, version unknown
dateutil: 1.4.1
pytz: 2008i
OPTIONAL USETEX DEPENDENCIES
dvipng: no
ghostscript: 8.61
latex: no
EXPERIMENTAL CONFIG PACKAGE DEPENDENCIES
configobj: matplotlib will provide
enthought.traits: 2.6b1-mpl
[Edit setup.cfg to suppress the above messages]
============================================================================
pymods ['pylab', 'configobj']
packages ['matplotlib', 'matplotlib.backends', 'matplotlib.projections', 
'mpl_toolkits', 'matplotlib.numerix', 'matplotlib.numerix.mlab', 
'matplotlib.numerix.ma', 'matplotlib.numerix.npyma', 
'matplotlib.numerix.linear_algebra', 'matplotlib.numerix.random_array', 
'matplotlib.numerix.fft', 'matplotlib.delaunay', 'matplotlib.config']
warning: no files found matching 'MANIFEST'
warning: no files found matching 'lib/mpl_toolkits'
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
In file included from /usr/X11/include/freetype2/freetype/freetype.h:41,
from src/ft2font.h:14,
from src/ft2font.cpp:1:
/usr/X11/include/freetype2/freetype/config/ftconfig.h:65:1: warning: 
"SIZEOF_LONG" redefined
In file included from 
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Python.h:8,
from ./CXX/WrapPython.h:42,
from ./CXX/Extensions.hxx:48,
from src/ft2font.h:4,
from src/ft2font.cpp:1:
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyconfig.h:814:1: 
warning: this is the location of the previous definition
In file included from /usr/X11/include/freetype2/freetype/freetype.h:41,
from src/ft2font.h:14,
from src/ft2font.cpp:1:
/usr/X11/include/freetype2/freetype/config/ftconfig.h:65:1: warning: 
"SIZEOF_LONG" redefined
In file included from 
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Python.h:8,
from ./CXX/WrapPython.h:42,
from ./CXX/Extensions.hxx:48,
from src/ft2font.h:4,
from src/ft2font.cpp:1:
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyconfig.h:814:1: 
warning: this is the location of the previous definition
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
/Library/Python/2.5/site-packages/numpy-1.1.0.dev5077-py2.5-macosx-10.3-i386.egg/numpy/core/include/numpy/__multiarray_api.h:948: 
warning: ‘int _import_array()’ defined but not used
/Library/Python/2.5/site-packages/numpy-1.1.0.dev5077-py2.5-macosx-10.3-i386.egg/numpy/core/include/numpy/__multiarray_api.h:948: 
warning: ‘int _import_array()’ defined but not used
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
In file included from /usr/X11/include/freetype2/freetype/freetype.h:41,
from src/ft2font.h:14,
from src/backend_agg.cpp:10:
/usr/X11/include/freetype2/freetype/config/ftconfig.h:65:1: warning: 
"SIZEOF_LONG" redefined
In file included from 
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Python.h:8,
from ./CXX/WrapPython.h:42,
from ./CXX/Extensions.hxx:48,
from src/ft2font.h:4,
from src/backend_agg.cpp:10:
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyconfig.h:814:1: 
warning: this is the location of the previous definition
In file included from /usr/X11/include/freetype2/freetype/freetype.h:41,
from src/ft2font.h:14,
from src/backend_agg.cpp:10:
/usr/X11/include/freetype2/freetype/config/ftconfig.h:65:1: warning: 
"SIZEOF_LONG" redefined
In file included from 
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/Python.h:8,
from ./CXX/WrapPython.h:42,
from ./CXX/Extensions.hxx:48,
from src/ft2font.h:4,
from src/backend_agg.cpp:10:
/System/Library/Frameworks/Python.framework/Versions/2.5/include/python2.5/pyconfig.h:814:1: 
warning: this is the location of the previous definition
ld: warning in /sw/lib/freetype219/lib/libfreetype.dylib, file is not of 
required architecture
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
ld: warning in /sw/lib/libpng12.dylib, file is not of required architecture
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
cc1plus: warning: command line option "-Wstrict-prototypes" is valid for 
C/ObjC but not for C++
powerpc-apple-darwin9-gcc-4.0.1: -framework: linker input file unused 
because linking not done
powerpc-apple-darwin9-gcc-4.0.1: Tcl: linker input file unused because 
linking not done
powerpc-apple-darwin9-gcc-4.0.1: -framework: linker input file unused 
because linking not done
powerpc-apple-darwin9-gcc-4.0.1: Tk: linker input file unused because 
linking not done
i686-apple-darwin9-gcc-4.0.1: -framework: linker input file unused 
because linking not done
i686-apple-darwin9-gcc-4.0.1: Tcl: linker input file unused because 
linking not done
i686-apple-darwin9-gcc-4.0.1: -framework: linker input file unused 
because linking not done
i686-apple-darwin9-gcc-4.0.1: Tk: linker input file unused because 
linking not done
ld: warning in /sw/lib/freetype219/lib/libfreetype.dylib, file is not of 
required architecture
zip_safe flag not set; analyzing archive contents...
matplotlib.__init__: module references __file__
matplotlib.pyparsing: module MAY be using inspect.stack
matplotlib.backends.backend_cocoaagg: module references __file__
matplotlib.config.cutils: module references __file__
Removing matplotlib 0.98.5.1 from easy-install.pth file
Adding matplotlib 0.98.5.1 to easy-install.pth file
Installed 
/Library/Python/2.5/site-packages/matplotlib-0.98.5.1-py2.5-macosx-10.5-i386.egg
Finished processing dependencies for matplotlib==0.98.5.1
Exception exceptions.OSError: (2, 'No such file or directory', 
'src/image.cpp') in <bound method CleanUpFile.__del__ of 
<setupext.CleanUpFile instance at 0x14c5aa8>> ignored
Exception exceptions.OSError: (2, 'No such file or directory', 
'src/path.cpp') in <bound method CleanUpFile.__del__ of 
<setupext.CleanUpFile instance at 0x14c5300>> ignored
Exception exceptions.OSError: (2, 'No such file or directory', 
'src/backend_agg.cpp') in <bound method CleanUpFile.__del__ of 
<setupext.CleanUpFile instance at 0x14c55f8>> ignored
John Hunter wrote:
> On Mon, Dec 15, 2008 at 7:08 PM, Michael Hearne <mh...@us...> wrote:
> 
>> I get the following output when trying to install the latest version of
>> matplotlib from an egg. I'm running Mac OS X 10.5.5.
>> 
>
> We've had a lot of trouble with our eggs. I am not sure this is all
> our fault, because it looks like some combination of distutils and
> setuptools is breaking in the presence of symlinks, which we use. I'm
> modified our installs to work around this problem, and have posted new
> eggs at
>
> https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=278194&release_id=646644
>
> You have two choices for OS X :
>
> * matplotlib-0.98.5.1-py2.5-macosx10.5.zip - a binary mpkg installer
> * matplotlib-0.98.5.1-py2.5-macosx.egg - an egg with the known
> problems fixed.
>
> Please give it another whirl and let me know.
>
> JDH
> 

On Mon, Dec 15, 2008 at 7:08 PM, Michael Hearne <mh...@us...> wrote:
> I get the following output when trying to install the latest version of
> matplotlib from an egg. I'm running Mac OS X 10.5.5.
We've had a lot of trouble with our eggs. I am not sure this is all
our fault, because it looks like some combination of distutils and
setuptools is breaking in the presence of symlinks, which we use. I'm
modified our installs to work around this problem, and have posted new
eggs at
 https://sourceforge.net/project/showfiles.php?group_id=80706&package_id=278194&release_id=646644
You have two choices for OS X :
 * matplotlib-0.98.5.1-py2.5-macosx10.5.zip - a binary mpkg installer
 * matplotlib-0.98.5.1-py2.5-macosx.egg - an egg with the known
problems fixed.
Please give it another whirl and let me know.
JDH

On Tue, Dec 16, 2008 at 12:17 PM, jkitchin <jki...@an...> wrote:
>
> I also observed this with eps output. The png looked fine, but the eps legend
> was very large in my case.
>
> j
>
Hmm, it is not clear to me if this is a same issue. I think eps output
is not very sensitive to dpi thing in matplotlib.
I tried a few tests but couldn't see any obvious problems.
If my patch does not fix your problem, please report some more details.
Regards,
-JJ

I just found my previous message was only sent to Lebostein.
Anyhow, here is my original meesage.
On Tue, Dec 16, 2008 at 10:38 AM, Jae-Joon Lee <lee...@gm...> wrote:
> Yes, I can see the differences.
> Anyway, it seems to me the differences are primarily caused by
> different dpi, not by different backend.
> I guess the image in
> http://matplotlib.sourceforge.net/examples/pylab_examples/legend_demo3.html
> is also created with png backend, and that looks okay to me.
> And I'm afraid that I didn't correctly accounted the figure dpi when I
> calculate these dimensions.
> I'll try to correct this soon.
>
> Thanks.
>
> -JJ
>
>
And, Micheal, yes, it is a dpi issue. I was using font size in
"points" as a reference while it should be in "pixels". This should be
fixed both in the maintenance branch and in the trunk.
So, Lebostein and j, if you know how to check out using svn, can you
give a try either the svn trunk or the maintenance branch? I'm
attaching the patch just in case.
Regards,
-JJ

On Tue, Dec 16, 2008 at 12:38 PM, Jörgen Stenarson
<jor...@bo...> wrote:
> Hi
>
> I get the following error when I try to build matplotlib on a windows
> machine. It builds fine if I comment out the offending line in setup.py.
>
> C:\python\external\matplotlib-trunk>python setup.py config
> --compiler=mingw32 build --compiler=mingw32 bdist
> Traceback (most recent call last):
> File "setup.py", line 13, in <module>
> del os.link
> AttributeError: link
Thanks -- I'll fix it. This is a hack to prevent distutils from
copying our symlinks, which is breaking easy_install.
JDH

Hi,
I have a problem with svn. When updating trunk today I get the following 
from line 94 in matplotlib/__init__.py:
__date__ = '$Date: 2008年12月15日 21:46:00 +0100 (må, 15 dec 2008) $'
As you can see there is a 'å' in the Date string but there is no 
encoding specified at the top of the file so I get a SyntaxError about 
unspecified encoding when I import matplotlib. It seems svn assumes utf-8.
Traceback (most recent call last):
 File "C:\Python25\Scripts\ipython.py", line 28, in <module>
 IPython.Shell.start().mainloop()
 File "c:\python\external\ipython\IPython\Shell.py", line 1243, in start
 shell = _select_shell(sys.argv)
 File "c:\python\external\ipython\IPython\Shell.py", line 1200, in 
_select_shell
 import matplotlib
 File 
"c:\python\external\matplotlib-trunk\build\lib.win32-2.5\matplotlib\__init__.py", 
line 94
SyntaxError: Non-ASCII character '\xc3' in file 
c:\python\external\matplotlib-trunk\build\lib.win32-2.5\matplotlib\__init__.py 
on line 94, but no encoding declared; see 
http://www.python.org/peps/pep-0263.html for details
Does anyone know how I can force svn and tortoise svn to not include the 
last part with the weekday? I'm not sure if svn always uses utf-8 if 
that is the case then we could just add the encoding specification and 
everything will work. I believe it would be best if this can be fixed on 
the server side otherwise this problem will come up now and again 
depending on user configurations.
/Jörgen

Hi
I get the following error when I try to build matplotlib on a windows 
machine. It builds fine if I comment out the offending line in setup.py.
C:\python\external\matplotlib-trunk>python setup.py config 
--compiler=mingw32 build --compiler=mingw32 bdist
Traceback (most recent call last):
 File "setup.py", line 13, in <module>
 del os.link
AttributeError: link
/Jörgen

AlsCdz wrote:
> Hello, i need you help!
> I want to draw a plot with circles, which are coloured according to size. So
> let's say we have a list=[1,3,5,7] that would give me four circles, first
> very small, second bigger and so on. 
> Now i need a way to "convert" integers to color value which would match
> matplotlib.cm.spectral
> values.
> 
> I hope you understand what i want to do, something like: (
> http://zoonek2.free.fr/UNIX/48_R/g208.png
> http://zoonek2.free.fr/UNIX/48_R/g208.png )
> 
> I posted only the "important" bits of code: 
> 
> 
> listData = [[2,5,1],[2,4,15],[13,2,1],[1,10,2]]
> cmap = mpl.cm.spectral
> norm = mpl.colors.Normalize(vmin=1, vmax=15)
> 
> listA = ([i for i in range(len(listData))])
> for a in range(len(listData)):
> listB = ([a for i in range(len(listData[0]))])
> area = ([listData[a][i]*100 for i in range(len(listData[a]))])
> color = ([listData[a][i]*100 for i in range(len(listData[a]))])
> plt.scatter(listA,listB,s=area, cmap=cmap, c=??what to put here???)
> 
> cb1 = mpl.colorbar.ColorbarBase(ax1, cmap=cmap, norm=norm,
> orientation='vertical')
> 
> 
> 
> I hope someone could help me!
> 
> thank you very much
> ales
radius = np.arange(10)
area = np.pi*radius**2
x = np.random.rand(10)
y = np.random.rand(10)
cmap = plt.get_cmap('spectral')
plt.scatter(x, y, s=area, c=radius, cmap=cmap)
plt.colorbar()
I think the above illustrates what you need.
Eric

Ahh, because I have labels and other text already drawn on the image.
Squishing it alters the shape of the letters. And I have potentially many
of these coming out of WMS requests where I know the image size and corner
coords, but I can't alter the basic nature of the image. What I'd like to
do is use these images as figures in a report, so I need to be able to add
Axes with labeling, and also Figure titles and text.
Thanks,
Roger
--
On Tue, Dec 16, 2008 at 9:53 AM, Jeff Whitaker <js...@fa...> wrote:
> Roger André wrote:
>
>> Hi Jeff,
>>
>> I checked, and no the images are not geographically square. I wonder if I
>> could approach this problem in a different way. Would it be possible for me
>> to add tick marks and annotation to the image without using the Basemap
>> module alone? My thinking is that I could bring the image into Matplotlib,
>> define a square figure, and then manually define the size of the X and Y
>> axes and label them. Is it possible to "decorate" an image this way,
>> without using any projection support?
>>
>> Thanks for the help,
>>
>> Roger
>>
>
> Roger: Sure, you could do that. I'm not sure why you would want to
> display an image that's not geographically square as a square though.
> What's wrong with just letting Basemap show it as a rectange?
>
> -Jeff
>
>> --
>>
>>
>> On Tue, Dec 16, 2008 at 4:43 AM, Jeff Whitaker <js...@fa...<mailto:
>> js...@fa...>> wrote:
>>
>> Roger André wrote:
>>
>> Hi All,
>>
>> I have some square images which were generated via WMS
>> requests. I have imported them into Matplotlib via
>> pil_to_array, and then display them in a Basemap instance
>> where I have defined the projection as:
>>
>> m = Basemap(projection='cyl', lon_0=lon_0, llcrnrlon=ll_lon,
>> llcrnrlat=ll_lat, urcrnrlon=ur_lon,
>> urcrnrlat=ur_lat, suppress_ticks=False)
>>
>> While this works (it appears the tics are at the right
>> places), the image is no longer square, and I wonder if my
>> projection definition is correct.
>>
>> Can someone show me what the correct Basemap parameters are
>> for working with images that are in EPSG:4326?
>>
>> Thanks,
>>
>> Roger
>>
>>
>> Roger: The image will only be square if ur_lon-ll_lon =
>> ur_lat-ll_lat (i.e. the longitude range equals the latitude
>> range). Is this the case?
>> -Jeff
>>
>> -- Jeffrey S. Whitaker Phone : (303)497-6313
>> NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
>> 325 Broadway Boulder, CO, USA 80305-3328
>>
>>
>>
>
> --
> Jeffrey S. Whitaker Phone : (303)497-6313
> Meteorologist FAX : (303)497-6449
> NOAA/OAR/PSD R/PSD1 Email : Jef...@no...
> 325 Broadway Office : Skaggs Research Cntr 1D-113
> Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg
>
>

Roger André wrote:
> Hi Jeff,
>
> I checked, and no the images are not geographically square. I wonder 
> if I could approach this problem in a different way. Would it be 
> possible for me to add tick marks and annotation to the image without 
> using the Basemap module alone? My thinking is that I could bring the 
> image into Matplotlib, define a square figure, and then manually 
> define the size of the X and Y axes and label them. Is it possible to 
> "decorate" an image this way, without using any projection support?
>
> Thanks for the help,
>
> Roger
Roger: Sure, you could do that. I'm not sure why you would want to 
display an image that's not geographically square as a square though. 
What's wrong with just letting Basemap show it as a rectange?
-Jeff
> --
>
> On Tue, Dec 16, 2008 at 4:43 AM, Jeff Whitaker <js...@fa... 
> <mailto:js...@fa...>> wrote:
>
> Roger André wrote:
>
> Hi All,
>
> I have some square images which were generated via WMS
> requests. I have imported them into Matplotlib via
> pil_to_array, and then display them in a Basemap instance
> where I have defined the projection as:
>
> m = Basemap(projection='cyl', lon_0=lon_0, llcrnrlon=ll_lon,
> llcrnrlat=ll_lat, urcrnrlon=ur_lon,
> urcrnrlat=ur_lat, suppress_ticks=False)
>
> While this works (it appears the tics are at the right
> places), the image is no longer square, and I wonder if my
> projection definition is correct.
>
> Can someone show me what the correct Basemap parameters are
> for working with images that are in EPSG:4326?
>
> Thanks,
>
> Roger
>
>
> Roger: The image will only be square if ur_lon-ll_lon =
> ur_lat-ll_lat (i.e. the longitude range equals the latitude
> range). Is this the case?
> -Jeff
>
> -- 
> Jeffrey S. Whitaker Phone : (303)497-6313
> NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
> 325 Broadway Boulder, CO, USA 80305-3328
>
>
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
Meteorologist FAX : (303)497-6449
NOAA/OAR/PSD R/PSD1 Email : Jef...@no...
325 Broadway Office : Skaggs Research Cntr 1D-113
Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg

Hi Jeff,
I checked, and no the images are not geographically square. I wonder if I
could approach this problem in a different way. Would it be possible for me
to add tick marks and annotation to the image without using the Basemap
module alone? My thinking is that I could bring the image into Matplotlib,
define a square figure, and then manually define the size of the X and Y
axes and label them. Is it possible to "decorate" an image this way,
without using any projection support?
Thanks for the help,
Roger
--
On Tue, Dec 16, 2008 at 4:43 AM, Jeff Whitaker <js...@fa...> wrote:
> Roger André wrote:
>
>> Hi All,
>>
>> I have some square images which were generated via WMS requests. I have
>> imported them into Matplotlib via pil_to_array, and then display them in a
>> Basemap instance where I have defined the projection as:
>>
>> m = Basemap(projection='cyl', lon_0=lon_0, llcrnrlon=ll_lon,
>> llcrnrlat=ll_lat, urcrnrlon=ur_lon,
>> urcrnrlat=ur_lat, suppress_ticks=False)
>>
>> While this works (it appears the tics are at the right places), the image
>> is no longer square, and I wonder if my projection definition is correct.
>>
>> Can someone show me what the correct Basemap parameters are for working
>> with images that are in EPSG:4326?
>>
>> Thanks,
>>
>> Roger
>>
>
> Roger: The image will only be square if ur_lon-ll_lon = ur_lat-ll_lat
> (i.e. the longitude range equals the latitude range). Is this the case?
> -Jeff
>
> --
> Jeffrey S. Whitaker Phone : (303)497-6313
> NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
> 325 Broadway Boulder, CO, USA 80305-3328
>
>

I also observed this with eps output. The png looked fine, but the eps legend
was very large in my case.
j
Lebostein wrote:
> 
> Hi,
> 
> with the new version of matplotlib, the legend looks different in png and
> pdf!
> 
> I could post examples, but you can look in the galery also:
> http://matplotlib.sourceforge.net/gallery.html
> 
> for example the legend_demo3
> http://matplotlib.sourceforge.net/examples/pylab_examples/legend_demo3.html
> * PNG:
> http://matplotlib.sourceforge.net/_static/plot_directive/mpl_examples/pylab_examples/legend_demo3.hires.png
> * PDF:
> http://matplotlib.sourceforge.net/_static/plot_directive/mpl_examples/pylab_examples/legend_demo3.pdf
> 
> You see in the png the lines are short and not vertically centered,
> padding between axes an legend text are ignored .. and so on
> 
-- 
View this message in context: http://www.nabble.com/different-PNG-and-PDF-output...-tp21028686p21037465.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Tue, Dec 16, 2008 at 10:30 AM, John Hunter <jd...@gm...> wrote:
>> using in favour of matplotlib). Plotting the data twice- the first time
>> without
>> symbol showing every data point and the second time onlywith the symbol
>> and some skip in the data - doesn't help as I now get two entities in
>> the legend.
>
> There is a way to do this, but it is not terribly elegant. The tricky
> part is to get the legend right::
I just added a new line property called "markevery" to support
subsampling markers. Included below is the docstring and nosetest
which should clearly indicate usage:
 def set_markevery(self, every):
 """
 Set the markevery property to subsample the plot when using
 markers. Eg if ``markevery=5``, every 5-th marker will be
 plotted. *every* can be
 None
 Every point will be plotted
 an integer N
 Every N-th marker will be plotted starting with marker 0
 A length-2 tuple of integers
 every=(start, N) will start at point start and plot every
N-th marker
 ACCEPTS: None | integer | (startind, stride)
 """
def test_markevery():
 x, y = np.random.rand(2, 100)
 # check marker only plot
 fig = plt.figure()
 ax = fig.add_subplot(111)
 ax.plot(x, y, 'o')
 ax.plot(x, y, 'd', markevery=None)
 ax.plot(x, y, 's', markevery=10)
 ax.plot(x, y, '+', markevery=(5, 20))
 fig.canvas.draw()
 plt.close(fig)
 # check line/marker combos
 fig = plt.figure()
 ax = fig.add_subplot(111)
 ax.plot(x, y, '-o')
 ax.plot(x, y, '-d', markevery=None)
 ax.plot(x, y, '-s', markevery=10)
 ax.plot(x, y, '-+', markevery=(5, 20))
 fig.canvas.draw()
 plt.close(fig)

On Tue, Dec 16, 2008 at 10:09 AM, Michael Oevermann
<mic...@tu...> wrote:
> Hi all,
>
> I am trying to find a solution to the following problem (without
> success so far):
> I have some high frequency data which I want to plot with a simple
> plot command using a solid line and a symbol. However, since I have many
> many
> data points I want to plot the symbol only every N'th data point. Is
> there a skip parameter
> or any other way to tell matplotlib to actually plot the symbol only
> at every N'th data point (I know it is possible in grace which I have
> stopped
> using in favour of matplotlib). Plotting the data twice- the first time
> without
> symbol showing every data point and the second time onlywith the symbol
> and some skip in the data - doesn't help as I now get two entities in
> the legend.
There is a way to do this, but it is not terribly elegant. The tricky
part is to get the legend right::
 import numpy as np
 import matplotlib.pyplot as plt
 fig = plt.figure()
 ax = fig.add_subplot(111)
 N = 10
 x = np.arange(100.)
 y = x**2
 # the solid line, suppress auto legend
 line1, = ax.plot(x, y, linestyle='-', color='black', label='_nolegend_')
 # every N-th marker, suppress auto legend
 line2, = ax.plot(x[::N], y[::N], linestyle='', marker='o',
markerfacecolor='blue', label='_nolegend_')
 # the proxy line, both solid and markers. Don't add it to plot, just
 # use it in legend
 import matplotlib.lines as lines
 proxyline = lines.Line2D([0,1], [0,1], linestyle='-',
color='black', marker='o', markerfacecolor='blue')
 leg = ax.legend([proxyline], ['my label'])
 plt.show()
JDH

Hi all,
I am trying to find a solution to the following problem (without
success so far):
I have some high frequency data which I want to plot with a simple
plot command using a solid line and a symbol. However, since I have many
many
data points I want to plot the symbol only every N'th data point. Is
there a skip parameter
or any other way to tell matplotlib to actually plot the symbol only
at every N'th data point (I know it is possible in grace which I have
stopped
using in favour of matplotlib). Plotting the data twice- the first time
without
symbol showing every data point and the second time onlywith the symbol
and some skip in the data - doesn't help as I now get two entities in
the legend.
Thanks for any help
Michael

This looks like a dpi issue -- that is the only difference between the 
regular and hi-res png. Jae-Joon -- do you have any thoughts? Perhaps 
something is dpi-dependent in the new legend code where it shouldn't be?
Mike
Lebostein wrote:
> Hi,
>
> with the new version of matplotlib, the legend looks different in png and
> pdf!
>
> I could post examples, but you can look in the galery also:
> http://matplotlib.sourceforge.net/gallery.html
>
> for example the legend_demo3
> http://matplotlib.sourceforge.net/examples/pylab_examples/legend_demo3.html
> * PNG:
> http://matplotlib.sourceforge.net/_static/plot_directive/mpl_examples/pylab_examples/legend_demo3.hires.png
> * PDF:
> http://matplotlib.sourceforge.net/_static/plot_directive/mpl_examples/pylab_examples/legend_demo3.pdf
>
> You see in the png the lines are short and not vertically centered, padding
> between axes an legend text are ignored .. and so on
> 
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Angus McMorland wrote:
>>> I get this error:
>>>
>>> writing output... index modules/calculate
>>> /usr/lib/python2.5/site-packages/sphinx/ext/sphinxext/mathmpl.py:107:
>>> Warning: Could not render math expression $lpha$
>>> Warning)
>>> /usr/lib/python2.5/site-packages/sphinx/ext/sphinxext/mathmpl.py:107:
>>> Warning: Could not render math expression $lpha = 2$
>>> Warning)
>>> 
>
> Excellent - the use of raw docstrings _does_ fix the errors during the
> sphinx build.
>
> 
>> That doesn't seem to be the root of this problem, however, as these strings
>> should at least render to *something*, though probably not what you want.
>>
>> The warning is hiding the real error here. In mathmpl.py, after the line
>> where the warning is emitted:
>>
>> warnings.warn("Could not render math expression %s" % latex,
>> Warning)
>>
>> Add the line:
>>
>> raise
>>
>> and then post the output to this list?
>> 
>
> Just an FYI so you can probably tell what was going on, without the
> curative r'', and with raise in place, the error reported was:
>
> writing output... index modules/calculate
> /usr/lib/python2.5/site-packages/sphinx/ext/sphinxext/mathmpl.py:107:
> Warning: Could not render math expression $lpha$
> Warning)
> Exception occurred:
> File "/usr/lib/python2.5/site-packages/matplotlib/mathtext.py", line
> 1963, in raise_error
> raise ParseFatalException(msg + "\n" + s)
> ParseFatalException: Expected end of math '$'
> $lpha$ (at char 0), (line:1, col:1)
> 
Thanks -- that's a good clue, though I'm still not sure why it's 
failing. Glad to see you have it working for the time being anyway.
> Next, I initially got no pictures (a silent fail) in my browser, but I
> traced that back to an assumption that mathmpl makes that sphinx-build
> is being run from the html directory, whereas I was running it from
> one higher up the hierarchy (my docs directory). Running sphinx-build
> from the appropriate location makes it all work.
>
> Obviously this is fine for mpl's needs (and mine too, now I know the
> tricks). If, however, you're interested in making this a little more
> robust for general usage, then the path handling probably needs
> tweaking. I think the problem is that mathmpl.latex2html puts the
> _static directory in the current directory sphinx-build is run from,
> whereas in the html it points to '../_static/', which is not the same
> thing whenever html pages are being rendered at deeper directory
> levels.
>
> 
For clarification, the matplotlib doc build creates the images within 
the doc/ directory and then copies them to the build. But that's not 
ideal either -- I agree the "file handling" stuff needs to be improved.
Long term, I think I'll need to look at what the new(ish) math 
extensions in the sphinx core do and emulate that. Just haven't found 
the time to get around to it lately.
Cheers,
Mike
-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Roger André wrote:
> Hi All,
>
> I have some square images which were generated via WMS requests. I 
> have imported them into Matplotlib via pil_to_array, and then display 
> them in a Basemap instance where I have defined the projection as:
>
> m = Basemap(projection='cyl', lon_0=lon_0, llcrnrlon=ll_lon, 
> llcrnrlat=ll_lat, urcrnrlon=ur_lon,
> urcrnrlat=ur_lat, suppress_ticks=False)
>
> While this works (it appears the tics are at the right places), the 
> image is no longer square, and I wonder if my projection definition is 
> correct.
>
> Can someone show me what the correct Basemap parameters are for 
> working with images that are in EPSG:4326?
>
> Thanks,
>
> Roger
Roger: The image will only be square if ur_lon-ll_lon = ur_lat-ll_lat 
(i.e. the longitude range equals the latitude range). Is this the case? 
-Jeff
-- 
Jeffrey S. Whitaker Phone : (303)497-6313
NOAA/OAR/CDC R/PSD1 FAX : (303)497-6449
325 Broadway Boulder, CO, USA 80305-3328