matplotlib-users Mailing List for matplotlib (Page 3)

Sorry, just realized that I didn't send this to the
list:
John,
I've been running the same examples in all of the
IDE's with the WX backend without any problems. I ran
them again when I saw this message. To the examples I
just add the two lines:
import matplotlib
matplotlib.use("WXAgg")
and all is well. Without these lines the graph
windows freeze (in WinXP).
However, after upgrading to version 0.5.4.2 there is a
new problem: after show() is run, the app quits and
the window disappears without any diagnostic output. 
This happens with all of the examples that I've tried
so far. Before the upgrade they were working fine.
I haven't started debugging this yet. Any ideas?
System:
Win XP Pro, 1GB RAM, Pentium 4 2.6GHz
Python 2.3.3, GTK-Runtime-Environment-2.2.4-3,
pygtk-2.2.0-1.win32-py2.3
Regaards,
Barry Drake
--- John Hunter wrote:
> >>>>> "Ryugan" == Ryugan Mizuta
> <ryu...@sb...> writes:
> 
> Ryugan> Sorry, I'm a newbie and needed
some help
> to get started.
> Ryugan> I downlaoded the Enthought
version(for
> WXPython) which is
> Ryugan> recommended in the web-site and
> downloaded the latest
> Ryugan> version of matplot. I'm trying to
go
> through the tutorial
> Ryugan> and I'm stuck with the first
example. 
> The following is
> Ryugan> what I wrote down on the script:
> 
> Ryugan> import matplotlib
matplotlib.use("WX")
> 
> Ryugan> from matplotlib.matlab import *
> plot([1,2,3,4]) show()
> 
> Ryugan> When I run this script it creates
a
> graph but the the
> Ryugan> window freezes....
> 
> Ryugan> Anybody have any suggestions on
how I
> can fix this...????
> 
> I'll bet dollars to donuts you are running
> matplotlib inside an IDE,
> eg Idle, PythonWin, Scintilla, etc. Quoting from
> http://matplotlib.sourceforge.net/installing.html
> 
> Important: There are known conflicts with some
of
> the backends with
> some python IDEs such as pycrust, idle. If you
> want to use
> matplotlib from an IDE, please consult the
> backends documentation
> for compatibility information. You will have
the
> greatest likelihood
> of success if you run the examples from the
> command shell or by
> double clicking on them, rather than from an
IDE.
> If you are
> interactively generating plots, your best bet
is
> TkAgg from the
> standard python shell.
> 
> The "backends" page, referred to above, is at
> http://matplotlib.sourceforge.net/backends.html. 
> Basically, you
> should open up a command shell and try to run one
of
> the examples from
> the matplotlib src distribution (the *.zip file
for
> windows users);
> Eg,
> 
> c:\matplotlib\examples> python
simple_plot.py
> 
> if this works fine (my guess is it will), then
> you'll know you have an
> IDE problem and not a matplotlib specific
problem. 
> Unfortunately,
> this problem tends to crop up a lot. See for
> example
>
http://sourceforge.net/mailarchive/message.php?msg_id=8610351
> and the
> responses to that post for more information
> 
> 
> Let me know if this is the case. 
> 
> JDH
> 
> 
> 
>
-------------------------------------------------------
> This SF.Net email is sponsored by The 2004
> JavaOne(SM) Conference
> Learn from the experts at JavaOne(SM), Sun's
> Worldwide Java Developer
> Conference, June 28 - July 1 at the Moscone
Center
> in San Francisco, CA
> REGISTER AND SAVE! http://java.sun.com/javaone/sf
> Priority Code NWMGYKND
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
>
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

>>>>> "Istvan" == Istvan Albert <iu...@ps...> writes:
 Istvan> Hello Folks, At the end of a batch script using
 Istvan> matplotlib, once I close the plot window I'm getting a
 Istvan> python prompt:
 >>>>
This question comes up fairly often, so I added a FAQ entry to cover
it
 http://matplotlib.sourceforge.net/faq.html#PROMPT
Cheers!
JDH

Hello Folks,
At the end of a batch script using matplotlib, once I close the
plot window I'm getting a python prompt:
 >>>
that waits for input.
I searched the docs but I did not see this
mentioned. What do I need to do to have the
script exit once I close the plot window?
thanks,
Istvan.

