matplotlib-users Mailing List for matplotlib (Page 10)

>>>>> "Graeme" == Graeme O'Keefe <gj...@ne...> writes:

    Graeme> Hi, I've installed matplotlib 0.71 on Mac OS X 10.3 which
    Graeme> completed without errors.

    Graeme> when I run python "import matplotlib" is fine, but "import
    Graeme> pylab" bombs with "ImportError: cannot import name POLAR"


rm -rf the build directory *and* site-packages/matplotlib and
rebuild/reinstall.  This cures the problem 95% of the time.  It is
usually caused from some detritus from a previous build or install
that distutils doesn't handle so well.  Let mw know...

JDH

>>>>> "Eric" == Eric Emsellem <ems...@ob...> writes:

    Eric> Hi John, sorry to bother you about this again, but is there
    Eric> a fix to the bug in the imshow routine (using the
    Eric> aspect='preserve' option).  If not, let me know if you have
    Eric> an idea when this could be done (no pushing there, just to
    Eric> plan things on my side: I am at the moment using an
    Eric> artificial way to replace that option by calculating
    Eric> coordinates on the plot, just to know if I need to go on
    Eric> with that or not).

Hi Eric, there is not a fix yet, but there is a workaround in CVS.  

I played around with some things that got the initial coords right but
then broke under window resizes and I rolled these changes back.  It
is a somewhat tough problem, to preserve aspect ration under possible
figure and axes resizes, and/or view limit navigation.  It is a very
high priority bug for me, but because it is also a hard one its taking
a little while.  SO I can't give you a firm date -- I'll try and get
something serviceable in the next couple of weeks.

This is the same bug that causes zoom to rect on aspect=preserve plots
to get the wrong limits.

Fernando Perez submitted a patch in CVS that works around the problem
for now using the "matshow" command.  This command takes the same
arguments as imshow and creates a figure and an axes which are scaled
to have the same dimensions as the array.  Thus if you don't resize
your window, you can plot an array with matshow with either free or
preserve and the aspect ratio will be correct.  But, if you zoom to
rect or resize your window, even with matshow you'll lose the aspect
ratio.  I'll include the docstring for matshow below so you can see if
you're interested

I've very aware of the scientists need to "just see the data" w/o any
fancy stuff.  Hopefully a fix will be in soon.

JDH


matshow:

    """Display an array as a matrix.

    The origin is set at the upper left hand corner and rows (first dimension
    of the array) are displayed horizontally.  The aspect ratio of the figure
    window is that of the array, as long as it is possible to fit it within
    the constraints of your figure.figsize_min/max parameters with no
    stretching.  If the window dimensions can't accomodate this (extremely
    tall/wide arrays), some stretching will inevitably occur.

    matshow() calls imshow() with args and **kwargs, but by default
    it sets interpolation='nearest' (unless you override it).  All
    other arguments and keywords are passed to imshow(), so see its
    docstring for further details.

    Tick labels for the xaxis are placed on top by default.
    
    return value is a (fig, ax, im) tuple

    Example usage:
    
    def samplemat(dims):
        aa = zeros(dims)
        for i in range(min(dims)):
            aa[i,i] = i
        return aa

    dimlist = [(12,12),(128,64),(64,512),(2048,256)]

    
    for d in dimlist:
        fig, ax, im = matshow(samplemat(d))
    show()
    
    """

Hi John,
sorry to bother you about this again, but is there a fix to the bug
in the imshow routine (using the aspect='preserve' option).
If not, let me know if you have an idea when this could be done
(no pushing there, just to plan things on my side: I am at the moment
using an artificial way to replace that option by calculating coordinates
on the plot, just to know if I need to go on with that or not).

Let me know; Thanks!

Eric

-- 
===============================================================
Observatoire de Lyon                 ems...@ob...
9 av. Charles-Andre                      tel: +33 4 78 86 83 84
69561 Saint-Genis Laval Cedex            fax: +33 4 78 86 83 86
France               http://www-obs.univ-lyon1.fr/eric.emsellem
===============================================================

Hi,

