On Tue, 15 Sep 2009, Derek Gaston wrote: > I've been struggling for a while now with a way to detect (reliably) > that the mesh has changed. What I do now is force all of the > applications that use my code to call a function anytime they call one > of the refinement/coarsening functions.
Is this a sufficient definition of "mesh has changed" for you? You guys are trying to cache out some collision/intersection detection info, IIRC? In which case moving nodes would be just as much of a change as creating new nodes is. > Could we add a counter to the mesh that says the number of times it's > changed? And have that counter get incremented every time one of the > refine / coarsen functions gets called on a mesh? This way different > parts of the code could query to see if the number of times the mesh > has changed... has changes. (hmmm). This sounds reasonable. I'd worry about non-MeshRefinement objects trying to directly do refinement/coarsening, but there's already loads of stuff that might break if someone tried that. --- Roy ------------------------------------------------------------------------------ Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now! http://p.sf.net/sfu/devconf _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
