matplotlib-users Mailing List for matplotlib (Page 9)

Well the thread on the devel list that I referred to explicitly has the
win32 exe in its title ("Missing __init__.py in
matplotlib-0.87.5.win32-py2.4.exe ?") . The starting post there pretty
much says it all.

There's also a recent post on the numpy list that sounds like it's maybe
the same problem (quote):
"""
Is there a compatible matplotlib as well?  I was o.k. with mpl from
enthought until I switched numerix to numpy.  That made mpl unhappy.
I downloaded 0.87.5 but I broke something in the process because now
even switching back to Numeric doesn't make mpl happy.
"""

Thanks,
Sven

Charlie Moad schrieb:
> That error was relating to the source release.  Can you please post
> your error for the binary?
> 
> On 9/6/06, Sven Schreiber <sve...@gm...> wrote:
>> Charlie Moad schrieb:
>> > Minor rev bump for numpy 1.0b5 compatibility.  This release should
>> > remain compatible with future 1.0 releases of numpy.
>> >
>>
>> I keep running into the ImportError problem described on the devel list,
>> with the win32 2.4 binary (exe). Is that still just a case of waiting
>> for the mirrors to update, or is there a deeper problem? Are there
>> alternative download links? How to tell whether it's the "right" binary,
>> since version numbers are the same?
>>
>> Thanks for your help,
>> Sven
>>
> 

That error was relating to the source release.  Can you please post
your error for the binary?

On 9/6/06, Sven Schreiber <sve...@gm...> wrote:
> Charlie Moad schrieb:
> > Minor rev bump for numpy 1.0b5 compatibility.  This release should
> > remain compatible with future 1.0 releases of numpy.
> >
>
> I keep running into the ImportError problem described on the devel list,
> with the win32 2.4 binary (exe). Is that still just a case of waiting
> for the mirrors to update, or is there a deeper problem? Are there
> alternative download links? How to tell whether it's the "right" binary,
> since version numbers are the same?
>
> Thanks for your help,
> Sven
>

Hello,

I'm creating a program that plots data in real-time.  I  want the
x-axis to be the time in HH:MM:SS.  I'm still playing with the date
formatters, but have run into a problem where it seems the axis puts
in more points on the axis to make the plot fit nicely.  For instance,
I want to have 120 data points (seconds) on the graph.  Initially, the
x-axis starts at, say 0 and goes to 120 (I'd expect this to be 119).
The following second the x-axis should go from 1 to 120, then 2 to
121, etc.  But instead, the x-axis goes from 0 to 140.  Once 141
seconds have passed by, the axis shifts and goes from 20 to 160.

Is there any way to make the axis behave so that it keeps just 120
values on the axis and increment the values as described above?

Thanks!
-Roberto.

Thank you! I realized later how to do this when I realized that I  
hadn't looked at the code for the canvases.

R.

On Aug 29, 2006, at 12:08 AM, John Hunter wrote:

>>>>>> "Richard" == Richard Harvey Chapman <hchapman-matplotlib- 
>>>>>> us...@3g...> writes:
>
>     Richard> Briefly, is there a way to get a callback in the event
>     Richard> that the canvas has been redrawn (e.g. from a zoom or
>     Richard> pan)?
>
>     Richard> matplotlib 0.86.2 python 2.4.1 wxPython 2.6.2.1 Mac OS
>     Richard> X.4.7
>
>     Richard> I draw a circle at a certain point. I let the user drag
>     Richard> that point to a new location. However, if the plot is
>     Richard> redrawn for any reason, I have to redraw my circle in a
>     Richard> new position. I can't seem to find any way to get
>     Richard> notified of a redraw.
>
> Have you dried connecting to a draw_event?
>
>     def ondraw(event):
>         # do something
>         pass
>
>    fig.canvas.mpl_connect('draw_event', ondraw)
>
> FYI, the widgets module matplotlib.widgets is a good place to look for
> examples of mpl event handling, in addition to the class documentation
> in the Event hierarchy in
> http://matplotlib.sourceforge.net/matplotlib.backend_bases.html
>
> JDH

R.

Alan G Isaac wrote:
> Does anyone really care about 25% enough to make this 
> worthwhile?  Just wondering.

I tend to think not. You put 80,000 points in a PS, it's going to be 
big. That's all there is to it, it's the nature of Postscript.

I do think clipping is a good idea though.

What is the maximum precision in Postscript? It seems unlikely that you 
could plot 80,000 points and not have number of them overlap, unless 
it's clipped, so removing essentially redundant points may be another 
way to to go.

-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...

On 9/6/06, Rob Hetland <he...@ta...> wrote:
>
> I have been having problems with postscript output from MPL on my
> various Macs that is just beyond the problem discussed in the tread
> here.  But this seemed like the best place to bring it up.  The basic
> problem is that Adobe products like Illustrator can't read MPL .eps
> output.

FWIW, I've had very good luck recently using inkscape
(http://www.inkscape.org/) to edit PS files, both old ones made by
who-knows-what and fresh mpl-off-svn ones.  I've been able to fix old
labels that needed changes for figures whose data source is nowhere to
be found, change a line color and dashing/cap style, etc.  I'm not a
graphics artist and have never used Illustrator, but for my needs,
inkscape has so far been an excellent (and free!) solution.

Note that this is on a Linux Ubuntu Dapper box, with the pstoedit
program installed, which inkscape uses to read *PS files into an
editable vector format.

Cheers,

f

On Wednesday 06 September 2006 11:04, Rob Hetland wrote:
> Well, the fonts are correct -- I checked in both the EPS source, and
> what Illustrator thinks the font is (after translation with pstopdf).
>
> The definition of the fonts looks right in the EPS source (checked by
> comparing against a sample from illustrator).
>
> If nobody else is having the same problem, typing pstopdf is really
> not a tremendous burden.  I just thought I would raise this issue.
>
> BTW, SVG files seem to do fine with fonts.  However, it can take a
> very long time to save large files in MPL and import large files into
> Illustrator, which seems to want to translate them into some native
> format, and does so poorly.
>
> If I ever figure out a better solution, I'll let you all know,

One of these days, we'll have to figure out how to embed individual glyphs 
rather than the entire font set.

Charlie Moad schrieb:
> Minor rev bump for numpy 1.0b5 compatibility.  This release should
> remain compatible with future 1.0 releases of numpy.
> 

I keep running into the ImportError problem described on the devel list,
with the win32 2.4 binary (exe). Is that still just a case of waiting
for the mirrors to update, or is there a deeper problem? Are there
alternative download links? How to tell whether it's the "right" binary,
since version numbers are the same?

Thanks for your help,
Sven

Well, the fonts are correct -- I checked in both the EPS source, and  
what Illustrator thinks the font is (after translation with pstopdf).

The definition of the fonts looks right in the EPS source (checked by  
comparing against a sample from illustrator).

If nobody else is having the same problem, typing pstopdf is really  
not a tremendous burden.  I just thought I would raise this issue.

BTW, SVG files seem to do fine with fonts.  However, it can take a  
very long time to save large files in MPL and import large files into  
Illustrator, which seems to want to translate them into some native  
format, and does so poorly.

If I ever figure out a better solution, I'll let you all know,

-Rob

On Sep 6, 2006, at 8:46 AM, John Hunter wrote:

>>>>>> "Rob" == Rob Hetland <he...@ta...> writes:
>
>     Rob> I have been having problems with postscript output from MPL
>     Rob> on my various Macs that is just beyond the problem discussed
>     Rob> in the tread here.  But this seemed like the best place to
>     Rob> bring it up.  The basic problem is that Adobe products like
>     Rob> Illustrator can't read MPL .eps output.
>
> Are you sure you have set the font paths properly *and* flushed your
> ~/.matplotlib/ttffont.cache before regenerating your files.  Use
> --verbose-debug when creating your test EPS to make sure you are
> getting bitstream fonts.  If you still have trouble, post an errant
> eps file somewhere and maybe someone can poke into it.
>
>     Rob> I think that opening an EPS in Illustrator is the ultimate
>     Rob> test of EPS format compliance, as those are the folks who
>     Rob> made it.
>
> I think this is debatable, as it is a closed source implementation of
> an open document format specification.  But I am willing to accept
> that it is more likely that Illustrator is right than that mpl is
> right.
>
>     Rob> What can we do to make MPL output universally readable
>     Rob> postscript?
>
> Find the bug and fix it :-)
>
> JDH

----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

On Wed, 6 Sep 2006, John apparently wrote:=20
> could make it an rc param for those who want to trade=20
> accuracy for space.

Does anyone really care about 25% enough to make this=20
worthwhile?  Just wondering.

Cheers,
Alan Isaac

>>>>> "humufr" == humufr  <hu...@ya...> writes:
    humufr> Another things that can be good to add is a better
    humufr> clipping. For the moment there are no clipping that means
    humufr> if I have something like::

Here is a little demo that shows you how to do a line that clips
itself to the data view (assuming x is sorted).  It also adds a level
of detail marker when the number of points is not too large.  We used
to have this as a feature in mpl, but removed it because noone ever
used it.  We could add something like this again...


"""
Clip a line according to the current xlimits
"""

from matplotlib.lines import Line2D
import matplotlib.numerix as nx
from pylab import figure, show

class ClippedLine(Line2D):
    """
    Clip the xlimits to the axes view limits -- this example assumes x is sorted
    """

    def __init__(self, ax, *args, **kwargs):
        Line2D.__init__(self, *args, **kwargs)
        self.ax = ax


    def set_data(self, *args, **kwargs):
        Line2D.set_data(self, *args, **kwargs)
        self.xorig = nx.array(self._x)
        self.yorig = nx.array(self._y)
        
    def draw(self, renderer):
        xlim = self.ax.get_xlim()

        ind0, ind1 = nx.searchsorted(self.xorig, xlim)
        self._x = self.xorig[ind0:ind1]
        self._y = self.yorig[ind0:ind1]
        N = len(self._x)
        if N<1000:
            self._marker = 's'
            self._linestyle = '-'
        else:
            self._marker = None
            self._linestyle = '-'
        
    
        Line2D.draw(self, renderer)
        self._x = self.xorig
        self._y = self.yorig


fig = figure()
ax = fig.add_subplot(111, autoscale_on=False)

t = nx.arange(0.0, 100.0, 0.01)
s = nx.sin(2*nx.pi*t)
line = ClippedLine(ax, t, s, color='g', ls='-', lw=2)
ax.add_line(line)
ax.set_xlim(10,30)
ax.set_ylim(-1.1,1.1)
show()
        
        

Le mercredi 6 septembre 2006 09:49, Darren Dale a =E9crit=A0:
> On Wednesday 06 September 2006 07:49, jo...@st... wrote:
> > Hi,
> >
> > The following plot
> >
> > >>> from numarray import *
> > >>> x =3D arange(80000)
> > >>> from pylab import plot,show
> > >>> plot(x,x)
> > >>> show()
> >
> > and saving in postscript format generated a file of 1.5MB, while the
> > equivalent is only 288KB in xmgrace (another plotting program). If I use
> > plot(x,x,"k,"), this even leads to a horrible 8.0MB. How come? I
> > understand there is an issue with the fonts, but this can't be the only
> > responsible, can it? Plotting no points, just a title, and saving in
> > postscript leads to a file size of only 133KB.
> >
> > FWIW, I'm trying to make postscript plots using Python 2.4.1, latest
> > numarray, and matplotlib 0.83.2.
>
> Each data point consists of a line like
>
> 54.3869 28.6788 l
>
> which is 17 bytes long. 17*80000 =3D 1.36MB. Maybe we dont need as many s=
ig
> figs, that could cut the size down by maybe 25%.
>
> Darren

Another things that can be good to add is a better clipping. For the moment=
=20
there are no clipping that means if I have something like::


x =3D  arange(1000)
plot(x,x)
xlim(30,40)
savefig('test.svg')


All the point are stored in the file, not only the part between 30 and 40.

This is something I spoke before and I fill a bug or feature request on=20
sourceforge (I'have been unable to find it today but I looked fast).

You can check the problem with the svg created if you open it with inkscape=
,=20
you'll see all the point. I understood that this is a bug inside inkscape t=
oo=20
butthat means that all the point are there and it's a big concern for me wh=
en=20
I have to plot plenty of spectra and use only a small range because I know=
=20
that my file at the end will be huge. The only way I found is 1) save in pn=
g=20
and use another software to save it in eps but I loose the fact that eps is=
 a=20
vectoriel format 2) do the clipping myself or 3) create my plot with anothe=
r=20
software like pgplot or gnuplot.=20

