Re: Sync two clocks

Liste des GroupesRevenir à sp relativity 
Sujet : Re: Sync two clocks
De : ttt_heg (at) *nospam* web.de (Thomas Heger)
Groupes : sci.physics.relativity
Date : 23. Aug 2024, 06:41:50
Autres entêtes
Message-ID : <liqlo1Fr49eU1@mid.individual.net>
References : 1 2 3 4 5 6 7 8 9
User-Agent : Mozilla Thunderbird
Am Mittwoch000021, 21.08.2024 um 20:42 schrieb Paul.B.Andersen:
Den 20.08.2024 17:12, skrev Richard Hachel:
Le 20/08/2024 à 15:39, Python a écrit :
>
Hachel now pretends that tB − tA = t'A − tB can be true or false
depending on the observer.
>
You are lying.
>
I do not claim it "now". This is what I have always said for at least 40 years.
>
Now, yes, obviously I assume it.
>
The value (tA'-tA) = 2AB/c is the same not only for A and B, but also for all the stationary points of the inertial frame of reference of A and B.
>
Better, if I change frame of reference it will remain true, by invariance of the transverse speed of light in any frame of reference.
>
On the other hand the value tB-tA (go) will vary for most observers in R (where A and B are stationary), as will the value tA'-tB (return).
>
But you cannot understand this, because 1. You are stupid and because 2. because you are tied up with relativistic thoughts all learned, but false.
>
R.H.
 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.
Meant is, that time would not change, if you switch from one frame of reference to another.
But 'own time' (as 'proper time') is actually the only time you would have, because you cannot move in respect to yourself.
But other observers could and usually do.
Now the other observers movement would cause relative movement and that had an impect on what the other observer would regard as your time.
Therefore your time isn't invariant, if observed from somewhere else.

How is it possible to fail to understand this?
 If we have two stationary clocks in an inertial frame,
  and clock A shows tA = t1 when it emits light,
  and clock B shows tB = t1 + td when the light hits it,
  and clock A shows tA'= t1 + 2⋅td when it is hit by the reflected light,
 then tA, tB, tA', t1 and td are all proper times which are frame
independent (invariants) and "the same for all".
   tB − tA = t'A − tB = td
If time is a local phenomenon, you cannot assume, that perceived delay (or 'transit time') would be independent of movement.
Let's take you as 'A' and some other observer 'B' in inertial motion moving away with c/2.
Then the remote observer would see your timing signals shifted down in frequency and would regard your clock as going slow.
Seen from your perspective the same would happen and you would see B's clocks run slow.
Therefore, 'time-stretching' is an apparent effect, caused by relative motion.
To avoid this effect, you would need to compensate delay altogether by measurements and by adding the measured delay to the received time in the timing signal.

The transit time td is a frame independent invariant and
the same in both directions, which means that the clocks according
to Einstein's _definition_ are synchronous in the inertial frame.
 
Whether this is actually true or not is irrelevant here, because you need to compensate the delay somehow. Otherwise you would get a 'mutual time stretching' effect, what cannot be a real physical effect, because it is visible only at the far side by the remote observer.
Since both of these observers are of equal rights, both could claim the other time reading invalid, hence both readings ARE invalid.
Therefore you must compensate the delay 'by hand'.
...
TH

Date Sujet#  Auteur
15 Aug 24 * Sync two clocks154Richard Hachel
15 Aug 24 +- Re: Sync two clocks1Akaike Takashita
16 Aug 24 `* Re: Sync two clocks152Python
16 Aug 24  +* Re: Sync two clocks13Maciej Wozniak
16 Aug 24  i+* Re: Sync two clocks11Python
16 Aug 24  ii+- Re: Sync two clocks1Python
16 Aug 24  ii+* Re: Sync two clocks6Maciej Wozniak
16 Aug 24  iii+* Re: Sync two clocks4Python
16 Aug 24  iiii`* Re: Sync two clocks3Maciej Wozniak
16 Aug 24  iiii `* Re: Sync two clocks2Python
16 Aug 24  iiii  `- Re: Sync two clocks1Maciej Wozniak
16 Aug 24  iii`- Re: Sync two clocks1Richard Hachel
16 Aug 24  ii`* Re: Sync two clocks3Richard Hachel
16 Aug 24  ii `* Re: Sync two clocks2Python
16 Aug 24  ii  `- Re: Sync two clocks1Richard Hachel
16 Aug 24  i`- Re: Sync two clocks1Richard Hachel
16 Aug 24  `* Re: Sync two clocks138Richard Hachel
17 Aug 24   +* Re: Sync two clocks6Mikko
17 Aug 24   i+* Re: Sync two clocks4Richard Hachel
17 Aug 24   ii+* Re: Sync two clocks2gharnagel
17 Aug 24   iii`- Re: Sync two clocks1Python
18 Aug 24   ii`- Re: Sync two clocks1Mikko
17 Aug 24   i`- Re: Sync two clocks1Schepkin Baiguloff
19 Aug 24   `* Re: Sync two clocks131Paul.B.Andersen
19 Aug 24    +- Re: Sync two clocks1Maciej Wozniak
20 Aug 24    +* Re: Sync two clocks66Richard Hachel
20 Aug 24    i+* Re: Sync two clocks10gharnagel
20 Aug 24    ii+- Re: Sync two clocks1Richard Hachel
20 Aug 24    ii+- Re: Sync two clocks1Richard Hachel
20 Aug 24    ii+- Re: Sync two clocks1Richard Hachel
20 Aug 24    ii`* Re: Sync two clocks6Richard Hachel
20 Aug 24    ii `* Re: Sync two clocks5gharnagel
20 Aug 24    ii  +* Re: Sync two clocks3Richard Hachel
20 Aug 24    ii  i`* Re: Sync two clocks2gharnagel
20 Aug 24    ii  i `- Re: Sync two clocks1Richard Hachel
20 Aug 24    ii  `- Re: Sync two clocks1Richard Hachel
20 Aug 24    i+* Re: Sync two clocks52Mikko
20 Aug 24    ii+* Re: Sync two clocks30Richard Hachel
20 Aug 24    iii+* Re: Sync two clocks4Python
20 Aug 24    iiii`* Re: Sync two clocks3Richard Hachel
20 Aug 24    iiii +- Re: Sync two clocks1Python
20 Aug 24    iiii `- Re: Sync two clocks1gharnagel
22 Aug 24    iii`* Re: Sync two clocks25Mikko
22 Aug 24    iii `* Re: Sync two clocks24J. J. Lodder
22 Aug 24    iii  `* Re: Sync two clocks23Python
22 Aug 24    iii   `* Re: Sync two clocks22Richard Hachel
22 Aug 24    iii    `* Re: Sync two clocks21Richard Hachel
22 Aug 24    iii     `* Re: Sync two clocks20Paul.B.Andersen
22 Aug 24    iii      `* Re: Sync two clocks19Richard Hachel
23 Aug 24    iii       `* Re: Sync two clocks18Paul.B.Andersen
23 Aug 24    iii        +* Re: Sync two clocks4Richard Hachel
23 Aug 24    iii        i+- Re: Sync two clocks1Mikko
23 Aug 24    iii        i+- Re: Sync two clocks1Python
23 Aug 24    iii        i`- Re: Sync two clocks1Paul.B.Andersen
23 Aug 24    iii        +* Re: Sync two clocks2Richard Hachel
23 Aug 24    iii        i`- Re: Sync two clocks1Paul.B.Andersen
23 Aug 24    iii        +* Re: Sync two clocks8Richard Hachel
23 Aug 24    iii        i+* Re: Sync two clocks4Python
23 Aug 24    iii        ii`* Re: Sync two clocks3Richard Hachel
23 Aug 24    iii        ii +- Re: Sync two clocks1Paul.B.Andersen
24 Aug 24    iii        ii `- Re: Sync two clocks1Paul.B.Andersen
23 Aug 24    iii        i`* Re: Sync two clocks3Paul.B.Andersen
23 Aug 24    iii        i +- Re: Sync two clocks1Richard Hachel
25 Aug 24    iii        i `- Re: Sync two clocks1Maciej Wozniak
23 Aug 24    iii        +* Re: Sync two clocks2Richard Hachel
23 Aug 24    iii        i`- Re: Sync two clocks1Paul.B.Andersen
23 Aug 24    iii        `- Re: Sync two clocks1Maciej Wozniak
20 Aug 24    ii`* Re: Sync two clocks21Richard Hachel
20 Aug 24    ii +* Re: Sync two clocks19Python
20 Aug 24    ii i`* Re: Sync two clocks18Richard Hachel
20 Aug 24    ii i +* Re: Sync two clocks16Python
20 Aug 24    ii i i`* Re: Sync two clocks15Richard Hachel
20 Aug 24    ii i i +* Re: Sync two clocks13Python
20 Aug 24    ii i i i`* Re: Sync two clocks12Maciej Wozniak
20 Aug 24    ii i i i `* Re: Sync two clocks11Python
20 Aug 24    ii i i i  +* Re: Sync two clocks8Fehmi Bezrukov
21 Aug 24    ii i i i  i`* Re: Sync two clocks7Python
21 Aug 24    ii i i i  i +* Re: Sync two clocks2Athel Cornish-Bowden
21 Aug 24    ii i i i  i i`- Re: Sync two clocks1Python
22 Aug 24    ii i i i  i `* Re: Sync two clocks4Mikko
23 Aug 24    ii i i i  i  `* Re: Sync two clocks3Python
24 Aug 24    ii i i i  i   +- Re: Sync two clocks1Python
24 Aug 24    ii i i i  i   `- Re: Sync two clocks1Mikko
21 Aug 24    ii i i i  `* Re: Sync two clocks2Python
21 Aug 24    ii i i i   `- Re: Sync two clocks1Maciej Wozniak
20 Aug 24    ii i i `- Re: Sync two clocks1Badyaev Pavlinov
22 Aug 24    ii i `- Re: Sync two clocks1Mikko
22 Aug 24    ii `- Re: Sync two clocks1Mikko
20 Aug 24    i`* Re: Sync two clocks3Paul.B.Andersen
20 Aug 24    i `* Re: Sync two clocks2Python
20 Aug 24    i  `- Re: Sync two clocks1Python
20 Aug 24    +* Re: Sync two clocks57Richard Hachel
20 Aug 24    i`* Re: Sync two clocks56Paul.B.Andersen
20 Aug 24    i `* Re: Sync two clocks55Python
20 Aug 24    i  +* Re: Sync two clocks53Richard Hachel
20 Aug 24    i  i+- Re: Sync two clocks1Python
21 Aug 24    i  i+* Re: Sync two clocks50Paul.B.Andersen
21 Aug 24    i  ii+* Re: Sync two clocks10Richard Hachel
22 Aug 24    i  iii+- Re: Sync two clocks1Mikko
22 Aug 24    i  iii`* Re: Sync two clocks8Paul.B.Andersen
22 Aug 24    i  iii `* Re: Sync two clocks7Richard Hachel
22 Aug 24    i  ii+* Re: Sync two clocks18Thomas Heger
23 Aug 24    i  ii`* Re: Sync two clocks21Thomas Heger
22 Aug 24    i  i`- Re: Sync two clocks1Mikko
22 Aug 24    i  `- Re: Sync two clocks1Mikko
20 Aug 24    +* Re: Sync two clocks3Thomas Heger
20 Aug 24    `* Re: Sync two clocks3Hanoi Bagdasaroff

Haut de la page

Les messages affichés proviennent d'usenet.

NewsPortal