matplotlib-users Mailing List for matplotlib

How up-to-date is Macports?
This is a reasonable approximation of how I got my OX 10.6 machine set up:
http://newmediaandcapitalmarkets.org/component/content/article/68-how-i-got-matplotlib-working-on-my-macbook.html
> -----Original Message-----
> From: Christopher Barker [mailto:Chr...@no...]
> Sent: Wednesday, March 24, 2010 3:47 PM
> To: mat...@li...
> Subject: Re: [Matplotlib-users] where's superpack?
> 
> David Kremer wrote:
> >> Does anybody know where I could get a
> >> copy of superpack?
> 
> I don't know of the status of that, but this is what I recommend:
> 
> install the python2.6 from python.org
> install the numpy1.3 binary from scipy.org
> install the matplotlib binary (*.dmg) from matplotlib.org
> 
> (optional)
> install the scipy binary from scipy.org
> 
> and there you go -- I suppose it would be nice to have it all in one
> install, but that's not too hard.
> 
> (if you really want all in one -- check out Python(x,y) or EPD)
> 
> 
> -Chris
> 
> 
> --
> Christopher Barker, Ph.D.
> Oceanographer
> 
> Emergency Response Division
> NOAA/NOS/OR&R (206) 526-6959 voice
> 7600 Sand Point Way NE (206) 526-6329 fax
> Seattle, WA 98115 (206) 526-6317 main reception
> 
> Chr...@no...
> 
> -------------------------------------------------------------------------
> -----
> Download Intel® Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi,
Here's a version that goes to the list too :-)
On Fri, Mar 26, 2010 at 9:10 AM, Jae-Joon Lee <lee...@gm...> wrote:
> With the current svn, I cannot reproduce the problem, i.e., bars with
> 0 height are correctly displayed. The x-range is incorrectly set, but
> it is not clear if this is what you meant.
Uhm I tried to use the svn trunk on revision 8214 but it wouldn't
display anything. The script just runs and doesn't open any window.
Anyway the script wasn't quite working, here's an update:
/---------------------------------------------
from pylab import *
import sys
figure(8)
if(len(sys.argv) > 1 and sys.argv[1].lower() == 'y'):
 bar([1, 2, 3, 4, 5], [0, 1, 0, 0, 0])
else:
 bar([1, 2, 3, 4, 5], [1, 2, 3, 4, 5])
show()
\---------------------------------------------
> Can you post a screenshot of your figure? Also, version of your
> matplotlib will be helpful.
Should have thought of that myself, thanks ... The issue occurs with
0.98.3-4ubuntu1 as well as with 0.99.0-1ubuntu1.
Also I had the script save the bar charts. Here's what it produced: if
branch http://img153.imageshack.us/img153/7817/01000.png / else branch
http://img87.imageshack.us/img87/3021/12345my.png .
Thanks for the help.
Cheers, B.

On Thu, Mar 25, 2010 at 4:17 PM, Tom Kuiper <ku...@jp...> wrote:
>
> > Date: 2010年3月25日 13:17:01 -0500
> > From: G?khan Sever <gok...@gm...>
> > Subject: Re: [SciPy-User] milliseconds in matplotlib.dates?
> > To: SciPy Users List <sci...@sc...>
> > Cc: Matplotlib Users <mat...@li...>
> >
> ...
> > Alternatively, you might use just floating-point version of your time
> values
> > and with a little adjustment (Ryan mentioned this in the recently, and
> will
> > forward there for other suggestions) millisecond resolutions should be
> > visible when zoomed in furthest.
> >
> > Something like:
> >
> > sci_fmt = plt.FormatStrFormatter("%.2f")
> > plt.gca().xaxis.set_major_formatter(sci_fmt)
> >
> Here's how I modified my code:
> sci_fmt = FormatStrFormatter("%.2f")
> fig = figure()
> top_axes = subplot(211)
> top_axes.xaxis.set_major_formatter(sci_fmt)
> #plot_date(times,kurts,fmt='b-')
> #plot_date(times,kurt_sm,fmt='r-',label=("Hamming 1-sec FWHM"))
> plot(times,kurts,'b-')
> plot(times,kurt_sm,'r-',label=("Hamming 1-sec FWHM"))
> I then restarted 'ipython -pylab' because I've noticed that date
> formatting problems seems to linger even after a code change. However,
> I see no change in behaviour. I can get six 1-sec ticks across my
> plot. If I expand the plot any more, the ticks disappear.
>
> Regards
>
> Tom
> _______________________________________________
> SciPy-User mailing list
> Sci...@sc...
> http://mail.scipy.org/mailman/listinfo/scipy-user
>
Here is how it looks when I run your code till plot(times...)
http://img202.imageshack.us/img202/5415/ss1i.png
and one with zoom:
http://img411.imageshack.us/img411/8292/ss2el.png
I am not sure this could be related to the mpl version you have.
-- 
Gökhan

