Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: "Paul.B.Andersen" Newsgroups: sci.physics.relativity Subject: Re: The problem of relativistic synchronisation Date: Mon, 2 Sep 2024 19:24:58 +0200 Organization: A noiseless patient Spider Lines: 42 Message-ID: References: <2VJMHmUL3oTjzHTxkbHeeVgwp1A@jntp> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Injection-Date: Mon, 02 Sep 2024 19:23:40 +0200 (CEST) Injection-Info: dont-email.me; posting-host="dcec4cda9125e37d18460db61bdf902b"; logging-data="3081267"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/a84vzoD4oIZNLuiBILTyx" User-Agent: Mozilla Thunderbird Cancel-Lock: sha1:mu5i4w9lpqpcKPnnUhnGb94ICT8= In-Reply-To: Content-Language: en-GB Bytes: 2431 Den 02.09.2024 01:39, skrev Python: > Le 01/09/2024 à 22:29, M.D. Richard "Hachel" Lengrand a écrit : >> tA (e1)= 0 > > If you insist, but this in no way a requisite of Einstein-Poincaré's > synchronization procedure. t_A = 451 is another possible value :-) > >> tA'(e1)= 0 > > LOL!!! Whaaat the Hell is that??? > >> tA (e2)= 0.75 > > Irrelevant. The time marked by clock A "when" B received the first > signal is undefined at that time (i.e. "when" is undefined for remote > events). It does play any role in the procedure. Fortunately. > You are misunderstanding. Richard never quote what he is responding to, so the context is lost. This is not about Einstein's synchronisation method, but about this paper: https://paulba.no/pdf/Mutual_time_dilation.pdf tA(e1) = 0 tA'(e1)= 0 by definition With Richards (unrealistic as always) numbers: c ≈ 3e8 m/s d = 3e8 m v = 0.8c tA(e2) = (d/v)⋅√(1−v²/c²) ≈ 0.75 seconds -- Paul https://paulba.no/