matplotlib-users Mailing List for matplotlib (Page 10)

T24gMy8xMy8wNywgQW50b25pbm8gSW5nYXJnaW9sYSA8dHJpdGVtaW9AZ21haWwuY29tPiB3cm90
ZToKCj4gMS4gVXNlIHRoZSB1bmljb2RlIHN0cmluZzogeGxhYmVsKHUnV2F2ZWxlbmd0aCBb7G1d
JykKPiAyLiBVc2UgbWF0aHRleHQ6IHhsYWJlbChyJyRccm17V2F2ZWxlbmd0aCBbXG11IG1dfSQn
KQo+IDMuIFVzZSB1c2V0ZXg6IHJjKHRleHQsIHVzZXRleD1UcnVlKSwgeGxhYmVsKHInV2F2ZWxl
bmd0aCBbJFxybXtcbXUgbX0kXScpCj4KPiBJIGhhdmUgc29tZSBwcm9ibGVtIHdpdGggZWFjaCBt
ZXRob2QgKGFueSBoaW50IGlzIGFwcHJlY2lhdGVkKS4KCldoYXQgaXMgdGhlIHByb2JsZW0gd2l0
aCBtZXRob2QgMz8KCkpESAo=

On 13/03/07, Antonino Ingargiola <tri...@gm...> wrote:
> 1. This method works ok as far as I choose a unicode font with the
> greek letters, for example:
>
> rcParams['font.serif'] = 'DejaVu Serif'
>
> However with unicode strings I'm not able to do exponent and deponent
> text (i.e cm^-1)
You should be able to do super/subscripts in unicode. For example a
superscript '-' is unicode 207B. If you haven't already found it you
should check out:
http://unicode.org/charts/symbols.html
for more codes. However, the font you choose must support the unicode
(most only support a certain subset).
Regards,
John

Hello,
I'm trying to display some unicode text in matplotlib graphs embedded in
a Qt application. The text contains characters belonging to Turkish and
Korean idioms.
I've started modifying the simple demo examples/unicode_demo.py, I ran
it and I got a nice test.svg file with the correct glyphs. So far
everything was good.
Then I moved to examples/embedding_in_qt.py, and placed there the very
same unicode strings I used in the previous example: in the running
application, Turkish glyphs are displayed correctly, Korean ones are
represented by "squares" instead.
(I'm attaching the modified sources if somebody wants to do some quick
tests)
It seems that the unicode handling code is different between SVG and Qt
backends. If so, am I missing something in the Qt code to get all the
correct glyphs?
This is with matplotlib 0.86.2, pyqt 3.16.
Thanks in advance!
-- 
Lorenzo Mancini