On Wednesday 06 September 2006 09:49, John Hunter wrote:
> >>>>> "Darren" == Darren Dale <dd...@co...> writes:
>
>     Darren> which is 17 bytes long. 17*80000 = 1.36MB. Maybe we dont
>     Darren> need as many sig figs, that could cut the size down by
>     Darren> maybe 25%.
>
> We could make the fmt string for PS and SVG output floats a
> configurable parameter and be done with it.  As you know, we've spent
> a lot of time trying to get the right string that doesn't produce
> visual errors and I'm not inclined to change the default.  But we
> could make it an rc param for those who want to trade accuracy for
> space.

Good idea. Should we make it a kwarg or an rc parameter? The number of rc 
parameters continues to grow...

>>>>> "Darren" == Darren Dale <dd...@co...> writes:


    Darren> which is 17 bytes long. 17*80000 = 1.36MB. Maybe we dont
    Darren> need as many sig figs, that could cut the size down by
    Darren> maybe 25%.

We could make the fmt string for PS and SVG output floats a
configurable parameter and be done with it.  As you know, we've spent
a lot of time trying to get the right string that doesn't produce
visual errors and I'm not inclined to change the default.  But we
could make it an rc param for those who want to trade accuracy for
space.

JDH

>>>>> "Rob" == Rob Hetland <he...@ta...> writes:

    Rob> I have been having problems with postscript output from MPL
    Rob> on my various Macs that is just beyond the problem discussed
    Rob> in the tread here.  But this seemed like the best place to
    Rob> bring it up.  The basic problem is that Adobe products like
    Rob> Illustrator can't read MPL .eps output.

