Thanks, the only alternative I am left with is therefore having a flattened
mesh and defining my own hanging node constraints with
System::attach_constraint_object(). The only issue is that I need to be careful
with the refinement.
--
On 1/25/18, 12:48 PM, "Roy Stogner" <royst...@ices.utexas.edu> wrote:
On Thu, 25 Jan 2018, Salazar De Troya, Miguel wrote:
> An easier question to make would be: Can I have a parent element
> with just two children?
Ah! I'm not sure if this was an easier question to make, but it's a
*much* easier question to answer: no.
The last time I tried counting, we had literally more than a hundred
places where libMesh core library code made the core assumption that
any hierarchical refinement was done isotropically. IIRC there are
even many places in the code that make the assumption that the
refinement pattern within each parent element of a hierarchic mesh
matches one of the few refinement patterns which libMesh creates
itself.
It's something we'd all love to change; anisotropic AMR is nice. But
I don't see it changing any time soon.
---
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