I've installed matplotlib 0.71 on Mac OS X 10.3 which completed without  
errors.

when I run python
	"import matplotlib"
is fine, but
	"import pylab"
bombs with
	"ImportError: cannot import name POLAR"

see below  for a screendump of the reported errors when I try to import  
pylab.
I did not run this in the build directory.

/System/Library/Frameworks/Python.framework/Versions/2.3/lib/python2.3/ 
site-packages
(which is linked to /Library/Python/2.3)

/Library/Python/2.3/matplotlib/transforms.py, line 189: from  
_transforms import IDENTITY, LOG10, POLAR, Func, FuncXY
/Library/Python/2.3/matplotlib/_transforms.so exists and is 3503536  
bytes in size.

here is a screendump of the reported errors when I try to import pylab.
I did not run this in the build directory.

can anyone help?

regards,

Graeme

[graeme:~/Desktop/downloads/matplotlib-0.71] gjok% python
Python 2.3 (#1, Sep 13 2003, 00:49:11)
[GCC 3.3 20030304 (Apple Computer, Inc. build 1495)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
 >>> import pylab
Traceback (most recent call last):
   File "<stdin>", line 1, in ?
   File  
"/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/pylab.py", line 1, in ?
     from matplotlib.pylab import *
   File  
"/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/matplotlib/pylab.py", line 190, in ?
     from axes import Axes, PolarAxes
   File  
"/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/matplotlib/axes.py", line 12, in ?
     from artist import Artist
   File  
"/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/matplotlib/artist.py", line 3, in ?
     from transforms import identity_transform
   File  
"/System/Library/Frameworks/Python.framework/Versions/2.3/lib/ 
python2.3/site-packages/matplotlib/transforms.py", line 189, in ?
     from _transforms import IDENTITY, LOG10, POLAR, Func, FuncXY
ImportError: cannot import name POLAR

>>>>> "Chris" == Chris Barker <Chr...@no...> writes:

    Chris> Hi all, I think I've successfully build a binary matplotlib
    Chris> package for use with Apple's Python on OS-X 10.3.* In
    Chris> theory the only other thing it requires is Numeric, and I
    Chris> have a package for that too (courtesy of Bob Ippolito).

    Chris> It's almost 5 MB, so I haven't included it here. I also
    Chris> don't have a web site to put it on at the moment, so:

    Chris> A) if you send me a note, I'll send it to you B) if you
    Chris> have a place to host it, please volunteer to do so.

    Chris> I'd like people to test it out, all I know now is that it
    Chris> works on my system.

    Chris> Once it's been better tested, perhaps we can get it put on
    Chris> the sourceforge download page.

High Chris,

Thanks for doing this.  Are either the GTK or Tk GUI backends compiled
in.  If not, wx* will still work on boxes that have wxpython
installed, but it would be a good idea to summarize what is available
in the package.

Thanks!
JDH

Hi all,

I think I've successfully build a binary matplotlib package for use with 
Apple's Python on OS-X 10.3.* In theory the only other thing it requires 
is Numeric, and I have a package for that too (courtesy of Bob Ippolito).

It's almost 5 MB, so I haven't included it here. I also don't have a web 
site to put it on at the moment, so:

A) if you send me a note, I'll send it to you
B) if you have a place to host it, please volunteer to do so.

I'd like people to test it out, all I know now is that it works on my 
system.

Once it's been better tested, perhaps we can get it put on the 
sourceforge download page.

thanks,
-Chris




-- 
Christopher Barker, Ph.D.
Oceanographer
                                     		
