SourceForge logo
SourceForge logo
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
(2)
3
(16)
4
(22)
5
(7)
6
7
(9)
8
(2)
9
10
(7)
11
(15)
12
(7)
13
(4)
14
(7)
15
(3)
16
(6)
17
(20)
18
(18)
19
(15)
20
(27)
21
(14)
22
23
(1)
24
(18)
25
(22)
26
(36)
27
(17)
28
(6)
29
(2)
30
(3)
31
(6)





Showing 6 results of 6

From: Philipp K. J. <py...@be...> - 2010年05月16日 22:04:15
Thanks, that was helpful.
On Sunday 16 May 2010 02:23:02 pm Eric Firing wrote:
> On 05/16/2010 10:19 AM, Philipp K. Janert wrote:
> > Let's say I am running an interactive session
> > (ipython -pylab), and now issue the following
> > commands:
> >
> > 	x = linspace(0, 10, 100 )
> > 	plot( x, sin(x) )
> > 	ylim( -2, 2 )
> > 	plot( x, cos(x) )
> >
> > Then the second plot command seems to reset
> > the plot limits to [-1,1] - which makes sense for
> > the figure, but is not what I requested.
> >
> > Is this behavior intended? It seems odd to me,
> > since generally matplotlib seems to retain state
> > that has between invocations of plot().
>
> Good question. The control of autoscaling has a somewhat clunky
> interface via Axes methods, and via the plot function. Your two options
> are to follow the ylim call with the ugly
>
> gca().set_autoscaley_on(False)
>
> or to add a kwarg to all subsequent plot calls:
>
> plot(x, cos(x), scaley=False)
>
> A possible mpl improvement would be to add a kwarg to the pyplot.ylim
> and xlim functions, e.g.
>
> ylim(-2, 2, keep=True)
>
> Calling the kwarg "hold" would read better to my eye, but would conflict
> with the use of "hold" to mean "keep all prior plot elements". Maybe
> there is a better name, e.g. setting "auto=False" to mean "don't
> autoscale this on the next plot command". Or "save=True". I suspect we
> would have to leave the default behavior as it is for continuity and
> backwards compatibility, although I think that changing it would be an
> improvement overall.
>
> Eric
>
>
> ---------------------------------------------------------------------------
>---
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
From: Eric F. <ef...@ha...> - 2010年05月16日 21:23:12
On 05/16/2010 10:19 AM, Philipp K. Janert wrote:
>
> Let's say I am running an interactive session
> (ipython -pylab), and now issue the following
> commands:
> 	
> 	x = linspace(0, 10, 100 )
> 	plot( x, sin(x) )
> 	ylim( -2, 2 )
> 	plot( x, cos(x) )
>
> Then the second plot command seems to reset
> the plot limits to [-1,1] - which makes sense for
> the figure, but is not what I requested.
>
> Is this behavior intended? It seems odd to me,
> since generally matplotlib seems to retain state
> that has between invocations of plot().
Good question. The control of autoscaling has a somewhat clunky 
interface via Axes methods, and via the plot function. Your two options 
are to follow the ylim call with the ugly
gca().set_autoscaley_on(False)
or to add a kwarg to all subsequent plot calls:
plot(x, cos(x), scaley=False)
A possible mpl improvement would be to add a kwarg to the pyplot.ylim 
and xlim functions, e.g.
ylim(-2, 2, keep=True)
Calling the kwarg "hold" would read better to my eye, but would conflict 
with the use of "hold" to mean "keep all prior plot elements". Maybe 
there is a better name, e.g. setting "auto=False" to mean "don't 
autoscale this on the next plot command". Or "save=True". I suspect we 
would have to leave the default behavior as it is for continuity and 
backwards compatibility, although I think that changing it would be an 
improvement overall.
Eric
From: Philipp K. J. <py...@be...> - 2010年05月16日 20:19:51
Let's say I am running an interactive session 
(ipython -pylab), and now issue the following
commands:
	
	x = linspace(0, 10, 100 )
	plot( x, sin(x) )
	ylim( -2, 2 )
	plot( x, cos(x) )
Then the second plot command seems to reset
the plot limits to [-1,1] - which makes sense for 
the figure, but is not what I requested.
Is this behavior intended? It seems odd to me,
since generally matplotlib seems to retain state 
that has between invocations of plot().
Best,
		Ph.
From: Philipp K. J. <py...@be...> - 2010年05月16日 19:45:53
 
Assume I am running an interactive session, using
 ipython -pylab
and have added a bunch of curves
 x = linspace(0, 10, 100 )
 plot( x, sin(x) )
 plot( x, cos(x) )
and also added a text label
 text( 1, 1, "Hello" )
But now I decide that I don't want the text anymore.
What's the best way to remove it from the graph?
(Because the graph is complicated I don't just want 
to clf() and start all over - I just want to remove that
one element.)
What I have found is that if I save the object created,
I can invoke its remove() function:
 t =text( 2, 1, "Hello again" )
 t.remove()
 draw()
Is this the best way to do this, or is there another way
(or one that does not require an explicit draw()?). Also,
what if I have failed to save the text instance - do I have
to walk the object tree using findobj()?
Thanks!
Best,
 Ph.
From: Fabrice S. <si...@lm...> - 2010年05月16日 19:08:06
FIY, with the help of Sylvestre Ledru (debian atlas maintainer), the
problem was solved installing libatlas3g-sse*.
From: Tomáš F. <sen...@em...> - 2010年05月16日 14:05:34
Hello,
I am writing a GUI using GTK+ library. I have a question about axes class imshow method memory consumption. If I pass the imshow an array, the resulting memory consuption is approximatelly 40 times greater than the array size. If I do not add the canvas to a window (in a code below), the memory consuption is as expected. Any tips on how to reduce the memory consuption would be very appreciated. Configuration and script are below.
os: Windowx XP
matplotlib version: 0.99.1
downloaded from: sourceforge.net
script:
from matplotlib.figure import Figure
from matplotlib.backends.backend_gtkagg import FigureCanvasGTKAgg
from pylab import rand
import gtk
window = gtk.Window()
window.connect("destroy", gtk.main_quit)
figure = Figure(figsize=(8,6), dpi=72)
canvas = FigureCanvasGTKAgg(figure)
axes = figure.add_subplot(111)
window.add(canvas)
axes.imshow(rand(1024,1024))
canvas.draw()
window.show_all()
gtk.main()
verbose-helpful output:
$HOME=C:\Documents and Settings\Sensej
CONFIGDIR=C:\Documents and Settings\Sensej\.matplotlib
matplotlib data path C:\Python26\lib\site-packages\matplotlib\mpl-data
loaded rc file C:\Python26\lib\site-packages\matplotlib\mpl-data\matplotlibrc
matplotlib version 0.99.1
verbose.level helpful
interactive is False
units is False
platform is win32
Using fontManager instance from C:\Documents and Settings\Sensej\.matplotlib\fontList.cache
backend GTKAgg version 2.12.1
findfont: Matching :family=sans-serif:style=normal:variant=normal:weight=normal:stretch=normal:size=medium to Bitstream Vera Sans (C:\Python26\lib\site-packages\matplotlib\mpl-data\fonts\ttf\Vera.ttf) with score of 0.000000
Thank you,
Tomas.

Showing 6 results of 6

Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X





Briefly describe the problem (required):
Upload screenshot of ad (required):
Select a file, or drag & drop file here.
Screenshot instructions:

Click URL instructions:
Right-click on the ad, choose "Copy Link", then paste here →
(This may not be possible with some types of ads)

More information about our ad policies

Ad destination/click URL:

AltStyle によって変換されたページ (->オリジナル) /