U29ycnkgZm9yIHRoZSBwcmV2aW91cyBtYWlsIEkndmUgaGl0IFNlbmQgZm9yIGVycm9yIGJlZm9y
ZSB0aGUgbWFpbAp3YXMgY29tcGxldGUuCgpIZXJlIGl0IGlzIHRoZSBjb21wbGV0ZSBtYWlsOgoK
SGkgdG8gdGhlIGxpc3QsCgpJJ20gdXNpbmcgbWF0cGxvdGxpYiB0byBnZW5lcmF0ZSBncmFwaHMg
ZHVyaW5nIG15IG1hc3RlciB0aGVzaXMuIEkKd2FudCB0byB0aGFuayBhbGwgdGhlIGRldmVsb3Bl
ciBmb3IgcHJvdmlkaW5nIHN1Y2ggZmxleGlibGUgdG9vbC4KCkluIHNvbWUgcGxvdHMgSSBoYXZl
IHRvIHB1dCBncmVlayBsZXR0ZXJzIChvciBzb21ldGltZXMgc21hbGwgZm9ybXVsYXMpCmFzIGF4
aXMgbGFiZWwuIEkndmUgZm91bmQgdGhyZWUgd2F5IHRvIGFjY29tcGxpc2ggdGhpczoKCjEuIFVz
ZSB0aGUgdW5pY29kZSBzdHJpbmc6IHhsYWJlbCh1J1dhdmVsZW5ndGggW+xtXScpCjIuIFVzZSBt
YXRodGV4dDogeGxhYmVsKHInJFxybXtXYXZlbGVuZ3RoIFtcbXUgbV19JCcpCjMuIFVzZSB1c2V0
ZXg6IHJjKHRleHQsIHVzZXRleD1UcnVlKSwgeGxhYmVsKHInV2F2ZWxlbmd0aCBbJFxybXtcbXUg
bX0kXScpCgpJIGhhdmUgc29tZSBwcm9ibGVtIHdpdGggZWFjaCBtZXRob2QsIGFueSBoaW50IGlz
IGFwcHJlY2lhdGVkLgoKMS4gVGhpcyBtZXRob2Qgd29ya3Mgb2sgYXMgZmFyIGFzIEkgY2hvb3Nl
IGEgdW5pY29kZSBmb250IHdpdGggdGhlCmdyZWVrIGxldHRlcnMsIGZvciBleGFtcGxlOgoKICBy
Y1BhcmFtc1snZm9udC5zZXJpZiddID0gJ0RlamFWdSBTZXJpZicKCkhvd2V2ZXIgd2l0aCB1bmlj
b2RlIHN0cmluZ3MgSSdtIG5vdCBhYmxlIHRvIGRvIGV4cG9uZW50IGFuZCBkZXBvbmVudAp0ZXh0
IChpLmUgY21eLTEpCgpNZXRob2RzIDEuIGFuZCAyLiBhcmUgbW9yZSBmbGV4aWJsZSwgaG93ZXZl
ciBJJ20gbm8gYWJsZSB0byB0byBwdXQgdGhlClxtdSBjaGFyYWN0ZXIgaW4gcm9tYW4gZm9udHMu
IEkgZG9uJ3Qga25vdyBpZiB0aGlzIGlzIHRoZSBpbnRlbmRlZApiZWhhdmlvciBvciBpZiBpdCdz
IGEgYnVnLi4uCgpGdXJ0aGVybW9yZSwgaXMgdGhlcmUgYSBzaW1wbGUgd2F5IHRvIHNldCBmb250
c2l6ZSBmb3IgYWxsIHRleHQKZWxlbWVudHMgKGxhYmVscywgdGl0bGUsIHRpY2tsYWJlbHMpLiBD
dXJyZW50bHkgSSdtIGRvaW5nOgoKcmNQYXJhbXNbJ2ZvbnQuc2l6ZSddID0gMTIKcmNQYXJhbXNb
J3h0aWNrLmxhYmVsc2l6ZSddID0gMTQKcmNQYXJhbXNbJ2F4ZXMudGl0bGVzaXplJ10gPSAxNgpy
Y1BhcmFtc1snYXhlcy5sYWJlbHNpemUnXSA9IDE0CgpUaGUgcmVsYXRpdmUgc2V0dGluZyAobGFy
Z2UsIHNtYWxsLC4uLikgc2VlbXMgdG8gcmVmZXIgYWx3YXlzIHRvIHRoZQpkZWZhdWx0IGZvbnQg
c2l6ZSAoc2V0IGluIG1hdHBsb3RsaWJyYykuIElzIHRoZXJlIGEgd2F5IHRvIHNldCB0aGUKZm9u
dC5zaXplIHByb3BlcnR5IGFuZCB0aGVuIHVwZGF0ZSBhbGwgdGhlIG90aGVyIHJlbGF0aXZlIHZh
bHVlcyB0bwpyZWZsZWN0IHRoZSBjaGFuZ2U/CgpNYW55IHRoYW5rcyBmb3IgYW55IGhlbHAuCgog
IH4gQW50b25pbwo=

