Menu
▾
▴
matplotlib-users — Discussion related to using matplotlib
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(12) |
Sep
(12) |
Oct
(56) |
Nov
(65) |
Dec
(37) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(59) |
Feb
(78) |
Mar
(153) |
Apr
(205) |
May
(184) |
Jun
(123) |
Jul
(171) |
Aug
(156) |
Sep
(190) |
Oct
(120) |
Nov
(154) |
Dec
(223) |
| 2005 |
Jan
(184) |
Feb
(267) |
Mar
(214) |
Apr
(286) |
May
(320) |
Jun
(299) |
Jul
(348) |
Aug
(283) |
Sep
(355) |
Oct
(293) |
Nov
(232) |
Dec
(203) |
| 2006 |
Jan
(352) |
Feb
(358) |
Mar
(403) |
Apr
(313) |
May
(165) |
Jun
(281) |
Jul
(316) |
Aug
(228) |
Sep
(279) |
Oct
(243) |
Nov
(315) |
Dec
(345) |
| 2007 |
Jan
(260) |
Feb
(323) |
Mar
(340) |
Apr
(319) |
May
(290) |
Jun
(296) |
Jul
(221) |
Aug
(292) |
Sep
(242) |
Oct
(248) |
Nov
(242) |
Dec
(332) |
| 2008 |
Jan
(312) |
Feb
(359) |
Mar
(454) |
Apr
(287) |
May
(340) |
Jun
(450) |
Jul
(403) |
Aug
(324) |
Sep
(349) |
Oct
(385) |
Nov
(363) |
Dec
(437) |
| 2009 |
Jan
(500) |
Feb
(301) |
Mar
(409) |
Apr
(486) |
May
(545) |
Jun
(391) |
Jul
(518) |
Aug
(497) |
Sep
(492) |
Oct
(429) |
Nov
(357) |
Dec
(310) |
| 2010 |
Jan
(371) |
Feb
(657) |
Mar
(519) |
Apr
(432) |
May
(312) |
Jun
(416) |
Jul
(477) |
Aug
(386) |
Sep
(419) |
Oct
(435) |
Nov
(320) |
Dec
(202) |
| 2011 |
Jan
(321) |
Feb
(413) |
Mar
(299) |
Apr
(215) |
May
(284) |
Jun
(203) |
Jul
(207) |
Aug
(314) |
Sep
(321) |
Oct
(259) |
Nov
(347) |
Dec
(209) |
| 2012 |
Jan
(322) |
Feb
(414) |
Mar
(377) |
Apr
(179) |
May
(173) |
Jun
(234) |
Jul
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
| 2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
| 2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
| 2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
| 2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
| 2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| S | M | T | W | T | F | S |
|---|---|---|---|---|---|---|
|
1
|
2
(1) |
3
(1) |
4
(6) |
5
(12) |
6
(13) |
7
|
|
8
(2) |
9
(21) |
10
(19) |
11
(2) |
12
(9) |
13
(22) |
14
(1) |
|
15
(1) |
16
(12) |
17
(5) |
18
(6) |
19
(7) |
20
(13) |
21
(6) |
|
22
(3) |
23
(14) |
24
(15) |
25
(7) |
26
(16) |
27
(7) |
28
(6) |
|
29
(1) |
30
(12) |
31
(3) |
|
|
|
|
|
From: <sk...@po...> - 2006-10-04 10:11:29
|
Hello,
I'm using python-matplotlib from debian unstable and the plots doesn't display
properly polish fonts, instead I get squares on graphs.
Simple example
#!/usr/bin/python
# -*- coding: iso-8859-2 -*-
from pylab import *
plot([1, 2, 3], [1, 4, 2])
xlabel(unicode('Miesiąc maj','iso-8859-2'))
ylabel(unicode('ążęńół','iso-8859-2'))
show()
Any idea?
Regards,
Seweryn Kokot
|
|
From: Miriam G. <mi...@ho...> - 2006-10-04 08:18:51
|
<html><div style='background-color:'><P>Hi,</P> <P>Is it possible in python/matplotlib to link the x-axis in the subplots. So if you zoom in in one of the graphs of the subplot, that then the other subplots also zoom in. In Matlab this function is called 'linkaxis'.</P> <P>Thanks in advance,</P> <P>Miriam<BR><BR><BR></P> <P> </P></div></html> |
|
From: George N. <gn...@go...> - 2006-10-04 02:28:46
|
I have been trying to
i. plot a figure using pcolormesh
ii. set the proportions of the figure using ax.set_aspect
iii. draw colorbar
Problem is, colorbar height uses whole of axes box, not just height of
figure (whose proportions were set by call of
ax.set_aspect(aspect=2.,adjustable='box')).
I can't set the colorbar height manually either, as I don't know how
to get out the bounding box of the figure -- ax.get_position() just
gives the full axes box, which is unaffected by ax.set_aspect.
Is there any way of recovering the actual bounding box of the figure?
The docstring for the method ax.set_position says:
There are two position variables: one which is ultimately
used, but which may be modified by apply_aspect, and a second
which is the starting point for apply_aspect.
which = 'active' to change the first;
'original' to change the second;
'both' to change both
which sounds relevant, but these variables don't seem to apply to
ax.get_position()
--George Nurser.
|
|
From: Mark B. <ma...@gm...> - 2006-10-04 02:05:23
|
What I don't understand is why we need previews at all? Is this because Microsoft software cannot display an eps file? Why not? Isn't that one of the easiest drivers to write? Are they not adding eps format out of spite? Mark > From: "Theodore R Drain" <dr...@jp...> > Subject: Re: [Matplotlib-users] eps file format > To: "Christian Meesters" <mee...@un...> > Cc: mat...@li... > Message-ID: <1159480577-30640.00012.00075-smmsdV2.1.4@localhost> > Content-Type: text/plain; charset="us-ascii" > > FYI I don't know what the current state of affairs was but I > looked into this a little bit about 5 or so years ago. Adobe has > a spec for what the preview image in an EPS file is suppose to be > (I can't remember the details on what it is but you can google > for the EPS spec) but I don't think anyone really followed it. > On Mac's, everything produced a PICT image and on Windows > everything produced something else (I forget exactly what it > was). In short, at the time I checked it out, it was very > difficult to make a high quality preview image that would work > well on a Mac and a Windows box. > > It would be nice if things were different now. We do a lot of > plotting that ends up in presentations and it would be nice if > you could embed an EPS in the presentation with a high quality > preview. > > Ted > > ---------Included Message---------- > >Date: 28-sep-2006 14:04:55 -0700 > >From: "Christian Meesters" <mee...@un...> > >To: <mat...@li...> > >Subject: Re: [Matplotlib-users] eps file format > > > >> As for the preview header, I suspect there arte 3rd part tools > that > >> can do this (ImageMagick?). We should be able to do it > ourself with > >> agg, but it would require someone to dig in and figure out the > spec. > >> > >> JDH > >One last remark on this: Since so many journals demand this, > would it be worth > >a feature request? (I don't have the time nor the skills to work > on this.) > >One may think of this as one wishes (don't like these publishing > companies > >and their demands, either), but matplotlib wants to enable its > users to > >produce figures ready for publication, right? > > > >Christian > > > >------------------------------------------------------------------------- > >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 > > > > > ---------End of Included Message---------- > > > > > > ------------------------------ > > ------------------------------------------------------------------------- > 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 > > > End of Matplotlib-users Digest, Vol 5, Issue 1 > ********************************************** > |
|
From: <ah...@cs...> - 2006-10-04 01:11:42
|
Hi,
I am trying to compile matplotlib in order to use numpy as the numerix
option. I can apt-get a version of it which works, but it does not seem t=
o
support numpy.
I also compiled numpy-1.0rc1 (released 2 weeks ago), and it works fine in
python. However, when I import matplotlib (0.87.6), I get the error
message below. A quick internet search suggests to me that it is some kin=
d
of mismatch in libraries, possibly caused by compiler differences in g++ =
4
(numpy at least seems to use g++.. so I tried a different g++ version,
but it made no difference).
Does someone have an idea what the problem is, or what I could try?
Thanks,
Allan
--------------------------------
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:
Traceback (most recent call last):
File "/usr/bin/ipython", line 28, in ?
IPython.Shell.start().mainloop()
File "/usr/lib/python2.4/site-packages/IPython/Shell.py", line 883, in
start
return shell()
File "/usr/lib/python2.4/site-packages/IPython/Shell.py", line 810, in
__init__
IPShellGTK.__init__(self,argv,user_ns,debug,shell_class=3DMatplotlibM=
TShell)
File "/usr/lib/python2.4/site-packages/IPython/Shell.py", line 618, in
__init__
on_kill=3D[mainquit])
File "/usr/lib/python2.4/site-packages/IPython/ipmaker.py", line 85, in
make_IPython
IP =3D shell_class('__IP',user_ns=3Duser_ns,**kw)
File "/usr/lib/python2.4/site-packages/IPython/Shell.py", line 500, in
__init__
user_ns,b2 =3D self._matplotlib_config(name)
File "/usr/lib/python2.4/site-packages/IPython/Shell.py", line 373, in
_matplotlib_config
from matplotlib import backends
File "/usr/lib/python2.4/site-packages/matplotlib/backends/__init__.py"=
,
line 55, in ?
new_figure_manager, draw_if_interactive, show =3D pylab_setup()
File "/usr/lib/python2.4/site-packages/matplotlib/backends/__init__.py"=
,
line 23, in pylab_setup
globals(),locals(),[backend_name])
File
"/usr/lib/python2.4/site-packages/matplotlib/backends/backend_gtkagg.py",
line 8, in ?
from matplotlib.figure import Figure
File "/usr/lib/python2.4/site-packages/matplotlib/figure.py", line 5, i=
n ?
from artist import Artist
File "/usr/lib/python2.4/site-packages/matplotlib/artist.py", line 4, i=
n ?
from transforms import identity_transform
File "/usr/lib/python2.4/site-packages/matplotlib/transforms.py", line
223, in ?
from _transforms import Value, Point, Interval, Bbox, Affine
File "/usr/lib/python2.4/site-packages/matplotlib/_transforms.py", line
17, in ?
from matplotlib._ns_transforms import *
ImportError:
/usr/lib/python2.4/site-packages/matplotlib/_ns_transforms.so: undefined
symbol: _ZNSt24__default_alloc_templateILb1ELi0EE8allocateEj
|
|
From: Zack <za...@gm...> - 2006-10-04 00:40:49
|
Hi,
I've got a problem some days ago doing saving the plots with certain resolution (dpi)
under windows. In this maillist I've found that in some cases dpi parameter is defined
in the source code. Moreover, there are more then _one_ definition of that parameter in
matplotlib. Can we get rid of this behaviour? It's quite confusing till one starts browse
the code by his own. For example I see absolutely no reasons to have more then one
such a parameter. And it should be defined only one time in the matplotlibrc.
Look at this. Is it not ugly ???
backend_bases.py:
def print_figure(self, filename, dpi=300, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_agg2.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_agg.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_cairo.py:
class FigureCanvasCairo (FigureCanvasBase):
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
def _save_ps_pdf (self, figure, filename, ext, orientation, **kwargs):
orientation = kwargs.get('orientation', 'portrait')
dpi = 72
backends/backend_emf.py:
hackoffsetper300dpi=10
xhack=math.sin(angle*math.pi/180.0)*hackoffsetper300dpi*self.dpi/300.0
yhack=math.cos(angle*math.pi/180.0)*hackoffsetper300dpi*self.dpi/300.0
def print_figure(self, filename, dpi=300, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_fltkagg.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_gdk.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_gd.py:
PIXELS_PER_INCH = 96 # constant GD uses for screen DPI
class FigureCanvasGD(FigureCanvasBase):
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_gtkagg.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_gtk.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_paint.py:
#paint/font.c defined dpi as 96
PIXELS_PER_INCH = 96 # a constant used to scale text with dpi
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait, '**kwargs):
backends/backend_pdf.py:
def print_figure(self, filename, dpi=72, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
self.figure.dpi.set(72)
backends/backend_ps.py:
def print_figure(self, outfile, dpi=72, facecolor='w', edgecolor='w',
orientation='portrait', papertype=None)
self.figure.dpi.set(72) # ignore the dpi kwarg
backends/backend_qt4agg.py:
def print_figure( self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs ):
backends/backend_qtagg.py:
def print_figure( self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs ):
backends/backend_svg.py:
self.figure.dpi.set(72)
backends/backend_template.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_tkagg.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
self.canvas.print_figure(fname, dpi=300)
backends/backend_wxagg.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
backends/backend_wx.py:
def print_figure(self, filename, dpi=150, facecolor='w', edgecolor='w',
orientation='portrait', **kwargs):
ps.figure.dpi.set(72)
__init__.py:
'figure.dpi' : [ 80, validate_float], # DPI
'savefig.dpi' : [ 150, validate_float], # DPI
'ps.distiller.res' : [6000, validate_int], # dpi
mathtext.py:
w, h, fonts = math_parse_s_ft2font(s, dpi=27, fontsize=12, angle=0)
if get_backend()=='PS': dpi = 72
matplotlibrc:
figure.dpi : 80 # figure dots per inch
savefig.dpi : 100 # figure dots per inch
ps.distiller.res : 6000 # dpi
It is just a mess! Please do something with that!
--
Zack
|
