On Tue, 27 Jan 2009, Kirk, Benjamin (JSC-EG) wrote: >> Reusing the parent pointer scares me.
As long as you're not arguing the point. ;-) Just be careful. > Not sure about that... Since the orientation of the elements on the > manifold introduce the notion of 'inside' and 'outside' I think the notion > is still valid - the parent is the higher-dimensional element the surface > normal points away from. If you need to get access to the element you are > pointing in to then you can query the parent's neighbor. That makes sense. When we create the manifold, which subdomain we call it for (or which we order "first") will determine the manifold orientation, which will determine which side is the interior. > True, except for the level-0 (N-1)-dimensional elements. I still think it > might be useful to have these know the level-0 N-dimensional element from > which it came. If the refined (N-1)-d elements need to know the N-d element > they are adjacent to they can grab the family tree from the N-d level-0 > element and at least have a small amount of elements to check. Okay. So from the user's perspective the operation is O(log(N)), but at least it can be seamless. >> We already have a class that I think was designed to associate >> arbitrary user information with elements and/or nodes, MeshData. >> It's a real shame that this class isn't really supported by any of the >> active developers. Perhaps this is the right opportunity to actually >> become familiar with how that class is supposed to work, get it >> working properly with newer libMesh features, and write some code that >> we can use for regression testing it. > > Agreed. Unfortunately, I think this is one area we cannot hide the user > from parallel communication. I can imagine a user-defined class derived > from some abstract DofObjectAdditionalData base class or something, but the > user will have to provide pack/unpack functions for redistribution to work. I see. We can attach their data to a System and the library can handle which data goes to which processor, but there's no way to second-guess the user about how to properly destroy it here and instantiate it there. --- Roy ------------------------------------------------------------------------------ This SF.net email is sponsored by: SourcForge Community SourceForge wants to tell your story. http://p.sf.net/sfu/sf-spreadtheword _______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
