matplotlib-users Mailing List for matplotlib

Thank you very much Steve! This helped a lot, it worked in the ipython as well, there is no difference, only that the ipython is interactive and has more supplementary features. :)

Thanks, 
Tomislav
----- Original Message -----
From: Stephen George
Sent: 04/21/10 03:33 AM
To: mat...@li...
Subject: Re: [Matplotlib-users] plotting in a loop

 Hi,

 Sorry haven't used ipython, so not sure if there is another/better ipython way.

 Attached is how I solved it in normal python.
 I added a "next line" button to the graph, and set the ydata for the line each time the button is pushed.

 There is a couple of set_ylim lines commented out, depending on the nature of your data, it might be appropriate to uncomment one of those, however the set_aspect line may might mean the graph is very tall and skinny with the supplied data.

 Hope that gives you some ideas for your own code.

 Steve


 On 21/04/2010 3:35 AM, tom...@gm... wrote: Hello everyone, 

 if I read a column file like this (simplified to integers):

 0 1 2 3
 1 2 3 4
 2 3 4 5
 3 4 5 6

with: "data = np.loadtxt("fileName")", why can't I use a for loop inside ipython (started with "-pylab" option) to plot each of the Line2D objects and then draw them on the plot? I am using matplotlib to debug a computational geometry code and I would like these lines to plot paused by the user input so that I can identify when (where) exactly the wrong calculations happen:

import numpy as np
import matplotlib.pyplot as plt
fig1 = plt.figure()
ax1 = fig1.add_subplot(111)
ax1.set_aspect("equal")
for line in data:
 raw_input("press enter to plot the line")
 ax1.plot([line[0],line[2]],[line[1],line[3]],'b')
 plt.draw()


This way I could see with pressing e.g. the return key when my calculations go wrong.... any advice?


 ------------------------------------------------------------------------------ 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 http://p.sf.net/sfu/intel-sw-dev  _______________________________________________ Matplotlib-users mailing list Mat...@li...://lists.sourceforge.net/lists/listinfo/matplotlib-users https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Wed, Apr 21, 2010 at 12:06 PM, Gökhan Sever <gok...@gm...>wrote:

>
>
> On Wed, Apr 21, 2010 at 4:39 AM, Matthias Michler <Mat...@gm...
> > wrote:
>
>> I think it works like expected, i.e. it toggles the state of showing grid
>> lines for minor and major ticks.
>> The problem it the case were people set only major tick grid lines
>> ax.grid(True, which='major')
>> and than press the key 'g', because than they change between having major
>> and
>> minor tick grid lines and this is somehow a strange behavior, isn't it?
>> Therefore I myself am not convinced of that solution.
>> [...]
>>
>
> Interesting that setting and using "g" doesn't toggle both minor and major
> grids at the same time. It behaves erratically.
> event.inaxes.grid(which='minormajor')
>
>  I'm sorry, I don't get your point. If I ran your script I get a window
>> without
>> gridlines as expected. The result is independent of the call of
>> ax.grid(False, which='majorminor').
>> By the way are you using matplotlib-svn?
>>
>
> Yes I test this again and it doesn't work. That setting only disables major
> grids. Grids are cleared in my second explicit call. This is rev 8226 using
> WXAgg backend.
>
>
>>
>> Kind regards,
>> Matthias
>>
>>
>> ------------------------------------------------------------------------------
>> _______________________________________________
>> Matplotlib-users mailing list
>> Mat...@li...
>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>
>
>
>
> --
> Gökhan
>

I removed mpl directory and re-checked out and re-installed it using rev
8260.

Applied your patch with patch -p0 -i grid_for_major_minor_ticks.patch

That simple example still doesn't work here (cannot get rid of major - minor
grids at the same in a double log scaled plot). Could someone confirm this
behaviour?

Thanks.

-- 
Gökhan

On Wed, Apr 21, 2010 at 4:39 AM, Matthias Michler
<Mat...@gm...>wrote:

> I think it works like expected, i.e. it toggles the state of showing grid
> lines for minor and major ticks.
> The problem it the case were people set only major tick grid lines
> ax.grid(True, which='major')
> and than press the key 'g', because than they change between having major
> and
> minor tick grid lines and this is somehow a strange behavior, isn't it?
> Therefore I myself am not convinced of that solution.
> [...]
>

Interesting that setting and using "g" doesn't toggle both minor and major
grids at the same time. It behaves erratically.
event.inaxes.grid(which='minormajor')

 I'm sorry, I don't get your point. If I ran your script I get a window
> without
> gridlines as expected. The result is independent of the call of
> ax.grid(False, which='majorminor').
> By the way are you using matplotlib-svn?
>

Yes I test this again and it doesn't work. That setting only disables major
grids. Grids are cleared in my second explicit call. This is rev 8226 using
WXAgg backend.


>
> Kind regards,
> Matthias
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>



-- 
Gökhan

On Tue, Apr 20, 2010 at 11:11 AM, Gökhan Sever <gok...@gm...>wrote:

