Remix.run Logo
exegete 3 hours ago

> The difference between Coordinated Universal Time UTC and the International Atomic Time TAI is :

>

> from 2017 January 1, 0h UTC, until further notice : UTC-TAI = -37s

This means the atomic clock is behind the solar clock by 37 seconds? I also don’t understand the reference to 2017.

pdonis 2 hours ago | parent | next [-]

> This means the atomic clock is behind the solar clock by 37 seconds?

If anything, it's the other way around.

A UTC day is defined as exactly 86400 SI seconds. But an actual mean solar day is a few milliseconds longer (although the difference is not constant due to irregularities in the Earth's rotation--but the average difference is expected to slowly increase over time). SI seconds are counted by atomic clocks, so UTC advances its day by one every 86400 atomic clock seconds.

But a solar clock that advances its day by one every time the mean sun reaches noon (it has to be the mean sun because the rate at which the actual sun moves across the sky varies over the course of a year, we need to look at the average) will advance its day a few milliseconds later than UTC does. Or, to put it another way, each time period that the solar clock says is exactly 86400 seconds, is a few milliseconds longer according to the atomic clock.

As this happens day after day, the difference accumulates, and when it gets close to being a full second, a leap second gets inserted into UTC, so that one of its days is 86401 seconds long instead of 86400. The reason for this is that UTC is not just counting atomic clock time; it also has to stay in sync with where the sun is in the sky since so many human activities are tied to that. And we humans have defined "in sync with the sun" to be "within a second of the average sun". In other words, we want UTC noon to be within a second of mean solar noon on the prime meridian.

So the 37 seconds is how far mean solar noon would be behind UTC noon, if we didn't use leap seconds--at UTC noon, the mean sun would be 37 seconds short of actually crossing the prime meridian in the sky.

Vvector 2 hours ago | parent [-]

"In other words, we want UTC noon to be within a second of mean solar noon on the prime meridian."

Why?

If I travel 1 mile east or west of the prime meridian, my solar noon now comes 2-3 seconds earlier/later. It's nearly impossible to have your local time match your local solar noon. For most of the population, solar noon is, on average, 30 minutes off of 12:00 noon.

Plus, solar noon varies from day to day by 10-20 seconds. Check the charts out. https://www.timeanddate.com/sun/usa/new-york

pdonis an hour ago | parent | next [-]

> Why?

Um, because it's the prime meridian and that's how UTC is defined?

> It's nearly impossible to have your local time match your local solar noon.

Which is why I specified on the prime meridian, which is the particular local meridian that UTC is defined as corresponding to.

> solar noon varies from day to day by 10-20 seconds.

Which is why I was careful to specify mean solar noon.

I'm not quite sure what your issue is. Yes, we have time zones tied to specific meridians, and the actual sun's speed in the sky varies (which I mentioned in my post, so I'm not sure why you seem to think I'm unaware of it) so in most places local time by the clock doesn't match local time by the sun. Yes, a leap second adjustment to UTC is quite a bit smaller, taken in isolation, than the annual variation in actual solar time vs. mean solar time.

But over time, if we didn't have leap seconds, the difference would accumulate. The accumulated difference now between UTC and TAI is 37 seconds--which is almost twice the maximum variation in actual solar noon from mean solar noon that you refer to. We humans have collectively decided that we don't want that, and that it's better to do the adjustments a little at a time rather than in bigger lumps.

Perz1val an hour ago | parent | prev [-]

Probably there are things more important than your lunch that need time to be exactly synced with sun position

oasisaimlessly 43 minutes ago | parent [-]

For things that need much more precusion than my lunch, ±1 second probably still isn't good enough, so they need another layer of correction anyway. Given that exists, might as well push leap seconds into that layer too.

flohofwoe 2 hours ago | parent | prev | next [-]

Apparently December 2016 was the last time a leap second was inserted, at least that's what Wikipedia says:

https://en.wikipedia.org/wiki/Leap_second

NooneAtAll3 2 hours ago | parent [-]

we were ought to insert a negative leap second, but cowards got too afraid it would break code

2 hours ago | parent | prev | next [-]
[deleted]
doctoboggan 2 hours ago | parent | prev [-]

> I also don’t understand the reference to 2017.

My guess is that is when they last changed the offset, so the -37s has been in effect since then.