matplotlib-users Mailing List for matplotlib

On Fri, Mar 12, 2010 at 3:47 PM, Alan G Isaac <ala...@gm...> wrote:
> I suggest instead
> "These values are measure in font-size units.
> E.g., a fontsize of 10 points and a handlelength=5
> implies a handlelength of 50 points."
>
Thanks. Applied in r8159.
Regards,
-JJ

Note that there is a significant bug in the path.simplify code in the
latest released version that is fixed in svn. The simplification
should not be visible to the human eye. Please try the release
candidate at
 http://drop.io/xortel1#
if you don't have access to svn
JDH
On Fri, Mar 12, 2010 at 2:12 PM, Tornes, Ivan E <to...@ba...> wrote:
>
> Thanks for the information. I'll give the suggestions a try. In the meantime setting Simplify = True in the matplotlibrc file gets it to plot without failing.
>
> I know I lose some of the screen information by doing this, but I can live with that for now, so I can continue work on the rest of my project.

> On Thu, Mar 11, 2010 at 8:32 PM, Alan G Isaac <ai...@am...> wrote:
> > 1. What are the units (and why not points)?
On 3/11/2010 11:00 PM, Jae-Joon Lee wrote:
> Fraction of (legend) font size (in points). It was decided that it is
> these dimensions are better to be scale with font size.
> For example, handlelength=5 means 50 points when legend font size is 
10 points.
OK, I see the reasoning,
although I personally would still prefer points.
In any case, I see that this information was in
the documentation, but I failed to understand it.
The documentation reads:
"The dimensions of these values are given as a fraction of the fontsize."
I suggest instead
"These values are measure in font-size units.
E.g., a fontsize of 10 points and a handlelength=5
implies a handlelength of 50 points."
Thanks!
Alan Isaac

Hello,
I read a simple data stream from my computers serial port. I can nicely read
the data using pyserial library but couldn't get it *nicely* working neither
with WXAgg nor Qt4Agg using the following code. Although with WX I could get
updated looks, the figure isn't very responsive in this way. I have looked
at simple_idle_wx example but for some reason I can't make it work to update
the canvas whenever the condition satisfied.
What is the trick to make the real-time data plotted on the screen easily
without blocking the figure itself?
import serial
import matplotlib.pyplot as plt
plt.ion()
ser = serial.Serial(0)
conc = []
while True:
 s = ser.readline()
 if s.startswith('CONC'):
 conc.append(float(s.split()[2]))
 plt.plot(conc)
 plt.show()
 plt.clf()
ser.close()
-- 
Gökhan

Ah perfect, thanks a lot, sorry for the mundane question :)
-- 
View this message in context: http://old.nabble.com/xlim-with-dates-tp27881612p27882177.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Alex S wrote:
> 
> Hi there, does anyone know if there's a simple way to set an axis limit to
> a date? "viewlim_to_dt()" looks promising, but I can't figure out how to
> use it...
> 
> Thanks a lot,
> Alex
> 
Alex,
I've done something like this in the past:
 ax.set_xlim( ( min_val, max_val ) )
 # improve formatting
 fig.autofmt_xdate( bottom = 0.20000000000000001, rotation = 30,
ha = 'right' )
 where min_val and max_val are values from
matplotlib.dates.date2num( dt ) because
 dt is a datetime object, which is not the format matplotlib
uses. 
So, setting the xlimit ( or ylimit ) using the values expected by
matplotlib manually is one option.
def date2num(d):
 """
 *d* is either a :class:`datetime` instance or a sequence of datetimes.
 Return value is a floating point number (or sequence of floats)
 which gives number of days (fraction part represents hours,
 minutes, seconds) since 0001年01月01日 00:00:00 UTC.
 """
-Erik
-- 
View this message in context: http://old.nabble.com/xlim-with-dates-tp27881612p27882067.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi there, does anyone know if there's a simple way to set an axis limit to a
date? "viewlim_to_dt()" looks promising, but I can't figure out how to use
it...
Thanks a lot,
Alex
-- 
View this message in context: http://old.nabble.com/xlim-with-dates-tp27881612p27881612.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Fri, Mar 12, 2010 at 12:15 PM, Eric Firing <ef...@ha...> wrote:
> This example is mostly obsolete--the clipping procedure is built-in. (The
> value added by the example is the change in marker style.)
Right, which is what I was trying to get at in the following:
 While this may not solve your case, because it looks like you may be
 exceeding the rendering complexity with data in the viewport, the
 design pattern may help inspire to you to write a custom class to
 handle adaptively decimating your data so you can still see a sketch
 of your data when panned out, but nonethless get the full detail when
 zoomed in.
