On Mon, Jan 17, 2011 at 6:36 PM, Gaurish Telang <gaurish108 at gmail.com>wrote:
> Thank you that seems to have worked! Just to confirm, I have posted the > output at the end of this message. I hope this is the way the generic output > should look like. > > I have still have a few questions though. > > (1) > > So all I need to do, is to specify the location of the correct executable > mpiexec which is $PETSC_DIR/$PETSC_ARCH/bin/mpiexec > while running the program, right? > Yes > The contents of my $PETSC_DIR/$PETSC_ARCH/bin are > > gaurish108 at > gaurish108-laptop:~/Desktop/ResearchMeetings/SUPERPETS/petsc-3.1-p5/linux-gnu-c-debug/bin$ > ls > mpicc mpich2version mpiexec mpif77 mpif90 parkill > > > (2) > Do I need to make any changes in the makefiles of the PETSc programs that I > have written? And hence recompile my codes by using the "new" mpiexec > mpiexec is only for execution, not compiling or linking. > I mean, since $PETSC_DIR/$PETSC_ARCH/bin/ also contains mpicc (as seen > above), I want to be sure that the correct mpicc is being used during > execution. > > (3) Should I run the mpd daemon before using mpiexec??? On the MPICH2 that > I had installed prior to my PETSc it required me type "mpd &" > before program execution. > > But it seems for my PETSc mpiexec I don;t need mpd. But should I type it in > ?? I mean I am not sure if this affects program performance > The new version of MPICH uses hydra, not mpd, to manage the startup. Matt > Sincere thanks, > > Gaurish > -- What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead. -- Norbert Wiener -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20110117/a1995b89/attachment.htm>