Are you sure you have set the font paths properly *and* flushed your
~/.matplotlib/ttffont.cache before regenerating your files.  Use
--verbose-debug when creating your test EPS to make sure you are
getting bitstream fonts.  If you still have trouble, post an errant
eps file somewhere and maybe someone can poke into it.

    Rob> I think that opening an EPS in Illustrator is the ultimate
    Rob> test of EPS format compliance, as those are the folks who
    Rob> made it.  

I think this is debatable, as it is a closed source implementation of
an open document format specification.  But I am willing to accept
that it is more likely that Illustrator is right than that mpl is
right.  

    Rob> What can we do to make MPL output universally readable
    Rob> postscript?

Find the bug and fix it :-)

JDH

>>>>> "joris" == joris  <jo...@st...> writes:

    joris> Hi, The following plot

    >>>> from numarray import * x = arange(80000) from pylab import
    >>>> plot,show plot(x,x) show()

    joris> and saving in postscript format generated a file of 1.5MB,
    joris> while the equivalent is only 288KB in xmgrace (another
    joris> plotting program). If I use plot(x,x,"k,"), this even leads
    joris> to a horrible 8.0MB. How come? I understand there is an
    joris> issue with the fonts, but this can't be the only
    joris> responsible, can it? Plotting no points, just a title, and
    joris> saving in postscript leads to a file size of only 133KB.

    joris> FWIW, I'm trying to make postscript plots using Python
    joris> 2.4.1, latest numarray, and matplotlib 0.83.2.