What I was trying to point out is you can hook into the event handling
/ callback mechanism to do *custom* level of detail clipping based on
viewport or some other feature if the default simplification is not
adequate. Along these lines Ivan, you may want to take a look at the
event handling tutorial
http://matplotlib.sourceforge.net/users/event_handling.html
Perhaps we should wework the example to do something more useful that
is not already handled better by path simplification.
JDH

John Hunter wrote:
> On Fri, Mar 12, 2010 at 8:30 AM, Tornes, Ivan E <to...@ba...> wrote:
>> I’m working on a project that handles large data sets. Up to this point I
>> had not had any issues using matplotlib, but I tried yesterday to have it
>> plot a file that had 8 million float,float pairs in it and dies with the
>> following message:
> 
> There have been some enhancements in path simplification in svn, so
> you may want to try this but no guarantees this will help
> 
> http://matplotlib.sourceforge.net/faq/installing_faq.html#install-from-svn
> 
> Alternatively, you could use something like the "clippedline" example.
> The basic idea is that most screen devices have order of a couple
> million pixels, so there is no way to resolve more points than that.
> But you may want to be able to zoom into a certain region will full
> detail, which is not possible if you decimate your data before hand.
> What the clippedline demo does is just pass the points that are in the
> current viewport to mpl.
> 
> http://matplotlib.sourceforge.net/examples/pylab_examples/clippedline.html
John,
This example is mostly obsolete--the clipping procedure is built-in. 
(The value added by the example is the change in marker style.)
Path simplification does a more thorough and general job of clipping. 
The reason for having the pre-clipping in the special but common case of 
monotonic x is that it can take advantage of a binary search, which is 
faster than the path-simplification's linear search for large datasets.
Eric
> 
> While this may not solve your case, because it looks like you may be
> exceeding the rendering complexity with data in the viewport, the
> design pattern may help inspire to you to write a custom class to
> handle adaptively decimating your data so you can still see a sketch
> of your data when panned out, but nonethless get the full detail when
> zoomed in.
> 
> This is in part what what the path simplification algorithm tries to
> achieve, so do take a look if things work better on svn HEAD.
> 
> Hope this helps,
> JDH
> 
> ------------------------------------------------------------------------------
> 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

On Fri, Mar 12, 2010 at 8:30 AM, Tornes, Ivan E <to...@ba...> wrote:
> I’m working on a project that handles large data sets. Up to this point I
> had not had any issues using matplotlib, but I tried yesterday to have it
> plot a file that had 8 million float,float pairs in it and dies with the
> following message:
There have been some enhancements in path simplification in svn, so
you may want to try this but no guarantees this will help
 http://matplotlib.sourceforge.net/faq/installing_faq.html#install-from-svn
Alternatively, you could use something like the "clippedline" example.
 The basic idea is that most screen devices have order of a couple
million pixels, so there is no way to resolve more points than that.
But you may want to be able to zoom into a certain region will full
detail, which is not possible if you decimate your data before hand.
What the clippedline demo does is just pass the points that are in the
current viewport to mpl.
 http://matplotlib.sourceforge.net/examples/pylab_examples/clippedline.html
While this may not solve your case, because it looks like you may be
exceeding the rendering complexity with data in the viewport, the
design pattern may help inspire to you to write a custom class to
handle adaptively decimating your data so you can still see a sketch
of your data when panned out, but nonethless get the full detail when
zoomed in.
This is in part what what the path simplification algorithm tries to
achieve, so do take a look if things work better on svn HEAD.
Hope this helps,
JDH

Pierre de Buyl wrote:
> change line 29 to:
> left, bottom, width, height = 0.1, 0.07, 1., 0.84 # values in 0-1 
> relative figure coordinates -- allow space on left for colorbar
>
> it works on my machine (python 2.5 and mpl 0.99, mac os X 10.4).
>
> Pierre
> Le 11 mars 10 à 23:36, Jim Vickroy a écrit :
Thanks Pierre. Your suggestion (along with a change in the figsize 
parameter setting) got me going in the right direction -- so to speak. 
-- jv
>
>> Hello,
>>
>> The attached script was used to generate the attached figure.
>>
>> I am seeking guidance on how to (at run-time) reduce the width of the 
>> (black) border on the right side of the figure.
>>
>> All of my attempts have either cropped the color bar (on the left) or 
>> shifted the color bar over the "image" area of the figure.
>>
>> Thanks,
>> -- jv
>>
>> P.S.
>> I'm using Python 2.6.4 and matplotlib 0.99.1.
>> <figure with colorbar on left.py><trial.png>
>> ------------------------------------------------------------------------------ 
>>
>> 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
>

