matplotlib-users Mailing List for matplotlib

Hi all,
I like this patch and it works fine. So if nobody is against including
this, I'll commit it in a few days.
I'll move the example from the class comment to an example script.
Cheers,
Reinier
On Wed, Dec 2, 2009 at 1:40 PM, John Hunter <jd...@gm...> wrote:
> On Wed, Dec 2, 2009 at 4:02 AM, Matthias Michler
> <Mat...@gm...> wrote:
>> Hi Jason, Hi list,
>>
>> First of all let me say I like the EngFormatter of Jason.
>> Are there plans to incorparate it into matplotlib?
>> I cannot find any indication for this in current svn, but I would like to see
>> the EngFormatter in matplotlib. Therefore I tried to include Jasons proposal
>> into the ticker.py as a new class EngFormatter including the
>> method 'self.format_eng'.
>
>
> I am interested in this -i I just missed Jason's original email last
> week so thanks for bringing it back to our attention. Please post
> this as a patch on the tracker
>
> http://sourceforge.net/tracker2/?group_id=80706
>
> since I don't have time to review it right now and I don't want it to
> fall through the cracks.
>
> JDH
>
> ------------------------------------------------------------------------------
> Join us December 9, 2009 for the Red Hat Virtual Experience,
> a free event focused on virtualization and cloud computing.
> Attend in-depth sessions from your desk. Your couch. Anywhere.
> http://p.sf.net/sfu/redhat-sfdev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
-- 
Reinier Heeres
Tel: +31 6 10852639

On Sun, Dec 27, 2009 at 2:37 PM, Eric Firing <ef...@ha...> wrote:
> What are the circumstances under which one would call set_data() and not
> want or need an update?
If you ask me, I'm +1 to update the plot always. But, apparently, the
original author of this code wanted to do some checks to avoid
unnecessary recaching. So, I'm not sure which is better.
On the other hand, I think there is a general issue of whether the
current behavior of the cache is broken or not. In the code below,
the function test_cache() gives different results depending on the
input is a list or a numpy array. And, to me, this is something that
needs to be fixed despite it may add a little bit of complication into
the code.
I did not want to step into this issue as I didn't write the code, but
there has been no responses from other developers while this issue (I
mean, the original issue of set_data not updating the plot) has been
raised a few times in the mailing list.
So, if Eric and others have any other thoughts, please speak.
Regards,
-JJ
from matplotlib.pyplot import subplot, show
import numpy as np
import matplotlib.lines as mlines
def test_cache(ax, yy):
 l = mlines.Line2D([0, 1], yy)
 yy[1]=0.7
 ax.add_line(l)
ax = subplot(111)
a1 = [0, 1]
test_cache(ax, a1)
a2 = np.array([0, 1], dtype="d")
test_cache(ax, a2)
show()

Jae-Joon Lee wrote:
> I just filed a bug related with this.
> 
> https://sourceforge.net/tracker/?func=detail&aid=2917758&group_id=80706&atid=560720
> 
> 
> I think the possible solution could be
> 
> 1) we keep the copied version of the input data as a cache, and
> provide a api to access the cache.
> 2) Or forsce set_[x|y]data to always update.
> 
> My current inclination is the option 1.
> If there is any other opinion, I'll go ahead and make a change in a few days.
> 
> -JJ
Jae-Joon,
I wonder whether things are getting more and more complicated here, for 
no real benefit. The logic even of some of the present code in set_data 
and recache is not immediately clear upon casual inspection. What are 
the circumstances under which one would call set_data() and not want or 
need an update?
Eric
> 
> 
> On Tue, Dec 15, 2009 at 9:12 AM, Antonino Ingargiola <tri...@gm...> wrote:
>> Hi to all,
>>
>> I'm doing a simple animation like this:
>>
>> --
>> ion()
>> x = arange(0,2,0.01)
>> y = zeros_like(x)
>> y[45:55]=1
>> l, = plot(x,y)
>>
>> D = 0.1
>> h = x[1]-x[0]
>> dt = 0.0001;
>>
>> def nabla(v,h):
>> na = zeros_like(v)
>> na[1:-1] = (v[2:]-2*v[1:-1]+v[:-2])
>> na[0],na[-1] = 0,0
>> return na/(h**2)
>>
>> for i in range(1000):
>> y = y + D*nabla(y,h)*dt
>> if i%10 == 0:
>> l.set_ydata(y)
>> draw()
>> --
>>
>> however, changing the line
>>
>> y = y + D*nabla(y,h)*dt with
>>
>> in
>>
>> y += D*nabla(y,h)*dt
>>
>> the plot is not updated anymore. I have to replace l.set_ydata(y) with
>> y.recache() to make the the animation work again.
>>
>> I think this is a bug since the line should be updated even using the
>> += operator.
>>
>> Regards,
>> Antonio
>>
>> ------------------------------------------------------------------------------
>> Return on Information:
>> Google Enterprise Search pays you back
>> Get the facts.
>> http://p.sf.net/sfu/google-dev2dev
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
> 
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev 
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Thu, Dec 24, 2009 at 3:53 PM, per freem <per...@gm...> wrote:
> i want it to eliminate the second
> subplot of the first row and instead make the first subplot on the
> first row take up two plots worth of space,
Matpltlib's subplot does not support it as of now.
There a few work around you may try, but it will at least take a few
tens of lines of code. Attached is a way to do this by patching the
object method, which I personally do not prefer but may be one of the
easiest for normal users.
Also, there is a patch I once worked on, but haven't pushed into the
svn yet (i'm not sure if I ever will). So give it a try if you want.
http://article.gmane.org/gmane.comp.python.matplotlib.general/19097
Regards,
-JJ
import matplotlib.transforms as mtransforms
def expand_subplot(ax, num2):
 update_params_orig = ax.update_params
 ax._num2 = num2 - 1
 def _f(self=ax):
 num_orig = self._num
 self._num = self._num2
 update_params_orig()
 right, top = self.figbox.extents[2:]
 self._num = num_orig
 update_params_orig()
 left, bottom = self.figbox.extents[:2]
 self.figbox = mtransforms.Bbox.from_extents(left, bottom,
 right, top)
 ax.update_params = _f
 ax.update_params()
 ax.set_position(ax.figbox)
ax = subplot(231)
expand_subplot(ax, 2)

Hi, I want to capture mouse and keyboard events on a plot while updating it
in regular intervals.
I succeeded doing both tasks independently however not in combination.
For the updating I use a subthread to analyze the data while the main thread
redraws the plot in a loop. However while redrawing it doesn't capture any
other events. When I put a simple sleep in the redrawing thread it shows the
same behavior.
Is there a way to fix this?