matplotlib embeds the truetype fonts directly into the postscript
file, so what you see on the screen is what you get in the ps file.
This is a feature and not a bug :-).  The file size ocst is fixed and
does not grow with plot size.  If you find these largish PS files
unpalatable, you can use native postscript fonts by setting

ps.useafm         : True    # use of afm fonts, results in small files

in your matplotlibrc file -- http://matplotlib.sf.net/matplotlibrc

JDH

On Wednesday 06 September 2006 07:49, jo...@st... wrote:
> Hi,
>
> The following plot
>
> >>> from numarray import *
> >>> x = arange(80000)
> >>> from pylab import plot,show
> >>> plot(x,x)
> >>> show()
>
> and saving in postscript format generated a file of 1.5MB, while the
> equivalent is only 288KB in xmgrace (another plotting program). If I use
> plot(x,x,"k,"), this even leads to a horrible 8.0MB. How come? I understand
> there is an issue with the fonts, but this can't be the only responsible,
> can it? Plotting no points, just a title, and saving in postscript leads to
> a file size of only 133KB.
>
> FWIW, I'm trying to make postscript plots using Python 2.4.1, latest
> numarray, and matplotlib 0.83.2.

Each data point consists of a line like 

54.3869 28.6788 l

which is 17 bytes long. 17*80000 = 1.36MB. Maybe we dont need as many sig 
figs, that could cut the size down by maybe 25%.

