New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Criteria to decide whether to try to re-parameterize in FitCurves is bad (scale-dependent) #23
Comments
Thanks. I've attempted to contact the author, Phil Schneider, for his opinion. |
Alternatively I could do a PR that exposes the error scale factor as a parameter? (and that line would then become |
The good news is that Philip Schneider recently responded, so I'm hoping he'll look at the code soon and figure out what's the most sensible. |
Pinged Philip. |
Philip replied: "The suggested change is probably OK." So I've checked it in, and pointed the interested user at this issue for more details. |
e.g. if units are such that user's
error
threshold is less than 1, the function will never try to re-parameterize. Based on the usage example (where error is 4.0), I think the intent would be preserved if you just setiterationError = error * 4.0;
bad code is here:
GraphicsGems/gems/FitCurves.c
Line 113 in 4d1d0a0
(and iterationError is used at line 146)
The text was updated successfully, but these errors were encountered: