Sujet : Re: Why a time of the real world must be galilean
De : jpierre.messager (at) *nospam* gmail.com (Python)
Groupes : sci.physics.relativityDate : 08. Dec 2024, 17:40:58
Autres entêtes
Organisation : Nemoweb
Message-ID : <Wwh1p3Iqx8dwLkBIzFkBJuIT330@jntp>
References : 1
User-Agent : Nemo/1.0
Le 08/12/2024 à 04:56, Maciej Wozniak a écrit :
Time is what clocks indicate, and we need clocks
to be synchronized (i.e. indicating t'=t).
Yes, that's that simple.
No it is not that simple. To begin with every clock show a
lot of different values t (and t' for another clock, t'' for
a third one, and so on). So static t'=t without any reference
to what's happening at that clocks when they are showing such
or such value is meaningless (as allmost all of your rants, btw).
Could you show us your talent as an "information engineer" ?
Let two separated clocks A and B, as identical as possible,
being initially set at a arbitrary value when they left the
factory before being moved to position A and B.
How to *practically* check if they are synchronized or not? How to compute the offset(s) to apply in order to insure that
they are in synch?
it's a practical directive for the clock makers.
Sure. This is why I asked you about a practical procedure.