>>>>> "Ryugan" == Ryugan Mizuta <ryu...@sb...> writes:
 Ryugan> Sorry, I'm a newbie and needed some help to get started.
 Ryugan> I downlaoded the Enthought version(for WXPython) which is
 Ryugan> recommended in the web-site and downloaded the latest
 Ryugan> version of matplot. I'm trying to go through the tutorial
 Ryugan> and I'm stuck with the first example. The following is
 Ryugan> what I wrote down on the script:
 Ryugan> import matplotlib matplotlib.use("WX")
 Ryugan> from matplotlib.matlab import * plot([1,2,3,4]) show()
 Ryugan> When I run this script it creates a graph but the the
 Ryugan> window freezes....
 Ryugan> Anybody have any suggestions on how I can fix this...????
I'll bet dollars to donuts you are running matplotlib inside an IDE,
eg Idle, PythonWin, Scintilla, etc. Quoting from
http://matplotlib.sourceforge.net/installing.html
 Important: There are known conflicts with some of the backends with
 some python IDEs such as pycrust, idle. If you want to use
 matplotlib from an IDE, please consult the backends documentation
 for compatibility information. You will have the greatest likelihood
 of success if you run the examples from the command shell or by
 double clicking on them, rather than from an IDE. If you are
 interactively generating plots, your best bet is TkAgg from the
 standard python shell.
The "backends" page, referred to above, is at
http://matplotlib.sourceforge.net/backends.html. Basically, you
should open up a command shell and try to run one of the examples from
the matplotlib src distribution (the *.zip file for windows users);
Eg,
 c:\matplotlib\examples> python simple_plot.py
if this works fine (my guess is it will), then you'll know you have an
IDE problem and not a matplotlib specific problem. Unfortunately,
this problem tends to crop up a lot. See for example
http://sourceforge.net/mailarchive/message.php?msg_id=8610351 and the
responses to that post for more information
Let me know if this is the case. 
JDH

Sorry, I'm a newbie and needed some help to get started.
I downlaoded the Enthought version(for WXPython) which is recommended =
in the web-site and downloaded the latest version of matplot. I'm =
trying to go through the tutorial and I'm stuck with the first example. =
The following is what I wrote down on the script:
import matplotlib
matplotlib.use("WX")
from matplotlib.matlab import *
plot([1,2,3,4])
show()
When I run this script it creates a graph but the the window freezes....
Anybody have any suggestions on how I can fix this...????
Thanks.
Ryugan

Hi John:
> plot_date looks at the range of your date data and tries to pick the 
> appropriate
> date tick locator based on that range (ie a YearLocator, MonthLocator,
> MinuteLocator, etc). 
It does?! Do you mean that this is done automatically? Can you show me 
an example of this using only the time module (since I use python2.2, 
dont have datetime)? I thought that I had to manually set things up and 
tell matplotlib whether to use YearLocator, MonthLocator, etc.. via 
calls to: axes.xaxis.set_minor_locator(), 
axes.xaxis.set_major_locator(), axes.xaxis.set_major_formatter().
In other words for every plot, check the time range of my data, figure 
out how many ticks I want, and decide whether to use months, days, 
hours, etc...
In fact, because I was getting some inconsistent results with using the 
above, I decided that for the most part (excluding a few special cases), 
I would print the time ticks myself 'manually'. The script below shows 
what I mean.
On the other note, regarding the weird scaling that I talked about (and 
showed pretty pics for) in my last mail, I finally put together a small 
script that exposes the problem. It is a bit rough because I ripped bits 
and pieces from here and there, but shows the issue. Use the 
'wantBadPlot' and 'wantStandardDateTics' to see how things go wrong.
--------------------------------
#!/usr/bin/env python
import time
from matplotlib.dates import EpochConverter
from matplotlib.matlab import *
from matplotlib.ticker import FuncFormatter, NullLocator, 
MinuteLocator, DayLocator, HourLocator, MultipleLocator, DateFormatter
wantBadPlot=1
wantStandardDateTics=1
wantLegend=1
if wantBadPlot:
 time1=[1087192789.89]
 data1=[-65.54]
else:
 time1=[1087192289.89, 1087193789.89]
 data1=[-44.343, -65.54]
 time2=[
1087161589.89 ,
1087192289.0,
1087192389.0,
1087192489.0,
1087192589.0,
1087192689.0,
1087192789.89 ,
1087192889.0,
1087192989.0,
1087193089.0,
1087193189.0,
1087193289.0,
1087238100.0 ,
]
data2=[
-55.44
-64.54 ,
-66.54 ,
-61.54 ,
-69.54 ,
-45.66,
-55.54 ,
-77.54,
-65.54 ,
-49.54 ,
-57.54 ,
-68.54 ,
-55.54 ,
-23.44
]
ax = subplot(111)
p1Size=len(time1)
p2Size=len(time2)
p1=plot_date(time1, data1, None, '-', color='r')
p2=plot_date(time2, data2, None, '-', color='b')
if wantStandardDateTics:
 fmt=DateFormatter('%H:%M')
 hours=HourLocator(4)
 ax.xaxis.set_minor_locator(NullLocator())
 ax.xaxis.set_major_locator(hours)
 ax.xaxis.set_major_formatter(fmt)
 ax.autoscale_view()