Darren

I have been having problems with postscript output from MPL on my  
various Macs that is just beyond the problem discussed in the tread  
here.  But this seemed like the best place to bring it up.  The basic  
problem is that Adobe products like Illustrator can't read MPL .eps  
output.

When I 'Open' the file, OS X uses ghostscript to convert the EPS to  
PDF, and this displays fine.  I can use Preview to save this file,  
and it looks alright, however, none of the Adobe products can read  
the PDF either.  Usually the file will open, but the fonts are all  
screwed up.

When I use pstopdf from teTeX (but *not* epstopdf -- that doesn't  
work for some strange reason), then I can open my new PDF file in  
illustrator.

I think that opening an EPS in Illustrator is the ultimate test of  
EPS format compliance, as those are the folks who made it.  What can  
we do to make MPL output universally readable postscript?

-Rob

p.s.  One I finally do get it into Illustrator, it becomes clear that  
MPL makes very nice, efficient, easily editable files...  unlike  
MATLAB.  For me this is yet another big reason to switch to python/ 
numpy/mpl.

----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331

Is there a method of using the show() command more
than once in a script?  I know that it should be
called once all commands have been entered for the
graph, but I'm wondering if there is a way of
resetting this so that I can call show() a second time
without my program crashing.

Thanks,
Matt

__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

I cannot help you with making matplotlib create smaller files but sam2p
<http://www.inf.bme.hu/%7Epts/sam2p/> is an image conversion program
that creates small files. You might be able to convert your file to make
it smaller.

Bill

jo...@st... wrote:
> Hi,
>
> The following plot
>
>   
>>>> from numarray import *
>>>> x = arange(80000)
>>>> from pylab import plot,show
>>>> plot(x,x)
>>>> show()
>>>>         
>
> and saving in postscript format generated a file of 1.5MB, while the equivalent is 
> only 288KB in xmgrace (another plotting program). If I use plot(x,x,"k,"), this
> even leads to a horrible 8.0MB. How come? I understand there is an issue 
> with the fonts, but this can't be the only responsible, can it? Plotting no points, 
> just a title, and saving in postscript leads to a file size of only 133KB.
>
> FWIW, I'm trying to make postscript plots using Python 2.4.1, latest numarray, 
> and matplotlib 0.83.2.
>
> Cheers,
> Joris
>
>
>
> Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>   

Hi,

The following plot

>>> from numarray import *
>>> x = arange(80000)
>>> from pylab import plot,show
>>> plot(x,x)
>>> show()