NOAA/OR&R/HAZMAT         (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

Hello,

How complicated would it be to obtain the add_patch() capability in 
polar axes? Right now, the script

--------------------
from pylab import *
import matplotlib.patches as patches

ax = axes( [0.1, 0.1, 0.8, 0.8], polar = True )
ptch = patches.RegularPolygon( (pi/2,.5), 5, orientation = 20 )
ax.add_patch()
show()
--------------------

fails, Python complaining that polar axes don't have an add_patch() method.

Now, I believe if we simply mimic what's in the Axes class and try to use

artists.extend(patches)

in PolarAxes, the coordinates are going to be all wacko.

The following works for me, and I wonder whether it is a useful addition 
to PolarAxes (sorry for the wrapped lines):

--------------------
from matplotlib.pylab import *


def RegularPolygon_polar( ax, xy, numVertices, radius = 5, orientation = 
0, **kwargs ):
     import matplotlib.patches as patches
     import matplotlib.transforms as transforms

     ptch = patches.RegularPolygon( (0,0),
                                    numVertices,
                                    radius = radius,
                                    orientation = orientation,
                                    **kwargs )

     trans = transforms.identity_affine()
     trans.set_offset( xy, ax.transData )
     ptch.set_transform( trans )
     return ptch

ax = axes( [0.1, 0.1, 0.8, 0.8], polar = True )
ptch = RegularPolygon_polar( ax, (150*pi/180,.5), 5, radius = 10, 
orientation = 80 )
ax.add_patch( ptch )
show()
--------------------

If this sounds like the way to go, let me know. I'm willing to write the 
few methods similar to the above and add them to PolarAxes.

On the other hand, it might be easier to simply modify the classes in 
patches.py, but I am not sure how they would access the Axes instance.

Cheers,
Dominique

>>>>> "Delbert" == Delbert D Franz <iq...@so...> writes:

    Delbert> I just did another test. mx2num fails for dates prior to
    Delbert> 1970 because it uses the magical Unix seconds from epoch.
    Delbert> We need mx2num to work for the whole range of dates for
    Delbert> which date2num works-at least that is my vote.  Delbert
    Delbert> On Wednesday 02 February 2005 10:10 am, Delbert D. Franz wrote:

If you feel up to making an mx2num that satisfies these requirements,
I'm happy to include it as a patch.

JDH

I just did another test. mx2num fails for dates prior to 1970 because
it uses the magical Unix seconds from epoch.  We need mx2num to work 
for the whole range of dates for which  date2num  works-at least that
is my vote. 
                                  Delbert
On Wednesday 02 February 2005 10:10 am, Delbert D. Franz wrote:
> John, thanks for the updated mx2num but I still found something
> puzzling: date2num takes the timezone from the matplotlibrc file
> but mx2num must take it from some info on my machine.  There is a
> consistent seven hour difference between the two even though the 
> datetime instances  give exactly the same time. 
> 
> I need to point out that in my applications I have no interest in 
> the time zone and I want it always treated as if I am 
> on the Greenwich Meridian.  Here's why:  My simulation software
> has used what is essentially the modified Julian Day number 
> from astronomy with a zero point  around 1878 or so.  I just add 
> the fraction of the day to it.   This works
> fine in my applications because there is no data to run the model 
> earlier than about the 1900!  Also I have users in different time 
> zones sending me test cases and it would be a mess to have to 
> somehow always adjust for time zone.  Thus I have effectively 
> computed the day numbers relative to the local time zone always. 
> 
> Another benefit is that there is a fixed offset between my 
> time scale and the one used in plot_dates.  Makes life a little
> simpler. 
> 
> Questions: 
> 
> 1. Should mx2num use a different time zone than does date2num?
> 
> 2. If so, how do I get mx2num at its invocation only, to use 
>    the time zone in the matplotlibrc file?  I assume I have 
>    to use the set_tzinfo method right before mx2num is invoked
>    and then use set_tzinfo again right after to return to 
>    what it was. 
> 
> Heres an example test file: 
> 
> from matplotlib.dates import mx2num, date2num
> import datetime
> import mx.DateTime
> 
> for ihr in xrange(24):
>     yr = 2003
>     mn = 10
>     day = 20
>     imin = 30
>     second = 0.0
>     isec = 0
> 
>     dt = mx.DateTime.DateTime(yr, mn, day, ihr, imin, second)
>     dt2 = datetime.datetime(yr, mn, day, ihr, imin, isec)
>     print 'hour=', ihr
>     print 'mx dt=',dt
>     print 'dt2=', dt2
>     diff =  mx2num(dt) - date2num(dt2)
>     print 'mx2num(dt)=',mx2num(dt)
>     print 'date2num(dt2) =', date2num(dt2)
>     print 'difference=', diff*24.0
>     print ' '
> 
> 
> Here's some output at my time zone:
> 
> 
> hour= 0
> mx dt= 2003-10-20 00:30:00.00
> dt2= 2003-10-20 00:30:00
> mx2num(dt)= 731508.3125
> date2num(dt2) = 731508.020833
> difference= 6.99999999907
>  
> hour= 1
> mx dt= 2003-10-20 01:30:00.00
> dt2= 2003-10-20 01:30:00
> mx2num(dt)= 731508.354167
> date2num(dt2) = 731508.0625
> difference= 6.99999999907
>  
> hour= 2
> mx dt= 2003-10-20 02:30:00.00
> dt2= 2003-10-20 02:30:00
> mx2num(dt)= 731508.395833
> date2num(dt2) = 731508.104167
> difference= 7.00000000186
>  
> hour= 3
> mx dt= 2003-10-20 03:30:00.00
> dt2= 2003-10-20 03:30:00
> mx2num(dt)= 731508.4375
> date2num(dt2) = 731508.145833
> difference= 6.99999999907
>  
> hour= 4
> mx dt= 2003-10-20 04:30:00.00
> dt2= 2003-10-20 04:30:00
> mx2num(dt)= 731508.479167
> date2num(dt2) = 731508.1875
> difference= 6.99999999907
>  
> hour= 5
> mx dt= 2003-10-20 05:30:00.00
> dt2= 2003-10-20 05:30:00
> mx2num(dt)= 731508.520833
> date2num(dt2) = 731508.229167
> difference= 7.00000000186
>  
>                                 Delbert
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 

John, thanks for the updated mx2num but I still found something
puzzling: date2num takes the timezone from the matplotlibrc file
but mx2num must take it from some info on my machine.  There is a
consistent seven hour difference between the two even though the 
datetime instances  give exactly the same time. 

I need to point out that in my applications I have no interest in 
the time zone and I want it always treated as if I am 
on the Greenwich Meridian.  Here's why:  My simulation software
has used what is essentially the modified Julian Day number 
from astronomy with a zero point  around 1878 or so.  I just add 
the fraction of the day to it.   This works
fine in my applications because there is no data to run the model 
earlier than about the 1900!  Also I have users in different time 
zones sending me test cases and it would be a mess to have to 
somehow always adjust for time zone.  Thus I have effectively 
computed the day numbers relative to the local time zone always. 

Another benefit is that there is a fixed offset between my 
time scale and the one used in plot_dates.  Makes life a little
simpler. 

Questions: 

1. Should mx2num use a different time zone than does date2num?

2. If so, how do I get mx2num at its invocation only, to use 
   the time zone in the matplotlibrc file?  I assume I have 
   to use the set_tzinfo method right before mx2num is invoked
   and then use set_tzinfo again right after to return to 
   what it was. 

Heres an example test file: 

from matplotlib.dates import mx2num, date2num
import datetime
import mx.DateTime

for ihr in xrange(24):
    yr = 2003
    mn = 10
    day = 20
    imin = 30
    second = 0.0
    isec = 0

    dt = mx.DateTime.DateTime(yr, mn, day, ihr, imin, second)
    dt2 = datetime.datetime(yr, mn, day, ihr, imin, isec)
    print 'hour=', ihr
    print 'mx dt=',dt
    print 'dt2=', dt2
    diff =  mx2num(dt) - date2num(dt2)
    print 'mx2num(dt)=',mx2num(dt)
    print 'date2num(dt2) =', date2num(dt2)
    print 'difference=', diff*24.0
    print ' '


Here's some output at my time zone:


hour= 0
mx dt= 2003-10-20 00:30:00.00
dt2= 2003-10-20 00:30:00
mx2num(dt)= 731508.3125
date2num(dt2) = 731508.020833
difference= 6.99999999907
 
hour= 1
mx dt= 2003-10-20 01:30:00.00
dt2= 2003-10-20 01:30:00
mx2num(dt)= 731508.354167
date2num(dt2) = 731508.0625
difference= 6.99999999907
 
hour= 2
mx dt= 2003-10-20 02:30:00.00
dt2= 2003-10-20 02:30:00
mx2num(dt)= 731508.395833
date2num(dt2) = 731508.104167
difference= 7.00000000186
 
hour= 3
mx dt= 2003-10-20 03:30:00.00
dt2= 2003-10-20 03:30:00
mx2num(dt)= 731508.4375
date2num(dt2) = 731508.145833
difference= 6.99999999907
 
hour= 4
mx dt= 2003-10-20 04:30:00.00
dt2= 2003-10-20 04:30:00
mx2num(dt)= 731508.479167
date2num(dt2) = 731508.1875
difference= 6.99999999907
 
hour= 5
mx dt= 2003-10-20 05:30:00.00
dt2= 2003-10-20 05:30:00
mx2num(dt)= 731508.520833
date2num(dt2) = 731508.229167
difference= 7.00000000186
 
                                Delbert

>>>>> "Delbert" == Delbert D Franz <dd...@lk...> writes:

    Delbert> I am now able to create multiple figures, each with one
    Delbert> or more subplots with my software.  What a great
    Delbert> collection of software.  Thanks for all the work.

Great, glad it helped.  I was pretty sure that was the answer.

    Delbert> I tried using mx.datetime to create an mx.datetime
    Delbert> instance which worked fine. However, mx2num() fails with
    Delbert> python claiming an undefined mxdates.  I checked the
    Delbert> source and found only one mxdates.  No idea how it should
    Delbert> be defined.  In the mean time I am using a datetime
    Delbert> instance but I lose a small bit of precision with only
    Delbert> integer seconds.

Oops, replace mx2num in matplotlib/dates.py with 

def mx2num(mxdates):
    """
    Convert mx datetime instance (or sequence of mx instances) to the
    new date format,
    """
    scalar = False
    if not iterable(mxdates):
        scalar = True
        mxdates = [mxdates]
    ret = epoch2num([m.ticks() for m in mxdates])
    if scalar: return ret[0]
    else: return ret


Thanks for the report!
JDH

>>>>> "Nils" == Nils Wagner <nw...@me...> writes:

    Nils> Hi all, Is it possible to rule the distance between subplots
    Nils> ?  How about the setting of x axis tic marks ? The default
    Nils> is not very promising (see bsp5.py)

For axes placement, see also the axes command, which gives you a finer
degree of control than subplot.

For the tick labeling, you are right, the default xticklabels in your
example are a mess.  We'll take a look at this case to see where the
bug is.  In my experience, getting default ticking and labeling right
is hard, and matplotlib has gotten a lot better at it since the bad
old days but there is a ways to go.

Until we get this fixed, you do have the option of using a custom
ticker, which is explained in the user's guide Chapter 5, and
illustrated in examples/custom_ticker1.py in the matplotlib src
distro.

JDH

>>>>> "Cory" == Cory Davis <cd...@st...> writes:

    Cory> try title('$\mu='+str(p[ic-1])+'$') Cory.

Make sure you quote the string as a raw string with the "r" prefix.  I
also suggest format strings for formatting numeric values, something
like

title(r'$\mu=%1.2f$' % p[ic-1])
      ^

JDH

On Wednesday 02 February 2005 04:51 am, Steve Chaplin wrote:
>
> When resizing the FigureCanvas on my system I notice:
> GTK   sets a FigureCanvas size that can only be increased.
> QtAgg sets a FigureCanvas size that can be increased or decreased
> TkAgg sets a FigureCanvas size that can be increased or decreased to a
> minimum (of perhaps 400 x 300 pixels)
> Wx I do not have, is it like Qt or Tk or is there a 4th variation?

on linux, wx lets me increase or decrease all the way. I wonder if it is 
different on windows.

>
> I looked at changing GTK so the FigureCanvas could be decreased a while
> ago but the problem is that while the axes scale/shrink nicely the text
> stays the same size and becomes misaligned or clipped and gives an odd
> looking graph. Perhaps thats why Tk allows you shrink the window but
> only to a certain size.
>
> Matplotlib currently has 3 (or more) ways of handling window resizing,
> which one of these behaviours is 'correct' or most desirable?
>

I think the most desirable for interactive use would be to allow scaling, but 
if it doesn't scale properly, I think the current behavior is appropriate. I 
guess I just didnt notice it before now.

Darren

try title('$\mu='+str(p[ic-1])+'$')

Cory.

On Wed, 2005-02-02 at 12:48, Nils Wagner wrote:
> Hi all,
> 
> I am going to change the title of each subplot with respect to the 
> actual value of \mu within a loop.
> How can I do that ?
> 
> p = array(([0.1,0.01,0.001,0.0001]))
> ic = 1
> for mu in p:
>  title('$\mu=$'+str(p[ic-1]))  # This version doesn't work
>  ic = ic + 1
> 
> Nils
> 
>  
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> Tool for open source databases. Create drag-&-drop reports. Save time
> by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
))))))))))))))))))))))))))))))))))))))))))))
Cory Davis
Meteorology
School of GeoSciences
University of Edinburgh
King's Buildings
EDINBURGH EH9 3JZ