SGkgdG8gdGhlIGxpc3QsCgpJJ20gdXNpbmcgbWF0cGxvdGxpYiB0byBnZW5lcmF0ZSBncmFwaHMg
ZHVyaW5nIG15IG1hc3RlciB0aGVzaXMuIEkKd2FudCB0byB0aGFuayBhbGwgdGhlIGRldmVsb3Bl
ciBmb3IgcHJvdmlkaW5nIHN1Y2ggZmxleGlibGUgdG9vbC4KCkluIHNvbWUgcGxvdHMgSSBoYXZl
IHRvIHB1dCBncmVlayBsZXR0ZXJzIChvciBzb21ldGltZXMgc21hbGwgZm9tdWxhcykKYXMgYXhp
cyBsYWJlbC4gSSd2ZSBmb3VuZCB0aHJlZSB3YXkgdG8gYWNjb21wbGlzaCB0aGlzOgoKMS4gVXNl
IHRoZSB1bmljb2RlIHN0cmluZzogeGxhYmVsKHUnV2F2ZWxlbmd0aCBb7G1dJykKMi4gVXNlIG1h
dGh0ZXh0OiB4bGFiZWwocickXHJte1dhdmVsZW5ndGggW1xtdSBtXX0kJykKMy4gVXNlIHVzZXRl
eDogcmModGV4dCwgdXNldGV4PVRydWUpLCB4bGFiZWwocidXYXZlbGVuZ3RoIFskXHJte1xtdSBt
fSRdJykKCkkgaGF2ZSBzb21lIHByb2JsZW0gd2l0aCBlYWNoIG1ldGhvZCAoYW55IGhpbnQgaXMg
YXBwcmVjaWF0ZWQpLgoKMS4gVGhpcyBtZXRob2Qgd29ya3Mgb2sgYXMgZmFyIGFzIEkgY2hvb3Nl
IGEgdW5pY29kZSBmb250IHdpdGggdGhlCmdyZWVrIGxldHRlcnMsIGZvciBleGFtcGxlOgo=

I fixed another filehandle leak in the pdf backend, so here's a more
complete patch. There are also several cases of file(...) being passed
to pickle.dump or pickle.load in font_manager.py. I was going to take
care of these by writing some utility functions, but I started
wondering why the import of cPickle or pickle is done only within
methods of FontManager and not at the top level. Are there some
platforms where neither is available, or what is the rationale?
Index: backend_pdf.py
===================================================================
--- backend_pdf.py (revision 3044)
+++ backend_pdf.py (revision 3046)
@@ -457,7 +457,9 @@
 self.writeObject(self.fontObject, fonts)
 
 def _write_afm_font(self, filename):
- font = AFM(file(filename))
+ fh = file(filename)
+ font = AFM(fh)
+ fh.close()
 fontname = font.get_fontname()
 fontdict = { 'Type': Name('Font'),
 'Subtype': Name('Type1'),
@@ -1081,7 +1083,9 @@
 font = self.afm_font_cache.get(key)
 if font is None:
 filename = fontManager.findfont(prop, fontext='afm')
- font = AFM(file(filename))
+ fh = file(filename)
+ font = AFM(fh)
+ fh.close()
 self.afm_font_cache[key] = font
 return font
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

kc1...@ya... writes:
> Now, I am running into another problem. Everything works fine up to
> 8 page plots. Starting with the 9th page, MPL chokes at line 1084 in
> backend_pdf.py and couldn't find the cooresponding ttf file
> (VeraSe.ttf) but it had no problem reading that file for the first 8
> plots.
Does the following change help with this? (If you are following svn,
just run "svn update"; otherwise, the easiest way is to replace line
1084 by the three lines prefixed with + below.)
Index: backend_pdf.py
===================================================================
--- backend_pdf.py (revision 3044)
+++ backend_pdf.py (revision 3045)
@@ -1081,7 +1081,9 @@
 font = self.afm_font_cache.get(key)
 if font is None:
 filename = fontManager.findfont(prop, fontext='afm')
- font = AFM(file(filename))
+ fh = file(filename)
+ font = AFM(fh)
+ fh.close()
 self.afm_font_cache[key] = font
 return font
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hi list,=0A=0AFirst of all, thanks to Bill Dandreta and Jouni Seppanen for =
helping with my combining single page pdf into multipage pdf question. I t=
ried both method and went with pdftex because it's very simple (and fits my=
 need).=0A=0ANow, I am running into another problem. Everything works fin=