and saving in postscript format generated a file of 1.5MB, while the equivalent is 
only 288KB in xmgrace (another plotting program). If I use plot(x,x,"k,"), this
even leads to a horrible 8.0MB. How come? I understand there is an issue 
with the fonts, but this can't be the only responsible, can it? Plotting no points, 
just a title, and saving in postscript leads to a file size of only 133KB.

FWIW, I'm trying to make postscript plots using Python 2.4.1, latest numarray, 
and matplotlib 0.83.2.

Cheers,
Joris



Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

Refer to the top of the setupext.py file.

On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
> Where can I find these mingw instructions?  Sorry for asking such a simple
> question but I can not seem to find them, ive googled it looked in the
> readme file and cant find them :/.
>
> ----- Original Message -----
> From: "Charlie Moad" <cw...@gm...>
> To: "Kenny Ortmann" <ya...@em...>
> Cc: "matplotlib-users" <mat...@li...>
> Sent: Tuesday, September 05, 2006 2:45 PM
> Subject: Re: [Matplotlib-users] installation
>
>
> > VS2003.Net is needed to easily build the python 2.4 version. (e.g.
> > python setup.py build)  You can also follow the mingw instructions for
> > a more open-source way of building matplotlib for windows.  We still
> > have to do this for python 2.3.  You can supposedly download the .net
> > compiler tools for free, but I haven't tried.  I am pasting my
> > previous post since I didn't re-all.
> >
> >> > In order to build mpl with visual studio it requires VS.Net 2003.
> >> > Python 2.5 will be a little more "open" since it requires VS2005 and
> >> > there is a free edition of VS2005 called "Express Edition".  Python
> >> > 2.3 required the version of VS before .Net.
> >
> > - Charlie
> >
> > On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
> >> Do i need to reinstall vs2003.net?  I do not have access to that product
> >> anylonger.  I tried to obtain the latest SVN and i still recieved the
> >> same
> >> error.  Is there a certain way you are supposed to compile mpl on windows
> >> if
> >> you dont use the .exe?  for instance do i have to build it first?  or
> >> anything like that
> >>
> >>
> >> ----- Original Message -----
> >> From: "Charlie Moad" <cw...@gm...>
> >> To: "Kenny Ortmann" <ya...@em...>
> >> Sent: Tuesday, September 05, 2006 1:21 PM
> >> Subject: Re: [Matplotlib-users] installation
> >>
> >>
> >> > On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
> >> >> Hey Charlie thanks for the info.
> >> >>
> >> >> I went ahead and installed Active Tcl
> >> >> I removed microsft visual studio 2003 .net from my computer because I
> >> >> never
> >> >> used it, and I did not want it on here in the first place but i had it
> >> >> on
> >> >> here from being an intern over the summer.
> >> >
> >> > You can use the new mpl release from today.
> >> >
> >> > In order to build mpl with visual studio it requires VS.Net 2003.
> >> > Python 2.5 will be a little more "open" since it requires VS2005 and
> >> > there is a free edition of VS2005 called "Express Edition".  Python
> >> > 2.3 required the version of VS before .Net.
> >> >
> >>
> >>
> >
>
>

Where can I find these mingw instructions?  Sorry for asking such a simple
question but I can not seem to find them, ive googled it looked in the
readme file and cant find them :/.

----- Original Message -----
From: "Charlie Moad" <cw...@gm...>
To: "Kenny Ortmann" <ya...@em...>
Cc: "matplotlib-users" <mat...@li...>
Sent: Tuesday, September 05, 2006 2:45 PM
Subject: Re: [Matplotlib-users] installation