I am using vlines to draw multiple bar graphs in a single figure. I would
like for lines at adjacent x-values to have no gap between them, but I
can't figure out how to make this happen, other than to use a really fat
line width (which I would prefer not to do). Any help is appreciated. I can
make the code available if necessary.

Hi All,
An update:
I have likely figured out the problem. When I did a fresh install of 
Python-2.6 on my mac, I simply used
./configure
and reading more about installing on the mac, I believe I should have 
used
./configure --enable-framework
to support all the GUI stuff. Well, I tried this, but got the warning,
Failed to find the necessary bits to build these modules:
_bsddb gdbm linuxaudiodev
ossaudiodev readline spwd
sunaudiodev
so, instead of trying to track down the solution to this problem (I am 
still new at learning how to properly install software from binaries) 
I just grabbed the latest python-2.6 .dmg file for mac, and installed 
with that.
Now, everything seems to work fine. :)
Cheers,
Andre
On Mar 11, 2010, at 4:56 PM, James Boyle wrote:
> I have the same problem with nearly identical setup:
> OS X 10.5.8 - intel
> matplotlib 99.1.1
> python 2.6.1
> ipython 0.9.1
> numpy-1.3.0
>
> --Jim
>
>
> On Mar 11, 2010, at 1:31 PM, Andre Walker-Loud wrote:
>
>> Hi All,
>>
>> I am having a problem saving figures produced with matplotlib. Right
>> now, I am running a freshly built
>>
>> matplotlib-0.99.1.2 (unzipped, the directory reads 0.99.1.1?) built 
>> on
>> python-2.6
>> numpy-1.3.0
>> scipy-0.7.1
>> ipython-0.10
>>
>>
>> All on an OSX 10.5 intel.
>>
>> When I try to save a figure, in the "Save the figure" dialogue box,
>> the "Save As:" window does not recognize any keyboard entries. If I
>> copy and paste, that works (at first). But I remembered reading 
>> about
>> this problem people were having with Snow Leopard.
>>
>> Originally, copy/pasting worked to "workaround" this problem, but I
>> find that after trying a few other things, I can no longer even paste
>> anything into the "Save As:" Box. Further, when I click the "Save" 
>> or
>> "Cancel" buttons, they flash like normal, however the dialogue box
>> does not go away, the file is not saved, and I can't escape!
>> Ahhhhhh! I can still navigate through my folders with the mouse in
>> the dialogue box, but clearly something is not right.
>>
>>
>> Last week, I had Python 2.5, matplotlib 0.98.6 and everything worked
>> just fine.
>>
>> I have the problem whether running through python or ipython.asdfasdf
>>
>>
>> Any ideas how to fix this?
>>
>>
>> Thanks,
>>
>> Andre
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>
>
> ------------------------------------------------------------------------------
> 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

change line 29 to:
left, bottom, width, height = 0.1, 0.07, 1., 0.84 # values in 0-1 
relative figure coordinates -- allow space on left for colorbar
it works on my machine (python 2.5 and mpl 0.99, mac os X 10.4).
Pierre
Le 11 mars 10 à 23:36, Jim Vickroy a écrit :
> Hello,
>
> The attached script was used to generate the attached figure.
>
> I am seeking guidance on how to (at run-time) reduce the width of 
> the (black) border on the right side of the figure.
>
> All of my attempts have either cropped the color bar (on the left) 
> or shifted the color bar over the "image" area of the figure.
>
> Thanks,
> -- jv
>
> P.S.
> I'm using Python 2.6.4 and matplotlib 0.99.1.
> <figure with colorbar on left.py><trial.png>
> ---------------------------------------------------------------------- 
> --------
> 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

