News for hackers. Stuff that matters.
Re:All clocks are 30 seconds late by Straw on Monday January 06, 2025 @01:16PM (#42613362)
The average error is in fact 0! The average absolute error is reduced but not 0.
Re:All clocks are 30 seconds late by jtbayly on Monday January 06, 2025 @01:22PM (#42613457)
That may technically be correct, but it is incorrect in the real world. I submit that error is error in the real world. Mathematics can go jump off a cliff unless it wants to be helpful. :)
Re:All clocks are 30 seconds late by roywiggins on Monday January 06, 2025 @01:25PM (#42613491)
Zero average error conveys something important though: the error that there is, isn't biased positive or negative.
Re:All clocks are 30 seconds late by pkilgore on Monday January 06, 2025 @03:13PM (#42615132)
That's language failing us, not maths :-)
Re:All clocks are 30 seconds late by noqc on Monday January 06, 2025 @05:01PM (#42616465)
What are you talking about? Error is a metric.
Re:All clocks are 30 seconds late by jy14898 on Tuesday January 07, 2025 @09:13AM (#42622480)
By this logic, a broken 24 hour clock stuck at mid day has 0 error.
Re:All clocks are 30 seconds late by Straw on Saturday January 11, 2025 @12:52PM (#42667570)
The average of its errors is 0- ie it is not biased. Ofc, the average absolute error, which in English one could very reasonably refer to as "average error" is much greater than 0.