With the current svn, I cannot reproduce the problem, i.e., bars with
0 height are correctly displayed. The x-range is incorrectly set, but
it is not clear if this is what you meant.
Can you post a screenshot of your figure? Also, version of your
matplotlib will be helpful.
Regards,
-JJ
On Wed, Mar 24, 2010 at 10:46 PM, b b <coo...@gm...> wrote:
> Hi there,
>
> While creating bar plots I found that bars with height 0 are not being
> displayed. Their space is distributed evenly between the other
> columns.
>
> Sample script:
> /--------------------------------------
> from pylab import *
> import sys
> figure(8)
> if(sys.argv[1].lower() == 'y'):
>  bar([0, 1, 0, 0, 0], [0, 1, 0, 0, 0])
> else:
>  bar([1, 2, 3, 4, 5], [1, 2, 3, 4, 5])
> show()
> \--------------------------------------
>
> Try it with argument 'y' and without.
>
> So far I didn't find a solution. '0' is not an easy thing to google
> :-) Anyone got an idea?
>
> Cheers, B.
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Greetings everyone,
This year, there will be two days of tutorials (June 28th and 29th) before the
main SciPy 2010 conference. Each of the two tutorial tracks (intro, advanced)
will have a 3-4 hour morning and afternoon session both days, for a total of 4
intro sessions and 4 advanced sessions.
The main tutorial web page for SciPy 2010 is here:
http://conference.scipy.org/scipy2010/tutorials.html
We are currently in the process of planning the tutorial sessions. You
can help us in two ways:
Brainstorm/vote on potential tutorial topics
============================================
To help us plan the tutorials, we have setup a web site that allow everyone in
the community to brainstorm and vote on tutorial ideas/topics.
The website for brainstorming/voting is here:
http://conference.scipy.org/scipy2010/tutorialsUV.html
The tutorial committee will use this information to help select the tutorials.
Please jump in and let us know what tutorial topics you would like to see.
Tutorial proposal submissions
=============================
We are now accepting tutorial proposals from individuals or teams that would
like to present a tutorial. Tutorials should be focused on covering a well
defined topic in a hands on manner. We want to see tutorial attendees coding!
We are pleased to offer tutorial presenters stipends this year for the first
time:
 * 1 Session: 1,000ドル (half day)
 * 2 Sessions: 1,500ドル (full day)
Optionally, part of this stipend can be applied to the presenter's
registration costs.
To submit a tutorial proposal please submit the following materials
to 201...@sc... by April 15:
* A short bio of the presenter or team members.
* Which track the tutorial would be in (intro or advanced).
* A short description and/or outline of the tutorial content.
* A list of Python packages that attendees will need to have installed to
 follow along.
Cheers,
Brian Granger
SciPy 2010, Tutorial Chair

