On Tue, Jun 12, 2018 at 7:48 PM, Povolotskyi, Mykhailo
wrote:
> Dear Libmesh develepers,
>
> I want to create different instances of mesh on several MPI processes.
> Then I want to output the mesh from one MPI process.
>
>
> I am facing problems with the following code:
>
>
> #include
Hi John,
It would be absolutely impossible for me to use Mesh on MPI_COMM_WORLD.
Do you thing, will it possible either to reset the vtkMPIController or
to split his communicator?
Michael.
On 06/13/2018 12:28 PM, John Peterson wrote:
On Wed, Jun 13, 2018 at 10:14 AM, Michael Povolotskyi
Hello John,
I played with it, and this is what worked for me.
#include
#include
using namespace std;
#define private public//to get access to
libMesh::LibMeshInit._vtk_mpi_controller
#include "libmesh/mesh_generation.h"
#include "libmesh/mesh.h"
#include "libmesh/vtk_io.h"
#include
On Wed, 13 Jun 2018, John Peterson wrote:
MPI is already initialized in LibMeshInit, so no need to do this manually
unless your real code does MPI communication before LibMeshInit...
MPI_Finalize();
MPI_Finalize is called in the LibMeshInit destructor, no need to call it
manually.
Thank you,
now I see.
On 06/13/2018 01:29 PM, Roy Stogner wrote:
On Wed, 13 Jun 2018, John Peterson wrote:
MPI is already initialized in LibMeshInit, so no need to do this
manually
unless your real code does MPI communication before LibMeshInit...
MPI_Finalize();
MPI_Finalize is
On Wed, Jun 13, 2018 at 11:03 AM, Michael Povolotskyi
wrote:
> Hello John,
>
> I played with it, and this is what worked for me.
>
> #include
> #include
> using namespace std;
>
> #define private public //to get access to libMesh::LibMeshInit._vtk_mpi_
> controller
>
> #include
On 06/13/2018 03:15 PM, John Peterson wrote:
On Wed, Jun 13, 2018 at 11:03 AM, Michael Povolotskyi
mailto:mpovo...@purdue.edu>> wrote:
Hello John,
I played with it, and this is what worked for me.
#include
#include
using namespace std;
#define private
