matplotlib-users Mailing List for matplotlib

Hello,
I am working on creating some distribution plots to analyze cloud droplet
and drop features. You can see one such plot at
http://atmos.uwyo.edu/~gsever/data/rf06_1second/rf06_belowcloud_SurfaceArea_1second.pdf
This file contains 38 pages and each page has 16 panels created via
MPL's AxesGrid toolkit. I am using PdfPages from pdf backend profile to
construct this multi-page plot. The original code that is used to create
this plot is in
http://code.google.com/p/ccnworks/source/browse/trunk/parcel_drizzle/rf06_moments.py
The problem I am reporting is due to the lengthier plot creation times. It
takes about 4 minutes to create such plot in my laptop. To better
demonstrate the issue I created a sample script which you can use to
reproduce my timing results --well based on pseudo/random data points. All
my data points in the original script are float64 so I use float64 in the
sample script as well.
The script is at
http://atmos.uwyo.edu/~gsever/data/matplotlib/test_speed.pyI also
included 2 pages output running the script with nums=2 setting
http://atmos.uwyo.edu/~gsever/data/matplotlib/test_speed.pdf
Comparing my original output, indeed cloud particles are not from a normal
distribution :)
Joke aside, running with nums=2 for 2 pages
time run test_speed.py
CPU times: user 12.39 s, sys: 0.10 s, total: 12.49 s
Wall time: 12.84 s
when nums=38, just like my original script, then I get similar timing to my
original run
time run test.py
CPU times: user 227.39 s, sys: 1.74 s, total: 229.13 s
Wall time: 234.87 s
In addition to these longer plot creation times, 38 pages plot creation
consumes about 3 GB memory. I am wondering if there are tricks to improve
plot creation times as well as more efficiently using the memory.
Attempting to create two such distributions blocks my machine eating 6 GB
of ram space.
Using Python 2.7, NumPy 2.0.0.dev-7e202a2, IPython
0.13.beta1, matplotlib 1.1.1rc on Fedora 16 (x86_64)
Thanks.
-- 
Gökhan

Hi Ben,
thanks for the tip!
I nevertheless hit another snag:
In [12]: [(k,p.rcParams[k]) for k in p.rcParams.keys() if 'keymap' in k]
Out[12]: 
[('keymap.all_axes', ['a']),
 ('keymap.back', ['left', 'c', 'backspace']),
 ('keymap.forward', ['right', 'v']),
 ('keymap.fullscreen', ['f']),
 ('keymap.grid', ['g']),
 ('keymap.home', ['h', 'r', 'home']),
 ('keymap.pan', ['p']),
 ('keymap.save', ['s']),
 ('keymap.xscale', ['k', 'L']),
 ('keymap.yscale', ['l']),
 ('keymap.zoom', ['o'])]
Meaning that up and down ar not in the mapping... Any clue?
Thanks again
Cheers
JF
-
Helmholtz Zentrum Geesthacht
Institut für Werkstoffforschung
Abteilung WPN, Instrument REFSANS
Lichtenbergstr. 1
85747 Garching FRM II
Tel.: +49 (0)89 289 10762
Internet: http://www.frm2.tum.de
---...@gm... schrieb: -----
An: Jea...@hz...
Von: Benjamin Root 
Gesendet von: ben...@gm...
Datum: 07/03/2012 06:29PM
Kopie: mat...@li...
Betreff: Re: [Matplotlib-users] conflicts with navigation bar events
On Mon, Jul 2, 2012 at 4:33 AM, <Jea...@hz...> wrote:
 Hi all!
 
 How can I use the keyboard events up/down/right/left without starting an interaction with the navigation toolbar?
 I connected to the keypress events and everything looks ok until I press the down key: my connected method gets called once and the navigation toolbar then gets the focus. From that point on it catches all of my arrow presses.
 I noticed that using shifted keys could be a workaround but I really do not like it...
 
 
 Thanks in advance for help!
 
 cheers JF
 
 
Yeah, this is annoying. A quick way out is to hit the ESC button. Took me forever to figure that out.
The more permanent fix is to remove the 'up' and 'down' events from the default key maps. I have some code that needed their own keymap and I checked for collisions with the default keymap:
 
https://github.com/WeatherGod/BRadar/blob/master/lib/BRadar/plotutils.py#L408
Might be overkill for what you need, but you should get the idea.
 
Cheers!
Ben Root
 Helmholtz-Zentrum Geesthacht 
Zentrum für Material- und Küstenforschung GmbH 
Max-Planck-Straße 1 I 21502 Geesthacht I Deutschland/Germany 
Geschäftsführer/Board of Management: Prof. Dr. Wolfgang Kaysser, Dipl.-Ing. Michael Ganß 
Vorsitzender des Aufsichtsrates/Chairman of the Supervisory Board: MinDirig Wilfried Kraus 
Amtsgericht Lübeck HRB 285 GE (Register Court) 
Internet: http://www.hzg.de