On Feb 10, 2009, at 1:18 PM, Vijay S. Mahadevan wrote: > I guess, the user_pointer can serve as a generic container to hold all > attributes. While refining, you could deduce the properties based on > parent. But I wonder how you would propagate these variables on to the > parent element when you are coarsening.
OMG! The nightmares are coming back to me! Oh the hours spent debugging refinement / coarsening algorithms for each Sierra application! Oh god no! Since every application could hang whatever data it wanted to off of mesh structures there were these extremely complicated "prolongation" and "restriction" algorithms that were run whenever h-adaptivity happened. Oh the horrors. Many people who work on Sierra _still_ don't believe me whenever I tell them that you don't have to hand code prolongation / restriction algorithms for h-adaptivity with libmesh..... Ok - off my soapbox. Be wary of the apple with a snake in it (or something)... Derek ------------------------------------------------------------------------------ Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM) software. With Adobe AIR, Ajax developers can use existing skills and code to build responsive, highly engaging applications that combine the power of local resources and data with the reach of the web. Download the Adobe AIR SDK and Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
