On 07/15/2014 10:51 PM, Roy Stogner wrote: > > On Tue, 15 Jul 2014, David Knezevic wrote: > >> I use MeshFunction a lot, it's very helpful. But sometimes due to >> rounding error, I evaluate a MeshFunction at a point just outside the >> mesh, and hence the evaluation fails. >> >> I'd like to prevent this type of failure. >> >> I was thinking of perturbing the evaluation point in various directions >> (p + (delta,0,0), p + (0,delta,0), etc) until I find a point that is >> inside the mesh. This seems like it would work, but it's not very >> elegant. I was wondering if anyone has any other ideas about how to go >> about this? > > We currently use Elem::contains_point() with default tolerance in the > point_locator in MeshFunction. Perhaps we could switch that to > Elem::close_to_point(), add functionality to the point locators to > allow increasing the tolerance, and expose that in the MeshFunction?
That sounds very good to me. David ------------------------------------------------------------------------------ Want fast and easy access to all the code in your enterprise? Index and search up to 200,000 lines of code with a free copy of Black Duck Code Sight - the same software that powers the world's largest code search on Ohloh, the Black Duck Open Hub! Try it now. http://p.sf.net/sfu/bds _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
