Sujet : Re: Sync two clocks
De : python (at) *nospam* invalid.org (Python)
Groupes : sci.physics.relativityDate : 25. Aug 2024, 08:44:55
Autres entêtes
Organisation : CCCP
Message-ID : <vaendn$1q24g$6@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10 11
User-Agent : Mozilla Thunderbird
Le 24/08/2024 à 13:47, Richard "Hachel" Lengrand a écrit :
Le 24/08/2024 à 12:08, "Paul.B.Andersen" a écrit :
Den 23.08.2024 13:30, skrev Richard Hachel:
Le 23/08/2024 à 10:55, Mikko a écrit :
On 2024-08-23 05:41:50 +0000, Thomas Heger said:
>
Am Mittwoch000021, 21.08.2024 um 20:42 schrieb Paul.B.Andersen:
>
Richard, read your watch NOW. Write down the time nn:nn:nn.
The time nn:nn:nn is a proper time (read off a clock), it is
invariant, not depending on frame of reference.
>
Nobody can have another opinion of what time YOU read of YOUR watch.
>
This is not, what 'invariant' means in the context of relativity.
>
Yes, it is.
>
Meant is, that time would not change, if you switch from one frame of reference to another.
>
No, it means that whatever is called "invariant" is the same for all
frames. In the current case, the number wirtten on the paper is invariant.
>
Mikko
>
Here is yet another proof of what I am saying, and of the need to re-explain things correctly.
>
Do you mean that the fact that Tomas Heger doesn't know what
"invariant" means, is a proof of the need to re-explain
my statement correctly?
>
My statement was:
" Richard, read your watch NOW. Write down the time nn:nn:nn.
The time nn:nn:nn is a proper time (read off a clock), it is
invariant, not depending on frame of reference.
Nobody can have another opinion of what time YOU read of YOUR watch."
>
Both "proper time" and "invariant" are explained in the text.
>
Exactly what do you not understand?
What is needed to be re-explained correctly?
What you say is quite obvious, and that is not the problem.
We all say, even the buffoon Python, that when the event e1 occurs (A beeps), A starts his watch.
At A, we note tA(e1)=0
There is nothing like "starts his watch" and "set to 0" in Einstein's
procedure.
This is something you've made up, in an Hegerian way.
e2 is the capture of the beep by B...
e3 is the event that characterizes the return of the signal to A.
We note tA(e3)=2
We know that AB=3.10^8m/s
This leads to tA(e3)-tA(e1)=2AB/c
You are putting the horses before the car.
Time of events can only be valid when clock have been synchronized.
The synchronization procedure allow to compute an offset that has
to be applied to B or A in order for clocks to be synchronized.
THEN, you can apply this offset to the values you've written down
during synchronization phases in order to attribute a time (in the
rest frame of the clocks) for these events.
That's what I say, and I see with sadness (don't laugh friends), that my intelligence seems to surpass the entire scientific community, and that for having taken, what I say is distorted.
Nothing has be be distorted in order to prove that your claims are
absolutely nonsensical and contradictory.