2010年3月24日 Jonno <jon...@gm...>:
> Well I realized my error with the extra window being caused by the
> TopLevel() command. I switched this to Tk.Tk() and it works nicely.
> However I still have to pack the frame instead of using grid. I can
> work around this but I wonder if there isn't something else I'm
> missing.
If I'm not completely mistaken you can .grid() your Frame as well, but
you might have to .columnconfigure() and/or .rowconfigure() the Tk
instance with argument weight = 1 or something integer positive, to
make the row containing the plot not collapse to zero?
The main problem is, that the NavigationToolbar2TkAgg actually in
matplotlib.backends.backend_tkagg.py:681 calls self.pack(side =
Tkinter.BOTTOM, fill = Tk.X), where the toolbar is actually derived
from Tkinter.Frame. This means, subclass and overload, or:
toolbar_frame = Tkinter.Frame(tl)
toolbar_frame.grid(column = 0, row = 1)
toolbar=NavigationToolbar2TkAgg(canvas, toolbar_frame)
Now I see why your script hangs, because when you try to pack() and
grid() widgets to the same master, Tk somehow hangs up without error
message, weird if you ask me. But this I encounter often.
hth,
Friedrich

You must give a proper :param width: argument:
 plt.bar(bins, height, 0.01)
http://matplotlib.sourceforge.net/api/axes_api.html#matplotlib.axes.Axes.bar
Friedrich
2010年3月25日 timothee cezard <tc...@st...>:
> Hi all,
> I'm trying to plot a distribution using bar() but when I'm setting the
> left variable to as a sequence of float some of the bar look weird.
> When I replace this sequence by a sequence of int it works fines
> Does anybody know why this happens and how I can fix it?
>
> Here is the code I'm using:
>
> if __name__=="__main__":
>  bins=[0.0, 0.02, 0.04, 0.06, 0.08, 0.1, 0.12, 0.14, 0.16,
>     0.18, 0.2, 0.22, 0.24, 0.26, 0.28, 0.30, 0.32, 0.34,
>     0.36, 0.38, 0.40, 0.42, 0.44, 0.46, 0.48, 0.5, 0.52,
>     0.54, 0.56, 0.58, 0.60, 0.62, 0.64, 0.66, 0.68, 0.70,
>     0.72, 0.74, 0.76, 0.78, 0.80, 0.82, 0.84, 0.86, 0.88,
>     0.90, 0.92, 0.94, 0.96, 0.98, 1.0]
>  height=[89775, 1665, 1791, 1695, 1467, 1395, 1306, 1169,
>      1252, 1134, 1190, 1117, 1018, 995, 1055, 904, 960,
>      886, 810, 821, 829, 763, 766, 857, 737, 862, 724,
>      852, 742, 644, 733, 679, 630, 672, 665, 659, 663,
>      653, 657, 700, 731, 721, 699, 871, 837, 913, 940,
>      966, 1028, 159774, 40002]
>  fig = plt.figure()
>  ax = fig.add_subplot(1,1,1)
>  plt.bar(bins, height)
>  plt.show()

Hi
I would expect
hgt=ma.masked_where(div == 0,hgt)
m.contourf(x,y,hgt,15,cmap=plt.cm.jet)
to produce a map complementary to the map produced by
hgt=ma.masked_where(div != 0,hgt)
m.contourf(x,y,hgt,15,cmap=plt.cm.jet)
But, this is not the case.
What am I missing?
Mathew

On Wed, Mar 24, 2010 at 1:25 PM, Tom Kuiper <ku...@jp...> wrote:
> Greetings, everyone.
>
> I have some time tagged data spanning about three minutes with 4 ms
> resolution. If I plot these with plot_data and focus in on some event
> at high resolution I lose the tick marks. It seems that the minimum
> tick spacing is 1 sec. That appears consistent with strftime which does
> not provide for fractional seconds.
>
> I thought I saw this issue go by not long ago but I don't recall the
> solution, if any.
>
> I'm using python 2.5.2 and matplotlib 1.1.0.
>
> Thanks and regards,
>
> Tom
>
Hi,
As far as I know SecondLocator() is the smallest it gets for time-date
plotting in matplotlib. Probably a new class needs to be written for
MilliSecondLocator() in dates.py
Alternatively, you might use just floating-point version of your time values
and with a little adjustment (Ryan mentioned this in the recently, and will
forward there for other suggestions) millisecond resolutions should be
visible when zoomed in furthest.
Something like:
sci_fmt = plt.FormatStrFormatter("%.2f")
plt.gca().xaxis.set_major_formatter(sci_fmt)
By the way, where did you get mpl v1.1.0? Mine says:
In[19]: matplotlib.__version__
Out[19]: '1.0.svn'
-- 
Gökhan

