see https://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_dealii_dealii_pull_3956&d=CwIBaQ&c=Ngd-ta5yRYsqeUsEDgxhcqsYYY1Xs5ogLxWPA_2Wlc4&r=4k7iKXbjGC8LfYxVJJXiaYVu6FRWmEjX38S7JmlS9Vw&m=Kumuf8l3Od3XM93KDoNo2AFeuWqKbGvpUufysXzdnAE&s=847Vw5LGq1DTVk1pUvZNIpjoFirAOxRIkxnlS0VHYC8&e= for the work in progress pull request.
On Wed, Feb 8, 2017 at 1:53 PM, Timo Heister <heis...@clemson.edu> wrote: >> Are you willing to share that code, Timo? > > Yes, we will be creating a PR for that soon. > >> I suspect that if implemented right, it should not be terribly difficult to >> do refinement of the mesh, but because you can't repartition the coarse >> mesh, it will quickly become unbalanced if processors refine differently >> (i.e., in practice, if processors do not all refine globally). > > The issue with that is that you would need to update the ghost layer > correctly. Doable, but definitely requires some extra thought. > >> Do you implement this by building another class on top of >> dealii::Triangulation so that the base class only stored the coarse mesh >> plus one layer of ghosts, and the derived class is responsible for the >> communication? And then derive another class from DoFHandlerPolicy to deal >> with this triangulation? > > Yes. It is derived from parallel::Triangulation (and an alternative to > shared::Tria and distributed::Tria). > > -- > Timo Heister > http://www.math.clemson.edu/~heister/ -- Timo Heister http://www.math.clemson.edu/~heister/ -- The deal.II project is located at http://www.dealii.org/ For mailing list/forum options, see https://groups.google.com/d/forum/dealii?hl=en --- You received this message because you are subscribed to the Google Groups "deal.II User Group" group. To unsubscribe from this group and stop receiving emails from it, send an email to dealii+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
