On Tue, 13 Mar 2018, Vasileios Vavourakis wrote:
oh, I thought that the default setting in the Parallel::Communicator (i.e. see
default
constructor:
http://libmesh.github.io/doxygen/classlibMesh_1_1Parallel_1_1Communicator.html#a697f8e599333609a45761828e14659c1)
for the
“communicator” is: MP
thanks Roy for the quick turnaround.
my comments below to your reply…
> On 13 Mar 2018, at 21:02, Roy Stogner wrote:
>
>
> On Tue, 13 Mar 2018, Vasileios Vavourakis wrote:
>
>> I would like to run (in parallel mode) a piece of libMesh code where on
>> each processor, a libMesh::Mesh is initia
On Tue, 13 Mar 2018, Vasileios Vavourakis wrote:
I would like to run (in parallel mode) a piece of libMesh code where on
each processor, a libMesh::Mesh is initialised & stored locally and, hence,
subsequently initialise the EquationSystems accordingly, and for each
processor independently.
Th
Dear libMesh users/developers,
I would like to run (in parallel mode) a piece of libMesh code where on
each processor, a libMesh::Mesh is initialised & stored locally and, hence,
subsequently initialise the EquationSystems accordingly, and for each
processor independently.
The FE mesh, may be sam