On Fri, 29 Jun 2018, Griffith, Boyce Eugene wrote:
On Jun 20, 2018, at 9:48 AM, Griffith, Boyce Eugene <boy...@email.unc.edu>
wrote:
On Jun 19, 2018, at 11:58 PM, Roy Stogner <royst...@ices.utexas.edu> wrote:
On Tue, 12 Jun 2018, Griffith, Boyce Eugene wrote:
OK, so something like:
partiontiner->repartition();
equation_systems->reinit();
and then continue?
Did this work for you?
The code above is what I'd have written as v0.1 too, but I added a
quick unit test to make sure and (at least with DistributedMesh) no
luck. I'll see what I can figure out; surely you can do this without
a whole prepare_for_use()…
I haven’t gotten a chance to implement the new partitioner yet. We will be
using ReplicatedMesh for the foreseeable future.
Did you get a chance to figure out the correct sequence of calls to
make something like this work? I am happy to run some tests with
your unit test if it would be helpful.
It looks like my unit test inadvertently triggered a *different*
failure, simply because my set up (moving a mesh back on to processor
0 even if it was already distributed) was a corner case we'd never
supported.
https://github.com/libMesh/libmesh/pull/1773 should fix that corner
case and add the unit test, and in theory your above code should
already have worked fine on more realistic cases.
---
Roy
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users
