On Fri, 14 Nov 2008, Norbert Stoop wrote: > I started to hack together some code which will add subdivision surface > based FEM to libmesh. Assuming the mesh is a triangulation, I need to > take special care of triangles with nodes that do not all have 6 edges > (a consequence of the subdiv. approach). To do this in a smooth way, it > is best to internally renumber a triangle's nodes so that the > problematic node is the first node of the triangle (ie Elem::_nodes[0] > returns that node).
Wait... which is "the problematic node"? A hanging node? A midedge node that isn't a hanging node? There could be two of either of those. And in any case, we do assume that the first three nodes of a triangle are vertices. > Any idea if this renumbering would break something else in libmesh? Don't change the local ordering (even from clockwise to counter-clockwise), and make sure to reorder any children and neighbor links at the same time... those are the only certain problems that come immediately to mind. But I wouldn't guarantee I'm not forgetting something. --- Roy ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
