One additional point: If using 'parallel processing' - then you shouldn't be trying to circumvent this part of MPI standard [mpiexec -n].
And if you are primarily doing sequential stuff - you can build PETSc with '--with-mpi=0' [so MPI is not used. However when working with multiple MPI software packages there could be issues here - so its recommended to use a proper MPI impl like MPICH2 across all these software packages] Satish On Tue, 6 Jul 2010, Aron Ahmadia wrote: > Dear Nemanja, > > Welcome to PETSc! It is important to note that PETSc's parallel > functionality is implemented on top of MPI. Your MPI vendor (Microsoft, > MPICH, OpenMPI, etc...) is responsible for providing you the interface for > launching your jobs in parallel, PETSc does not care how your MPI jobs are > launched. Although mpiexec is the standard on UNIXy-style operating systems > and distributions, it is not uncommon to see graphical interfaces for > launching these programs in the OS X and Microsoft HPC worlds. > > I suggest that you raise this question with the implementors/providers of > your MPI libraries (PETSc downloads and installs mpich: > http://www.mcs.anl.gov/research/projects/mpich2/ for you in many standard > configurations). > > Good luck, > Aron > > On Tue, Jul 6, 2010 at 7:43 PM, ?????? ???? (Nemanja Ilic) < > nemanja.ilic.81 at gmail.com> wrote: > > > Hello, > > > > I am currently working on a project involving Petsc library. My core > > library that uses Petsc has several functionalities that are invoked via > > function calls. Is there a way to call these functions from another library > > and to have parallel processing, without using "mpiexec -np ..." command > > line format? > > > > Thank you in advance, > > Best regards, > > Nemanja Ilic > > >
