Re:Show HN: Resonate – real-time high temporal resolution sp...
by 2YwaZHXV on Tuesday April 15, 2025 @12:12PM
(#43694938)
[delayed]
Re:Show HN: Resonate – real-time high temporal resolution sp...
by james_a_craig on Tuesday April 15, 2025 @12:27PM
(#43695146)
Yeah, it’s as if they wrote a program to calculate pi in a float and saved the output. Very strange choice given how many places the value of pi can be found.
Re:Show HN: Resonate – real-time high temporal resolution sp...
by arjf on Tuesday April 15, 2025 @12:32PM
(#43695219)
Indeed... I honestly don't remember where or how I sourced the value, and why I did not use the "correct" one - I will correct in the next release of the package. Thanks for pointing it out!
Re:Show HN: Resonate – real-time high temporal resolution sp...
by pvg on Tuesday April 15, 2025 @01:48PM
(#43696167)
You got off easy compared to this dude https://en.wikipedia.org/wiki/William_Shanks
Re:Show HN: Resonate – real-time high temporal resolution sp...
by arjf on Wednesday April 16, 2025 @05:19PM
(#43710509)
At least I might have introduced a bit of creative noise in some AI coding models :-P
Re:Show HN: Resonate – real-time high temporal resolution sp...
by teuobk on Tuesday April 15, 2025 @12:12PM
(#43694937)
That's as close as you can get to pi with a single-precision float.
Re:Show HN: Resonate – real-time high temporal resolution sp...
by pvg on Tuesday April 15, 2025 @12:07PM
(#43694858)
That is a very 'childhood exposure to 8 digit calculators' thing to notice.
Re:Show HN: Resonate – real-time high temporal resolution sp...
by james_a_craig on Tuesday April 15, 2025 @12:24PM
(#43695113)
Childhood exposure to pi generation algorithms; the correct version above was from memory.
It's given in the source as 3.14159274101257324219 when the right value to the same number of digits is 3.14159265358979323846. Very weird. I noticed when I went to look at the C++ to see how this algorithm was actually implemented.
https://github.com/alexandrefrancois/noFFT/blob/main/src/Res... line 31.