else:
 #Manually display dates for tick-labels. Technically could use plot() 
and
 #get the same result.
 now=time2[-1]
 then=time2[0]
 deltaSec=now-then
 deltaTickSec=deltaSec/7.0
 tickList=[item for item in list(arange(then, now, deltaTickSec))]
 def tickString(x, pos):
 return time.strftime("%H:%M:%S", time.localtime(x))
 formatter = FuncFormatter(tickString)
 ax.set_xticks(tickList)
 ax.xaxis.set_major_formatter(formatter)
 ax.xaxis.set_minor_locator(NullLocator())
 ax.autoscale_view()
 #This will fix the problem!!
 #ax.set_xlim((then, now))
if wantLegend:
 legend((p1, p2), ('small data set (%d)' % p1Size, 'large data set 
(%d)' % p2Size))
xlabel('time')
grid(True)
show()
#savefig('./blah.png')
-------------------------------
Any ideas?
Finally, just want to verify (form my last email) that in axes.py:
 def get_ylim(self):
 "Get the y axis range [ymin, ymax]"
 return self.viewLim.intervalx().get_bounds()
should intervax() be intervaly()??
Thanks,
-- 
Peter Groszkowski Gemini Observatory
Tel: +1 808 974-2509 670 N. A'ohoku Place
Fax: +1 808 935-9235 Hilo, Hawai'i 96720, USA
John Hunter wrote:
>>>>>> "Peter" == Peter Groszkowski <pio...@ho...> writes:
>>>>>> 
>>>>>
>
> Peter> I found another issue with plot_date. Dont have a simple
> Peter> example yet, and hope that this is something 'obvious' and
> Peter> I don't have to bother.
>
> There is clearly something wrong with the autoscale function of one of
> the date tick locators. It would help to know which one. plot_date
> looks at the range of your date data and tries to pick the appropriate
> date tick locator based on that range (ie a YearLocator, MonthLocator,
> MinuteLocator, etc). If I knew which tick locator was behaving badly,
> it would help me fix the problem.
>
> If you
> print ax.xaxis._majorLocator
>
> after the call to plot_date, and let me know which locator it is, I
> can probably figure out where the problem is. To simplify, don't
> explicitly set the date xlim range when you do this.
>
> On a side note, in your example code you call
>
> ax.viewLim.intervalx().set_bounds(minXValueImPlotting, 
> maxXValueImPlotting)
>
> I assume you did this to narrow down the possible causes of problems.
> As you know, this is the call that ax.set_xlim makes under the hood.
> But in general, it's safest to stick to the axes API, ie, call
>
> ax.set_xlim(minXValueImPlotting, maxXValueImPlotting)
>
> since this interface is guaranteed to be stable.
>
> JDH
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by the new InstallShield X.
> From Windows to Linux, servers to mobile, InstallShield X is the
> one installation-authoring solution that does it all. Learn more and
> evaluate today! http://www.installshield.com/Dev2Dev/0504
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
>

>>>>> "Flavio" == Flavio Codeco Coelho <fcc...@fi...> writes:
 Flavio> Hi, This subject has already come up before and John
 Flavio> suggested using
 Flavio> f = figure(1, frameon=False)
 Flavio> for a totally transparent background which works fine as
 Flavio> an optional argumento to subplot in the matlab interface
 Flavio> subplot(111, frameon=False)
 Flavio> I want to know what would be the equivalent to
 Flavio> f._figurePatch.set_alpha(0.0)
 Flavio> for the matlab interface, since subplot does not have a
 Flavio> _figurePatch atribute.
I'm not sure exactly what you are asking. Axes and Subplot don't have
a _figurePatch, but they do have an _axesPatch, which as you note you
can turn off by using frameon=False. If you want to set it's alpha,
do
 ax = subplot(111)
 frame = ax.get_frame()
 frame.set_alpha(0.0)
Is this what you are looking for?
JDH

>>>>> "Mark" == Mark Engelhardt <ma...@st...> writes:
 Mark> If I have axis labels with line returns in them, they end up
 Mark> overlapping with the plot area and other elements in the
 Mark> figure. Is there a way to change their placement to move
 Mark> them away from the plot? Is there a way to define the area
 Mark> occupied by a subplot to include the axis labels and titles
 Mark> such that multiple subplots do not have overlapping text?
 Mark> (This is related to another question I just posted, but I
 Mark> tried to separate these issues for easier referencing by
 Mark> others later on).
There is no way to do this automatically at present. You can
explicitly define the size of your axes so that they don't overlap
each other, but this can take some trial and error. subplot is just a
special case of axes that specifies the left, bottom, width, height
rectangle of the axes in a matlab consistent way.
The axes coordinates are normalized as fractions of the entire
figure. See ganged_plots and axes_demo.py in the examples directory
of the matplotlib src distribution for examples of setting the axes
boundaries explicitly.
It is possible to write some automatic axes layout functions similar
to the ones you are looking for, eg, place axes 2 below axes 1 taking
into account tick labels and so on, but they doesn't currently exist.
It's also possible to write some GUI interaction code so these can be
dynamically resized - I can post some example code if you like.
The other things you may want to consider are
 * decreasing the tick padding (the spacing between the axes and tick label
 With the latest matplotlib this is controlled by tick.major.pad in
 the rc file
 * use a smaller tick font size, controlled by tick.labelsize
Hope this helps,
JDH

Hi,
I've spent a while searching for the answer to this, and I'm at the 
point of giving up... but it seems like it should be easy.
If I have axis labels with line returns in them, they end up 
overlapping with the plot area and other elements in the figure. Is 
there a way to change their placement to move them away from the plot? 
Is there a way to define the area occupied by a subplot to include the 
axis labels and titles such that multiple subplots do not have 
overlapping text? (This is related to another question I just posted, 
but I tried to separate these issues for easier referencing by others 
later on).
Thanks,
Mark

Hi,
Is there a way to change the spacing between subplots when using 
multiple subplots per figure? I'm getting overlap between titles and 
x-labels.
Thanks,
Mark

Mr. Hunter,
Thank you for your reply. I am considering trying to develop the 2D
vector field plots myself using line collections, as you suggest.
Cheers,
Curtis
On 2004年6月12日, John Hunter wrote:
> >>>>> "Curtis" == Curtis Cooper <cu...@hi...> writes:
>
> Curtis> Hi, I am excited about the relatively new imshow and
> Curtis> pcolor features in matplotlib. I am using numarray to
> Curtis> reduce/diagnose planetary atmospheres simulations, which
> Curtis> consist of temperature and velocity data on gridpoints in
> Curtis> longitude, latitude, and pressure.
>
> Curtis> In addition to contour plots, which is on the goals list
> Curtis> for this project, I would like a feature added that allows
> Curtis> me to make velocity arrows overlaying the pcolor or imshow
> Curtis> images, as is common in meteorology maps. Will such a
> Curtis> feature be available in matplotlib, and if so, how soon?
> Curtis> Thanks for all the great work so far!
>
> Hi Curtis,
>
> Actually this is on the goals page, listed as 2D vector plots - could
> be more descriptive there. So yes, it is a priority. But I can't
> really give an estimate at this point of when it will be done.
>
> Working in your favor is that it should be fairly easy now that line
> collections exist. These were implemented in 0.54 and allow the fast
> drawing of a bunch of independent line segments, which both contours
> and vector fields have. Now that the infrastructure exists to do
> these efficiently, it makes it more likely that they will be added
> sooner rather than later. But there are a number of other equally important
> features on the TODO list, which is why I don't have a definite
> estimate.
>
> As the goals page states
>
> Priorities can be changed in one of two ways: convincing one of the
> existing developers to make an item a higher priority (for example,
> if many users request the feature) or by helping to add the feature
> yourself (i.e., becoming a new developer).
>
> You've just done option 1. You're invited to try option 2!
>
> Cheers,
> JDH
>

Hello,
Just to report a very minor thing, a broken link on the matplotlib website
: in the tutorial page, in the table summarising the "Lines properties",
the "color" hyperlink is broken.
-- 
Yann Le Du
http://www-thphys.physics.ox.ac.uk/users/YannLeDu

I'm trying to 'freeze' a script of mine using py2exe and I cant seem to get 
it to play nicely with matplotlib. More specifically, my script is a 
wxpython frame that displays several data plots that are created with the 
Agg backend and converted to bitmaps. From my limited knowledge of py2exe 
it appears that the problem arises from py2exe trying to import several 
backends at once.
My specific setup is as follows:
Followed all the steps listed here: 
http://sourceforge.net/mailarchive/forum.php?thread_id=4031953&forum_id=33405
Also attempted using excludes as mentioned here: 
http://starship.python.net/crew/theller/moin.cgi/MatPlotLib
# setup.py
from distutils.core import setup
import py2exe
import glob
data = glob.glob(r"C:\Python23\share\matplotlib\*")
opts = {'py2exe': { 'excludes': ['_gtkagg', '_tkagg'],
 	 'dll_excludes': ['libgdk-win32-2.0-0.dll', 
'libgobject-2.0-0.dll']
 }
 }
setup(
 name="Sleepy",
 version="0.5.0",
 console=["sleepy.py"],
 data_files=[("share",data)],
 options = opt
)
#fsleepy.py import list if it helps at all
import wx
from wxPython.wx import *
from wxPython.gizmos import wxTreeListCtrl
from wxPython.lib.buttons import *
import matplotlib
import matplotlib.ft2font
import matplotlib.backends.backend_agg
import ttfquery
from matplotlib.matlab import *
matplotlib.use('Agg')
from matplotlib.backends.backend_agg import FigureCanvasAgg
from matplotlib.figure import Figure
from matplotlib.axes import Subplot
import win32com.client
import pickle, math, string, calendar, time, os, os.path
Finally, I'll attach output from two runs of py2exe on the target with and 
without the excludes listed in the py2exe wiki.
Thanks,
-Colin

>>>>> "Peter" == Peter Groszkowski <pio...@ho...> writes:
 Peter> I found another issue with plot_date. Dont have a simple
 Peter> example yet, and hope that this is something 'obvious' and
 Peter> I don't have to bother.
There is clearly something wrong with the autoscale function of one of
the date tick locators. It would help to know which one. plot_date
looks at the range of your date data and tries to pick the appropriate
date tick locator based on that range (ie a YearLocator, MonthLocator,
MinuteLocator, etc). If I knew which tick locator was behaving badly,
it would help me fix the problem.
If you 
 print ax.xaxis._majorLocator
after the call to plot_date, and let me know which locator it is, I
can probably figure out where the problem is. To simplify, don't
explicitly set the date xlim range when you do this.
On a side note, in your example code you call
 ax.viewLim.intervalx().set_bounds(minXValueImPlotting, maxXValueImPlotting)
I assume you did this to narrow down the possible causes of problems.
As you know, this is the call that ax.set_xlim makes under the hood.
But in general, it's safest to stick to the axes API, ie, call
 ax.set_xlim(minXValueImPlotting, maxXValueImPlotting)
since this interface is guaranteed to be stable.
JDH

>>>>> "Curtis" == Curtis Cooper <cu...@hi...> writes:
 Curtis> Hi, I am excited about the relatively new imshow and
 Curtis> pcolor features in matplotlib. I am using numarray to
 Curtis> reduce/diagnose planetary atmospheres simulations, which
 Curtis> consist of temperature and velocity data on gridpoints in
 Curtis> longitude, latitude, and pressure.
 Curtis> In addition to contour plots, which is on the goals list
 Curtis> for this project, I would like a feature added that allows
 Curtis> me to make velocity arrows overlaying the pcolor or imshow
 Curtis> images, as is common in meteorology maps. Will such a
 Curtis> feature be available in matplotlib, and if so, how soon?
 Curtis> Thanks for all the great work so far!
Hi Curtis,
Actually this is on the goals page, listed as 2D vector plots - could
be more descriptive there. So yes, it is a priority. But I can't
really give an estimate at this point of when it will be done.
Working in your favor is that it should be fairly easy now that line
collections exist. These were implemented in 0.54 and allow the fast
drawing of a bunch of independent line segments, which both contours
and vector fields have. Now that the infrastructure exists to do
these efficiently, it makes it more likely that they will be added
sooner rather than later. But there are a number of other equally important
features on the TODO list, which is why I don't have a definite
estimate.
As the goals page states
 Priorities can be changed in one of two ways: convincing one of the
 existing developers to make an item a higher priority (for example,
 if many users request the feature) or by helping to add the feature
 yourself (i.e., becoming a new developer).
You've just done option 1. You're invited to try option 2!
Cheers,
JDH

hmm... forgot to attach the images...
---
I found another issue with plot_date. Dont have a simple example yet, and 
hope that this is something 'obvious' and I don't have to bother.
I attach two images showing the issue. I can go get rid of the weird scaling 
in 'bad.png' when I do:
ax.viewLim.intervalx().set_bounds(minXValueImPlotting, maxXValueImPlotting)
after:
ax.autoscale_view()
I also noticed a couple of things inside axes.py, that might be wrong:
1)
 def get_ylim(self):
 "Get the y axis range [ymin, ymax]"
 return self.viewLim.intervalx().get_bounds()
should that intervax() be intervaly() ??
2) panx() and pany() are different as well, but perhaps they should be..
Changin these two things does not fix my problem so it has to be something 
else - hoping a simple typo. Will try to write a demo script that shows 
this... (I have matplotlib wrapped into other code so its not really a 
copy/paste-all type deal).
Peter
John Hunter wrote:
>>>>>>"Michael" == Michael Hauser <ha...@na...> writes:
>
>
>
> Michael> Hello, I am having a problem with plot_date. I keep
> Michael> getting the error:
>
> Michael> Am I missing something obvious?
>
>No, there is a bug in plot_date in setting the tick formatter object.
>I didn't find this in any of my test or example scripts since all
>those explicitly set the formatter and hence hid the bug. At the end
>of the Axes.plot_date function in matplotlib.axes, replace
>
> self.xaxis.set_minor_locator(formatter)
>
>with self.xaxis.set_major_formatter(formatter)
>
>and you'll be good to go. Note however that there is a problem with
>your script in that the length of your x and y arrays must be the
>same. After making the changes above, try
>
>from datetime import datetime
>from matplotlib.dates import EpochConverter
>from matplotlib.matlab import *
>
>times = [1084195314, 1084195375, 1084195436, 1084195497, 1084195557]
>vals = [10.2, 11.1, 8.7, 12.1, 12.2]
>converter = EpochConverter()
>ax = subplot(111)
>plot_date(times, vals, converter)
>savefig('test')
>show()
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
>one installation-authoring solution that does it all. Learn more and
>evaluate today! http://www.installshield.com/Dev2Dev/0504
>_______________________________________________
>Matplotlib-users mailing list
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
-------------------------------------------------------
This SF.Net email is sponsored by the new InstallShield X.
From Windows to Linux, servers to mobile, InstallShield X is the
one installation-authoring solution that does it all. Learn more and
evaluate today! http://www.installshield.com/Dev2Dev/0504
_______________________________________________
Matplotlib-users mailing list
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I found another issue with plot_date. Dont have a simple example yet, and 
hope that this is something 'obvious' and I don't have to bother.
I attach two images showing the issue. I can go get rid of the weird scaling 
in 'bad.png' when I do:
ax.viewLim.intervalx().set_bounds(minXValueImPlotting, maxXValueImPlotting)
after:
ax.autoscale_view()
I also noticed a couple of things inside axes.py, that might be wrong:
1)
 def get_ylim(self):
 "Get the y axis range [ymin, ymax]"
 return self.viewLim.intervalx().get_bounds()
