2 ms·
That's interesting. Can you point to an example? Is it a resolution problem?
by egsmi 6y ago
That's interesting. Can you point to an example? Is it a resolution problem?
- klodolph 6y agoIt’s a resolution problem if you want to measure something within 1s, which is fairly tame and reasonable. Like, let's say you’re measuring the time between two events, and you’re logging a stream of them. If you use Unix timestamp, the timer will jump during a leap second. This is because a day in Unix time is always exactly 86,400 “seconds”, but an actual civil day may be from 86,399 to 86,401 seconds. (It has never been 86,399 seconds, but it “could” be.) So you should probably be using TAI. UTC is theoretically good enough but it is inconvenient to use because of the leap seconds. Unix time is a bit broken. It is actually very easy to use TAI. You just need a GPS receiver. TAI is a fixed offset from GPS time (TAI = GPS + 19 seconds).