On Mon, 16 Feb 2015, Peter Wijeratne wrote: > Still having the same problem. I now initialise using the > Communicator from LibMeshInit::comm(); is this correct, or should I > be creating my own Communicators?
No, you'll need to create your own subcommunicators. The communicator from LibMeshInit::comm() is either what you initialized libMesh with or MPI_COMM_WORLD; you'll probably want to wrap MPI_COMM_SELF in a Parallel::Communicator if you want a mesh that really only lives on one processor. --- Roy ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
