On Friday, 8 January 2021 at 20:19:59 UTC, Bastiaan Veelo wrote:
Off topick, the original js implementation is documented to not generate results that are guaranteed to be correct. I could not find information on what the conditions are that cause deviations, and how large these then can be. Do you have an idea about this or experience with accuracy of the algorithm? I am looking into whether earcutd can replace GLU tesselation. We use the result for engineering purposes (not only visualisation) and correctness is important to us.
I've used documentation and implementations from David Eberly at https://www.geometrictools.com/ and also on github nowadays to get 'correct' or at least 'predictable' behavior for various geometric challenges.
Using this library solved various issues for us. The documentation is great!
