XPost: sci.physics.relativity   
   From: ttt_heg@web.de   
      
   Am Samstag000013, 13.09.2025 um 10:45 schrieb Python:   
   > Le 13/09/2025 à 08:29, Thomas Heger a écrit :   
   >> Am Freitag000012, 12.09.2025 um 07:56 schrieb Python:   
   >> ...   
   >>>>> Your "analyze" of Einstein's text is an abysmal failure, a complete   
   >>>>> bunch of nonsense from start to finish.   
   >>>>>> For instance I had taken 'The Galactic Black Hole' and analyzed that.   
   >>>>   
   >>>> I made an English version called 'Annotated version of SRT'.   
   >>>>   
   >>>> It was a pdf of the English translation of Einstein's paper 'On the   
   >>>> electrodynamics of moving bodies'.   
   >>>>   
   >>>> Then I marked every questionable statement with the annotation   
   >>>> function of that pdf software and wrote a comment, why that was in   
   >>>> my view a questionable statement (and whether or not that was an   
   >>>> error).   
   >>>>   
   >>>> I wrote more than 420 annotations.   
   >>>>   
   >>>> This actually means: the text contains a colossal number of errors   
   >>>> of all kinds.   
   >>>>   
   >>>> About those comments I had several discussions in this group of the   
   >>>> UseNet in a period of about two years.   
   >>>>   
   >>>> The comments helped me a lot to clarify my own statements and   
   >>>> rethink a number of comments.   
   >>>>   
   >>>> But the total number of annotation was only reduced insignificantly   
   >>>> in this process.   
   >>>>   
   >>>> The vast majority remained unchallenged.   
   >>>>   
   >>>> That means: there are a HUGE number of errors in this text, where   
   >>>> the text itself could not be defended against critique.   
   >>>>   
   >>>> This in turn would qualify Einstein's text as among the worst   
   >>>> articles ever printed in a scientific journal.   
   >>>   
   >>> 100% of your "comments" are idiotic garbage. You failed at   
   >>> understanding the most obvious basic statements.   
   >>>   
   >>> Especially about synchronization of clocks. Remember?   
   >>   
   >> No, not at all.   
   >   
   > Are you kidding ? It was a few days ago !   
   >   
   > See:   
   >   
   > Le 04/09/2025 à 17:40, Python a écrit :   
   >> Le 02/09/2025 à 12:28, Python a écrit :   
   >>> Le 02/09/2025 à 11:39, Python a écrit :   
   >>>> Le 01/09/2025 à 08:23, Thomas Heger a écrit :   
   >>>> ...   
   >>>>> station 'A' is located in Houston, Texas and station 'B' upon the   
   >>>>> Moon.   
   >>>>>   
   >>>>> A-time is usual Texas-time and 'B-time' was named 'Moon mean time'.   
   >>>>>   
   >>>>> Now we have a huge clock on the Moon and also an 'Apollo' crew to   
   >>>>> maintain the clock there.   
   >>>>   
   >>>> No reason for this clock to be huge.   
   >>>>   
   >>>>> You wrote, that a number of methods would be possible by which   
   >>>>> Houston could be informed about t_B, which included also letters   
   >>>>> sent by mail.   
   >>>>>   
   >>>>> And I have written, that you should explain to me, what a letter   
   >>>>> with the time 'it's now 13:00:00 Moon mean time' arriving one week   
   >>>>> later would say.   
   >>>>>   
   >>>>> But you are in fact correct and t_B was defined as time of arrival   
   >>>>> of the signal in B, which was the meaning of t_B.   
   >>>>>   
   >>>>> Therefore the letter from the Moon should contain the message '   
   >>>>> your signal arrived here at 13:00:00 Moon mean time'.   
   >>>>>   
   >>>>> Now: how do you synchronize the clock on the Moon with that   
   >>>>> information?   
   >>>>   
   >>>> The message is sent to A in your scenario, so it is the clock on   
   >>>> Earth that could be synchronized, by applying a computed offset,   
   >>>> with clock B.   
   >>>>   
   >>>> In order to do so A also need to uses t_A and t'_A. As both are   
   >>>> values that have been read on clock A before, there is no   
   >>>> communication issues here. Right?   
   >>>>   
   >>>> Let's suppose that these values are:   
   >>>>   
   >>>> t_A = 12:30:00   
   >>>> t'_A = 11:30:2.56444   
   >>>   
   >>> Typo: t_A  = 12:30:00   
   >>> t'_A = 12:30:2.56444   
   >>>   
   >>>   
   >>>> t_B = 13:00:00   
   >>>>   
   >>>> A few questions now:   
   >>>> 1. Can you check if 2*d/(tpA - tA) = c [d is the Earth-Moon distance] ?   
   >>>> 2. Can you check if t_B - t_A = t'_A - t_B ? What does this means in   
   >>>> term of clocks synchronization according to Einstein?   
   >>>> 3. Can you compute an offset to be applied to clock A so that clocks   
   >>>> A & B will be, then, synchronized?   
   >>   
   >> No answer? How weird...   
   >   
   >   
   >   
   >> I have criticized Einstein's method, because Einstein didn't mention   
   >> any means to correct the error caused by the finite speed of light and   
   >> the resulting delay.   
   >   
   > It is not an "error", it is what it is. And Einstein take this (what you   
   > call "delay") into account in this explicit equation :  t_B - t_A = t'_A   
   > - t_B   
      
   This is the delay, but only under certain conditions.   
      
   Main requirements: A and B should not move in respect to each other and   
   the speed of light on the way had always to be the same.   
      
   But there ain't no variables for delay (like e.g. 'd') in Einstein's text.   
      
   What was also missing, that is a connection between delay and clock-setting.   
      
   The correct method would be to adjust the remote clock to a timing   
   signal, which is already corrected by the estimated delay.   
      
   E.g. a position on the Moon shall be exactly 1 light-seconds away and a   
   clock there should become synchronized with a master clock in Houston.   
      
   Houston would send a timing signal to the Moon at say 1:00:00 pm, but   
   with the content 1:00:01 pm.   
      
   The man in the Moon reads out this signal and turns the knob, that the   
   Moon clock is set according to that signal from Houston.   
      
   Since Einstein didn't mention this method or anything similar or even   
   the delay itself, we can only assume, that he didn't want.   
      
   TH   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)