As a software engineer, I would like to add that we are done dealing with time and dates and Martians and Moonfolk better pick UTC and shut up or they aren’t touching the database.
Timezones are one thing. Accounting for relativistic drift will be a whole different problem.
I’m glad I’ll be dead before I have to think about dates and times that hard. I’ll never forgive that one island that moved the international dateline or the parts of the United States that don’t follow daylight savings.
Nobody should follow DST. It’s archaic and outdated.
If I have to build a new Python library for relativistic drift, I might actually punch a bitch. 😆
Seriously though, if I had a dollar for every time someone asked me to do the impossible just because I’m a software engineer, I don’t know that I’d be rich, but I would have a decent amount of money.
I can appreciate the thought experiment that is coming up with a framework for interplanetary timezones because some people probably enjoy the challenge.
Simultaneously I posit that it’s ambitious as fuck to assume that humanity is going to get off this rock before we burn it to the ground, or to assume that whoever gets off this rock will have enough people and resources to start a society that can grow while the society on Earth also survives.
Furthermore, as a software engineer, I say no thank you. Earth and other planets will function off of digital systems that never EVER communicate with each other, and we will be happy that way
As humanity aspires to explore the solar system and investigate distant worlds such as the Moon, Mars, and beyond, there is a growing need to establish and broaden coordinate time references that depend on the rate of standard clocks. According to Einstein’s theory of relativity, the rate of a standard clock is influenced by the gravitational potential at the location of the clock and the relative motion of the clock. A coordinate time reference is established by a grid of synchronized clocks traceable to an ideal clock at a predetermined point in space. This allows for the comparison of local time variations of clocks due to gravitational and kinematic effects. We present a relativistic framework to introduce a coordinate time for the Moon. This framework also establishes a relationship between the coordinate times for the Moon and the Earth as determined by standard clocks located on the Earth’s geoid and the Moon’s equator. A clock near the Moon’s equator ticks faster than one near the Earth’s equator, accumulating an extra 56.02 microseconds per day over the duration of a lunar orbit. This formalism is then used to compute the clock rates at Earth-Moon Lagrange points. Accurate estimation of the rate differences of coordinate times across celestial bodies and their inter-comparisons using clocks onboard orbiters at relatively stable Lagrange points as time transfer links is crucial for establishing reliable communications infrastructure. This understanding also underpins precise navigation in cislunar space and on celestial bodies’ surfaces, thus playing a pivotal role in ensuring the interoperability of various position, navigation, and timing (PNT) systems spanning from Earth to the Moon and to the farthest regions of the inner solar system.
Huh, neat paper.
Also, I had no idea that relativistic effects would cause a whole 56µs/d drift between a clock on Earth and one on the Moon, somehow I would have expected the difference to be smaller
200 milli seconds a decade
Oh yeah it’s not like it’s a lot lot, just more than I expected
It’s enough that clock drift still might be an issue.
Clock drift is an issue for GPS satellites.
It’s an issue for all clocks, just more noticeable with gps.
