matplotlib-users

[Matplotlib-users] spawning plots as separate processes

[signal s. <see...@gm...>]

Hi All,

I am very new to matplotlib and still trying to find my way through docs and
api, so please excuse me if there is a simple way to do this.

So the situation is this  - I would like to write a script that spawns
multiple
plots and exits, but the plots window do not die until they are
explicitly closed.
Is there a simple way to do this. All the examples that I have looked
at so far have scripts that only exit once the call to show() returns.
Is there some mechanism that
matplotlib provides to make the show() return? I am of course using the
pylab interface now, but I can start using the core matplotlib api if need.
Thanks in advance for your time.

Regards,
-ss

Re: [Matplotlib-users] spawning plots as separate processes

[Bill B. <wb...@gm...>]

I'm not sure what you're after exactly, but your design needs may be
solved by calling pylab.ion(True).
If not the ezplot library that I wrote may do it for you.
   http://www.python.org/pypi/ezplot/0.1.0a3

--bb

On 6/13/07, signal seeker <see...@gm...> wrote:
>
> Hi All,
>
> I am very new to matplotlib and still trying to find my way through docs and
> api, so please excuse me if there is a simple way to do this.
>
> So the situation is this  - I would like to write a script that spawns
> multiple plots and exits, but the plots window do not die
> until they are explicitly closed.
> Is there a simple way to do this. All the examples that
> I have looked at so far have scripts that
> only exit once the call to show() returns.
> Is there some mechanism that
> matplotlib provides to make the show() return? I am of course using the
> pylab interface now, but I can start using the core matplotlib api if need.
> Thanks in advance for your time.
>
> Regards,
> -ss
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by DB2 Express
> Download DB2 Express C - the FREE version of DB2 express and take
> control of your XML. No limits. Just data. Click to get it now.
> http://sourceforge.net/powerbar/db2/
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

Re: [Matplotlib-users] spawning plots as separate processes

[signal s. <see...@gm...>]

Bill,

Thanks for your reply. pylab(ion) is not what I meant. Consider this simply
script -
.....
# simple.py
from pylab import *
plot([1,2,3])
show()
....

Now, if I do python simple.py on a cmd prompt, this will open up a plot
window, but the script won't return until the plot window is closed.
I would like simple.py process to end but the plot window to be still up. I
have users who would like to type one command after
another and not have to close any of the plot windows created.

I looked at ezplot, but it looks like a rather heavy weight soln, but maybe
I need to do something similar. Is there any other way around this?

Thanks,
ss


On 6/12/07, Bill Baxter <wb...@gm...> wrote:
>
> I'm not sure what you're after exactly, but your design needs may be
> solved by calling pylab.ion(True).
> If not the ezplot library that I wrote may do it for you.
>    http://www.python.org/pypi/ezplot/0.1.0a3
>
> --bb
>
> On 6/13/07, signal seeker <see...@gm...> wrote:
> >
> > Hi All,
> >
> > I am very new to matplotlib and still trying to find my way through docs
> and
> > api, so please excuse me if there is a simple way to do this.
> >
> > So the situation is this  - I would like to write a script that spawns
> > multiple plots and exits, but the plots window do not die
> > until they are explicitly closed.
> > Is there a simple way to do this. All the examples that
> > I have looked at so far have scripts that
> > only exit once the call to show() returns.
> > Is there some mechanism that
> > matplotlib provides to make the show() return? I am of course using the
> > pylab interface now, but I can start using the core matplotlib api if
> need.
> > Thanks in advance for your time.
> >
> > Regards,
> > -ss
> >
> >
> -------------------------------------------------------------------------
> > This SF.net email is sponsored by DB2 Express
> > Download DB2 Express C - the FREE version of DB2 express and take
> > control of your XML. No limits. Just data. Click to get it now.
> > http://sourceforge.net/powerbar/db2/
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
>

Re: [Matplotlib-users] spawning plots as separate processes

[signal s. <see...@gm...>]

Bill,

The problem is I am writing a bunch of diagonistic tools for users who do
not know anything about unix.
they just want to type a bunch of commands on a shell and see the plots and
they hardly know anything fancy like sending processes to the background :)

I guess, I am going to have to use threads or sub processes to spawn new
plots.

Thanks,
ss

On 6/13/07, Bill Baxter <wb...@gm...> wrote:
>
> On 6/13/07, signal seeker <see...@gm...> wrote:
> >
> > Bill,
> >
> > Thanks for your reply. pylab(ion) is not what I meant. Consider this
> simply
> > script -
> > .....
> > # simple.py
> > from pylab import *
> > plot([1,2,3])
> > show()
> > ....
> >
> > Now, if I do python simple.py on a cmd prompt, this will open up a plot
> > window, but the script won't return until the plot window is closed.
> > I would like simple.py process to end but the plot window to be still
> up. I
> > have users who would like to type one command after another and not have
> to
> > close any of the plot windows created.
>
> I see.  In that case, I think you just want
> $ simple.py &
> on unix and
> c:\> start python simple.py
> on Windows.
>
> In both cases you can put those commands into a script so the user
> just types 'run_simple'.
>
> --bb
>

Re: [Matplotlib-users] spawning plots as separate processes

[Andrew S. <str...@as...>]

signal seeker wrote:
> Bill,
> 
> The problem is I am writing a bunch of diagonistic tools for users who
> do not know anything about unix.
> they just want to type a bunch of commands on a shell and see the plots
> and they hardly know anything fancy like sending processes to the
> background :)
> 
> I guess, I am going to have to use threads or sub processes to spawn new
> plots.

That's exactly what Bill's ezplot is supposed to do. I am sure that he
will appreciate any helping making it easier to just work without the
user having to know or do anything. (I know I will.)