ph: +44(0)131 6505092
fax +44(0)131 6505780
cd...@st...
co...@me...
http://www.geos.ed.ac.uk/contacts/homes/cdavis
))))))))))))))))))))))))))))))))))))))))))))

Hi Nils,

On Wed, 2005-02-02 at 12:22, Nils Wagner wrote:
> Hi all,
> 
> Is it possible to rule the distance between subplots ?
> How about the setting of x axis tic marks ? The default is not very 
> promising
> (see bsp5.py)

Here is a function I use instead of the matplotlib subplot.

It has the same arguments as the matlab version except for the 
figpos argument, which determines where in the figure your
array of plots goes, and the axpos argument, which determines where in each 
panel the axes goes.  It returns an axes object, which you can use 
to set xticks etc.  

Hope this helps,
Cheers,
Cory.

Hi all,

I am going to change the title of each subplot with respect to the 
actual value of \mu within a loop.
How can I do that ?

p = array(([0.1,0.01,0.001,0.0001]))
ic = 1
for mu in p:
 title('$\mu=$'+str(p[ic-1]))  # This version doesn't work
 ic = ic + 1

Nils

 

 

>>>>> "dimitri" == dimitri pater <dim...@gm...> writes:

    dimitri> hello, I want to create a barchart on a website, somebody
    dimitri> advised me to use matplotlib and it does look very
    dimitri> promising. The problem that I now face is that I can't
    dimitri> seem to get things right, the following code results in
    dimitri> an import error:

    dimitri> from cgi import escape
 
    dimitri> try: import cgitb cgitb.enable() except: sys.stderr =
    dimitri> sys.stdout

    dimitri> # test import pylab import pylab

    dimitri> Does this mean that the webserver doesn't have pylab
    dimitri> installed or am I missing something? (bit of a newbie in
    dimitri> this area, so please bear with me...)

