• Tavi
    link
    fedilink
    English
    arrow-up
    2
    ·
    5 months ago

    Well, moving them is out of the question, since, you know, motion will change the clocks time. If you re-sync them, you bake the “error” into your framework. If you try a timer, the timer is offset. If you try and propagate a signal, the signal is offset. And eventually, you have to compare the two times, which muddies the waters by introducing a third clock.

    Basically, there is no way to sync two clocks without checking both clocks, ergo, no way of proving or disproving. That’s the premise.

    In practicality, I assume it is constant, but it’s like N=NP. You can’t prove it within the framework, even if you really, really want to believe one thing.

    • Richard@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      5 months ago

      If you move one clock very slowly away from the other, the error is minimised, perhaps even to a degree that allows for statistically significant measurements.

      To cite the Wikipedia entry that one of the other commenters linked:

      “The clocks can remain synchronized to an arbitrary accuracy by moving them sufficiently slowly. If it is taken that, if moved slowly, the clocks remain synchronized at all times, even when separated, this method can be used to synchronize two spatially separated clocks.”

      One-Way Speed of Light

      • InnerScientist@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        And further down:

        Unfortunately, if the one-way speed of light is anisotropic, the correct time dilation factor becomes {isplaystyle {athcal {T}}={rac {1}{amma (1-appa v/c)}}}, with the anisotropy parameter κ between -1 and +1.[17] This introduces a new linear term, {isplaystyle im {eta o 0}{athcal {T}}=1+appa eta +O(eta ^{2})} (here {isplaystyle eta =v/c}), meaning time dilation can no longer be ignored at small velocities, and slow clock-transport will fail to detect this anisotropy. Thus it is equivalent to Einstein synchronization.

        • Richard@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          Yes, I understand that part, but it doesn’t disprove that such an experiment could show isotropy. Instead, it says that it would always indicate isotropy, which is not entirely useful either, of course. I’ll dig deeper into the publication behind that section when I have the time. Nonetheless, my original point still stands. With a highly synchronised clock, you could measure the (an)isotropy of the one-way speed of light. To determine whether the time dilation issue is surmountable I’ll have to look at the actual research behind it.

      • hikaru755@feddit.de
        link
        fedilink
        English
        arrow-up
        1
        ·
        5 months ago

        Except if you continue reading beyond your Quote, it goes on to explain why that actually doesn’t help.

        • Richard@lemmy.world
          link
          fedilink
          English
          arrow-up
          1
          ·
          5 months ago

          That the measurements from the slow clock transport synchronisation method are equivalent to the Einstein synchronisation and its isotropic speed of light can be interpreted to show that the one-way speed of light is indeed isotropic for a given set-up and not anisotropic. The problem with this is that anisotropy could not even be measured if it were to exist in this context. But this is definitely not a clear-cut zero sum game, there’s no evidence suggesting anisotropy while there are observations that would at least suggest isotropy, but neither possibility can be ruled out. However, my initial point was that, could you have ultra-synchronised clocks, you could potentially be able to draw a reliable conclusion. But I’ll dig into the publication the Wiki entry cites for the time dilation part in the slow clock section when I have the time.