4 ms·
> including applications that require a certain level of accuracy (e.g. processing pricing feeds from financial institutions) Should leap seconds matter then?
by 908B64B197 5y ago
> including applications that require a certain level of accuracy (e.g. processing pricing feeds from financial institutions)
Should leap seconds matter then? As long as you are synchronizing with the same source of truth as the financial institution's back-end, both clocks should tell the same time.
- sporkle-feet 5y agoWhat if we're trying to correlate prices from two different financial institutions? Maybe one uses smearing and one doesn't, who knows?
- sla29970 5y agoIn that case UTC is the wrong answer to the question "What timescale will produce robust results for this application?" As soon as leap seconds were recommended by the CCIR in 1970 radionavigation system administrators announced they would switch to purely atomic TAI-10s and astronomical almanacs continued to use just plain UT. Proceedings of international standards bodies show them discussing how the new CCIR timescale with leap seconds (not yet officially named UTC) need not apply to anything other than radio broadcast time signals.