e up to 8 page plots. Starting with the 9th page, MPL chokes at line 1084=
 in backend_pdf.py and couldn't find the cooresponding ttf file (VeraSe.ttf=
) but it had no problem reading that file for the first 8 plots.=0A=0A???=
=0A=0ARegards,=0A =0A--=0AJohn Henry=0A=0A

>
> What version of mpl are you using?
The latest, I compiled it from the source as FC5 has a very old version -
can't update myself the distribution -
In recent versions, the collections should accept 2D numpy arrays as
> well as any sequence of tuples (and several other possibilities).
For 2D plots, numpy arrays is accepted - but not for colors, it tells me
there is a problem with tuples, I do not remember exactly, but I can check
the error tomorrow -.
For 3D plots, the offsets must be special, I suppose, as the array must be
iterated on with a zip, I don't know why there is this need, but I didn't
write it :) This difference in format is akward :| And the fact that the
example file cannot be executed is still stranger.
Autoscaling does not work well with arbitrary collections because there
> is a chicken-and-egg problem: a collection member may be drawn in pixels
> or other physical units, in which case its size in data units cannot be
> determined until it is drawn with a given xlim and ylim (and sometimes
> dpi).
That is not my worst problem, I imposed the limits and it works now like a
charm :)
Matthieu

Matthieu Brucher wrote:
> I manage to do what I wanted to do, it was not that easy - the colours 
> were in an array I had to transform into an array of tuples, the 
> autoscale did not function, I had to put in the fig.subplot the correct 
> xlim and ylim -, but now it works like a charm.
> Many thanks.
What version of mpl are you using?
In recent versions, the collections should accept 2D numpy arrays as 
well as any sequence of tuples (and several other possibilities).
Autoscaling does not work well with arbitrary collections because there 
is a chicken-and-egg problem: a collection member may be drawn in pixels 
or other physical units, in which case its size in data units cannot be 
determined until it is drawn with a given xlim and ylim (and sometimes dpi).
Eric

>
> There may be, but all 3D plotting is shaky right now. The 3D code is
> essentially unmaintained and unsupported.
>
> Eric
>
Sad to hear this, I hope someone will enhance it :)
Matthieu

Matthieu Brucher wrote:
> OK, I'm trying to the same but in 3D, and there, no documentaion.
> I tried to launch axes3d.py to see exactly what I can do, but the 
> example file does not work. For instance, Axes3D takes two parameters 
> for method __init__ and only one is provided. Did someone test it ?
> I'm trying to use collection as well, but for once I prefer MatLab 
> simplicity here, it's way to complicated, some arguments must be zipped, 
> other are passed not in the collection, but when the collection is added 
> to the subplot, ...
> Is there a simple and clear way to do 3D plotting with collections ?
There may be, but all 3D plotting is shaky right now. The 3D code is 
essentially unmaintained and unsupported.
Eric

Hi All,
 I am using matplotlib-0.90.0 with numpy-1.0.1 for my python
