Thanks, Roy. I have a preference for Lagrange interpolation for the structural (and some thermal) applications that I am working on, primarily due to easy application of Dirichlet boundary conditions. Perhaps hierarchic polynomials would also offer a similar feature (please correct if I am wrong) due to the presence of node and edge functions whose dof values can be specified, and bubble functions that are zero on the boundaries.
I was considering the possibility of experimenting with increasingly higher order interpolation for my shell element. This does not necessarily have to be Lagrange polynomials (although it would be nice to experiment), and can be a hierarchic basis like the one I mentioned above. I am curious about your comment "mapped the Lagrange bases on to nodes topologically". Are you implying a software fix of telling the dof that it is associated with a node, or some sort of a mathematical mapping process? Thanks, Manav On Thu, Feb 21, 2013 at 3:34 PM, Roy Stogner <[email protected]>wrote: > > On Thu, 21 Feb 2013, Manav Bhatia wrote: > > L2_LAGRANGE provides the *discontinuous* interpolation using Lagrange >> polynomials, so I could use a quad4 and have as high as third order >> (currently, and I will be glad to contribute more). However, is there a >> way >> to achieve the same order of *C0 continuous* Lagrange interpolation on >> quad4. This would require that the node and edge dofs be consolidated >> between elements. >> > > If we stuck with the same isoparametric element paradigm that current > LAGRANGE code in libMesh uses, then there's no way to add higher order > Lagrange FE support without first adding higher order geometric > support, which would be a huge pain in the neck. > > If we simply mapped the Lagrange bases on to nodes topologically, > though, it shouldn't be any harder than writing the high order > HIERARCHIC and other bases was, though. We'd still need new geometric > elements in a few cases (pyramids, tets, prisms) to give us side > nodes, but that's something we've been wanting anyway. > > I'm not sure how useful people would find that second case, though. > In my experience, users who like Lagrange because of its conditioning > properties are well outnumbered by users who like Lagrange because > it's easy to (sometimes inadvertently) write code which assumes that > there's exactly one DoF per variable per Node and that this DoF > corresponds to the variable's value at that Point. > --- > Roy > ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_feb _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
