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
(8) |
|
2
(2) |
3
(8) |
4
(19) |
5
(19) |
6
(25) |
7
(8) |
8
(1) |
|
9
|
10
(15) |
11
(22) |
12
(8) |
13
(4) |
14
(1) |
15
|
|
16
(1) |
17
(20) |
18
(17) |
19
(13) |
20
(17) |
21
(7) |
22
(5) |
|
23
(6) |
24
(14) |
25
(14) |
26
(18) |
27
(21) |
28
(5) |
29
(9) |
|
30
(6) |
|
|
|
|
|
|
|
From: Glen W. M. <Gle...@sw...> - 2006-04-19 20:09:52
|
Hello,
I'm in the process of migrating some software I've written from a
machine with MPL 0.86.2 on it to another with 0.87.2 .
The app is Qt-based with MPL embedded as a widget. The plot itself uses
dates on the x-axis.
It appears that the behavior of autoscale_view() changed quite a bit
somewhere between these two versions.
In my application I create a patches.Rectangle that is 100 seconds wide:
start_time_num = matplotlib.dates.date2num( start_time )
lower_left = [ matplotlib.dates.date2num( start_time ), start_y ]
width = matplotlib.dates.date2num( start_time + datetime.timedelta( seconds=10 ) ) - start_time_num
r = matplotlib.patches.Rectangle( lower_left, width, height )
With the 0.86.2 version, the total span of the x-axis after an
autoscale_view() call is about 12 seconds. For the 0.87.2 version
however, the span is more than 200 years. (see attached .png files)
I don't see this type of behavior in the pylab environment, yet I'm
having a hard time creating a concise example that demonstrates the
behavior.
I can keep working on extracting an snippet, but I thought I'd ask
if this is some intended behavioral change, and if so, if there is a
workaround.
Thank you!
Glen Mabey
|
|
From: ark p. <ar...@gm...> - 2006-04-19 19:34:17
|
On 4/19/06, Marin Manuel <mar...@gm...> wrote: > > christophe wrote: > > > Hi, > > > > Type error : RuntimeError* > > *Error value : Could not open file /home/image.png > > > What path did you try ? From this error message it seems you tried to > save in the /home folder where you dont have write permission. Try to > save in /home/christophe/image.png (replace christophe by whatever your > user name is) > it's the same problem with any path |
|
From: Eric F. <ef...@ha...> - 2006-04-19 17:52:15
|
It sounds like there are two questions here: whether the colorbar=20 correctly tracks the actual color mapping used in the image or contour=20 plot or whatever (it should always do this, but I think that at present=20 it does not), and whether the limits should change even if the mapping=20 does not. I think the behavior you request is sensible, so that would=20 be my target, either as a standard behavior or as an option. Thanks for=20 pointing out this aspect of the problem. There is another problem with the colorbar code, and I have been trying=20 to decide how to handle that before looking at the update question, so I=20 have not resolved either one yet. Eric Jo=C3=A3o Lu=C3=ADs Silva wrote: > Eric Firing wrote: >=20 >> Andrea, >> >> I agree, the colorbar should dynamically update. A workaround might=20 >> be to simply call colorbar every time you update the image data. >> >> At least part of a longer-term solution may be to change colorbar so=20 >> that instead of always using contourf, it uses imshow when it is being= =20 >> used with a nearly continuous set of colors instead of a small=20 >> discrete set. >> >> I have not had time to look at this closely, but I can add it to my li= st. >> >> Eric >> >=20 > Although updating the colorbar when the image data changes should be th= e=20 > default behaviour will there be a way to keep the colorbar from=20 > changing? I've got a visualization application where an image changes=20 > according to the position it's currently displaying but I want to keep=20 > the colorbar that reflects the largest value. Right now I just display=20 > first the image that has the largest value and the colorbar stays the=20 > same. Whatever the buggy behaviour an application has someone is taking= =20 > advantage of it :-) >=20 > Jo=C3=A3o Silva >=20 >=20 >=20 > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting lang= uage > that extends applications into web and mobile media. Attend the live=20 > webcast > and join the prime developer group breaking into this new coding territ= ory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users |
|
From: Andrew B. Y. <and...@sr...> - 2006-04-19 16:09:12
|
How can one partially overlay text on top of text so as to obscure
the underlying text?
I want to print a beginning date at (0,0) and the current date
at (0.1,0) such that the current date's bounding box masks the
underlying beginning date. What currently happens is the two dates
blend together to form a mess. (I am creating an mpeg4 where the
current date marches from beginning to end.)
I have tried two things: set a bounding box, set a background color.
rectangle = matplotlib.patches.Rectangle( (0,0), 0, 0 )
rectangle.set_fill( True )
# Drawing beginning date
s = "%s UTC" % beginning.strftime( "%Y-%m-%d %H:%M" )
t = matplotlib.text.Text( 0.0, 0.0, s )
t.set_bbox( rectprops = rectangle.__dict__ )
t.set_backgroundcolor( color='r' )
axes.add_artist( t )
# Draw current date
txt = "%s UTC" % now.strftime( "%Y-%m-%d %H:%M" )
t = matplotlib.text.Text( x, 0.0, s )
t.set_bbox( rectprops = rectangle.__dict__ )
t.set_backgroundcolor( color='r' )
axes.add_artist( t )
The set_background color seems to do nothing.
The set_bbox raises the following--
File "/usr/lib/python2.4/site-packages/matplotlib/artist.py", line
193, in update
raise AttributeError('Unknown property %s'%k)
AttributeError: Unknown property _facecolor
Thanks,
Andrew
Python 2.4, __version__ = '0.85', __revision__ = '$Revision: 1.83 $'
|
|
From: Marin M. <mar...@gm...> - 2006-04-19 16:05:50
|
christophe wrote: > Hi, > > Type error : RuntimeError* > *Error value : Could not open file /home/image.png > What path did you try ? From this error message it seems you tried to save in the /home folder where you dont have write permission. Try to save in /home/christophe/image.png (replace christophe by whatever your user name is) |
|
From: Stefan v. d. W. <st...@su...> - 2006-04-19 16:02:56
|
Here is a one-line patch to make setup complain if tk.h isn't found. St=E9fan |
|
From: Stefan v. d. W. <st...@su...> - 2006-04-19 15:45:40
|
Hi Etienne On Wed, Apr 19, 2006 at 11:02:41AM -0400, Etienne Ringuet wrote: > I am trying to build matplotlib on a freshly installed CentOS 4 worksta= tion. >=20 > > error: Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe > -m32 -march=3Di386 -mtune=3Dpentium4 -D_GNU_SOURCE -fPIC -fPIC > -I/usr/share/tcl8.4/../../include -I/usr/share/tk8.4/../../include > -I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include -I= . > -I/usr/local/include -I/usr/include -I. > -I/usr/share/tcl8.4/../../include/freetype2 > -I/usr/share/tk8.4/../../include/freetype2 > -I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2 > -Isrc/freetype2 -Iswig/freetype2 -Iagg23/include/freetype2 -I./freetype= 2 > -I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2 > -I/usr/include/python2.3 -c src/_tkagg.cpp -o > build/temp.linux-i686-2.3/src/_tkagg.o" failed with exit status 1 > > I also have an error at the beginning that says I miss tk.h, my system = is in > french so I will not paste this part. I just ran into this problem again myself, on an Ubuntu machine. It has been present for a while. A quick fix is to edit 'setup.py' and change the line BUILD_TKAGG =3D 'auto' to BUILD_TKAGG =3D 0 Another solution is to install the Tk development headers. Under Ubuntu it is in the package tk8.4-dev. This is probably something that should be caught by setup.py before building though! Regards St=E9fan |
|
From: Johann R. <jr...@su...> - 2006-04-19 15:12:21
|
On Wednesday, 19 April 2006 17:02, Etienne Ringuet wrote: > [root@institut-c33109 matplotlib-0.87.2]# rpm -qa | grep pygtk > pygtk2-2.4.0-1 Have you installed the "devel" version of the package (contains headers required for compilation)? Johann |
|
From: Etienne R. <eri...@gm...> - 2006-04-19 15:02:53
|
Hi, This is my first post to the list so hi everyone! I am trying to build matplotlib on a freshly installed CentOS 4 workstation. I have read the FAQ about build problems with pygtk 2.4 is the problem fixed in my version? [root@institut-c33109 matplotlib-0.87.2]# rpm -qa | grep pygtk pygtk2-2.4.0-1 When I try python setup.py build it ends with: error: Command "gcc -pthread -fno-strict-aliasing -DNDEBUG -O2 -g -pipe -m32 -march=i386 -mtune=pentium4 -D_GNU_SOURCE -fPIC -fPIC -I/usr/share/tcl8.4/../../include -I/usr/share/tk8.4/../../include -I/usr/local/include -I/usr/include -I. -Isrc -Iswig -Iagg23/include -I. -I/usr/local/include -I/usr/include -I. -I/usr/share/tcl8.4/../../include/freetype2 -I/usr/share/tk8.4/../../include/freetype2 -I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2 -Isrc/freetype2 -Iswig/freetype2 -Iagg23/include/freetype2 -I./freetype2 -I/usr/local/include/freetype2 -I/usr/include/freetype2 -I./freetype2 -I/usr/include/python2.3 -c src/_tkagg.cpp -o build/temp.linux-i686-2.3/src/_tkagg.o" failed with exit status 1 I also have an error at the beginning that says I miss tk.h, my system is in french so I will not paste this part. Thanks for your help and time, Etienne |
|
From: christophe <ar...@gm...> - 2006-04-19 14:37:16
|
Hi,
when I use savefig() to save the image, it saves it in the bin directory
of the instance (../instance/bin/)
when I try to pass the path in the name (savefig('path/image.png')), I
get an error :*
Type error : RuntimeError*
*Error value : Could not open file /home/image.png
*How can I set the save directory ?
thks
|
|
From: John H. <jdh...@ac...> - 2006-04-19 13:09:10
|
>>>>> "andrea" == andrea gavana@tin it <and...@ti...> writes:
andrea> Hello John & NG, thank you very much for your answer. I
andrea> had actually make it working using Line2D instances for
andrea> every point in the plot (every well location has its own
andrea> Line2D object associated). It works reasonably well, but I
andrea> have some doubts about my implementation... First of all,
andrea> I don't know how actually *delete* a Line2D from the plot
ax.lines.remove(someline)
andrea> (when the well should be hidden) and, moreover, when I
andrea> have a large number of wells it takes quite a long time to
andrea> create all the Line2D instances and plot them... Do you
andrea> think it will work faster/better if I use a
andrea> RegularPolyCollection?
Yes, plotting a large number of Line2D instances will be significantly
slower than using a collection. Give it a try!
JDH
|
|
From: <and...@ti...> - 2006-04-19 10:07:39
|
Hello John & NG,
thank you very much for your answer. I had
actually make it working using Line2D instances for every point in the
plot (every well location has its own Line2D object associated). It
works reasonably well, but I have some doubts about my
implementation...
First of all, I don't know how actually *delete* a
Line2D from the plot (when the well should be hidden) and, moreover,
when I have a large number of wells it takes quite a long time to
create all the Line2D instances and plot them...
Do you think it will
work faster/better if I use a RegularPolyCollection?
Thank you very
much for your suggestions.
Andrea.
>----Original Message----
>From:
jdh...@ac...
>Date: 18-Apr-2006 16:16
>To:
"and...@ti..."<and...@ti...>
>Cc: <matplotlib-
us...@li...>
>Subj: Re: [Matplotlib-users] Single Point
Stored Plot
>
>>>>>> "andrea" == andrea gavana@tin it
<and...@ti...> writes:
>
> andrea> Hello NG, I am facing a
small problem for which I was
> andrea> unable to find a solution.
Basically, I have to make a
> andrea> scatter plot of x, y
coordinates (they represents oil
> andrea> wells positions) on a 2D
map, but I have some constraints:
>
> andrea> 1) I would like to
have each point as a separate "plot
> andrea> object", because the
user may decide to hide/show only a
> andrea> particular well, or
show/hide them all, or show/hide
> andrea> whatever combination of
wells. 2) At the moment when the
> andrea> class that holds a
single well position/status is created,
> andrea> the plot window
may not be there (because is the user that
> andrea> decides when to
open a new plot window).
>
> andrea> I have tried something like:
>
>Hey Andrea, sorry for the delay. This is a neat problem and one that
>collections were designed to solve. You probably want to use a
>RegularPolyCollection rather than a PolyCollection (the latter is for
>arbitrary polygons and you must compute all the vertices yourself).
>Here is an example that allows you to add and delete markers -- it
>inserts them with random positions and colors. You should be able to
>adapt it to your application quite easily.
>
>import random
>from
matplotlib.colors import colorConverter
>from matplotlib.collections
import RegularPolyCollection
>import matplotlib.cm as cm
>from pylab
import figure, show, nx
>
>fig = figure()
>ax = fig.add_subplot(111,
xlim=(0,1), ylim=(0,1), autoscale_on=False)
>ax.set_title("Press 'a' to
add a point, 'd' to delete one")
># a single point
>offsets =
[(0.5,0.5)]
>facecolors = [cm.jet(0.5)]
>
>collection =
RegularPolyCollection(
> fig.dpi,
> numsides=5, # a pentagon
>
rotation=0,
> sizes=(50,),
> facecolors = facecolors,
>
edgecolors = (colorConverter.to_rgba('black'),),
> linewidths =
(1,),
> offsets = offsets,
> transOffset = ax.transData,
> )
>
>ax.add_collection(collection)
>
>def onpress(event):
> """
>
press 'a' to add a random point from the collection, 'd' to delete one
> """
> if event.key=='a':
> x,y = nx.mlab.rand(2)
> color = cm.jet(nx.mlab.rand())
> offsets.append((x,y))
> facecolors.append(color)
> fig.canvas.draw()
> elif
event.key=='d':
> N = len(offsets)
> if N>0:
>
ind = random.randint(0,N-1)
> offsets.pop(ind)
>
facecolors.pop(ind)
> fig.canvas.draw()
>
>fig.canvas.
mpl_connect('key_press_event', onpress)
>
>show()
>
|
|
From: <rom...@ya...> - 2006-04-19 10:05:41
|
Eric Firing wrote: > Andrea, > > I agree, the colorbar should dynamically update. A workaround might be > to simply call colorbar every time you update the image data. > > At least part of a longer-term solution may be to change colorbar so > that instead of always using contourf, it uses imshow when it is being > used with a nearly continuous set of colors instead of a small discrete > set. > > I have not had time to look at this closely, but I can add it to my list. > > Eric > Although updating the colorbar when the image data changes should be the default behaviour will there be a way to keep the colorbar from changing? I've got a visualization application where an image changes according to the position it's currently displaying but I want to keep the colorbar that reflects the largest value. Right now I just display first the image that has the largest value and the colorbar stays the same. Whatever the buggy behaviour an application has someone is taking advantage of it :-) João Silva |