I'm working on a project that handles large data sets. Up to this point I had not had any issues using matplotlib, but I tried yesterday to have it plot a file that had 8 million float,float pairs in it and dies with the following message:
pException in Tkinter callback
Traceback (most recent call last):
 File "/usr/lib/python2.6/lib-tk/Tkinter.py", line 1413, in __call__
 return self.func(*args)
 File "/usr/lib/pymodules/python2.6/matplotlib/backends/backend_tkagg.py", line 212, in resize
 self.show()
 File "/usr/lib/pymodules/python2.6/matplotlib/backends/backend_tkagg.py", line 215, in draw
 FigureCanvasAgg.draw(self)
 File "/usr/lib/pymodules/python2.6/matplotlib/backends/backend_agg.py", line 314, in draw
 self.figure.draw(self.renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/artist.py", line 46, in draw_wrapper
 draw(artist, renderer, *kl)
 File "/usr/lib/pymodules/python2.6/matplotlib/figure.py", line 774, in draw
 for a in self.axes: a.draw(renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/artist.py", line 46, in draw_wrapper
 draw(artist, renderer, *kl)
 File "/usr/lib/pymodules/python2.6/matplotlib/axes.py", line 1721, in draw
 a.draw(renderer)
 File "/usr/lib/pymodules/python2.6/matplotlib/artist.py", line 46, in draw_wrapper
 draw(artist, renderer, *kl)
 File "/usr/lib/pymodules/python2.6/matplotlib/lines.py", line 535, in draw
 drawFunc(renderer, gc, tpath, affine.frozen())
 File "/usr/lib/pymodules/python2.6/matplotlib/lines.py", line 874, in _draw_lines
 self._lineFunc(renderer, gc, path, trans)
 File "/usr/lib/pymodules/python2.6/matplotlib/lines.py", line 918, in _draw_solid
 renderer.draw_path(gc, path, trans)
 File "/usr/lib/pymodules/python2.6/matplotlib/backends/backend_agg.py", line 98, in draw_path
 self._renderer.draw_path(gc, path, transform, rgbFace)
RuntimeError: Agg rendering complexity exceeded. Consider downsampling or decimating your data.
I would prefer to not decimate my data if possible.
Ivan E. Tornes

Jae-Joon Lee wrote:
> 
> 
> Please post a complete example that demonstrate your problem. My guess
> is that maybe you are not setting the transform of the clipping path
> correctly.
> Regards,
> 
> -JJ
> 
> 
> 
Here's a short example that does the opposite of what I'm looking for. The
goal is to take a the polygon "poly_patch" and "cut" regions out of it. 
All I've managed to achieve so far has been to show regions of the
"poly_patch". 
I'm apparently missing a detail somewhere. Thanks for the help!
---
import matplotlib
from matplotlib import patches
import pylab
fig=pylab.figure()
ax=fig.add_subplot(111)
# background line
line = ax.plot( [ 1, 2, 3], [ 1, 2, 3 ] )
# part I would like to see through
hole_patch = patches.Circle((2,2), radius=.5, facecolor='none')
# mask polygon that should cover/hide the area not intersecting the
"hole_patch"
poly_patch = patches.Polygon(((1,1),(1,3),(3,3), (3,1)))
ax.add_patch( hole_patch )
ax.add_patch( poly_patch )
# gets the opposite effect intended
poly_patch.set_clip_path( hole_patch )
pylab.show()
-- 
View this message in context: http://old.nabble.com/Remove%2C-mask%2C-or-hide-parts-of-a-polygon--tp27842142p27874544.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Thu, Mar 11, 2010 at 8:32 PM, Alan G Isaac <ai...@am...> wrote:
> 1. What are the units (and why not points)?
Fraction of (legend) font size (in points). It was decided that it is
these dimensions are better to be scale with font size.
For example, handlelength=5 means 50 points when legend font size is 10 points.
> 2. Can this be set on a legend object (after creation)?
> (There does not appear to be a setter on the legend;
> do I have to get the handles and set each?)
>
Right now, public setter method is not supported for these attributes.
While this is possible it is a bit tricky. I need to double-check but
you need to change the dimension of not only the associated artist
(e.g., lines) but also its container (offsetbox).
The current design recommends you to create a new legend (by calling
legend again) if you want to change its attribute.
If this approach is not applicable, please describe your use case.
Regards,
-JJ
As of now, some (maybe most) of legend attributes are not exposed is
possible but a bit tricky to do

On Thu, Mar 11, 2010 at 3:14 PM, afancy <gr...@gm...> wrote:
> Hi,
>
> Could anybody know if there is IRC for matplotlib? as I cannot find it.
> Thanks
#scipy is an appropriate for all things numpy, matplotlib, scipy, etc.
Ryan
-- 
Ryan May
Graduate Research Assistant
School of Meteorology
University of Oklahoma

On 3/11/2010 1:44 PM, Jae-Joon Lee wrote:
> Did you try*handlelength*?
> http://matplotlib.sourceforge.net/api/pyplot_api.html#matplotlib.pyplot.legend
OK, now I know what "handlelength" means.
1. What are the units (and why not points)?
2. Can this be set on a legend object (after creation)?
(There does not appear to be a setter on the legend;
do I have to get the handles and set each?)
Thanks,
Alan