program which I later convert in to an executable with the help of
pyinstaller,
I am installing matplotlib-0.90.0 from source and it installs fine.when
I create the executable of my program (I include matplotlib as a .pkg in
it) and run it
I get the following error only on linux , it fails at with this message
=20
matplotlib._ns_transforms.so: undefined symbol:
_ZNSs4_Rep20_S_empty_rep_storage
=20
but same set of source of matplotlib-0.90.0 with numpy-1.0.1 installed
from source works fine on windows and solaris,any idea what is going
wrong here?
I am using gcc version 3.4.3 on red hat linux 2.6.9-11
=20
Here is the complete stack trace
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
Extracting mpl-data.pkg data ... ok
Extracting numpy.pkg data ... ok
working dir /home/rik/output/var/projects
/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib:931:
UserWarning: Could not find matplotlibrc; using defaults
/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib:982:
UserWarning: could not find rc file; returning defaults
=20
The import of the numpy version of the _transforms module,
_ns_transforms, failed. This is is either because numpy was
unavailable when matplotlib was compiled, because a dependency of
_ns_transforms could not be satisfied, or because the build flag for
this module was turned off in setup.py. If it appears that
_ns_transforms was not built, make sure you have a working copy of
numpy and then re-install matplotlib. Otherwise, the following
traceback gives more details:
=20
Traceback (most recent call last):
 File "/home/rik/are_new/exe/linux/buildare_top/out1.pyz/exe_harness",
line 97, in __init__
 File "<string>", line 69, in dispatch
 File "<string>", line 109, in handleReportRequest
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File "/home/rik/are_new/exe/linux/buildare_top/out1.pyz/convert_dom",
line 12, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File "/home/rik/are_new/exe/linux/buildare_top/out1.pyz/report", line
29, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File "/home/rik/are_new/exe/linux/buildare_top/out1.pyz/page_setup",
line 14, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File "/home/rik/are_new/exe/linux/buildare_top/out1.pyz/graph_view",
line 11, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File "/home/rik/are_new/exe/linux/buildare_top/out1.pyz/pylab", line
1, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File
"/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib.pylab",
line 203, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File
"/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib.axes",
line 14, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File
"/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib.artist",
line 4, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File
"/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib.transforms
", line 223, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 398, in doimport
 exec co in mod.__dict__
 File
"/home/rik/are_new/exe/linux/buildare_top/out1.pyz/matplotlib._transform
s", line 17, in ?
 File "/home/rik/pyinstaller-1.3/iu.py", line 312, in importHook
 mod =3D _self_doimport(nm, ctx, fqname)
 File "/home/rik/pyinstaller-1.3/iu.py", line 373, in doimport
 mod =3D importfunc(nm)
 File "/home/rik/pyinstaller-1.3/iu.py", line 215, in getmod
 mod =3D owner.getmod(nm)
 File "/home/rik/pyinstaller-1.3/archive.py", line 409, in getmod
 return iu.DirOwner.getmod(self, self.prefix+'.'+nm)
 File "/home/rik/pyinstaller-1.3/iu.py", line 77, in getmod
 mod =3D imp.load_module(nm, fp, attempt, (ext, mode, typ))
ImportError: /tmp/_MEI22558/matplotlib._ns_transforms.so: undefined
symbol: _ZNSs4_Rep20_S_empty_rep_storageE
=20
Regards
Rishi
This email and any files transmitted with it are confidential, proprietar=
y
and intended solely for the individual or entity to whom they are address=
ed.
If you have received this email in error please delete it immediately.
=0D

