On Tue, 12 Apr 2011, Boyce Griffith wrote: > I have an application in which I would like to use a coarse mesh for one > system and a (statically or adaptively) refined mesh for another system. > The systems will be loosely coupled --- I will need to evaluate coarse > variables onto the refined grid and vice versa. The elements of the > fine mesh will remain nested within the coarse mesh, and I currently > expect only to do h-refinement with Lagrangian elements. > > It seems like the easiest way to couple these two systems would be to > use MeshFunction; however, I expect that there are more efficient ways > to go about this. Can the system projection functionality be used for > this kind of thing?
Unfortunately no - the inefficiency of MeshFunction is due to the element lookup, the system projection code avoids this inefficiency by using the tree structure of the mesh to locate which element to project from. Modifying the tree structure to reflect multiple nested meshes at once would be possible (active elements in one could be subactive in another, with some changes to the RefinementFlags and Mesh::*iterator code) but that would be a fairly extensive modification. My suggestion would be to start with the MeshFunction code, and then if that needs speeding up cache an unordered_map<Elem*,Elem*> between the meshes. --- 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
