On Fri, 7 Feb 2014, Derek Gaston wrote:
> The doxygen is out of date.
Yeah, we really need to get in the habit of doing a "make upload" with
every release.
It's up to date now.
---
Roy
--
Managing the Performance of Cl
On 02/07/2014 11:27 AM, Derek Gaston wrote:
> Michael - I can vouch that using different communicators for Mesh (and
> everything else) does work in libMesh... it's something we have done
> quite a bit of.
>
> If you are struggling, please send along a small example.
>
> Thanks,
> Derek
>
>
Hi, m
The doxygen is out of date.
Also - we really need to move it to GitHub... it's one of the few things
left back at Sourceforge
Derek
On Fri, Feb 7, 2014 at 9:35 AM, Michael Povolotskyi wrote:
> On 02/07/2014 11:27 AM, Derek Gaston wrote:
>
>> Michael - I can vouch that using different commu
Michael - I can vouch that using different communicators for Mesh (and
everything else) does work in libMesh... it's something we have done quite
a bit of.
If you are struggling, please send along a small example.
Thanks,
Derek
On Thu, Feb 6, 2014 at 4:20 PM, Michael Povolotskyi wrote:
> On 0
On 02/06/2014 05:53 PM, Roy Stogner wrote:
>
> On Thu, 6 Feb 2014, Roy Stogner wrote:
>
>> Note that the communicator you pass to the Mesh will be propagated
>> through any objects that you build from that mesh, but if you want to
>> build any parallel objects yourself you'll have to make the
>> co
On Thu, 6 Feb 2014, Roy Stogner wrote:
> Note that the communicator you pass to the Mesh will be propagated
> through any objects that you build from that mesh, but if you want to
> build any parallel objects yourself you'll have to make the
> communicator consistent between them.
I'm not saying
On Thu, 6 Feb 2014, Michael Povolotskyi wrote:
> it it possible to create a mesh with a communicator that is different
> from the communicator that was used for LibMeshInit ?
Of course! Back when that wasn't possible, we didn't bother to make
the communicator a constructor argument.
Note that
