4 ms·

Time dilation from general relativity is approximately gh/c^2 (1e-18 -ish), which is an order of magnitude bigger than the uncertainty on your clock frequency (

Time dilation from general relativity is approximately gh/c^2 (1e-18 -ish), which is an order of magnitude bigger than the uncertainty on your clock frequency (1e-19 -ish). But you would need a more precise characterization of the clock to answer this. There might be significant noise on individual measurements, meaning that you need to take multiples to get precise enough (see https://en.wikipedia.org/wiki/Allan_variance https://en.wikipedia.org/wiki/Allan_variance). Edit: If you just have clock output in ticks, you also need enought time to elapse to get a deviation of at least one tick between both bot clocks you are comparing. This is a big limitation, because at a clock rate of 1GHz you are still waiting for like 30 years (!!). (In practice you could probably cheat a bit to get around this limit)

rcxdude 1y ago
>Edit: If you just have clock output in ticks, you also need enought time to elapse to get a deviation of at least one tick between both bot clocks you are comparing. This is a big limitation, because at a clock rate of 1GHz you are still waiting for like 30 years (!!). (In practice you could probably cheat a bit to get around this limit) In practice with this level of precision you are usually measuring the relative phase of the two clocks, which allows substantially greater resolution than just looking at whole cycles, which is 'cheating' to some degree, I guess. (The limit is usually how noisy your phase measurement is) (To give some intuition, imaging comparing two pendulum clocks. I think you can probably see how if you take a series of pictures of the pendulums next to each other you could gauge whether one of them is running fast relative to the other, and by how much, without one completing one full swing more than the other)
fsh 1y ago
These are optical clocks, so their rates are in the hundreds of THz to PHz range (1.121 PHz in the case of the Al+ clock). A 1e-18 shift corresponds to a ~mHz frequency deviation which a decent frequency counter can resolve in around 1s. However, no optical clock is actually that stable at short time scales, and the averaging is required to get rid of these fluctuations.

rcxdude 1y ago

>Edit: If you just have clock output in ticks, you also need enought time to elapse to get a deviation of at least one tick between both bot clocks you are comparing. This is a big limitation, because at a clock rate of 1GHz you are still waiting for like 30 years (!!). (In practice you could probably cheat a bit to get around this limit) In practice with this level of precision you are usually measuring the relative phase of the two clocks, which allows substantially greater resolution than just looking at whole cycles, which is 'cheating' to some degree, I guess. (The limit is usually how noisy your phase measurement is) (To give some intuition, imaging comparing two pendulum clocks. I think you can probably see how if you take a series of pictures of the pendulums next to each other you could gauge whether one of them is running fast relative to the other, and by how much, without one completing one full swing more than the other)

fsh 1y ago

These are optical clocks, so their rates are in the hundreds of THz to PHz range (1.121 PHz in the case of the Al+ clock). A 1e-18 shift corresponds to a ~mHz frequency deviation which a decent frequency counter can resolve in around 1s. However, no optical clock is actually that stable at short time scales, and the averaging is required to get rid of these fluctuations.