Ok, thanks for the answers, I think that I was mixing up a few of
libMesh's concepts - for example, I thought that the default mesh class
was parallelized (from looking at MeshBase's inheritance graph), and
that the SerialMesh was a specific type. I should've looked more on the
documentation. O
On 10/03/16 14:15, Kirk, Benjamin (JSC-EG311) wrote:
>> On Mar 10, 2016, at 6:59 AM, Thiago Milanetto Schlittler
>> wrote:
>>
>> In my code, I have a situation where each processor needs a full
>> copy of a rather small mesh.
> One option would be to have each processor create a serial mesh b
On Thu, 10 Mar 2016, Thiago Milanetto Schlittler wrote:
>In my code, I have a situation where each processor needs a full
> copy of a rather small mesh. I seems like
> libMesh::ParallelMesh::allgather() does the trick,
It does, but if you're serializing a ParallelMesh then it's more
efficien
> On Mar 10, 2016, at 6:59 AM, Thiago Milanetto Schlittler
> wrote:
>
>In my code, I have a situation where each processor needs a full
> copy of a rather small mesh.
One option would be to have each processor create a serial mesh bound to the
communicator comm_self and then everyone rea
