On Wed, 13 Apr 2011, John Peterson wrote:
> So we just never implemented it, but it's definitely possible there > would be other changes needed in the library to do it, as it would be > the only element with heterogeneous children... Yup - Elem::refine would need a special case. > If anybody out there is thinking about it, it might be nice if the > refinement pattern didn't include *any* pyramids at all! Not possible. Compatibility with neighboring hexes requires the quad side to have tensor product basis functions, so you can't just chop the quads there up into triangles, so you need at least 4 pyramid children per pyramid parent. The other two pyramids would be easy to replace with 4 tets, though. Do the same diagonal selection trick that we do on a tet refinement's octahedral core, and it might even be a nice result. Nice from a mesh quality perspective, anyway; from a "making is_child_on_side correct" perspective it'll be annoying. --- Roy ------------------------------------------------------------------------------ Forrester Wave Report - Recovery time is now measured in hours and minutes not days. Key insights are discussed in the 2010 Forrester Wave Report as part of an in-depth evaluation of disaster recovery service providers. Forrester found the best-in-class provider in terms of services and vision. Read this report now! http://p.sf.net/sfu/ibm-webcastpromo _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
