<div dir="ltr">Dear Zhisong,<br><br><div>Jed asked you to use the makefile to actually launch the test, as so:</div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13.2px; border-collapse: collapse; "><br>
</span></div><div><span class="Apple-style-span" style="font-family: arial, sans-serif; font-size: 13.2px; border-collapse: collapse; ">cd src/snes/examples/tutorials && make -n runex5</span></div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br>
</span></font><div class="gmail_quote">You'll notice in your reply that you only built ex5, and didn't use the make command to launch the job. This is important to ensure that you can execute your code in parallel using the MPI that PETSc detected or installed.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">"All the machines have mpi package installed before I got to touch PETSc. That might be the potential problem. But "Portability" is one of the main features of PETSc. Doesn't that mean the user can run the final executable anywhere as long as c and mpi libraries are available?"<br>
</div><div class="gmail_quote"><br></div><div class="gmail_quote">Traditionally, portability means that the code will compile and link anywhere, not that you can drag and drop executables as you wish. You are responsible for re-building PETSc applications or at least ensuring binary and MPI compatibility.</div>
<div class="gmail_quote"><br></div><div class="gmail_quote">Hope this helps...</div><div class="gmail_quote"><br></div><div class="gmail_quote">Warm Regards,</div><div class="gmail_quote">Aron Ahmadia</div><div class="gmail_quote">
<br></div><div class="gmail_quote">On Mon, Apr 19, 2010 at 11:05 PM, Li, Zhisong (lizs) <span dir="ltr"><<a href="mailto:lizs@mail.uc.edu">lizs@mail.uc.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Mat and Jed,<br>
<br>
Thank you for your reply.<br>
<br>
As far as I remembered, the make test was successful except the Fortran complier, but I only use C for my work.<br>
<br>
I tried " $ cd src/snes/examples/tutorials && make -n ex5" and it shows: /home/lizs/petsc/linux-gnu-c-debug/bin/mpicc ex5.c -o ex5<br>
<br>
All the machines have mpi package installed before I got to touch PETSc. That might be the potential problem. But "Portability" is one of the main features of PETSc. Doesn't that mean the user can run the final executable anywhere as long as c and mpi libraries are available?<br>
<br>
Thanks,<br>
<br>
Zhisong Li<br>
<br>
<br>
________________________________________<br>
Subject: petsc-users Digest, Vol 16, Issue 23<br>
<br>
<br>
The mpiexec in your path is not the one you configured with. What<br>
MPI is begin used?<br>
<br>
Matt<br>
<br>
<br>
> > I've tried to run some PETSc examples and my own simple PETSc codes on my<br>
> > office's cluster as well as on Ohio Supercomputer Center's machine. At first<br>
> > I found no speedup for parallel processing and later I noticed by checking<br>
> > the rank that actually each node is doing the same sequential processing.<br>
> > I'm sure the codes are parallel codes (such as ex19.c in SNES and ex7.c in<br>
> > TS tutorial codes). Is there anything I am missing in the installation or<br>
> > the run command such as"mpiexec -n 3 ex7"? How can I realize a parallel<br>
> > running?<br>
> ><br>
><br>
> The mpiexec in your path is not the one you configured with. What<br>
> MPI is begin used?<br>
<br>
Does make test run successfully? If so, then<br>
<br>
$ cd src/snes/examples/tutorials && make -n runex5<br>
<br>
will tell you which mpiexec PETSc is using.<br>
<br>
Jed<br>
<br>
<br>
</blockquote></div><br></div></div>