should that intervax() be intervaly() ??
2) panx() and pany() are different as well, but perhaps they should be..
Changin these two things does not fix my problem so it has to be something 
else - hoping a simple typo. Will try to write a demo script that shows 
this... (I have matplotlib wrapped into other code so its not really a 
copy/paste-all type deal).
Peter
John Hunter wrote:
>>>>>>"Michael" == Michael Hauser <ha...@na...> writes:
>
>
> Michael> Hello, I am having a problem with plot_date. I keep
> Michael> getting the error:
>
> Michael> Am I missing something obvious?
>
>No, there is a bug in plot_date in setting the tick formatter object.
>I didn't find this in any of my test or example scripts since all
>those explicitly set the formatter and hence hid the bug. At the end
>of the Axes.plot_date function in matplotlib.axes, replace
>
> self.xaxis.set_minor_locator(formatter)
>
>with self.xaxis.set_major_formatter(formatter)
>
>and you'll be good to go. Note however that there is a problem with
>your script in that the length of your x and y arrays must be the
>same. After making the changes above, try
>
>from datetime import datetime
>from matplotlib.dates import EpochConverter
>from matplotlib.matlab import *
>
>times = [1084195314, 1084195375, 1084195436, 1084195497, 1084195557]
>vals = [10.2, 11.1, 8.7, 12.1, 12.2]
>converter = EpochConverter()
>ax = subplot(111)
>plot_date(times, vals, converter)
>savefig('test')
>show()
>
>
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by the new InstallShield X.
>From Windows to Linux, servers to mobile, InstallShield X is the
>one installation-authoring solution that does it all. Learn more and
>evaluate today! http://www.installshield.com/Dev2Dev/0504
>_______________________________________________
>Matplotlib-users mailing list
>Mat...@li...
>https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