I would like to add tick labels to a 3d plot, but so far have had no
luck. I would like to start with something like the bars3d example:
http://matplotlib.sourceforge.net/examples/mplot3d/bars3d_demo.html
But I would like to have each bar chart labeled by its tick on the
y-axis. The traditional ax.yaxis.set_ticklabels() method has no
effect, and the ax.yaxis.set_ticks() just messes up the output
catastrophically.
My attempt at modifying the example is below. Any thoughts?
Thanks,
Jeff
-------------------
from mpl_toolkits.mplot3d import Axes3D
import matplotlib.pyplot as plt
import numpy as np
fig = plt.figure()
ax = Axes3D(fig)
for c, z in zip(['r', 'g', 'b', 'y'], [30, 20, 10, 0]):
 xs = np.arange(20)
 ys = np.random.rand(20)
 ax.bar(xs, ys, zs=z, zdir='y', color=c, alpha=0.8)
## My changes
ax.yaxis.set_ticks([0, 10, 20, 30]) # This totally screws things up
ax.yaxis.set_ticklabels(['first', 'second', 'third', 'fourth']) # This
does absolutely nothing
## End my changes
ax.set_xlabel('X')
ax.set_ylabel('Y')
ax.set_zlabel('Z')
plt.show()
------------------------
|| Jeff Klukas, Research Assistant, Physics
|| University of Wisconsin -- Madison
|| jeff.klukas@gmail | jeffyklukas@aim | jeffklukas@skype
|| http://www.hep.wisc.edu/~jklukas/

Hi all,
I'm trying to plot a distribution using bar() but when I'm setting the 
left variable to as a sequence of float some of the bar look weird.
When I replace this sequence by a sequence of int it works fines
Does anybody know why this happens and how I can fix it?
Here is the code I'm using:
if __name__=="__main__":
 bins=[0.0, 0.02, 0.04, 0.06, 0.08, 0.1, 0.12, 0.14, 0.16,
 0.18, 0.2, 0.22, 0.24, 0.26, 0.28, 0.30, 0.32, 0.34,
 0.36, 0.38, 0.40, 0.42, 0.44, 0.46, 0.48, 0.5, 0.52,
 0.54, 0.56, 0.58, 0.60, 0.62, 0.64, 0.66, 0.68, 0.70,
 0.72, 0.74, 0.76, 0.78, 0.80, 0.82, 0.84, 0.86, 0.88,
 0.90, 0.92, 0.94, 0.96, 0.98, 1.0]
 height=[89775, 1665, 1791, 1695, 1467, 1395, 1306, 1169,
 1252, 1134, 1190, 1117, 1018, 995, 1055, 904, 960,
 886, 810, 821, 829, 763, 766, 857, 737, 862, 724,
 852, 742, 644, 733, 679, 630, 672, 665, 659, 663,
 653, 657, 700, 731, 721, 699, 871, 837, 913, 940,
 966, 1028, 159774, 40002]
 fig = plt.figure()
 ax = fig.add_subplot(1,1,1)
 plt.bar(bins, height)
 plt.show()
Tim
-- 
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

I finally found a binary package at rpm bones, so all is fine. Thank you very 
much.