> VS2003.Net is needed to easily build the python 2.4 version. (e.g.
> python setup.py build)  You can also follow the mingw instructions for
> a more open-source way of building matplotlib for windows.  We still
> have to do this for python 2.3.  You can supposedly download the .net
> compiler tools for free, but I haven't tried.  I am pasting my
> previous post since I didn't re-all.
>
>> > In order to build mpl with visual studio it requires VS.Net 2003.
>> > Python 2.5 will be a little more "open" since it requires VS2005 and
>> > there is a free edition of VS2005 called "Express Edition".  Python
>> > 2.3 required the version of VS before .Net.
>
> - Charlie
>
> On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
>> Do i need to reinstall vs2003.net?  I do not have access to that product
>> anylonger.  I tried to obtain the latest SVN and i still recieved the
>> same
>> error.  Is there a certain way you are supposed to compile mpl on windows
>> if
>> you dont use the .exe?  for instance do i have to build it first?  or
>> anything like that
>>
>>
>> ----- Original Message -----
>> From: "Charlie Moad" <cw...@gm...>
>> To: "Kenny Ortmann" <ya...@em...>
>> Sent: Tuesday, September 05, 2006 1:21 PM
>> Subject: Re: [Matplotlib-users] installation
>>
>>
>> > On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
>> >> Hey Charlie thanks for the info.
>> >>
>> >> I went ahead and installed Active Tcl
>> >> I removed microsft visual studio 2003 .net from my computer because I
>> >> never
>> >> used it, and I did not want it on here in the first place but i had it
>> >> on
>> >> here from being an intern over the summer.
>> >
>> > You can use the new mpl release from today.
>> >
>> > In order to build mpl with visual studio it requires VS.Net 2003.
>> > Python 2.5 will be a little more "open" since it requires VS2005 and
>> > there is a free edition of VS2005 called "Express Edition".  Python
>> > 2.3 required the version of VS before .Net.
>> >
>>
>>
>

VS2003.Net is needed to easily build the python 2.4 version. (e.g.
python setup.py build)  You can also follow the mingw instructions for
a more open-source way of building matplotlib for windows.  We still
have to do this for python 2.3.  You can supposedly download the .net
compiler tools for free, but I haven't tried.  I am pasting my
previous post since I didn't re-all.

> > In order to build mpl with visual studio it requires VS.Net 2003.
> > Python 2.5 will be a little more "open" since it requires VS2005 and
> > there is a free edition of VS2005 called "Express Edition".  Python
> > 2.3 required the version of VS before .Net.

- Charlie

On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
> Do i need to reinstall vs2003.net?  I do not have access to that product
> anylonger.  I tried to obtain the latest SVN and i still recieved the same
> error.  Is there a certain way you are supposed to compile mpl on windows if
> you dont use the .exe?  for instance do i have to build it first?  or
> anything like that
>
>
> ----- Original Message -----
> From: "Charlie Moad" <cw...@gm...>
> To: "Kenny Ortmann" <ya...@em...>
> Sent: Tuesday, September 05, 2006 1:21 PM
> Subject: Re: [Matplotlib-users] installation
>
>
> > On 9/5/06, Kenny Ortmann <ya...@em...> wrote:
> >> Hey Charlie thanks for the info.
> >>
> >> I went ahead and installed Active Tcl
> >> I removed microsft visual studio 2003 .net from my computer because I
> >> never
> >> used it, and I did not want it on here in the first place but i had it on
> >> here from being an intern over the summer.
> >
> > You can use the new mpl release from today.
> >
> > In order to build mpl with visual studio it requires VS.Net 2003.
> > Python 2.5 will be a little more "open" since it requires VS2005 and
> > there is a free edition of VS2005 called "Express Edition".  Python
> > 2.3 required the version of VS before .Net.
> >
>
>

Karl Edler wrote:
> Hello,
> 
> I am trying to construct a contour plot where the contours are separated 
> by a constant amount but I would like a color bar (or something) to show 
> what the values of the different levels are. I will have too many 
> contours for clabels to be effective.
> 
> When I use colorbar with unequally spaced contours and use 
> cspacing='linear' the ticks are spaced nicely but the colors are not.

Karl,

This was fixed some time ago with completely new colorbar code, 
including a change in the API.  Attached are a modification of your test 
program to suit the API (and make a smaller png file for this email), 
and the result.

Eric