Re: Sync two clocks

Liste des GroupesRevenir à sp relativity 
Sujet : Re: Sync two clocks
De : r.hachel (at) *nospam* jesauspu.fr (Richard Hachel)
Groupes : sci.physics.relativity
Date : 16. Aug 2024, 13:24:33
Autres entêtes
Organisation : Nemoweb
Message-ID : <vPP1Z1BJfE1Dt7SYhCzEo7ZQWFI@jntp>
References : 1 2
User-Agent : Nemo/0.999a
Le 16/08/2024 à 12:47, Python a écrit :
If the meaning of t_A, t_B, and t'_A are still unknown to you, you can
refer to Einstein 1905 article.
 t_A is the time shown by clock A when a light signal is emitted;
 t_B is the time shown by clock B when the signal is received and re-emitted;
 t'_A is the time shown by clock A when the returned signal is received.
Here's the clown continuing.
If we look closely, what he says seems sensible.
This is why all of humanity is wrong about the theory of special relativity as taught.
Because the more we rub our eyes, the more sensible it seems.
Except that... breathe, blow...
That clock A notes a time t1 when the signal leaves A (we don't care about the value by the way,
it could be t1=0 or it could be t1=153), I'm willing.
We place B at 3.10^8m, and time is measured in seconds.
That clock A notes a time t2 when the signal returns, I'm willing again, and as Jean-Pierre
Messager says (sometimes he says intelligent things, although it's rare), I'm going to say that t2=2 or that t2=155.
How will Jean-Pierre achieve this prophetic feat?
Let's not get carried away, I know how to do it too.
Here's how I do it, breathe, blow.
t2 = t1 + 2AB/c
And this is so true that it applies to the entire universe, and all inertial frames of reference.
But unlike Jean-Pierre, Henri or Albert, I'll stop here.
Because this is where the vast ocean of relativistic science begins.
What time is it in B when B receives the information? I don't know at all,
and first of all, depending on how I synchronized B, it could be t=4532 or t=-12.
So I don't know at all.
Jean-Pierre is intelligent enough to understand that it is therefore necessary to first synchronize B with A,
to have something coherent, because saying that tA=0 tB=4532 and tA'=2 is always feasible, we are not lying, but it is very unhelpful.
Except that Jean-Pierre still has not understood Hachel's thinking, and he remains in the hypothesis of a flat present (the horizontal plane of the present time), as others remain in the hypothesis of the flat earth.
Nature is not made like that, that's not how it works.
So what time is it in B?
Jean-Pierre does not bother with embellishments: "We only have to artificially set tB=(t2-t1)/2 and thus, everything will be very simple and very practical".
Except that it is an artificial synchronization.
And except that it will not be true for A, nor for B.
It will only be true for M, a point placed at an equal distance from A and B, and the synchronization will be called M synchronization.
Because in the universe of A, this M synchronization is completely false, everything that is part of the "3D present time" of M is not part, and we are infinitely far from it, of the present time of A, and ditto for B.
Each chosen point, A, B, or M have the same 3D inertial frame, but they are not part of the same 4D frame, and each can only have its own (because of anisochrony, and the fourth component t).
The synchronization of Einstein, Poincaré, physicists, is therefore only an abstract synchronization,
which represents a point M, placed very far perpendicularly, in an imaginary fourth dimension,
and which apprehends all the points of the 3D universe at the same distance and at the same present moment of M.
It is obviously totally imaginary, but it is very useful.
For this point, indeed, we can say that tB=(t2-t1)/2 but it is a convention M.
For A as for B, it is absolutely impossible to synchronize these two watches between them FOR them.
As it is also impossible to synchronize A or B with the imaginary point M.
Always, always, always, there will remain a universal anisochrony.
And always, always, always, in the reality of things, if we have practiced a synchronization M:
FOR A:
tB-t1=2AB/c
t2-tB=0
FOR B:
tB-t1=0
t2-tB=2AB/c
I don't know if it will take Lengruche four years to understand that (a+b)(a-b)=a²-b²
but it is certain that in 30 years Ybmuche will still not have understood what I have just detailed here.
R.H.

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