lmkli wrote:
> Thank you!
> 
> I just thought there must be a solution.
> I saw someone posted he can modified contour.py to fix this, but I failed.
> :(
> 
What version of mpl are you using? Are you modifying the default 
anti-aliasing in the patch collections that contour is creating? Are you 
seeing the problem when using the ps and pdf backends, or only with agg 
(that is, creating png files directly)?
There are two problems that can contribute to this, one related to the 
way the agg backend handles the boundaries between filled regions, and 
the other a bug in path simplification, which has been fixed in svn.
Eric
> 
> Marius 't Hart-3 wrote:
>> Actually, it does not draw the polygon edges, but leaves small gaps 
>> between them. Through those gaps you can see the background. (This also 
>> happens with polar plots and other polygons by the way.) I consider this 
>> a bug, though there are ways around it. For contour plots one can plot 
>> two contourplots over each other, one with different levels (or a 
>> different number of levels) than the other. Messy, but it works.
>>
>> Marius.
>>
>> lmkli wrote:
>>> When I use contourf to plot a filled contour map, I get some white-like
>>> lines
>>> between each two color patches, or you can call them gaps.
>>> This is not like the contourf doc string says: "it does not draw the
>>> polygon edges.", actually, it does.
>>> http://old.nabble.com/file/p27982822/contourf1.png contourf1.png 
>>> The figure above is what I get by contourf, but this is not exactlly what
>>> I
>>> want.
>>>
>>> The filled contour map I want should be like this one:
>>> http://old.nabble.com/file/p27982822/contourf2.png contourf2.png 
>>>
>>> Any advice?
>>>
>>> Thank you!
>>> 
>>
>> ------------------------------------------------------------------------------
>> Download Intel® Parallel Studio Eval
>> Try the new software tools for yourself. Speed compiling, find bugs
>> proactively, and fine-tune applications for parallel performance.
>> See why Intel Parallel Studio got high marks during beta.
>> http://p.sf.net/sfu/intel-sw-dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>>
> 

On Wed, Mar 24, 2010 at 8:03 PM, Angus McMorland <am...@gm...> wrote:
> On 24 March 2010 17:33, Nils Wagner <nw...@ia...> wrote:
>> Hi all,
>>
>> how can I change the output format of yticks from 1000000
>> to 1.e6 ?
>
> I'm not sure if there's an easier way still, but this works:
>
> from matplotlib.ticker import Formatter
> class SciFormatter(Formatter):
>  def __call__(self, x, pos=None):
>    return "%0.2e" % x
>
> ax = plt.gca()
> ax.yaxis.set_major_formatter(SciFormatter())
> plt.draw()
There's an easier way to format based on a string:
import matplotlib.pyplot as plt
#Also available in matplotlib.ticker namespace
sci_formatter = plt.FormatStrFormatter('%0.2e')
plt.gca().yaxis.set_major_formatter(sci_formatter)
plt.draw()
You can also make the default formatter (ScalarFormatter) display
scientific notation for smaller numbers (the default is anything with
an abs() >= 1e7). This displays in a slightly different way, with the
base power off to the side of the axis:
form = plt.gca().yaxis.get_major_formatter()
 # so anything with abs() >= 10000 will display in scientific notation
form.set_powerlimits((-4, 4))
plt.draw()
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

Hi there,
While creating bar plots I found that bars with height 0 are not being
displayed. Their space is distributed evenly between the other
columns.
Sample script:
/--------------------------------------
from pylab import *
import sys
figure(8)
if(sys.argv[1].lower() == 'y'):
 bar([0, 1, 0, 0, 0], [0, 1, 0, 0, 0])
else:
 bar([1, 2, 3, 4, 5], [1, 2, 3, 4, 5])
show()
\--------------------------------------
Try it with argument 'y' and without.
So far I didn't find a solution. '0' is not an easy thing to google
:-) Anyone got an idea?
Cheers, B.

At what point is a line Collection useful? 

On 24 March 2010 17:33, Nils Wagner <nw...@ia...> wrote:
> Hi all,
>
> how can I change the output format of yticks from 1000000
> to 1.e6 ?
I'm not sure if there's an easier way still, but this works:
from matplotlib.ticker import Formatter
class SciFormatter(Formatter):
 def __call__(self, x, pos=None):
 return "%0.2e" % x
ax = plt.gca()
ax.yaxis.set_major_formatter(SciFormatter())
plt.draw()
Angus.
-- 
AJC McMorland
Post-doctoral research fellow
Neurobiology, University of Pittsburgh