On Sep 17, 2015 9:13 AM, "Roy Stogner" <royst...@ices.utexas.edu> wrote: > > > On Wed, 16 Sep 2015, Christopher Haynes wrote: > >> I just wanted to make sure I am not missing something when I use the >> interior_parent of an Elem object. Basically I am using it in a sense that >> the interior_parent holds a reference to a "neighboring" higher dimension >> element. If this sounds correct, I'll continue its use. > > > This is correct. > > >> However, I am also wondering if there is a way to set the interior_parent >> in a more "automatic" way? That is, currently I have to specify which >> element will be the interior parent of an element, ensuring the selected >> element is at least 1 degree higher in dimension. > > > I'm afraid there's currently no avoiding this requirement on your > initial meshes. We should now be correctly setting interior_parent > after mesh refinement and ParallelMesh redistribution, but the initial > data comes from you. >
I did notice that the interior parent was being correctly set after mesh refinement. >> Will this be automated such that when a method like >> *prepare_for_use* is called the interior parents will also be set? > > > Hmm... That wasn't on my todo list, and it would be a big change, but > it's at least possible in principle, assuming the user shares nodes > between the two elements in a consistent way. > > And it really needs to be on my todo list, doesn't it? Otherwise > we're not likely to handle restarts on mixed dimensional meshes > properly without manual intervention. > > I don't know how many weeks (months?) it'll take before this works its > way to the *top* of the list, though, so if you want to take first > crack don't wait for me. > > >> Given there is some complications if an element has the possibility >> of having more than one interior parent (like the example mesh in >> tests/mesh/mixed_dim_mesh_test.C). > > > Hopefully we now (as of this summer) handle that case appropriately: > when library code needs to look at *all* an element's corresponding > interior elements, it doesn't just query interior_parent() and stop, > it uses find_interior_neighbors() to get the whole set. > --- > Roy Thank you for the feeback! -Chris ------------------------------------------------------------------------------ Monitor Your Dynamic Infrastructure at Any Scale With Datadog! Get real-time metrics from all of your servers, apps and tools in one place. SourceForge users - Click here to start your Free Trial of Datadog now! http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140 _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
