We use TypeVector::relative_fuzzy_equals in a number of places in the
library. I'm not convinced that this function makes sense, since the
tolerance effectively depends on where the points happen to be located. I
can't think of any situation where this behavior is desirable.
My preferred approach is to always use absolute_fuzzy_equals, and to use a
tolerance that is relative to some reference length, if a
reference length is available. (For example, the relative_fuzzy_equals
point comparisons in the "reference element" classes could be replaced with
this approach, where we use a relative size of 1, which ends up meaning
that we would use absolute_fuzzy_equals with the default tolerance.)
Just wondering what everyone else thinks about this?
David
------------------------------------------------------------------------------
What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic
patterns at an interface-level. Reveals which users, apps, and protocols are
consuming the most bandwidth. Provides multi-vendor support for NetFlow,
J-Flow, sFlow and other flows. Make informed decisions using capacity planning
reports. http://sdm.link/zohomanageengine
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