>>>>> "Michael" == Michael Hauser <ha...@na...> writes:
 Michael> Hello, I am having a problem with plot_date. I keep
 Michael> getting the error:
 Michael> Am I missing something obvious?
No, there is a bug in plot_date in setting the tick formatter object.
I didn't find this in any of my test or example scripts since all
those explicitly set the formatter and hence hid the bug. At the end
of the Axes.plot_date function in matplotlib.axes, replace
 self.xaxis.set_minor_locator(formatter)
with 
 self.xaxis.set_major_formatter(formatter)
and you'll be good to go. Note however that there is a problem with
your script in that the length of your x and y arrays must be the
same. After making the changes above, try
from datetime import datetime
from matplotlib.dates import EpochConverter
from matplotlib.matlab import *
times = [1084195314, 1084195375, 1084195436, 1084195497, 1084195557]
vals = [10.2, 11.1, 8.7, 12.1, 12.2]
converter = EpochConverter()
ax = subplot(111)
plot_date(times, vals, converter)
savefig('test')
show()

On Fri, 2004年06月11日 at 19:22, John Hunter wrote:
> Steve> For the last week or so I've been unable to use the GTK+
> Steve> backend with matplotlib (and PyGTK) from CVS. Instead of
> Steve> producing a plot it colors the whole figure black. I think
> Steve> this may be a colormap problem.
> 
> >From your post to the pygtk list, I assume you are using PyGTK 2.3.93.
> Unfortunately I don't have a good platform to test this version on
> since my system doesn't have the required glib/gtk version and I have
> learned from past experience not to try and upgrade these libs.
> 0.54.2 with the GTK backend runs fine with pygtk-2.2 on my system.
> 
> A couple of questions
> 
> * can you run matplotlib-0.54.1 on your current version of pygtk.
> This will help me figure out if something in matplotlib has changed
> or if something on your system has changed. The GTK backend is
> fairly stable at this point so not a lot has changed.
> 
> * Can you run matplotlib-0.54.2 with pygtk2.2 on your system?
> 
> If there is a 2.3.93 specific problem, we'll need to get it worked
> out, but I'd like to narrow the field of candidate problems first.
> 
> JDH
I've just ran lots of tests:
Matplotlib	PyGTK GTK+ backend
---------- ----- ------------
0.54.1 2.2.0 working
0.54.2 2.2.0 working
cvs 2.2.0 working
0.54.1 cvs(2.3.93) fails (the figure is all black)
0.54.2 cvs(2.3.93) fails
cvs cvs(2.3.93) fails
It must be a PyGTK bug. 
Strangely enough I opened a PyGTK bug report today (#144135), which
turns out to be serious bug - a 'stopper' for PyGTK 2.4. It may also be
causing this problem with matplotlib. Hopefully it will be fixed soon
and if it doesn't fix this problem running matplotlib I'll open another
PyGTK bug report.
Steve

>>>>> "Steve" == Steve Chaplin <ste...@ya...> writes:
 Steve> I ran your memory test script on my Fedora 2 PC, it gave
 Steve> Average memory consumed per loop: 168.3600 on the previous
 Steve> matplotlib Average memory consumed per loop: 41.7200 on the
 Steve> latest matplotlib from CVS. That's a big improvement.
Well that's interesting. I just reran the script myself because I was
getting approx 12 per loop and you are getting 40. But now when I
rerun it I get numbers compatible with yours. Annoying. Back to the
drawing board.
 Steve> For the last week or so I've been unable to use the GTK+
 Steve> backend with matplotlib (and PyGTK) from CVS. Instead of
 Steve> producing a plot it colors the whole figure black. I think
 Steve> this may be a colormap problem.
From your post to the pygtk list, I assume you are using PyGTK 2.3.93.
Unfortunately I don't have a good platform to test this version on
since my system doesn't have the required glib/gtk version and I have
learned from past experience not to try and upgrade these libs.
0.54.2 with the GTK backend runs fine with pygtk-2.2 on my system.
A couple of questions
 * can you run matplotlib-0.54.1 on your current version of pygtk.
 This will help me figure out if something in matplotlib has changed
 or if something on your system has changed. The GTK backend is
 fairly stable at this point so not a lot has changed.
 * Can you run matplotlib-0.54.2 with pygtk2.2 on your system?
If there is a 2.3.93 specific problem, we'll need to get it worked
out, but I'd like to narrow the field of candidate problems first.
JDH

On Thu, 2004年06月10日 at 05:52, John Hunter wrote:
> Hi Eric,
> 
> You can test the new release which includes both Steve's changes and a
> number of fixes on my end. I'll attach the script below that I used
> to profile the leak, a modified version of your script. By my
> numbers, the average memory consumed per loop is down from 145.9 using
> 0.54.1 to 12.3 using 0.54.2. Not perfect, but more than 10x better.
> 
> I have definitely identified a leak in freetype (as mentioned above,
> which is fixed in freetype CVS) and there appears to be a leak in
> libpng but I have tracked down precisely where. Neither of these are
> terribly large. I strongly suspect that some of the remaining leak is
> my doing, so I'll continue to try and sniff these out. The python
> code uses a lot of circular references (figures contain axes and text
> which in turn contain a reference to the figure that contains them and
> so on) which makes the task a little harder.
> 
> Let me know how it goes.
> 
> JDH
I ran your memory test script on my Fedora 2 PC, it gave
Average memory consumed per loop: 168.3600 on the previous matplotlib
Average memory consumed per loop: 41.7200 on the latest matplotlib
from CVS.
That's a big improvement.
For the last week or so I've been unable to use the GTK+ backend with
matplotlib (and PyGTK) from CVS. Instead of producing a plot it colors
the whole figure black. I think this may be a colormap problem.
Steve

John,
Compiling with numarray improved the pcolor_demo2 times by about a 
factor of 3 when selecting numarray via numerix, although it is still a 
little slower on my machine than Numeric-linkage/Numeric Python. No big 
deal. I am sticking with numarray. 
Eric
>The NUMERIX variable in setup.py determines which library the
>extension code is compiled against. Whether you use numeric or
>numarray, it will work with either, but you should get much better
>performance if you match this compile flag to the library you use
>most.
>
>Let us know if this is indeed the cause of the performance hit. Here
>are my numbers (best of three runs)
>
> 
>

Hello,
I am having a problem with plot_date. I keep getting the error:
File "E:\Python23\Lib\site-packages\matplotlib\axis.py", line 567, in
get_minor_ticks
 numticks = len(self._minorLocator())
TypeError: __call__() takes exactly 3 arguments (1 given)
I'm using Python 2.3.2, Numeric 23.1, and matplotlib 0.54.2. Here's a
short example that exhibits the problem behavior:
-----------------------------
from datetime import datetime
from matplotlib.dates import EpochConverter
from matplotlib.matlab import *
times = [1084195314, 1084195375, 1084195436, 1084195497, 1084195557]
vals = [10.2, 11.1, 8.7]
converter = EpochConverter()
ax = subplot(111)
plot_date(times, vals, converter)
show()
-----------------------------
Am I missing something obvious?
Thanks.
Michael Hauser

Hi,
I am excited about the relatively new imshow and pcolor features in
matplotlib. I am using numarray to reduce/diagnose planetary atmospheres
simulations, which consist of temperature and velocity data on gridpoints
in longitude, latitude, and pressure.
In addition to contour plots, which is on the goals list for this project,
I would like a feature added that allows me to make velocity arrows
overlaying the pcolor or imshow images, as is common in meteorology maps.
Will such a feature be available in matplotlib, and if so, how soon?
Thanks for all the great work so far!
Cheers,
Curtis
 * * * * * * * * * * * * * * * * * * * * * * * * * * * *
 * Curtis S. Cooper, Graduate Research Assistant *
 * Lunar and Planetary Laboratory, University of Arizona *
 * http://www.lpl.arizona.edu/~curtis/		 *
 * Kuiper Space Sciences, Rm. 318 *
 * 1629 E. University Blvd., *
 * Tucson, AZ 85721 * * * * * * * * * * * * * * *
 * Wk: (520) 621-1471 *
 * * * * * * * * * * * *
 'It is a great gift to have a beautiful mind but an even
 greater gift to discover a beautiful heart.`
	 --Akiva Goldsman
 (The Academy Award Winning Screenwriter of 'A Beautiful Mind`)

On Thu, 2004年06月10日 at 09:57, John Hunter wrote:
> >>>>> "Eric" == Eric Firing <ef...@km...> writes:
> 
> Eric> John, For the command-line selection mechanism of numerix.py
> Eric> to work, the following change is needed:
> 
> Eric> if which[0] is None: ## Add this line which =
> Eric> rcParams['numerix'], "rc"
> 
> Eric> Otherwise, the rcParams value clobbers the command-line
> Eric> value.
> 
> Thanks for the alert on the numerix problem. The numerix module was
> written before matplotlibrc existed and it appears was not properly
> updated. It may be better to simplify this and only provide 2
> choices, command line then rc file. Does anyone need any of the other
> methods of choosing numerix? Is there any reason to keep .numerix or
I don't think so. It's only useful outside the context of matplotlib.
> the NUMERIX env var?
I can't think of any reason here. What I'd use the env var for is
probably better handled by the command line option anyway.
If no one objects, I'll rip this stuff out and update the module
docstring as Eric suggested.
Todd