On Thu, 19 Aug 2010, Roy Stogner wrote: > This replicates here perfectly; thanks. And cutting down the mesh > size to 2x2 (then expanding the refinement criteria to y>5 to > compensate) reduces the problem to something I can look at by hand. > I'm swamped lately but I'll try to check it out this weekend.
I actually had time to look at the problem and I actually found a fix pretty quickly. Give the svn HEAD a try. And don't take my confidence as a replacement for verification. in particular, although I think the fix should work in 3D and for multi-level constraint cases I wouldn't trust it would testing. One more catch if you're using AMR with periodic BCs: I don't think the JumpErrorEstimator or PatchRecoveryErrorEstimator classes are currently PeriodicBoundary-aware. How suboptimal the resulting refinement patterns are will depend on your application. --- Roy ------------------------------------------------------------------------------ This SF.net email is sponsored by Make an app they can't live without Enter the BlackBerry Developer Challenge http://p.sf.net/sfu/RIM-dev2dev _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
