On Tue, Jun 19, 2012 at 11:27 AM, Roy Stogner <royst...@ices.utexas.edu> wrote: > > Not sure what the best solution is. Add a sanity check by calculating > xyz for the results of the inverse_map and making sure the distance > from the original point is under tol*h_max? Seems unnecessarily > expensive in 90% of case, but I suppose we'd only need to do the check > in 1D and 2D cases.
The attached patch implements this fix, it works for my simple test case and a more involved one I have... It could be made a bit faster by adding an FEInterface::map() function in the same vein as FEInterface::inverse_map() which forwards to FE<Dim,T>::map(). This seems like it would also be a useful feature in general... An even better optimization would be to add geometric-only specializations of Elem::contains_point(), at least for the linear element types. -- John
0001-Fixing-Elem-point_test-called-by-Elem-contains_point.patch
Description: Binary data
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ Libmesh-devel mailing list Libmesh-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-devel
