Thanks. I think I get it. I’ll try it. > On Jun 20, 2016, at 2:14 PM, Roy Stogner <royst...@ices.utexas.edu> wrote: > > > On Mon, 20 Jun 2016, John Peterson wrote: > >> On Mon, Jun 20, 2016 at 12:55 PM, 张江 <zhangjiang.d...@gmail.com> wrote: >> >>> Hi John, >>> >>> I am writing a parallel application program. It seems that libmesh already >>> packaged the MPI communication by Parallel::Communicator. >>> I intend to read and partition the unstructured data using libmesh library >>> (including the use of Communicator for parallel purpose), and complete >>> other parts of my application using the original MPI library. >>> So I am wondering that, how can I combine the use of libmesh Communicator >>> and the original MPI library? Or can you give me an example? >>> >> >> If I understand correctly, you are calling libmesh from another parallel >> application on a separate communicator? >> >> This should work, we removed all traces of a global MPI_COMM_WORLD a while >> ago. Unfortunately I don't have any examples handy... > > It's pretty simple; you initialize MPI yourself, create the > subcommunicator you want, and then pass that subcommunicator as a > third argument to the LibMeshInit constructor. > > I'm a little worried, though - this was well-tested functionality at > one point but I don't know if we have any regression testing of it. > --- > Roy
------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. http://sdm.link/zohomanageengine _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
