I sent this email couple days back but have not received any reply yet. I know you guys are busy but it would help me quite a bit in completing the implementation if one of the developers can explain the purpose of the embedding matrix.
I have implemented higher order lagrange basis for 1-d elements (till EDGE6) and am in the process of testing 2-d quad elements (QUAD16, QUAD25). But I have another question regarding the 2-d elements. What are the i0 and i1 arrays in fe_lagrange_shape_2d.C ? I am sure they represent some array indices to access data for the nodes in the element but the numbering is not completely obvious to me. If someone can shed some light on this part of the code, that will be helpful too. I have been testing my codes primarily with ex4 using higher order lagrange basis. I have not implemented any extensions/modifications for AMR capabilities with these higher order elements but if you can point out possible locations that might need modifications for this capability, I can look at these before sending you a patch. Vijay On Thu, Sep 30, 2010 at 7:33 PM, Vijay S. Mahadevan <[email protected]> wrote: > Hi all, > > I am working on system that requires me to start with a 4th order > element since the mesh for the domain is prescribed from an external > source. Now, since libMesh does not have 4th order lagrangian elements > and since I'm lazy to learn a new package (and since I'm constrained > in time), I decided to implement higher order lagrange elements (EDGE, > QUAD, HEX only for now) till order 5. But on my first look to proceed > with this idea, I noticed that there is an embedding matrix that is > prescribed for every element. And I do not exactly understand the > usage of this array in the bigger picture. If someone can help me > understand what exactly it represents, it would be tremendously > helpful for me in the implementation. > > I might have posed a similar question couple of years ago in the > context of higher order elements but when I'm done testing, I > definitely can create a patch to add the functionality to the library, > even though my focus is only for limited elements. > > Thanks, > vijay > ------------------------------------------------------------------------------ Virtualization is moving to the mainstream and overtaking non-virtualized environment for deploying applications. Does it make network security easier or more difficult to achieve? Read this whitepaper to separate the two and get a better understanding. http://p.sf.net/sfu/hp-phase2-d2d _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