OK, I'm trying to the same but in 3D, and there, no documentaion.
I tried to launch axes3d.py to see exactly what I can do, but the example
file does not work. For instance, Axes3D takes two parameters for method
__init__ and only one is provided. Did someone test it ?
I'm trying to use collection as well, but for once I prefer MatLab
simplicity here, it's way to complicated, some arguments must be zipped,
other are passed not in the collection, but when the collection is added to
the subplot, ...
Is there a simple and clear way to do 3D plotting with collections ?
Matthieu
2007年3月12日, Matthieu Brucher <mat...@gm...>:
>
> I manage to do what I wanted to do, it was not that easy - the colours
> were in an array I had to transform into an array of tuples, the autoscale
> did not function, I had to put in the fig.subplot the correct xlim and
> ylim -, but now it works like a charm.
> Many thanks.
>
> Matthieu
>
> 2007年3月9日, John Hunter <jd...@gm...>:
> >
> > On 3/9/07, Matthieu Brucher <mat...@gm...> wrote:
> >
> > > What I have is a set of points in a numpy.array - for instance size
> > (2000,
> > > 2) -. What I have as well is a nump.array of size (2000, 3). How can I
> > make
> > > plot understand that each line of the set points must be painted with
> > the
> > > corresponding line in the colour array ?
> >
> > You'll probably want to use a regular poly collection, as in the
> > example below. Your array of facecolors can pretty much be whatever
> > you want:
> >
> > from pylab import figure, nx, show, cm
> > from matplotlib.collections import RegularPolyCollection
> >
> >
> > fig = figure()
> > ax = fig.add_subplot(111)
> >
> > offsets = nx.mlab.rand(20,2)
> > facecolors = [cm.jet(x) for x in nx.mlab.rand(20)]
> > black = (0,0,0,1)
> >
> > collection = RegularPolyCollection(
> > fig.dpi,
> > numsides=5, # a pentagon
> > rotation=0,
> > sizes=(50,),
> > facecolors = facecolors,
> > edgecolors = (black,),
> > linewidths = (1,),
> > offsets = offsets,
> > transOffset = ax.transData,
> > )
> >
> > ax.add_collection (collection)
> >
> > show()
> >
> >
> >
> >
> >
> >
> >
> > > Matthieu
> > >
> > >
> > -------------------------------------------------------------------------
> > > Take Surveys. Earn Cash. Influence the Future of IT
> > > Join SourceForge.net's Techsay panel and you'll get the chance to
> > share your
> > > opinions on IT & business topics through brief surveys-and earn cash
> > >
> > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > > _______________________________________________
> > > Matplotlib-users mailing list
> > > Mat...@li...
> > > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> > >
> > >
> >
>
>

I manage to do what I wanted to do, it was not that easy - the colours were
in an array I had to transform into an array of tuples, the autoscale did
not function, I had to put in the fig.subplot the correct xlim and ylim -,
but now it works like a charm.
Many thanks.
Matthieu
2007年3月9日, John Hunter <jd...@gm...>:
>
> On 3/9/07, Matthieu Brucher <mat...@gm...> wrote:
>
> > What I have is a set of points in a numpy.array - for instance size
> (2000,
> > 2) -. What I have as well is a nump.array of size (2000, 3). How can I
> make
> > plot understand that each line of the set points must be painted with
> the
> > corresponding line in the colour array ?
>
> You'll probably want to use a regular poly collection, as in the
> example below. Your array of facecolors can pretty much be whatever
> you want:
>
> from pylab import figure, nx, show, cm
> from matplotlib.collections import RegularPolyCollection
>
>
> fig = figure()
> ax = fig.add_subplot(111)
>
> offsets = nx.mlab.rand(20,2)
> facecolors = [cm.jet(x) for x in nx.mlab.rand(20)]
> black = (0,0,0,1)
>
> collection = RegularPolyCollection(
> fig.dpi,
> numsides=5, # a pentagon
> rotation=0,
> sizes=(50,),
> facecolors = facecolors,
> edgecolors = (black,),
> linewidths = (1,),
> offsets = offsets,
> transOffset = ax.transData,
> )
>
> ax.add_collection(collection)
>
> show()
>
>
>
>
>
>
>
> > Matthieu
> >
> >
> -------------------------------------------------------------------------
> > Take Surveys. Earn Cash. Influence the Future of IT
> > Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> > opinions on IT & business topics through brief surveys-and earn cash
> >
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
>