>
>
> On Tue, Apr 20, 2010 at 2:42 AM, Matthias Michler <Mat...@gm...
> > wrote:
>
>> Hi Gökhan,
>>
>> thanks for testing this small patch. Maybe one of the developers could
>> submit
>> it or should I place it on the patch-tracker?
>>
>>
> Usually after some pinging someone picks up the code and commits in to the
> svn.
>
>
>> About the toggling of all grid-lines using
>> event.inaxes.grid(which='majorminor')
>> I not sure this is intended, because this means that you will allways
>> toggling
>> major and minor tick - grid lines using key 'g' instead of only toggling
>> major tick grid lines. Maybe a developer or other users could comment on
>> the
>> preferred behavior.
>>
>
> Just create a simple plot and log-log x,y-axes and try hitting "g". Both
> minor and major gridlines must be visible to get a clear view. In some cases
> grids clutter the figure instead of helping.
>
> In my previous post, the main point was change in
> event.inaxes.grid(which='majorminor') doesn't really work as expected. Could
> you at least check that behavior?
>
>
>
>>
>> Kind regards,
>> Matthias
>>
>>
>> ------------------------------------------------------------------------------
>> 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
>>
>
>
>
> --
> Gökhan
>

Hi Matthias,

I spotted another annoyance:

Save the following lines in a file called test.py and run python test.py

import matplotlib.pyplot as plt

plt.plot(range(100))
plt.xscale('log')
plt.yscale('log')
ax = plt.gca()
ax.grid(False, which='majorminor')
plt.show()

This doesn't work properly in the first call. If you call it from within
Ipython -pylab using run test.py again no difference. Only when you call
ax.grid(False, which='majorminor') grids disappear.


-- 
Gökhan

Well, the example with the comment "WARNING : illustrating how NOT to use show":

for i in range(10):
    # make figure i
    show()

works perfectly fine with the Mac OS X backend, and I doubt that there is some fundamental reason why this can work with the Mac OS X backend but not with other backends.

--Michiel


--- On Tue, 4/20/10, Alan G Isaac <ala...@gm...> wrote:

> From: Alan G Isaac <ala...@gm...>
> Subject: Re: [Matplotlib-users] show() at the end of each function of an ensemble of scripts
> To: mat...@li...
> Date: Tuesday, April 20, 2010, 9:51 PM
> http://matplotlib.sourceforge.net/faq/howto_faq.html#use-show
> 
> hth,
> Alan Isaac
> 
> 
> ------------------------------------------------------------------------------
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> 


      

http://matplotlib.sourceforge.net/faq/howto_faq.html#use-show

hth,
Alan Isaac

Hi,

Sorry haven't used ipython, so not sure if there is another/better 
ipython way.

Attached is how I solved it in normal python.
I added a "next line" button to the graph, and set the ydata for the 
line each time the button is pushed.

There is a couple of set_ylim lines commented out, depending on the 
nature of your data, it might be appropriate to uncomment one of those, 
however the set_aspect line may might mean the graph is very tall and 
skinny with the supplied data.

Hope that gives you some ideas for your own code.

Steve


On 21/04/2010 3:35 AM, tom...@gm... wrote:
> Hello everyone,
>
> if I read a column file like this (simplified to integers):
>
> 0 1 2 3
> 1 2 3 4
> 2 3 4 5
> 3 4 5 6
>
> with: "data = np.loadtxt("fileName")", why can't I use a for loop 
> inside ipython (started with "-pylab" option) to plot each of the 
> Line2D objects and then draw them on the plot? I am using matplotlib 
> to debug a computational geometry code and I would like these lines to 
> plot paused by the user input so that I can identify when (where) 
> exactly the wrong calculations happen:
>
>
> import numpy as np
>
> import matplotlib.pyplot as plt
>
> fig1 = plt.figure()
>
> ax1 = fig1.add_subplot(111)
>
> ax1.set_aspect("equal")
>
> for line in data:
>
>     raw_input("press enter to plot the line")
>
>     ax1.plot([line[0],line[2]],[line[1],line[3]],'b')
>
>     plt.draw()
>
>
>
> This way I could see with pressing e.g. the return key when my 
> calculations go wrong.... any advice?
>
>
>
>
> ------------------------------------------------------------------------------
> 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 Tue, 4/20/10, Ryan May <rm...@gm...> wrote:
> Antony Lee <ant...@en...> wrote:
> > That would be a solution, indeed.  However, is there
> > really no way of coming back to a pre-plt.show() state
> > once all windows are closed?  What kind of
> > irreversible things does plt.show() do?
> 
> It starts the GUI toolkit event loop, which starts to make
> things messy if you try to call show() again. It often works,
> but calling show() more than once is most-definitely not
> supported.
>
But what exactly does show() do that prevents it from being called again? At least for the Mac OS X and the gtkcairo backends, calling show() multiple times doesn't seem to cause any problems. Can you give an example where calling show() multiple times breaks things?  If there is such a case, it may reveal a lurking bug in show() itself.

--Michiel.