To run matplotlib in a web app server, you will probably want to set
"backend : Agg" in your .matplotlibrc file.  matplotlib supports
output to a variety of image devices and GUIs, and agg is a good
choice to make nice PNGs for app servers.  See
http://matplotlib.sf.net/.matplotlibrc.  On a standard linux install,
this file would be placed in /usr/share/matplotlib/.matplotlibrc, and
i can be copied to your HOME directory and edited.  Often times HOME
is not net in an app server environment.  You either need to set it,
or take a look at
http://groups-beta.google.com/group/comp.lang.python/msg/09eac15acef8ee40,
which describes some possible solutions.  matplotlib needs a directory
that is can write to to save some font cache information, and the link
above describes the role of the environment variables HOME and
MATPLOTLIBDATA in the choices matplotlib makes.

As for your error, I suggest taking a minimal matplotlib script

import pylab
pylab.plot([1,2,3])
pylab.savefig('test.png')

and running it with

> python myscript.py --verbose-helpful

and report any output and/or errors the script produces.  Saying that
you got an import error, without giving us the exact error message`,
doesn't help us help you.

Good luck!
JDH

Hi all,

Is it possible to rule the distance between subplots ?
How about the setting of x axis tic marks ? The default is not very 
promising
(see bsp5.py)

Any pointer or suggestion how to improve my example are welcome.

Thanks in advance.

        Nils
 

hello,

I want to create a barchart on a website, somebody advised me to use
matplotlib and it does look very promising. The problem that I now
face is that I can't seem to get things right, the following code
results in an import error:

from cgi import escape
 
try:
    import cgitb
    cgitb.enable()
except:
    sys.stderr = sys.stdout

# test import pylab
import pylab

Does this mean that the webserver doesn't have pylab installed or am I
missing something? (bit of a newbie in this area, so please bear with
me...)

best regards,
Dimitri
-- 
Please visit dimitri's website: www.serpia.com

On Tue, 2005-02-01 at 20:17 -0800, Darren Dale wrote:
> I am working in interactive mode, with the GTKAgg backend. When I make a 
> figure, I was not able to resize it on the screen. I tried changing my dpi 
> and default figure size in .matplotlibrc, and now I can increase the figure 
> size, but not decrease it passed its original size. I changed 
> my .matplotlibrc back to its original configuration, and the same behavior 
> persists: I can increase the figure size, but not decrease it passed the 
> original size. This is also true for the GTK backend, but not for WXAgg.
> 
> I rebuilt my atlas libraries today, along with Numeric, and numarray. I dont 
> think that should have anything to do with it, but I rebuilt gtk+, pygtk, and 
> matplotlib just in case. All are the latest version. 
> 
> Everything else seems to work, minimizing, maximizing, closing, but not 
> resizing. Does anyone have a suggestion as to what is wrong, or what I might 
> check?

Its related to the way the FigureCanvasGTK is implemented using
self.set_size_request() - it sets the widgets minimum size.
 
When resizing the FigureCanvas on my system I notice:
GTK   sets a FigureCanvas size that can only be increased.
QtAgg sets a FigureCanvas size that can be increased or decreased
TkAgg sets a FigureCanvas size that can be increased or decreased to a
minimum (of perhaps 400 x 300 pixels)
Wx I do not have, is it like Qt or Tk or is there a 4th variation?

I looked at changing GTK so the FigureCanvas could be decreased a while
ago but the problem is that while the axes scale/shrink nicely the text
stays the same size and becomes misaligned or clipped and gives an odd
looking graph. Perhaps thats why Tk allows you shrink the window but
only to a certain size.

Matplotlib currently has 3 (or more) ways of handling window resizing,
which one of these behaviours is 'correct' or most desirable?

Regards
Steve

John, 

Thanks for the tip.  I had thought of checking that as well as I 
drifted off to sleep.  That was it-in spades.   I had 
input two different subplot codes but somehow only one got saved. 
Then I got suckered in by the simplicity of initializing
the list using [ 2*Subpdata() ] where Subpdata is a class
defining the various attributes of a subplot in my program. 
However, I soon found out that this made my problem worse;
Python went into an endless loop.  Again, this gave me two
subplot codes but they were the same.   The simple list 
initialization binds the same instance object to the two 
list entries.  Not what I wanted.  After using a for statement
to initialize, I got my two subplots.  

I am now able to create multiple figures, each with one or more
subplots with my software.  What a great collection of software. 
Thanks for all the work. 

I tried using mx.datetime to create an mx.datetime instance
which worked fine. However, mx2num() fails with python 
claiming an undefined mxdates.  I checked the source and 
found only one  mxdates.  No idea how it should be defined. 
In the mean time I am using a datetime instance but I lose
a small bit of precision with only integer seconds. 

                            Delbert

 
On Tuesday 01 February 2005 05:38 am, John Hunter wrote:
> >>>>> "Delbert" == Delbert D Franz <dd...@lk...> writes:
> 
>     Delbert> I have made great progress with my GUI to plot
>     Delbert> time-series files from my unsteady-flow modeling
>     Delbert> software.  It works when I have one subplot per figure
>     Delbert> but I have not been able to get two subplots (211 and
>     Delbert> 212) to work.  Only the lower subplot appears and the
>     Delbert> trace or line assigned to the upper subplot (211) appears
>     Delbert> in the lower subplot.  The space for the upper subplot
>     Delbert> appears as blank space in the figure.
> 
> You code looks correct on first glance (except did you mean tht title
> to be in the loop?) .  My guess is your data structure has a bug in
> it.  Add a print statement and make sure the loc code is as you think
> it is.
> 
>         print fg.fgs[ifg].sp[isp].loc_code
>         ax = f.add_subplot(fg.fgs[ifg].sp[isp].loc_code)  
> 
> If they are correct, you need to compose a minimum, free standing
> script that replicates your problem and I can take a look.
> 
> Hope this helps,
> JDH
> 
> 

I am working in interactive mode, with the GTKAgg backend. When I make a 
figure, I was not able to resize it on the screen. I tried changing my dpi 
and default figure size in .matplotlibrc, and now I can increase the figure 
size, but not decrease it passed its original size. I changed 
my .matplotlibrc back to its original configuration, and the same behavior 
persists: I can increase the figure size, but not decrease it passed the 
original size. This is also true for the GTK backend, but not for WXAgg.

I rebuilt my atlas libraries today, along with Numeric, and numarray. I dont 
think that should have anything to do with it, but I rebuilt gtk+, pygtk, and 
matplotlib just in case. All are the latest version. 

Everything else seems to work, minimizing, maximizing, closing, but not 
resizing. Does anyone have a suggestion as to what is wrong, or what I might 
check?

 
Thanks,
Darren

> See my previous message about building matplotlib on OS-X. Now that 
> I've done that, I need to give it to some of my coworkers that don't 
> have the dev tools installed, and are aghast at the idea of typing 
> ./configure; make, make install.
>
> So, how do I make a binary distro?

Wow, serendipity!
I was just sitting down to the challenge of building matplotlib on os-x 
myself.  Please keep the list(s) updated on your progress.  I would 
certainly prefer running an install script or mpkg than trying to 
compile all the dependencies.
*sending karma,
    Brendan

______________________________________________________________________ 

Post your free ad now! http://personals.yahoo.ca

On Feb 1, 2005, at 19:04, Chris Barker wrote:

> See my previous message about building matplotlib on OS-X. Now that 
> I've done that, I need to give it to some of my coworkers that don't 
> have the dev tools installed, and are aghast at the idea of typing 
> ./configure; make, make install.
>
> So, how do I make a binary distro? I know I can get distutils to do 
> it, but it won't included the needed extra libs:
>
> freetype
> libpng
> zlib

zlib ships with OS X

> It seems I have three options:
>
> 1) Just give them a tarball of the compiled libs, ready to be dropped 
> into /usr/local (I don't like that option, what If I clobber 
> something?)
>
> 2) Somehow put the libs inside the matplotlib distro

That's possible

> 3) Statically link those libs into the matplotlib extensions

But this is better

> I have no idea how to do 2 or 3, but could probably figure it out.

This is (3)
Make sure you don't have libpng.dylib or libfreetype.dylib sitting 
around on your link paths...

Build them like this:
./configure --disable-shared --enable static

Make sure you only have libpng.a and libfreetype.a on your link paths.  
It will link statically.

> What do folks suggest? Any pointers?

After you've linked matplotlib statically, use bdist_mpkg from py2app 
to make a redistributable .pkg installer for it.  After installing 
py2app, you should have a tool in /usr/local/bin called "bdist_mpkg" 
that will Just Do It without any setup.py modifications to the target 
lib... so go into the matplotlib directory, type bdist_mpkg, and cross 
your fingers that a dist/matplotlib-xx.pkg will appear.  If you have 
any problems beyond that, let me know.

-bob