ghostscript can do it
gs -dBATCH -dNOPAUSE -q -sDEVICE=pdfwrite -sOutputFile=123.pdf 1.pdf
2.pdf 3.pdf
Bill
kc1...@ya... wrote:
> Hi list,
>
> I am using matplotlib to create single page plots and the whole process works fine. However, when I am done, I end up with lots of single page pdf files. Is there a way to get matplotlib to combine them all into a single PDF file?
>
> I tried using another package PyPDF but ended up with either file I/O problems or too many file opened problem. I am hoping that this can be done within matplotlib and not require yet another package.
>
> Thanks,
> 
> --
> John Henry
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
> 

kc1...@ya... writes:
> I am using matplotlib to create single page plots and the whole
> process works fine. However, when I am done, I end up with lots of
> single page pdf files. Is there a way to get matplotlib to combine
> them all into a single PDF file?
No, at least not currently. Tools that can do this include pdftk and
pdfTeX; in pdfTeX the easiest way to go is probably to use the
pdfpages package.
http://www.accesspdf.com/pdftk/
http://www.tug.org/applications/pdftex/
http://www.ctan.org/tex-archive/macros/latex/contrib/pdfpages/pdfpages.pdf
> I tried using another package PyPDF but ended up with either file
> I/O problems or too many file opened problem.
I was not aware of PyPDF, but it looks like it is being actively
developed. Perhaps you could submit a bug report to the author of
PyPDF?
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hi list,=0A=0AI am using matplotlib to create single page plots and the who=
le process works fine. However, when I am done, I end up with lots of sin=
gle page pdf files. Is there a way to get matplotlib to combine them all i=
nto a single PDF file?=0A=0AI tried using another package PyPDF but ended u=
p with either file I/O problems or too many file opened problem. I am hopi=
ng that this can be done within matplotlib and not require yet another pack=
age.=0A=0AThanks,=0A =0A--=0AJohn Henry=0A=0A

Jeff Peery <jef...@ya...> writes:
> I am having some confusion about how best to set my plot settings.
> Should I use rcParams, or carry around my own class object holding
> plot() and scatter() settings?
IMHO modifying rcParams is not a good way to use the object-oriented
interface. It can be very useful for interactive plotting using the
(state-machine) pylab interface, but such non-explicit state can make
an object-oriented program difficult to follow. Of course rcParams is
needed for things like selecting fonts.
> 1) from what I read, I expected a rcParams value to keep if I closed
> my app then reopened it. But it went back to some default... maybe the
> matplotlibrc file? are these things separate?
rcParams is initialized from the matplotlibrc file.
> 2) when I changed the rcParams for my line style (for example) ALL
> line styles changed not just the lines in plot().
If you want more detailed control, I think you have to use the keyword
arguments (or set the equivalent properties on the line objects).
> 3) I didn't see a rcParams object for the scatter() parameters,
> markers size, style, color, linewidth etc. Is this possible?
I think the patch.* parameters affect the markers created by
scatter().
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

"Jack Sankey" <jac...@gm...> writes:
> The problem is when I do errobar() I get not only the data lines, but
> also a bunch of small lines for drawing the error bars, and it's very
> difficult to sort them all out to get at the data of the plot.
One possibility could be to change the return value of errorbar() from
the current unstructured list of lines to e.g. a dict of lists of
lines, so you could modify them separately. Here is a patch of mine
that did this for boxplot (and was accepted):
http://sourceforge.net/tracker/index.php?func=detail&aid=1364810&group_id=80706&atid=560722
Would something like this help with your problem?
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hello, 
I apologize if this message was already posted, it was bounced back to me.
I am having some confusion about how best to set my plot settings. Should I use rcParams, or carry around my own class object holding plot() and scatter() settings? I have a wx app and I plot simple x y data. I manually add data values and each time I do my app clears then redraw the canvas. I'm using only plot() scatter() and axhline() in my app. My problem is that my code is a bit messy because I have my own class object that stores all the selected plot settings, ie colors, line widths, etc. 
I discovered the rcParams and I thought this would really clean up my code a bit. So I could set the rcParams and not have to keep track of my plot() and scatter() settings because matplotlib already does. Several problems happened when I did this:
1) from what I read, I expected a rcParams value to keep if I closed my app then reopened it. But it went back to some default... maybe the matplotlibrc file? are these things separate? 
2) when I changed the rcParams for my line style (for example) ALL line styles changed not just the lines in plot().
3) I didn't see a rcParams object for the scatter() parameters, markers size, style, color, linewidth etc. Is this possible?
Am I using rcParams correctly? I want to take advantage of setting my plot() and scatter() settings by using matplotlib instead of having to reset them each time I draw(). 
Thanks!
Jeff
 
