RE: [Pympi-users] Re: Never get to the python prompt >>> configure with "--with-isatty --with-prompt-nl"

[Julian C. <rjc...@cs...>]

Hi Mike

I did everything you said and it works just like you said it would!
1. I checked out the latest cvs (version 2.1b4 as of 26Nov04) i.e.
cvs -d:pserver:ano...@cv...:/cvsroot/pympi checkout pyMPI
2. ran ./boot
3. ran ./configure  --with-isatty --with-prompt-nl
4. ran make
5. ran make install
6. ran /opt/mpich/bin/mpirun -np 2 -machinefile ../machines.LINUX
/usr/local/bin/pyMPI

When you run interactive pyMPI, the extra carriage return after the prompt
will appear before the last node replies i.e.

>>>
print mpi.rank
0
>>>
1

As long as you know what's going on, it works fine..

tks for your help,

-----Original Message-----
From: pym...@li...
[mailto:pym...@li...]On Behalf Of Mike Steder
Sent: Wednesday, November 24, 2004 1:34 AM
To: pym...@li...
Subject: [Pympi-users] Re: Never get to the python prompt >>>


Hi Julian,

Sorry for the late response.

> I"m currently having a problem starting up pyMPI on a simple 2 node test
> setup
>
> 1. mpirun works correctly across 2+ plus nodes
> 2. pyMPI runs correctly if started up in single cpu mode, with -np set to
1.
> This works on both nodes.
> 3. pyMPI never gets to the >>> prompt, if I run it with -np set to 2.
> 4. I added printf statements to the pyMPI initialisation and it appears
that
> both nodes complete the MPI portion (because I get duplicate printfs). The
> first (local) node then enters Py_Main and displays the credits,  but the
> second node enters Py_Main and never displays anything (assuming it
should).
> 5. Result is that the process waits indefinitely for something to occur
and
> never displays the >>> prompt.
> 6. I am able to ssh to th> e second node and run pyMPI with -np set to 1.

I was having identitcal problems.  After contacting Pat he pointed out
to me a configure option worth trying.  Apparently the problem is
related to I/O buffers not being properly flushed for some reason.  We
can enforce/improve this behavior by adding some options to our
configure.

However, I would first recommend that you go ahead and check out the
latest version of pyMPI from CVS.  If you're unfamiliar with how to do
that check out this page:

http://sourceforge.net/cvs/?group_id=5335

Specifically you want to execute the following:
$ cvs -d:pserver:ano...@cv...:/cvsroot/pympi login
$ cvs -d:pserver:ano...@cv...:/cvsroot/pympi checkout pyMPI

Assuming you execute these commands from /home/cook/ it will create a
directory /home/cook/pyMPI with the most recent sources.

Now that you've got fresh sources you need to boostrap the CVS
distribution by doing( from the pyMPI directory)

$ ./boot

And then configure however you would normally but add either
"--with-isatty" or "--with-isatty --with-prompt-nl"

For instance:

$ CC=mpicc ./configure --prefix=/usr --with-isatty --with-prompt-nl
$ make
$ ./pyMPI

There is a minor formatting glitch with this version which should be
resolved before a stable tarball is released in which the
prompt begins on the line below the >>> , like
>>>
[]<-- cursor

Hopefully these changes will be rolled into the latest version 2.0b4
in the next few days.  I would suggest going with CVS rather then
waiting however.

Please let us know if you still have problems with the newer version
with the --with-isatty flag on.    Heck, let us know if it works for
you now as well.

Goodluck, keep us posted,

~Mike


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
Pympi-users mailing list
Pym...@li...
https://lists.sourceforge.net/lists/listinfo/pympi-users