matplotlib-users Mailing List for matplotlib

On 04/26/2011 09:36 AM, bu...@gm... wrote:
> I believe this feature, which has been requested a number of times, but
> is still missing from matplotlib is genuinely useful for interactive
> plotting. Moreover, I've heard matlab has it...
>
> Here's a potential solution to cover my simple plotting needs. The goal
> is not to support all the weird and wonderful matplotlib features, if
> you need those you probably work only from script anyway. My approach is
> based on figureoptions.py in matplotlib.backends.qt4_editor (or the more
> recent version in spyder):
>
> 1) Save figure file:
> . get xy data for each plot object
> . get object styles (color of plots, linestyle, etc.)
> . save to auto-generated python script
>
> Later...
>
> 2) Open figure file:
> The script will open a new figure, recreate all objects and then apply
> styles to each object.
> >> You have full control over the figure and its contents again for editing
>
> Using this approach backwards compatibility should not be a issue (as
> demonstrated by figureoptions). On the other hand not all matplotlib
> objects/options will be supported.
>
> Any comments or suggestions ?
Implementing anything like this will immediately lead to a stream of 
complaints that it doesn't support "all the weird and wonderful 
matplotlib features".
The vector backends are actually doing something like this, but saving 
in their respective graphics languages instead of in python. Presumably 
some sort of "matplotlib_script" backend could be written, using the pdf 
or svg backend as a template.
Better practice is to use something like the ipython logging facility to 
save one's interactive commands, and then manually to edit that down to 
a script that creates the desired figure. That way one retains full 
control, reproducibility, and documentation of what went into a figure.
Eric
>
>

I believe this feature, which has been requested a number of times, but is 
still missing from matplotlib is genuinely useful for interactive plotting. 
Moreover, I've heard matlab has it...
Here's a potential solution to cover my simple plotting needs. The goal is 
not to support all the weird and wonderful matplotlib features, if you need 
those you probably work only from script anyway. My approach is based on 
figureoptions.py in matplotlib.backends.qt4_editor (or the more recent 
version in spyder):
1) Save figure file:
. get xy data for each plot object
. get object styles (color of plots, linestyle, etc.)
. save to auto-generated python script
Later...
2) Open figure file:
The script will open a new figure, recreate all objects and then apply 
styles to each object.
>> You have full control over the figure and its contents again for editing
Using this approach backwards compatibility should not be a issue (as 
demonstrated by figureoptions). On the other hand not all matplotlib 
objects/options will be supported.
Any comments or suggestions ?

Indeed setting aspect = 'auto' in matshow solved my problem.
Thanks a lot !
Goyo wrote:
> 
> 2011年4月23日 _olivier_ <ol...@gm...>:
>> [...]
> 
>> I have got a matrix 6x500 (so one size is much biggger than the other
>> one)
>> and I try to expand the shorter axe so that the labels on it are well
>> displayed (not overlapped.
> 
> Use the aspect kwarg in matshow.
> 
> Goyo
> 
> ------------------------------------------------------------------------------
> Fulfilling the Lean Software Promise
> Lean software platforms are now widely adopted and the benefits have been 
> demonstrated beyond question. Learn why your peers are replacing JEE 
> containers with lightweight application servers - and what you can gain 
> from the move. http://p.sf.net/sfu/vmware-sfemails
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 
> 
-- 
View this message in context: http://old.nabble.com/Try-to-have-none-overlapping-labels-in-one-axe-using-matshow-tp31456159p31478955.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Thu, Apr 21, 2011 at 2:07 PM, Michael Droettboom <md...@st...> wrote:
> Ok. I think I've found a leak in the way the spines' paths were being
> updated.
>
> https://github.com/matplotlib/matplotlib/pull/89
>
> Can you apply the patch there and let me know how it improves things for
> you?
>
> Cheers,
> Mike
>
I applied the patch and (at least for a short run), it seems the leak
for wxagg has been fixed. The new results for wxagg is pretty much the
same as the old results for tkagg (which does not have the leak): a
plot of memory usage is very irregular (up and down), but a line fit
has a slope of about 0.009KB. I suspect if I ran this for a few hours
the slope would approach 0 KB.
Thanks so much!! This is a life saver for my project!
Caleb