On Fri, Nov 7, 2008 at 12:05 PM, Benjamin Kirk <[EMAIL PROTECTED]> wrote: >> Remind me again what was the reason for numbering it this way? I'm >> sure there was one, I just can't remember what it was. > > I'm not sure there was a reason, or at least I can't find anything that jogs > my memory looking back through the logs. One possible culprit, though - the > ordering of our pyramid matches exactly the ordering used in vtk. > > Would we be better off reorienting the base? In that case the side creation > would have to change, as well as any read functions which take in a pyramid. > > The only sucky part here is keeping backward compatiblity in the .xda/.xdr > mesh format.
Yeah, we could either renumber the shape functions or change the numbering of the reference element. I figured the former offered the path of least resistance, but I could be convinced to do either. -- John ------------------------------------------------------------------------- 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
