I like this idea, but since Fraction.js should be fairly small when packaged and only a small portion of input strings would be covered, namely numbers with fractional part, this is either a good idea of an own library that translates the locales, or by fixing it before passing it to Fraction.js.
Here in Germany, we probably have the format as you, "123,45" and "123.456,99" with 1000s separators. Fixing this is usually just removing the dots and replacing the
.. When you need it more flexible based on the locale, you could use something around the new
Intl object, as outlined here https://observablehq.com/@mbostock/localized-number-parsing
But as I said, this only covers numbers like
"123,45", fractions can also be
"44 123/456". So maybe checking if no
[ /:] exists in the string could lead to the
NumberParser approach stated on the referenced site.
Why when a
Number is converted to a
Fraction the library internally uses powers and logarithms in base 10? Shouldn't that potentially reduce floating-point precision? Why not base 2?
I'll close the ticket for now, feel free to bring up other optimizations on Fraction.js :)
The question is, if this is something p5.js should do, or rather another library such as Angles.js with its method
This link in the README.md is bad. When used, you're presented with a 500 server error as seen below.
Thanks, it seems they dropped jsperf. I removed the link from the readme, thanks!
Any progress on this? Having the same problem on a new project now
According to the equations I posted your calculation is wrong. GDOP can therefore be calculated with
GDOP = sqrt(PDOP^2 + TDOP^2)
GDPÜ = sqrt(HDOP^2 + VDOP^2 + TDOP^2)
as I already said. Maybe it can be defined like that but what you calculate I don't know.
Maybe this paper is of help to achieve your goal https://stc.fs.cvut.cz/history/2011/sbornik/papers/pdf/1100016-1.pdf
I think it depends on what you or your employer is trying to achieve. The definition of GDOP according to  is
From that follows that you could calculate the GDOP based on the PDOP or HDOP and VDOP as well as TDOP if you have it. However, I don't know a receiver that gives you that information. Which brings me back to the question: What are you trying to achive?
 Kalman Filtering Theory and Practice with MATLAB by Mohinder S. Grewal, Angus P. Andrews
Hi, Java and C# compatibility on that wasn't a design goal, but thanks for bringing this up! Could you please provide the full output of what you feed in and what you expect to come out? Thanks!