---------------------------------
 Get your own web address.
 Have a HUGE year through Yahoo! Small Business.

Hello,
When I plot using the errorbar() routine, I get beautiful plots,
complete with error bars. Then, when I want to perform manipulations
on the data after the fact, I use
lines = axes.get_lines()
to get at the lines
lines[n].get_xdata() and set_xdata()
to edit the data etc...
The problem is when I do errobar() I get not only the data lines, but
also a bunch of small lines for drawing the error bars, and it's very
difficult to sort them all out to get at the data of the plot.
My question is, is there an easy/bulletproof way to tell if a given
line from get_lines() is an error bar or the actual data?
Thanks!
Jack

Suresh Pillai wrote:
> I guess I didn't read the following carefully:
> 
> "... The aspect ratio of the figure window is that of the array
> ... Because of how matshow() tries to
> set the figure aspect ratio to be the one of the array, ..."
> 
> which would explain the behaviour below.
> 
> Why the restrictions? Seems one would want to put colorbars, etc in the 
> same figure and so why not behave like imshow() which it calls to make the 
> output. And why the new figure (so no possibility of subplots or 
> overlays)? Just curious ... I guess I will use imshow() directly and 
> modify the axes as suggested before to get the output looking like 
> matshow()
> 
Suresh,
I think the general answer to your questions is "historical accident". 
Matshow was contributed a long time ago, and has been updated only 
minimally to take into account changes made elsewhere. There was even a 
suggestion that it might not be needed any more, but I think that it can 
continue to be useful and is worth updating to be an axes method, etc. 
This is on my growing mental list of things to do, and is probably one 
of the easier ones.
Eric
> Cheers,
> Suresh
> 
> On Thu, 8 Mar 2007, Suresh Pillai wrote:
> 
>> If one inserts a colorbar after using matshow, then the matrix plot's aspect 
>> ratio is incorrect altered. Here are 2 cases to compare
>>
>> import pylab
>> matrix = pylab.rand(30,30)
>>
>> 1) matshow() before colorbar()
>>
>> pylab.matshow(matrix)
>> pylab.colorbar()
>> pylab.show()
>>
>> The matrix plot is squished in the x-direction while not in the y thus losing 
>> its proper aspect ratio (equal by default).
>>
>> 2) imshow() before colorbar()
>>
>> pylab.imshow(matrix)
>> pylab.colorbar()
>> pylab.show()
>>
>> Everthing is okay in this case.
>>
>>
>> Thanks,
>> Suresh
>>
>>
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Suresh Pillai <sto...@ya...> writes:
> I discovered the same problem, so I went looking and found the mailing 
> list properly archived at nabble.com:
Another useful mailing list archive is gmane.org:
http://dir.gmane.org/gmane.comp.python.matplotlib.general
http://dir.gmane.org/gmane.comp.python.matplotlib.devel
-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Jeff Peery <jef...@ya...> writes:
> hello, I have an application I'm working on, and I need to remove
> figtext() without using a figure.clear(). how can I do this? thanks.
When you call figtext, save the return value, and then call
set_visible(False) on it to hide it, or delete it from the figure's
texts list:
ft=fig.figtext(x, y, text)
# ...
ft.set_visible(False); draw()
# or:
fig.texts.remove(ft); draw()
-- 
Jouni K. Seppänen
http://www.iki.fi/jks