• Re: Conflicts in SR when using horizontal light clocks in the moving fr

    From Tom Roberts@21:1/5 to Richard Hertz on Wed Nov 8 17:12:00 2023
    On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.

    These clocks are at rest in different inertial frames, and thus cannot
    be synchronized with each other.

    Tom Roberts

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Tom Roberts@21:1/5 to Richard Hertz on Wed Nov 8 18:23:58 2023
    On 11/8/23 5:43 PM, Richard Hertz wrote:
    On Wednesday, November 8, 2023 at 8:12:14 PM UTC-3, Tom Roberts
    wrote:
    On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.
    These clocks are at rest in different inertial frames, and thus
    cannot be synchronized with each other.

    I clearly wrote that tK and tA are synchronized as Einstein claimed
    in his 1905 paper:

    You can write whatever you want; that does not make whatever you wrote
    correct or possible. It is PHYSICALLY IMPOSSIBLE to synchronize clocks
    that are at rest in different inertial frames [#], and Einstein NEVER
    described what you wrote as "synchronization".

    [#] The GPS synchronizes satellite clocks in ECI coordinates;
    while they are called "clocks", they are NOT standard clocks,
    and are not at rest in inertial frames (SR). Moreover, earth's
    gravitation is an essential aspect of this, required to keep
    them in orbit, which is not possible in SR.

    Note: you may set clocks tK and tA to the same value when they pass each
    other, but that does NOT synchronize them with each other, and that is
    NOT how Einstein synchronized clocks in his 1905 paper (or anywhere
    else). Only clocks at rest in a single inertial frame can be mutually synchronized, and Einstein's methods EXPLICITLY require this.

    You REALLY need to understand SR before attempting to write about it, or criticize it.

    Tom Roberts

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Tom Roberts on Wed Nov 8 20:00:35 2023
    On Wednesday, November 8, 2023 at 9:24:12 PM UTC-3, Tom Roberts wrote:
    On 11/8/23 5:43 PM, Richard Hertz wrote:
    On Wednesday, November 8, 2023 at 8:12:14 PM UTC-3, Tom Roberts
    wrote:
    On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.
    These clocks are at rest in different inertial frames, and thus
    cannot be synchronized with each other.

    I clearly wrote that tK and tA are synchronized as Einstein claimed
    in his 1905 paper:
    You can write whatever you want; that does not make whatever you wrote correct or possible. It is PHYSICALLY IMPOSSIBLE to synchronize clocks
    that are at rest in different inertial frames [#], and Einstein NEVER described what you wrote as "synchronization".

    [#] The GPS synchronizes satellite clocks in ECI coordinates;
    while they are called "clocks", they are NOT standard clocks,
    and are not at rest in inertial frames (SR). Moreover, earth's
    gravitation is an essential aspect of this, required to keep
    them in orbit, which is not possible in SR.

    Note: you may set clocks tK and tA to the same value when they pass each other, but that does NOT synchronize them with each other, and that is
    NOT how Einstein synchronized clocks in his 1905 paper (or anywhere
    else). Only clocks at rest in a single inertial frame can be mutually synchronized, and Einstein's methods EXPLICITLY require this.

    You REALLY need to understand SR before attempting to write about it, or criticize it.

    Tom Roberts

    I understand what is meant as SR, and reject it all for being fallacious and derived from preemptive circular thoughts. A pseudoscience.

    You may keep thinking that the 2,409 words written in the first part of the 1905 paper:

    Introduction
    § 1. Definition of Simultaneity
    § 2. On the Relativity of Lengths and Times
    § 3. Theory of the Transformation of Co-ordinates and Times from a Stationary System to another System in Uniform Motion
    of Translation Relatively to the Former (first 4 paragraphs)

    have a mystical meaning that only can be deciphered by a few chosen, illuminated people.

    You need to think that way, so you may feel "special".

    But the reality is that those 2,409 initial words are anything but mystical and that if they are REDUCED to 600 words by filtering the extra wording,
    done on purpose to retort, confuse and distort their meaning, a VERY SIMPLE description of the opening of the paper EMERGES.

    In particular, the clock's synchronization in the two frames is done by EQUATING their readings when selected points instantaneously coincide
    in the horizontal x position. This is EXACTLY the same as to say: "when x = x' = 0, then set t = t' = 0".

    If you negate the above paragraph, you are acting deceivingly to hide the simple truth embedded into these initial 2,409 words.

    This is how FANATICS act about their credence, even when the evidence is spitting at their face.

    I think that this is due to your current stance within SR/GR and the four-x "parameters", which caused that you LOST THE TRACK from the origin,
    which is the paper published in Sep 1905.

    Go back to the beginning, and re-read and simplify the wording, in the initial parts, as I marked above.

    Then, come back and try again to refute my post.

    The "word of god" is not contained in such small amount of bla-bla-bla, as you pretend or NEED to believe.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volney@21:1/5 to Richard Hertz on Thu Nov 9 00:51:42 2023
    On 11/8/2023 6:43 PM, Richard Hertz wrote:
    On Wednesday, November 8, 2023 at 8:12:14 PM UTC-3, Tom Roberts wrote:
    On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.

    These clocks are at rest in different inertial frames, and thus cannot
    be synchronized with each other.

    Tom Roberts

    I clearly wrote that tK and tA are synchronized as Einstein claimed in his 1905 paper:

    When A (at origin of K') passes BY THE ORIGIN of K, tA = tK = 0, exactly BEFORE the photon is emitted from A to B.

    That's not Einstein synchronization. Einstein synchronization is for two objects not located at the same point but stationary relative to each
    other. (so it's impossible to set t=t'=0 since x is never equal to x'
    (so x=x'=0 never happens).

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Volney on Wed Nov 8 22:02:44 2023
    On Thursday, November 9, 2023 at 2:52:15 AM UTC-3, Volney wrote:
    On 11/8/2023 6:43 PM, Richard Hertz wrote:
    On Wednesday, November 8, 2023 at 8:12:14 PM UTC-3, Tom Roberts wrote:
    On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.

    These clocks are at rest in different inertial frames, and thus cannot
    be synchronized with each other.

    Tom Roberts

    I clearly wrote that tK and tA are synchronized as Einstein claimed in his 1905 paper:

    When A (at origin of K') passes BY THE ORIGIN of K, tA = tK = 0, exactly BEFORE the photon is emitted from A to B.

    That's not Einstein synchronization. Einstein synchronization is for two objects not located at the same point but stationary relative to each
    other. (so it's impossible to set t=t'=0 since x is never equal to x'
    (so x=x'=0 never happens).

    K' origin is moving from - infinity towards + infinity, at 0.9c.

    When A pass by K origin, light signaling is used to set tK = tA = 0.

    You forgot that K' frame is moving at 0.9c relative to K frame. Why do you dismiss the positions in the negative axis? Is that the drawing of
    galilean transform is stuck into your brain, as it's commonly shown for x > 0?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Tom Roberts on Wed Nov 8 23:19:19 2023
    On Thursday, 9 November 2023 at 01:24:12 UTC+1, Tom Roberts wrote:
    On 11/8/23 5:43 PM, Richard Hertz wrote:
    On Wednesday, November 8, 2023 at 8:12:14 PM UTC-3, Tom Roberts
    wrote:
    On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.
    These clocks are at rest in different inertial frames, and thus
    cannot be synchronized with each other.

    I clearly wrote that tK and tA are synchronized as Einstein claimed
    in his 1905 paper:
    You can write whatever you want; that does not make whatever you wrote correct or possible. It is PHYSICALLY IMPOSSIBLE to synchronize clocks
    that are at rest in different inertial frames

    What is PHYSICALLY IMPOSSIBLE for your bunch of idiots
    was just a task of medium difficulty for the professionals
    of GPS.
    Many things would become possible also for you - if you ever
    understood you're not at all FORCED to THE BEST WAY of your
    idiot guru.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Thu Nov 9 06:43:35 2023
    On Wednesday, November 8, 2023 at 11:24:18 PM UTC-5, Richard Hertz wrote:

    My description is quite simple:

    1) Mount an artifact with two mirrors located at A and B. Let it move (being a moving frame K' with origin in A) at uniform speed v =0.9c.
    2) When the point A in the moving frame K' happens to be (for an infinitesimal amount of time) coincident with the
    origin of frame K (at relative rest) then set both clocks (tK at frame K origin and tA at frame K' origin) to zero.
    This is the same as of saying that when x = x' = 0, then make t = t' = 0.

    Then just say "when x = x' = 0, then make t = t' = 0".
    The rest of your paragraph is unnecessary. Be concise and remove all unnecessary stuff.

    3) Being that tK and tA are counting 1.0000000 μs ticks,
    ...

    classic physics said

    What I ate for breakfast is irrelevant to the scenario. Stay on topic.

    SR says that, while tK shows a TRUE COUNT of 1.0000000 μs ticks,

    No, SR does not say that. Nowhere in SR is there any mention of 'TRUE'.
    Thats a made up word by you and is unnecessary to the discussion.

    The setup is that all clocks will gradually display 0,1,2,3... (μs). No SR, no classical physics involved in that.

    any observer standing by tK will PERCEIVE that tA accumulates ticks at a higher rate.

    Again 'PERCEIVE ' is not part of the vocabulary (and less so in SR). Stop inserting random undefined words into the setup.
    This can also be said for the superfluous word 'rate'. Try to refrain from using those useless and ill defined concepts. Keep it clear and concise.

    BUT, any observer moving with frame K' (standing by the clock tA) will say that the
    accumulation of ticks keep going at 1.0000000 μs/tick.

    As implicitly posited by the setup, as I already mentioned, all clocks will gradually display 0,1,2,3... (μs).
    The difference between two successive values is 1.

    The best way to show the incoherence of SR is that the readings in the moving frame use digital counters

    Need not be digital... but lets go on...

    AND A GIANT DISPLAYS pointing at the origin of K,

    No need of giant displays, nor pointing in some direction.
    Observers, which is synonym to 'logging device', just logs, notes, its value as an event occurs at it.
    For instance, when tK & A coincide, the logged values of the devices 'clocks' are t=0 & t'=0 and
    the values of the devices 'rulers' are x=0 & x'=0.

    so the REAL COUNT

    'REAL COUNT'? Again, a made up and undefined expression by you, and unnecessary to the discussion.
    The device 'clock A' logs the value 0 as it coincides with tK. The words 'real' or 'apparent' will not change that, agreed?

    at K' could be observed from the origin of K (using a telescope, if needed in this thought experiment).

    K' can count how many photons he will *receive* from A (from the giant display).
    K' will receive 1 photon, then another, then another etc.
    These received photons will have the values 1,2,3,... (μs).
    Lets call these photons, photon #1, photon #2 etc... or just p1, p2, ....
    IOW, clock A sends out p1,p2,p3 as it logs 1,2,3... μs. eventually, tK will receive these p1,p2,p3...

    Nothing contradictory here!


    By moving to the DIGITAL DOMAIN in K', all the equations of SR COLLAPSE,

    How so? Digital or not, clock A will go through the values 0,1,2,3 (μs) and send out p1,p2,p3 for everyone to eventually receive.

    because the analog math of SR is KILLED by digitalization.

    The math of SR is indiscriminate to the nature of the clocks.
    They can be digital or not; the same math will be used, x' = (x-vt)γ.

    So, the observer at relative rest in the origin of K FACES A DILEMMA: Because of
    Lorentz, he PERCEIVES A FALLACIOUS TIME at tA,

    No, tK will *receive* p1, p2 p3.... as posited by the setup.
    The values displayed by these photons are 1,2,3,...(μs) as posited by the setup.
    And 'he PERCEIVES A FALLACIOUS TIME at tA' is impossible because he [tK] is not at tA.
    He [tK] receives the photons. He [tK] knows that tA will go through (tA will log) the values of 1,2,3 ...because
    it is posited by the setup.

    Nowhere in all the above has there been any use of SR.
    Everything you (and I) said above was devoid of SR. Its all describing the setup.

    which is in absolute conflict with the remote reading of the DIGITAL DISPLAY located at A, moving at 0.9c.

    The fact that clock A goes through the values 0,1,2,3... is not in conflict with anything.
    The fact that clock A sends out the corresponding photons is not in conflict with anything.
    The fact that clock K [tK] receives these photons (images) is not in conflict with anything.


    How do you assist, psychologically, to the observer at K origin, to avoid that he become crazy?

    How does my above 3 sentences make him crazy?

    His PERCEPTION crashes with his observation of the display.

    He receives successive photons. How does that boggle his mind & perceptions ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to All on Thu Nov 9 07:33:33 2023
    Observers, which is synonym to 'logging device'

    Where did you get this absurd, poor idiot?
    Right from your wishing, I bet.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volney@21:1/5 to Richard Hertz on Thu Nov 9 11:50:51 2023
    On 11/9/2023 1:02 AM, Richard Hertz wrote:
    On Thursday, November 9, 2023 at 2:52:15 AM UTC-3, Volney wrote:
    On 11/8/2023 6:43 PM, Richard Hertz wrote:
    On Wednesday, November 8, 2023 at 8:12:14 PM UTC-3, Tom Roberts wrote: >>>> On 11/8/23 3:56 PM, Richard Hertz wrote:
    [...] Then, tK and tA are synchronized in the einstenian way.

    These clocks are at rest in different inertial frames, and thus cannot >>>> be synchronized with each other.

    Tom Roberts

    I clearly wrote that tK and tA are synchronized as Einstein claimed in his 1905 paper:

    When A (at origin of K') passes BY THE ORIGIN of K, tA = tK = 0, exactly BEFORE the photon is emitted from A to B.

    That's not Einstein synchronization. Einstein synchronization is for two
    objects not located at the same point but stationary relative to each
    other. (so it's impossible to set t=t'=0 since x is never equal to x'
    (so x=x'=0 never happens).

    K' origin is moving from - infinity towards + infinity, at 0.9c.

    When A pass by K origin, light signaling is used to set tK = tA = 0.

    Fine. But that's not Einstein clock synchronizing. Einstein
    synchronizing is getting two stationary but separated clocks to display
    the same time. What you are doing is just pressing the "start" buttons
    on stopwatches.

    [snip crap]

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Thu Nov 9 21:20:34 2023
    Den 08.11.2023 22:56, skrev Richard Hertz:
    c = 299792458 m/s = 299.792458 m/μs

    Two perfect mirrors (A,B) are placed 149,896229 m apart, being A at the origin of the relatively moving frame K'.

    A photon, in the visible light range, is emitted from the mirror A (which also contains a clock) exactly towards mirror B.

    The photon bounces back at mirror B, towards mirror A. Its arrival from the roundtrip is marked in tA clock as being exactly 1.0000000 μs.

    This process continues forever, without any losses, while A clock is accumulating 1.0000000 μs counts.

    OK!


    The arrangement in K' moves at v speed wrt the origin at K, where a clock tK is located (it also ticks at 1.0000000 μs.

    Both clocks (tK and tA) are reset to zero exactly when A pass by the origin K, and it forces the emission of the photon.

    OK!


    Then, tK and tA are synchronized in the einstenian way.

    No, this has noting to do with Einstein's way of synchronizing
    clocks in inertial frames.

    Two clocks are set equal (to zero) when they pass each other,
    that's all.
    We will also assume that both clocks are placed at the origin of
    their respective rest frames.

    We then have:

    K':-tA------B-------->x'->v
    K :-tK--------------->x


    The speed v = 0.9 c = 269813212 m/s

    WHAT SR (LORENTZ) SAYS THAT HAPPENS AFTERWARDS.
    γ = 2.294157339

    In the following we will use L as the distance
    between the mirrors. We can put in numbers later.

    To find what SR says, we use the Lorentz transform.
    We have three event of interest.

    E0: tA and tK are aligned and the photon is emitted from A.
    E1: the photon is reflected from B.
    E2: the photon is reflected from A

    Let's find the coordinates of these event's in K and K':

    γ = 1/√(1 −v²/c²) = 2.294157339 when v = 0.9c

    EO:
    Coordinates in K': x₀' = 0, t₀' = 0
    Coordinates in K: x₀ = 0, t₀ = 0

    E1: (this event could be skipped)
    Coordinates in K': x₁' = L, t₁' = L/c
    Coordinates in K:
    x₁ = γ(x₁'+ v⋅t₁')=γ(L+ v⋅L/c) = L⋅√((c+v)/(c-v))
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L/c + (v/c²)⋅L) = (L/c)⋅√((c+v)/(c-v))

    E2:
    Coordinates in K': x₂' = 0, t₂' = 2L/c
    Coordinates in K:
    x₂ = γ(x₂'+ v⋅t₁') = γ(0 + v⋅2L/c) = (2Lv/c)/√(1 −v²/c²)
    t₂ = γ(t₂'+ (v/c²)⋅x₂') = γ(L/c + (v/c²)⋅L) = (2L/c)/√(1 −v²/c²)

    So while the moving clock tA has advanced the proper time
    t₂' = 2L/c = 1 μs ,
    the coordinate time in the stationary frame has advanced
    t₂ (2L/c)/√(1 −v²/c²) = 2.294157339 μs

    t₂'/t₂ = √(1 −v²/c²) = 0.435889894

    "Moving clocks run slow"


    LENGTH CONTRACTION (Horizontal light clock is perceived to run faster) http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c1

    x' = γ (x - vt)

    Δx' = AB AND Δx = AB/γ = 0.435889894 AB, as measured in the frame at rest. As both measurements are made simultaneously in the frame at rest, there is A PERCEIVED LENGTH CONTRACTION of AB in the moving frame.
    But the speed of light IS INVARIANT wrt to any frame, so IT'S PERCEIVED that clock tA IS RUNNING FASTER.

    The roundtrip of the photon is PERCEIVED to travel 2 x 0.435889894 AB = 0.871779789 x AB, which means that the clock's tick in the moving frame IS PERCEIVED TO TICK every 0.871779789 μs, instead of 1.00000000 μs.

    TIME DILATION (Horizontal light clock is perceived to run slower) http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c2

    t' = γ (t - vx/c)

    Δt' = Δt/γ = 0.435889894 Δt (Time is PERCEIVED as running slower in the moving frame).

    For every 1.00000000 μs in the frame at rest, it's PERCEIVED that only 0.435889894 μs passed in the moving frame.

    The time measurements are made in the same location, so it doesn't affect the results.

    CONCLUSION: Using an horizontal light clock, the results of TIME FLOW due to length contraction and time dilation are in conflict. Clock tA is PERCEIVED to run faster or slower than clock tK, in the two different transforms.


    QUESTION: WHERE IS THE TRICK EMBEDDED IN THIS PARADOX?

    There is no paradox.

    The trick is to know how to use the Lorentz transform.

    You don't.

    It's mathematics which you always screw up.


    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Thu Nov 9 15:15:11 2023
    On Thursday, November 9, 2023 at 5:50:00 PM UTC-5, Richard Hertz wrote:


    "Length contraction is the PHENOMENON that a moving

    <snip>. Irrelevant to the discussion.

    2) Measured = CALCULATED using the first Lorentz formula.

    That is not what 'measured' means.
    You have been systematically showing that you do not understand the meaning of the words you use.
    I explain to you the meanings, and you just 'disappear' or change the subject. That is crank behavior.


    This is very simple, and is clearly explained in the Wiki article:

    As I told you, forget what others say. Do what SR says, since that is what you want to analyze.

    <rest of confusions snipped>.

    I have explained to you what SR says and doesnt say. You have not given one rebuttal to my claims and calcs.
    But you did divert and changed the topic(s). You are looking more and more like a crank...More and more...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Paul B. Andersen on Thu Nov 9 14:49:58 2023
    On Thursday, November 9, 2023 at 5:18:57 PM UTC-3, Paul B. Andersen wrote:
    Den 08.11.2023 22:56, skrev Richard Hertz:
    c = 299792458 m/s = 299.792458 m/μs

    Two perfect mirrors (A,B) are placed 149,896229 m apart, being A at the origin of the relatively moving frame K'.

    A photon, in the visible light range, is emitted from the mirror A (which also contains a clock) exactly towards mirror B.

    The photon bounces back at mirror B, towards mirror A. Its arrival from the roundtrip is marked in tA clock as being exactly 1.0000000 μs.

    This process continues forever, without any losses, while A clock is accumulating 1.0000000 μs counts.
    OK!

    The arrangement in K' moves at v speed wrt the origin at K, where a clock tK is located (it also ticks at 1.0000000 μs.

    Both clocks (tK and tA) are reset to zero exactly when A pass by the origin K, and it forces the emission of the photon.
    OK!

    Then, tK and tA are synchronized in the einstenian way.
    No, this has noting to do with Einstein's way of synchronizing
    clocks in inertial frames.

    Two clocks are set equal (to zero) when they pass each other,
    that's all.
    We will also assume that both clocks are placed at the origin of
    their respective rest frames.

    We then have:

    K':-tA------B-------->x'->v
    K :-tK--------------->x

    The speed v = 0.9 c = 269813212 m/s

    WHAT SR (LORENTZ) SAYS THAT HAPPENS AFTERWARDS.
    γ = 2.294157339
    In the following we will use L as the distance
    between the mirrors. We can put in numbers later.

    To find what SR says, we use the Lorentz transform.
    We have three event of interest.

    E0: tA and tK are aligned and the photon is emitted from A.
    E1: the photon is reflected from B.
    E2: the photon is reflected from A

    Let's find the coordinates of these event's in K and K':

    γ = 1/√(1 −v²/c²) = 2.294157339 when v = 0.9c

    EO:
    Coordinates in K': x₀' = 0, t₀' = 0
    Coordinates in K: x₀ = 0, t₀ = 0

    E1: (this event could be skipped)
    Coordinates in K': x₁' = L, t₁' = L/c
    Coordinates in K:
    x₁ = γ(x₁'+ v⋅t₁')=γ(L+ v⋅L/c) = L⋅√((c+v)/(c-v))
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L/c + (v/c²)⋅L) = (L/c)⋅√((c+v)/(c-v))

    E2:
    Coordinates in K': x₂' = 0, t₂' = 2L/c
    Coordinates in K:
    x₂ = γ(x₂'+ v⋅t₁') = γ(0 + v⋅2L/c) = (2Lv/c)/√(1 −v²/c²) t₂ = γ(t₂'+ (v/c²)⋅x₂') = γ(L/c + (v/c²)⋅L) = (2L/c)/√(1 −v²/c²)

    So while the moving clock tA has advanced the proper time
    t₂' = 2L/c = 1 μs ,
    the coordinate time in the stationary frame has advanced
    t₂ (2L/c)/√(1 −v²/c²) = 2.294157339 μs

    t₂'/t₂ = √(1 −v²/c²) = 0.435889894

    "Moving clocks run slow"

    LENGTH CONTRACTION (Horizontal light clock is perceived to run faster) http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c1

    x' = γ (x - vt)

    Δx' = AB AND Δx = AB/γ = 0.435889894 AB, as measured in the frame at rest. As both measurements are made simultaneously in the frame at rest, there is A PERCEIVED LENGTH CONTRACTION of AB in the moving frame.
    But the speed of light IS INVARIANT wrt to any frame, so IT'S PERCEIVED that clock tA IS RUNNING FASTER.

    The roundtrip of the photon is PERCEIVED to travel 2 x 0.435889894 AB = 0.871779789 x AB, which means that the clock's tick in the moving frame IS PERCEIVED TO TICK every 0.871779789 μs, instead of 1.00000000 μs.

    TIME DILATION (Horizontal light clock is perceived to run slower) http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c2

    t' = γ (t - vx/c)

    Δt' = Δt/γ = 0.435889894 Δt (Time is PERCEIVED as running slower in the moving frame).

    For every 1.00000000 μs in the frame at rest, it's PERCEIVED that only 0.435889894 μs passed in the moving frame.

    The time measurements are made in the same location, so it doesn't affect the results.

    CONCLUSION: Using an horizontal light clock, the results of TIME FLOW due to length contraction and time dilation are in conflict. Clock tA is PERCEIVED to run faster or slower than clock tK, in the two different transforms.


    QUESTION: WHERE IS THE TRICK EMBEDDED IN THIS PARADOX?
    There is no paradox.

    The trick is to know how to use the Lorentz transform.

    You don't.

    It's mathematics which you always screw up.


    --
    Paul

    https://paulba.no/

    https://en.wikipedia.org/wiki/Length_contraction

    "Length contraction is the PHENOMENON that a moving object's length is MEASURED TO BE SHORTER than its proper length, which is the length as measured in the object's own rest frame.[1] It is also known as Lorentz contraction or Lorentz–FitzGerald
    contraction (after Hendrik Lorentz and George Francis FitzGerald) and is usually only noticeable at a substantial fraction of the speed of light."

    NOTES: 1) Phenomenon? ; 2) Measured = CALCULATED using the first Lorentz formula.

    Paul, you should stop scrambling concepts and using Lorentz mathemagics, and stick to what I posted, without changes.

    This is very simple, and is clearly explained in the Wiki article:

    L = L₀/γ(v)

    where

    L is the length OBSERVED by an observer in motion relative to the object.
    L₀ is the proper length (the length of the object in its rest frame).
    γ(v) is the Lorentz factor, defined as γ(v) = 1/√(1 - v²/c²).

    In my own terms,
    Δx(v) = AB/γ(v) ; roundtrip time "OBSERVED/PERCEIVED" in K' from K: Δt' = 2AB/(c.γ)
    Δx(0) = AB ; Δt' = 1.000000 μs
    Δx(0.9c) = 0.43589 AB ; Δt' = 0.87178 μs , because c is invariant. Δx(0.999c) = 0.04471 AB ; Δt' = 0.089420 μs , because c is invariant. Δx(0.999999c) = 0.001414 AB ; Δt' = 0.002828 μs , because c is invariant.
    Δx(0.999999999c) = 0.000045 AB ; Δt' = 0.000089 μs , because c is invariant.

    Use two arrays AB, with a digital counter tA located at the A side of the assembly AB. Put one of them at the origin
    of the K frame, with A located in the origin and put the other on the moving K' frame, with A at its origin.

    These twin systems are COUNTING 1.000000 μs ticks of the horizontal light clock AB.

    The observer at the origin of K frame monitor the counts of the two counters (moving and being at rest). He CAN CERTIFY that
    the local and remote digital displays show THE SAME ACCOUNT OF 1.000000 μs ticks.

    Yet, for his dismay and confusion, when use the Lorentz formula, it DECEIVES HIM telling that 1.000000 μs tick in his local clock/counter
    is happening at an increasingly lower value in the remote system (mathemagics), BUT it's in conflict with the value of the remote digital
    display, which IS EQUAL TO HIS LOCAL DISPLAY.

    Here, 60 years after the 1905 paper, digital electronics DESTROY THE ANALOG LORENTZ FORMULA, proving that it's a FICTION, a fairy tale.

    Now, what could happen in the head of the poor observer? He might arrive to the conclusion that SR is a flawed pseudo-science, and that all
    that he believed since his conversion to relativity IS A LIE.

    Blame the second postulate and the horizontal light clock, if you want.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to rotchm on Thu Nov 9 19:43:03 2023
    On Thursday, November 9, 2023 at 8:15:13 PM UTC-3, rotchm wrote:
    On Thursday, November 9, 2023 at 5:50:00 PM UTC-5, Richard Hertz wrote:


    "Length contraction is the PHENOMENON that a moving
    <snip>. Irrelevant to the discussion.
    2) Measured = CALCULATED using the first Lorentz formula.
    That is not what 'measured' means.
    You have been systematically showing that you do not understand the meaning of the words you use.
    I explain to you the meanings, and you just 'disappear' or change the subject. That is crank behavior.
    This is very simple, and is clearly explained in the Wiki article:
    As I told you, forget what others say. Do what SR says, since that is what you want to analyze.

    <rest of confusions snipped>.

    I have explained to you what SR says and doesnt say. You have not given one rebuttal to my claims and calcs.
    But you did divert and changed the topic(s). You are looking more and more like a crank...More and more...

    I didn't reply to your post because, besides the criticism on my use of words, you changed the meaning of my post by "counting photon clicks, not time".

    If 1.00000000 μs is too discrete for you, change the clock tick to 1.0000000 ps by reducing AB length to 149.896229 μm. And if this not enough for you,
    reduce the length another 100 times, so the photon travels about one wavelength.

    The passage from the analog domain, in which Lorentz transforms are developed, to the digital domain, is based on discretization of time, which has
    a logical limit that applies also to the analog domain. You can't work with a fraction of a wavelength as it has no meaning.

    One example of lower limit in the digital domain is to use 550 nm green photons and use AB = 1,1 μm, if you prefer to go to the end of this ensemble.

    The time measured is, in the digital domain, a multiple of the roundtrip time. Lorentz transforms work with infinitesimal fractions of time, but LOOSE
    ANY MEANING below the lowest possible visible wavelength, so your range for choices of wavelengths is narrowed between 440 nm and 750 nm.

    Said that, for me there is a functional light clock, at which you can modify the resolution of duration of ticks but until the limits written above.

    So, this thought experiment is about to accumulate counts of discretized time. In this case, digital math kills Lorentz math.

    Something equivalent to Planck's E = hf, which made the classic conception of infinitesimally low energy per resonator OBSOLETE.

    SR, with development based on visible light, has a similar low-end limit. I mentioned here this fact many times, and suggested that not only a lower
    limit of time and lengths, but also an upper limit for them should be applied.

    It's ridiculous to apply SR even for 1 second, if v is ALMOST c. The distance involved of 300,000 Km is RIDICULOUS. And better not to talk about 10 sec.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to rotchm on Thu Nov 9 21:12:24 2023
    On Friday, 10 November 2023 at 00:15:13 UTC+1, rotchm wrote:
    On Thursday, November 9, 2023 at 5:50:00 PM UTC-5, Richard Hertz wrote:


    "Length contraction is the PHENOMENON that a moving
    <snip>. Irrelevant to the discussion.
    2) Measured = CALCULATED using the first Lorentz formula.
    That is not what 'measured' means.

    That's not what it means, but that's what you
    and your fellow idiots mean when spelling
    it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to rotchm on Thu Nov 9 21:13:21 2023
    On Friday, 10 November 2023 at 05:33:24 UTC+1, rotchm wrote:
    On Thursday, November 9, 2023 at 10:43:06 PM UTC-5, Richard Hertz wrote:

    I didn't reply to your post because, besides the criticism on my use of words,
    For two parties to understand each other, they must know the meaning of the words they use.
    The words you use are ill defined and not necessary.

    So are, unfortunately, the words you and your fellow idiots
    use.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Thu Nov 9 20:33:21 2023
    On Thursday, November 9, 2023 at 10:43:06 PM UTC-5, Richard Hertz wrote:

    I didn't reply to your post because, besides the criticism on my use of words,

    For two parties to understand each other, they must know the meaning of the words they use.
    The words you use are ill defined and not necessary. Try to be to the point, w/o any unnecessary 'gibberish'.
    Its a skill to write clearly and efficiently.

    And I have explained to you the meaning of many of the words & concepts you use.
    You did not debunk my claims. So you either agreed with me or had no counterargument.


    you changed the meaning of my post by "counting photon clicks, not time".

    Not sure what you are specifically alluding to here.
    Clocks are devices that display (log) values. Its not necessary to say that they 'tick' and can also cause confusion on its meaning.

    If 1.00000000 μs is too discrete for you, change the clock tick to 1.0000000 ps

    It indicates a value. Your setup has chosen it. But fir clarity & simplicity, just call it 1, or 1 unit, or 1 μs etc.
    A clock will display successive values. For simplicity, "0,1,2,3,...". This is your setup.



    The passage from the analog domain, in which Lorentz transforms are developed, to the digital domain, is based
    on discretization of time, which has
    a logical limit that applies also to the analog domain. You can't work with a fraction of a wavelength as it has no meaning.

    All irrelevant to your OP. You gave a setup. You made claims of what SR 'says' about the setup and its results.
    I corrected you on it. I told you what SR 'says', what the *values* will be. You haven't presented any rebuttal, only changing the topic.

    One example of lower limit in the digital domain is to use 550 nm green photons and use AB = 1,1 μm,

    Off topic. Refer to your OP.

    The time measured is, in the digital domain, a multiple of the roundtrip time.

    The *values* displayed by the clock(s).

    Lorentz transforms work with infinitesimal fractions of time,

    The LT's give (predicts) the *values* on the respective devices. The quality & precision of the devices is a different topic and not part of SR.

    but LOOSE
    ANY MEANING below the lowest possible visible wavelength,

    Perhaps, but that has nothing to do with SR.
    SR will predict the value(s) on your instruments. But obviously if you want to verify it, you must have good quality instruments and of the desired precision. That consideration is not part of SR.


    So, this thought experiment is about to accumulate counts of discretized time. In this case, digital math kills Lorentz math.

    How so?

    Since you are continuously changing your setup, we cant have a sensible discussion of your OP.
    Try again. Restate your setup clearly w/o any 'embellishments'. Then make your claims concerning the results of measurements.

    It's ridiculous to apply SR even for 1 second, if v is ALMOST c. The distance involved of 300,000 Km
    is RIDICULOUS. And better not to talk about 10 sec.

    And all irrelevant to the topic. Consult your OP.
    We are discussing the predicts of SR relating to your setup.
    We are not discussing our current engineering limitations.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Fri Nov 10 20:45:33 2023
    Den 09.11.2023 23:49, skrev Richard Hertz:
    On Thursday, November 9, 2023 at 5:18:57 PM UTC-3, Paul B. Andersen wrote:
    Den 08.11.2023 22:56, skrev Richard Hertz:
    c = 299792458 m/s = 299.792458 m/μs

    Two perfect mirrors (A,B) are placed 149,896229 m apart, being A at the origin of the relatively moving frame K'.

    A photon, in the visible light range, is emitted from the mirror A (which also contains a clock) exactly towards mirror B.

    The photon bounces back at mirror B, towards mirror A. Its arrival from the roundtrip is marked in tA clock as being exactly 1.0000000 μs.

    This process continues forever, without any losses, while A clock is accumulating 1.0000000 μs counts.
    OK!

    The arrangement in K' moves at v speed wrt the origin at K, where a clock tK is located (it also ticks at 1.0000000 μs.

    Both clocks (tK and tA) are reset to zero exactly when A pass by the origin K, and it forces the emission of the photon.
    OK!

    Then, tK and tA are synchronized in the einstenian way.
    No, this has noting to do with Einstein's way of synchronizing
    clocks in inertial frames.

    Two clocks are set equal (to zero) when they pass each other,
    that's all.
    We will also assume that both clocks are placed at the origin of
    their respective rest frames.

    We then have:

    K':-tA------B-------->x'->v
    K :-tK--------------->x


    The speed v = 0.9 c = 269813212 m/s

    WHAT SR (LORENTZ) SAYS THAT HAPPENS AFTERWARDS.
    γ = 2.294157339

    In the following we will use L as the distance
    between the mirrors. We can put in numbers later.

    To find what SR says, we use the Lorentz transform.
    We have three event of interest.

    E0: tA and tK are aligned and the photon is emitted from A.
    E1: the photon is reflected from B.
    E2: the photon is reflected from A

    Let's find the coordinates of these event's in K and K':

    γ = 1/√(1 −v²/c²) = 2.294157339 when v = 0.9c

    EO:
    Coordinates in K': x₀' = 0, t₀' = 0
    Coordinates in K: x₀ = 0, t₀ = 0

    E1: (this event could be skipped)
    Coordinates in K': x₁' = L, t₁' = L/c
    Coordinates in K:
    x₁ = γ(x₁'+ v⋅t₁')=γ(L+ v⋅L/c) = L⋅√((c+v)/(c-v))
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L/c + (v/c²)⋅L) = (L/c)⋅√((c+v)/(c-v))

    E2:
    Coordinates in K': x₂' = 0, t₂' = 2L/c
    Coordinates in K:
    x₂ = γ(x₂'+ v⋅t₁') = γ(0 + v⋅2L/c) = (2Lv/c)/√(1 −v²/c²) >> t₂ = γ(t₂'+ (v/c²)⋅x₂') = γ(L/c + (v/c²)⋅L) = (2L/c)/√(1 −v²/c²)

    So while the moving clock tA has advanced the proper time
    t₂' = 2L/c = 1 μs ,
    the coordinate time in the stationary frame has advanced
    t₂ (2L/c)/√(1 −v²/c²) = 2.294157339 μs

    t₂'/t₂ = √(1 −v²/c²) = 0.435889894

    "Moving clocks run slow"


    LENGTH CONTRACTION (Horizontal light clock is perceived to run faster)
    http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c1

    x' = γ (x - vt)

    Δx' = AB AND Δx = AB/γ = 0.435889894 AB, as measured in the frame at rest. As both measurements are made simultaneously in the frame at rest, there is A PERCEIVED LENGTH CONTRACTION of AB in the moving frame.
    But the speed of light IS INVARIANT wrt to any frame, so IT'S PERCEIVED that clock tA IS RUNNING FASTER.

    The roundtrip of the photon is PERCEIVED to travel 2 x 0.435889894 AB = 0.871779789 x AB, which means that the clock's tick in the moving frame IS PERCEIVED TO TICK every 0.871779789 μs, instead of 1.00000000 μs.

    TIME DILATION (Horizontal light clock is perceived to run slower)
    http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c2

    t' = γ (t - vx/c)

    Δt' = Δt/γ = 0.435889894 Δt (Time is PERCEIVED as running slower in the moving frame).

    For every 1.00000000 μs in the frame at rest, it's PERCEIVED that only 0.435889894 μs passed in the moving frame.

    The time measurements are made in the same location, so it doesn't affect the results.

    CONCLUSION: Using an horizontal light clock, the results of TIME FLOW due to length contraction and time dilation are in conflict. Clock tA is PERCEIVED to run faster or slower than clock tK, in the two different transforms.


    QUESTION: WHERE IS THE TRICK EMBEDDED IN THIS PARADOX?
    There is no paradox.

    The trick is to know how to use the Lorentz transform.

    You don't.

    It's mathematics which you always screw up.


    --
    Paul

    https://paulba.no/


    https://en.wikipedia.org/wiki/Length_contraction


    "Length contraction is the PHENOMENON that a moving object's length is MEASURED TO BE SHORTER than its proper length, which is the length as measured in the object's own rest frame.[1] It is also known as Lorentz contraction or Lorentz–FitzGerald
    contraction (after Hendrik Lorentz and George Francis FitzGerald) and is usually only noticeable at a substantial fraction of the speed of light."

    Yes. Let's have a look at the Lorentz contraction.

    To measure the distance between the moving A and B in K means
    to measure the distance between the position of A in K at some
    time t, and the position of B _at the same time_ t.

    Of course we know the result will be L/γ, but let us
    do it properly:

    In K', A is at x' = 0, and B is at x' = L. Always.
    In K, A is at x = 0 at t=0.

    So let as find the position of B in K at t=0.
    Use the LT:
    t = γ(t'+ (v/c²)x') = γ(t'+ Lv/c²) = 0 => t' = -Lv/c²
    x = γ(x'+ vt') = γ(L- vLv/c²) = γL(1-v²/c²) = L⋅√(1 −v²/c²)

    So the _measured_ distance between A and B in K is:
    L⋅√(1 −v²/c²) as expected.

    But the important point to notice is that in K',
    the position of A was measured at t' = 0, but B was measured
    at t' = -Lv/c², that is earlier, when the B had not moved
    as far as A. That's why it is measured to be shorter!
    Relativity of simultaneity!

    The point is that relativity of simultaneity and Lorentz contraction
    are two sides of the same coin!


    NOTES: 1) Phenomenon? ; 2) Measured = CALCULATED using the first Lorentz formula.

    Paul, you should stop scrambling concepts and using Lorentz mathemagics, and stick to what I posted, without changes.

    This is very simple, and is clearly explained in the Wiki article:

    L = L₀/γ(v)

    where

    L is the length OBSERVED by an observer in motion relative to the object.
    L₀ is the proper length (the length of the object in its rest frame).
    γ(v) is the Lorentz factor, defined as γ(v) = 1/√(1 - v²/c²).

    In my own terms,
    Δx(v) = AB/γ(v) ; roundtrip time "OBSERVED/PERCEIVED" in K' from K: Δt' = 2AB/(c.γ)


    What is "round triptime "OBSERVED/PERCEIVED" in K' from K:"
    supposed to mean? It is meaningless babble.

    You can't "perceive" what is measured it K' from K.

    The round trip time _measured_ in K' is 2L₀/c.
    The round trip time _measured_ in K is (2L₀/c)/√(1 −v²/c²)

    I showed this above, but you have probably not read it.
    So let me remind you:

    It's very simple, and should be impossible to screw up: =======================================================
    When the light pulse has moved from A to B and back to A,
    the coordinates of A in K' are x' = 0, t' = 2L₀/c
    We must use the Lorentz transform to find the coordinates in K:

    t = γ(t'+ (v/c²)x') = γ(L₀/c + (v/c²)⋅L₀) = (2L₀/c)/√(1 −v²/c²)

    It is impossible to make the Lorentz transform give any other result.

    You have not used the Lorentz transform at all!

    The following is nonsense.

    Δx(0) = AB ; Δt' = 1.000000 μs
    Δx(0.9c) = 0.43589 AB ; Δt' = 0.87178 μs , because c is invariant. Δx(0.999c) = 0.04471 AB ; Δt' = 0.089420 μs , because c is invariant. Δx(0.999999c) = 0.001414 AB ; Δt' = 0.002828 μs , because c is invariant.
    Δx(0.999999999c) = 0.000045 AB ; Δt' = 0.000089 μs , because c is invariant.

    Use two arrays AB, with a digital counter tA located at the A side of the assembly AB. Put one of them at the origin
    of the K frame, with A located in the origin and put the other on the moving K' frame, with A at its origin.

    These twin systems are COUNTING 1.000000 μs ticks of the horizontal light clock AB.

    The observer at the origin of K frame monitor the counts of the two counters (moving and being at rest). He CAN CERTIFY that
    the local and remote digital displays show THE SAME ACCOUNT OF 1.000000 μs ticks.

    Yet, for his dismay and confusion, when use the Lorentz formula, it DECEIVES HIM telling that 1.000000 μs tick in his local clock/counter
    is happening at an increasingly lower value in the remote system (mathemagics), BUT it's in conflict with the value of the remote digital
    display, which IS EQUAL TO HIS LOCAL DISPLAY.

    Here, 60 years after the 1905 paper, digital electronics DESTROY THE ANALOG LORENTZ FORMULA, proving that it's a FICTION, a fairy tale.

    Now, what could happen in the head of the poor observer? He might arrive to the conclusion that SR is a flawed pseudo-science, and that all
    that he believed since his conversion to relativity IS A LIE.

    Blame the second postulate and the horizontal light clock, if you want.


    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Paul B. Andersen on Fri Nov 10 19:26:40 2023
    On Friday, November 10, 2023 at 4:43:55 PM UTC-3, Paul B. Andersen wrote:
    Den 09.11.2023 23:49, skrev Richard Hertz:

    <snip Paul's crap>

    In my own terms,
    Δx(v) = AB/γ(v) ; roundtrip time "OBSERVED/PERCEIVED" in K' from K: Δt' = 2AB/(c.γ)


    What is "round triptime "OBSERVED/PERCEIVED" in K' from K:"
    supposed to mean? It is meaningless babble.

    You can't "perceive" what is measured it K' from K.

    The round trip time _measured_ in K' is 2L₀/c.
    The round trip time _measured_ in K is (2L₀/c)/√(1 −v²/c²)



    You're full of historical shit.

    Let me RECAP: You CAN'T measure the round trip time of a K' event being in the frame K, at relative rest!. In particular, being that K' is moving at almost c.

    If you want to know the K' round trip time from K, read THE FUCKING DIGITAL DISPLAY IN K'!!

    And that is the ONLY TRUTH in your pseudo-scientific relativism.

    Because mathematics (Lorentz) IS NOT PHYSICS. But you'll never learn, fanatic indoctrinated relativist!

    Your early marriage with the Lorentz crap and Einstein pseudo-philosophy ruined your brain since decades ago. Now it's USELESS.





    I showed this above, but you have probably not read it.
    So let me remind you:

    It's very simple, and should be impossible to screw up: =======================================================
    When the light pulse has moved from A to B and back to A,
    the coordinates of A in K' are x' = 0, t' = 2L₀/c
    We must use the Lorentz transform to find the coordinates in K:

    t = γ(t'+ (v/c²)x') = γ(L₀/c + (v/c²)⋅L₀) = (2L₀/c)/√(1 −v²/c²)

    It is impossible to make the Lorentz transform give any other result.

    You have not used the Lorentz transform at all!

    YOU KEEP USING MATHEMAGICS, BELIEVING THAT IT EXPLAIN THE REAL WORLD OF PHYSICAL EVENTS. But you lost your mind
    in your journey toward full relativistic indoctrination. Again, mathematics IS NOT PHYSICS.

    You SHOULD/MUST read Newton's biography and learn what is producing BY REASONING, not by borrowed doctrines of a
    pseudo-science that ruined your brain.

    Newton, with Halley's help, created the modern world of physics and calculus, providing TRUE MATHEMATICAL TOOLS to describe
    events in nature, long time observed and documented by Kepler, Galileo and many others.

    Einstein perverted Newton mechanics by the way of fallacies and deceptions, wrapped in circular paradoxes, that only found
    applications in some aspects of the non-observable world of the quantum and some aspects of the NON-MENSURABLE events
    in marginal topics of celestial mechanics, which are ONLY CALCULABLE, not observable.

    And I prefer not to expand this shitty GR theory to cosmology, where fail CATASTROPHICALLY (since day 1).



    <snip>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Sat Nov 11 13:50:07 2023
    Den 11.11.2023 04:26, skrev Richard Hertz:
    On Friday, November 10, 2023 at 4:43:55 PM UTC-3, Paul B. Andersen wrote:
    Den 09.11.2023 23:49, skrev Richard Hertz:
    In my own terms,
    Δx(v) = AB/γ(v) ; roundtrip time "OBSERVED/PERCEIVED" in K' from K: Δt' = 2AB/(c.γ)

    What is "round triptime "OBSERVED/PERCEIVED" in K' from K:"
    supposed to mean? It is meaningless babble.

    You can't "perceive" what is measured it K' from K.

    The round trip time _measured_ in K' is 2L₀/c.
    The round trip time _measured_ in K is (2L₀/c)/√(1 −v²/c²)

    You're full of historical shit.

    Let me remind you of the subject line:
    "Conflicts in SR when using horizontal light clocks in the moving frame."

    Your opinion of SR is irrelevant.
    The question is: Have you succeeded in proving SR inconsistent?

    To prove SR inconsistent, that is self contradictory,
    you must show that the math of SR can give contradictory
    predictions for the same scenario.
    "The math of SR" is in this case the Lorentz transform.

    You claim to have proven that SR is inconsistent, but you
    haven't used the Lorentz transform to show it.

    Your attempt to use "the math SR" is only naive nonsense.


    Let me RECAP: You CAN'T measure the round trip time of a K' event being in the frame K, at relative rest!. In particular, being that K' is moving at almost c.

    The Lorentz transform predicts what would be _measured_.
    Not "PERCEIVED", whatever that might mean,

    There is only one way to measure the round trip time of
    a moving light clock.

    That is to:
    1. Compare it with a coordinate clock in K at the instant
    the photon leave A, and:
    2. Compare it with a coordinate clock in K at the instant
    the photon is back at A after being reflected from B.

    Let me RECAP:
    1. Photon leave A, Coordinates of A:
    In K': x₀' = 0, t₀' = 0
    In K: x₀ = 0, t₀ = 0
    2: Photon back at A, Coordinates of A:
    In K': x₁' = 0, t₁' = 2L₀/c
    In K:
    x₁ = γ(x₁'+ v⋅t₁') = γ(0 + v⋅2L₀/c) = (2L₀v/c)/√(1 −v²/c²)
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L₀/c + (v/c²)⋅L₀) = (2L₀/c)/√(1 −v²/c²)

    This means:
    Clock tA has advanced the proper time (t₁'-t₀') = 2L₀/c
    while the coordinate time of K has advanced
    (t₁-t₀) = (2L₀/c)/√(1 −v²/c²)

    In K the moving clock is measured to run slow by √(1 −v²/c²).

    -----

    Since you are so interested in the Lorentz contraction, we could ask:
    Where in K is B at the time t₁ = γ2L₀/c ?
    Coordinates of B:
    In K': x₂' = L₀, t₂' = ?
    In K:
    t₁ = γ(t₂'+ (v/c²)⋅x₂') = γ2L₀/c => t₂' = 2L₀/c - vL₀/c²
    x₂ = γ(x₂'+ v⋅t₂') = γ(L₀ + v⋅(2L₀/c -vL₀/c²)) = γ⋅L₀(1+2v/c-v²/c²)

    The distance between A and B measured in K is:
    x₂-x₁ = γ⋅L₀(1+2v/c-v²/c²)- γ⋅2L₀v/c = γ⋅L₀(1-v²/c²) = L₀⋅√(1−v²/c²)

    In K, the proper distance between the mirrors L₀ is Lorentz contracted (measured to be) L₀⋅√(1−v²/c²)

    ------

    The above is what SR predicts, and if you want to prove SR inconsistent
    you have to show that the Lorentz transform can produce alternative
    results to the above!


    If you want to know the K' round trip time from K, read THE FUCKING DIGITAL DISPLAY IN K'!!
    So when you proved SR inconsistent you to read
    THE FUCKING DIGITAL DISPLAY IN K' which showed that
    the round trip time in K' was 1μs, and then you PERCEIVED
    what it would be in K? :-D


    And that is the ONLY TRUTH in your pseudo-scientific relativism.

    Because mathematics (Lorentz) IS NOT PHYSICS. But you'll never learn, fanatic indoctrinated relativist!

    Your early marriage with the Lorentz crap and Einstein pseudo-philosophy ruined your brain since decades ago. Now it's USELESS.

    So now, when you have realized that you are unable to prove
    the Lorentz transform inconsistent, you overturn the table
    so the pieces are spread on the floor, shouting:

    "I don't want to play the game 'proving SR inconsistent' anymore,
    because mathematics (Lorentz) IS NOT PHYSICS. SO THERE"

    I accept your surrender.

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Sat Nov 11 06:35:53 2023
    On Friday, November 10, 2023 at 10:26:45 PM UTC-5, Richard Hertz wrote:
    On Friday, November 10, 2023 at 4:43:55 PM UTC-3, Paul B. Andersen wrote:

    The round trip time _measured_ in K' is 2L₀/c.
    The round trip time _measured_ in K is (2L₀/c)/√(1 −v²/c²)
    You're full of historical shit.

    Your OP is: What does SR predict for your setup, Agreed?
    For the purpose of this thread, SR is x'=(x-vt)γ and t'=(t-xv/c²)γ.
    By using the above LT, Paul and I here have shown you in a few lines of algebra, what
    SR predicts for the values on the clocks & rulers for your setup (events).

    Nowhere have you shown an error, nowhere have you provided a rebuttal to the steps
    we provided you. Your response to our 5 lines of algebra is " You're full of historical shit".
    What a convincing counterargument!

    Put 2 apples on the table. Then put 3 more. Count them all now. The answer you get is 5.
    According to you that must be wrong because"2+3=5" has already been demonstrated in
    the past; it is " historical shit". This is exactly the "argument" you provided us.


    Let me RECAP: You CAN'T measure the round trip time of a K' event being in the frame K,
    at relative rest!. In particular, being that K' is moving at almost c.

    Yes it can be done. Scientists do it all the time. But that is irrelevant to the OP since your query
    is about the predictions of SR to your setup.

    To measure the time of occurrence of an event, a given observer uses his clock that is located at the event.
    The predictions of SR are (with v=0.9c):

    As the photon returns to clock A, this clock A displays 1 (μs), agreed? (i.e.: t₁' = 1, or as Paul has symbolized it, t₁' = 2L₀/c)

    As the photon returns to clock A, the clock belonging to frame K which is located at the event,
    ("under", coinciding with clock A) has the value 2.29...(μs), agreed?
    (i.e.: t₁ = 2.29 (μs), or as Paul put it, t₁ = (2L₀/c)/√(1 −v²/c²)).

    These are SR's predictions. Can you point out where is our/SR's algebraic mistake?
    Note that 1 < 2.29; the value on the moving clock A is less that the fixed clock in K.
    This is what is called "time dilation" or "moving clocks run slow".
    Best just to say 1 < 2.29. Less confusing that way, no?

    If you want to know the K' round trip time from K, read THE FUCKING DIGITAL DISPLAY IN K'!!

    You do not seem to know the meaning of the word 'time', nor of the meaning of the symbols used in SR, namely "t" etc.

    A clock displays a value as it displays the value.
    For instance, when it displays "1" it there and then displays 1. Simple concept.
    This is what is meant to measure (observe) time on a given clock (or frame).

    The parameter "t" in SR represents the value displayed by a given clock.
    So, to predict the value displayed by clock A, SR says its 1 (μs). [why?]
    So, to predict the value displayed by K clock located there, SR says its 2.29 (μs).


    And that is the ONLY TRUTH in your pseudo-scientific relativism.
    Because mathematics (Lorentz) IS NOT PHYSICS. But you'll never learn, fanatic indoctrinated relativist!

    You wanted to know what SR predicted for your setup. We have shown you.
    You are now changing/requesting a different topic? That is, what actual exps give?
    Well, the results of exps concur with SR's predictions.


    in your journey toward full relativistic indoctrination. Again, mathematics IS NOT PHYSICS.

    Perhaps, but that is a different topic from your OP. Stay on topic.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Paul B. Andersen on Sat Nov 11 08:30:05 2023
    On Saturday, November 11, 2023 at 9:48:27 AM UTC-3, Paul B. Andersen wrote:
    Den 11.11.2023 04:26, skrev Richard Hertz:
    On Friday, November 10, 2023 at 4:43:55 PM UTC-3, Paul B. Andersen wrote:
    Den 09.11.2023 23:49, skrev Richard Hertz:
    In my own terms,
    Δx(v) = AB/γ(v) ; roundtrip time "OBSERVED/PERCEIVED" in K' from K: Δt' = 2AB/(c.γ)

    What is "round triptime "OBSERVED/PERCEIVED" in K' from K:"
    supposed to mean? It is meaningless babble.

    You can't "perceive" what is measured it K' from K.

    The round trip time _measured_ in K' is 2L₀/c.
    The round trip time _measured_ in K is (2L₀/c)/√(1 −v²/c²)

    You're full of historical shit.
    Let me remind you of the subject line:
    "Conflicts in SR when using horizontal light clocks in the moving frame."

    Your opinion of SR is irrelevant.
    The question is: Have you succeeded in proving SR inconsistent?

    To prove SR inconsistent, that is self contradictory,
    you must show that the math of SR can give contradictory
    predictions for the same scenario.
    "The math of SR" is in this case the Lorentz transform.

    You claim to have proven that SR is inconsistent, but you
    haven't used the Lorentz transform to show it.

    Your attempt to use "the math SR" is only naive nonsense.

    Let me RECAP: You CAN'T measure the round trip time of a K' event being in the frame K, at relative rest!. In particular, being that K' is moving at almost c.
    The Lorentz transform predicts what would be _measured_.
    Not "PERCEIVED", whatever that might mean,

    There is only one way to measure the round trip time of
    a moving light clock.

    That is to:
    1. Compare it with a coordinate clock in K at the instant
    the photon leave A, and:
    2. Compare it with a coordinate clock in K at the instant
    the photon is back at A after being reflected from B.

    Let me RECAP:
    1. Photon leave A, Coordinates of A:
    In K': x₀' = 0, t₀' = 0
    In K: x₀ = 0, t₀ = 0
    2: Photon back at A, Coordinates of A:
    In K': x₁' = 0, t₁' = 2L₀/c
    In K:
    x₁ = γ(x₁'+ v⋅t₁') = γ(0 + v⋅2L₀/c) = (2L₀v/c)/√(1 −v²/c²)
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L₀/c + (v/c²)⋅L₀) = (2L₀/c)/√(1 −v²/c²)

    This means:
    Clock tA has advanced the proper time (t₁'-t₀') = 2L₀/c
    while the coordinate time of K has advanced
    (t₁-t₀) = (2L₀/c)/√(1 −v²/c²)

    In K the moving clock is measured to run slow by √(1 −v²/c²).

    -----

    Since you are so interested in the Lorentz contraction, we could ask:
    Where in K is B at the time t₁ = γ2L₀/c ?
    Coordinates of B:
    In K': x₂' = L₀, t₂' = ?
    In K:
    t₁ = γ(t₂'+ (v/c²)⋅x₂') = γ2L₀/c => t₂' = 2L₀/c - vL₀/c² x₂ = γ(x₂'+ v⋅t₂') = γ(L₀ + v⋅(2L₀/c -vL₀/c²)) = γ⋅L₀(1+2v/c-v²/c²)

    The distance between A and B measured in K is:
    x₂-x₁ = γ⋅L₀(1+2v/c-v²/c²)- γ⋅2L₀v/c = γ⋅L₀(1-v²/c²) = L₀⋅√(1−v²/c²)

    In K, the proper distance between the mirrors L₀ is Lorentz contracted (measured to be) L₀⋅√(1−v²/c²)

    ------

    The above is what SR predicts, and if you want to prove SR inconsistent
    you have to show that the Lorentz transform can produce alternative
    results to the above!

    If you want to know the K' round trip time from K, read THE FUCKING DIGITAL DISPLAY IN K'!!
    So when you proved SR inconsistent you to read
    THE FUCKING DIGITAL DISPLAY IN K' which showed that
    the round trip time in K' was 1μs, and then you PERCEIVED
    what it would be in K? :-D

    And that is the ONLY TRUTH in your pseudo-scientific relativism.

    Because mathematics (Lorentz) IS NOT PHYSICS. But you'll never learn, fanatic indoctrinated relativist!

    Your early marriage with the Lorentz crap and Einstein pseudo-philosophy ruined your brain since decades ago. Now it's USELESS.
    So now, when you have realized that you are unable to prove
    the Lorentz transform inconsistent, you overturn the table
    so the pieces are spread on the floor, shouting:

    "I don't want to play the game 'proving SR inconsistent' anymore,
    because mathematics (Lorentz) IS NOT PHYSICS. SO THERE"

    I accept your surrender.

    --
    Paul

    https://paulba.no/


    Stating it as simply as I can:

    1) Put a DIGITAL DISPLAY pointing to K origin, so it displays the time of the moving light clock tA.

    2) Now, while CALCULATING the time elapsed in the moving frame, being at the K origin, READ AND COMPARE the remote digital display.

    Two completely different values:

    - THE REAL ONE: What is observed in the digital display.

    - THE PSEUDO-SCIENTIFIC calculation: What the observer at rest in K origin get, when applying Lorentz.

    REALITY VS. MYSTICISM.

    Now tell me, Paul, what the FUCK is the value of the Lorentz's results in the real world? Do you dispute the reading of the digital display?

    Of course, you do. Your credence is in danger and you have to write a tirade of shitty, retorted reasons to defend your posture.

    But electronics KILLS relativity. Try something for your unpleasant butthurt.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paparios@21:1/5 to All on Sat Nov 11 10:00:00 2023
    El sábado, 11 de noviembre de 2023 a las 13:30:07 UTC-3, Richard Hertz escribió:

    Stating it as simply as I can:

    1) Put a DIGITAL DISPLAY pointing to K origin, so it displays the time of the moving light clock tA.


    What nonsense is that: "a DIGITAL DISPLAY pointing to K origin.....
    and then, "so it displays the time of the moving light clock tA"?


    2) Now, while CALCULATING the time elapsed in the moving frame, being at the K origin, READ AND COMPARE the remote digital display.

    Who is calculating and how that person "READ AND COMPARE the remote digital display"?

    Two completely different values:

    - THE REAL ONE: What is observed in the digital display.

    Observed where?

    You really are not good at this stuff. Find another hobby!!!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Laurence Clark Crossen@21:1/5 to Richard Hertz on Sat Nov 11 15:24:50 2023
    On Wednesday, November 8, 2023 at 1:56:18 PM UTC-8, Richard Hertz wrote:
    c = 299792458 m/s = 299.792458 m/μs

    Two perfect mirrors (A,B) are placed 149,896229 m apart, being A at the origin of the relatively moving frame K'.

    A photon, in the visible light range, is emitted from the mirror A (which also contains a clock) exactly towards mirror B.

    The photon bounces back at mirror B, towards mirror A. Its arrival from the roundtrip is marked in tA clock as being exactly 1.0000000 μs.

    This process continues forever, without any losses, while A clock is accumulating 1.0000000 μs counts.

    The arrangement in K' moves at v speed wrt the origin at K, where a clock tK is located (it also ticks at 1.0000000 μs.

    Both clocks (tK and tA) are reset to zero exactly when A pass by the origin K, and it forces the emission of the photon.

    Then, tK and tA are synchronized in the einstenian way.

    The speed v = 0.9 c = 269813212 m/s

    WHAT SR (LORENTZ) SAYS THAT HAPPENS AFTERWARDS.
    γ = 2.294157339

    LENGTH CONTRACTION (Horizontal light clock is perceived to run faster) http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c1

    x' = γ (x - vt)

    Δx' = AB AND Δx = AB/γ = 0.435889894 AB, as measured in the frame at rest. As both measurements are made simultaneously in the frame at rest, there is A PERCEIVED LENGTH CONTRACTION of AB in the moving frame.
    But the speed of light IS INVARIANT wrt to any frame, so IT'S PERCEIVED that clock tA IS RUNNING FASTER.

    The roundtrip of the photon is PERCEIVED to travel 2 x 0.435889894 AB = 0.871779789 x AB, which means that the clock's tick in the moving frame IS PERCEIVED TO TICK every 0.871779789 μs, instead of 1.00000000 μs.

    TIME DILATION (Horizontal light clock is perceived to run slower) http://hyperphysics.phy-astr.gsu.edu/hbase/Relativ/tdil.html#c2

    t' = γ (t - vx/c)

    Δt' = Δt/γ = 0.435889894 Δt (Time is PERCEIVED as running slower in the moving frame).

    For every 1.00000000 μs in the frame at rest, it's PERCEIVED that only 0.435889894 μs passed in the moving frame.

    The time measurements are made in the same location, so it doesn't affect the results.

    CONCLUSION: Using an horizontal light clock, the results of TIME FLOW due to length contraction and time dilation are in conflict. Clock tA is PERCEIVED to run faster or slower than clock tK, in the two different transforms.


    QUESTION: WHERE IS THE TRICK EMBEDDED IN THIS PARADOX?
    The trick is that both length contraction and time dilation are merely alterations of the units of measure. Such an alteration would result in two different speeds of light in the two frames.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Sat Nov 11 15:46:31 2023
    On Saturday, November 11, 2023 at 11:30:07 AM UTC-5, Richard Hertz wrote:
    On Saturday, November 11, 2023 at 9:48:27 AM UTC-3, Paul B. Andersen wrote:

    Let me RECAP:
    1. Photon leave A, Coordinates of A:
    In K': x₀' = 0, t₀' = 0
    In K: x₀ = 0, t₀ = 0

    No comment?
    You agree with what he said there?

    2: Photon back at A, Coordinates of A:
    In K': x₁' = 0, t₁' = 2L₀/c

    No comment?
    No rebuttal?

    In K:
    x₁ = γ(x₁'+ v⋅t₁') = γ(0 + v⋅2L₀/c) = (2L₀v/c)/√(1 −v²/c²)
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L₀/c + (v/c²)⋅L₀) = (2L₀/c)/√(1 −v²/c²)

    No comment?
    Usw...


    1) Put a DIGITAL DISPLAY pointing to K origin, so it displays the time of the moving light clock tA.

    Clock tA will always display its own value...thats what a clock does.
    You request now that it sends out an "image" of this value (these values). Thus, clock A will sequentially display 0,1,2, .... and the images of these will propagate
    through space for K (x=0) to receive. This is what you are saying, right?

    2) Now, while CALCULATING the time elapsed in the moving frame,

    No. forget about the word 'elapsed' since its ambiguous and not even needed. Lets just use the word *value*.
    Clock A sequentially logs/displays the values 0,1,2,3...(or any value for that matter).
    Here, the difference between two successive values are (N+1) - N = 1. Agreed? Anything to comment on here?

    being at the K origin, READ AND COMPARE the remote digital display.

    We went through this already, step by step, and you simply ignored all those steps and changed topic. Why?
    Here I go again, with your new scenario, using normalized units:
    Clock A (of frame K') travels at speed |v| = 0.5c = 1/2 to the right along K, the usual scenario.

    Clock A eventually indicates the value 1, say (or use t' to remain symbolic). That is, this event x'=0 & t' = 1 is labeled as E1 = (0, 1)'.
    Agree with this? yes/no/why?

    What does SR conclude concerning frame K:
    The LT's are x' = (x-vt)γ & t' = (t-xv)γ.

    A little algebra gives E1 = (√3/3, 2√3/3) ~ (0.577, 1.15), as observed/measured in K.
    IOW, The event E1 at the ruler mark x = 0.577 and the clock there (of K) indicates 1.15.
    This is where the image of "1" is generated.
    Agree with this? yes/no/why?

    Now you seem to ask a different question, namely what does the origin of K [labeling it o_K] see ?
    That is, if this image of "1" of clock A is sent to o_K, what is the value of o_K upon reception of "1" ?
    Well, the "1" is sent out from position x = √3/3 at time t = 2√3/3.
    This image (photon, say) travels at the SoL, thus takes a time interval of 𝛥 = √3/3 [recalling that c=1] to reach
    o_K. It is now therefore time "t + 𝛥t" = 2√3/3 + √3/3 = √3.
    That is, in K, the event o_K receiving the image "1" is (0, √3 ≈ 1.73). Agree with this? yes/no/why?

    Summarizing: In K, the image of "1" of clock A is generated at x mark of 0.577, where the clock there indicates 1.15, and
    this image attains o_K as the clock there indicates 1.73.

    Agree with this? yes/no/why?

    The above is the math, the predictions of SR.
    This is what you requested?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to rotchm on Sat Nov 11 22:44:50 2023
    On Sunday, 12 November 2023 at 00:46:34 UTC+1, rotchm wrote:

    You request now that it sends out an "image" of this value (these values). Thus, clock A will sequentially display 0,1,2, ....

    Have you ever seen a cklock, poor halfbrain?
    No, they don't display what you're gedankening.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Sun Nov 12 15:15:11 2023
    Den 11.11.2023 17:30, skrev Richard Hertz:
    On Saturday, November 11, 2023 at 9:48:27 AM UTC-3, Paul B. Andersen wrote:

    There is only one way to measure the round trip time of
    a moving light clock.

    That is to:
    1. Compare it with a coordinate clock in K at the instant
    the photon leave A, and:
    2. Compare it with a coordinate clock in K at the instant
    the photon is back at A after being reflected from B.

    Let me RECAP:
    1. Photon leave A, Coordinates of A:
    In K': x₀' = 0, t₀' = 0
    In K: x₀ = 0, t₀ = 0
    2: Photon back at A, Coordinates of A:
    In K': x₁' = 0, t₁' = 2L₀/c
    In K:
    x₁ = γ(x₁'+ v⋅t₁') = γ(0 + v⋅2L₀/c) = (2L₀v/c)/√(1 −v²/c²)
    t₁ = γ(t₁'+ (v/c²)⋅x₁') = γ(L₀/c + (v/c²)⋅L₀) = (2L₀/c)/√(1 −v²/c²)

    This means:
    Clock tA has advanced the proper time (t₁'-t₀') = 2L₀/c
    while the coordinate time of K has advanced
    (t₁-t₀) = (2L₀/c)/√(1 −v²/c²)

    In K the moving clock is measured to run slow by √(1 −v²/c²).

    -----


    Stating it as simply as I can:

    Yes, let's state the light clock thought experiment as simply as we can.

    The light clock is a theoretical clock in a thought experiment.
    A photon (or short light pulse) is bouncing force and back between
    two mirrors A and B. The distance between the mirrors is L.

    According to the second postulate of SR the round trip time of
    the photon measured in the light clock's rest frame K' will be
    t₁' = 2L₀/c

    A variant of the thought experiment is to let the light clock
    be oriented horizontally.
    And as shown above, SR predicts that the round trip time of
    the photon measured in the stationary frame K will be:
    t₁ = (2L₀/c)/√(1 −v²/c²)

    IT IS IMPOSSIBLE TO MAKE SR PREDICT ANYTHING ELSE.

    So back to the issue of the thread shown in the subject line:
    According to Richard Hertz there are "Conflicts in SR when
    using horizontal light clocks in the moving frame."

    Richard Hertz claims that SR can predict two different values
    for the round trip time in the "stationary frame".

    Let's see how he did it:

    Richards starts with the equation x' = γ(x - vt) and claims that
    LENGTH CONTRACTION leads to the conclusion that the round trip time
    measured (He uses "perceived") in the stationary frame K is (2L₀/c)/γ,
    which means that the light clock is perceived to run fast, not slow.

    He hasn't calculated the length contraction, though. You can't do that
    from the equation x' = γ(x - vt) alone. But he knows that according
    to SR, the Lorentz contraction is L'= L₀/γ.

    He has made the very naive calculation that since the length is
    contracted by 1/γ in K, then the round trip time in K must be (2L₀/γ)/c. This is horribly wrong, because the mirrors are moving in K.
    (And this is the only calculation he has made!)

    Here is the correct calculation of the round trip time based
    on the correct Lorentz contraction L' = L₀/γ:

    In the following is tf the transit time from A to B,
    and tb is the transit time from B to A.

    |<--------------c⋅tf---------------->| |<----------L'------------->|<-v⋅tf->|

    c⋅tf = L' + v⋅tf => tf = L'/(c-v)

    |<-----------L'------------>|
    |<--------c⋅tb----->|<-v⋅tb->|

    L' = c⋅tb + v⋅tb => tb = L'/(c+v)

    t₁ = tf + tb = 2L'⋅c/(c² + v²) = (2L'/c)⋅γ² = (2L₀/c)⋅γ

    Which is correct, and the same as predicted by the Lorentz transform.

    -------------------

    Then he starts with the equation t' = γ (t - vx/c)
    and claim that TIME DILATION leads to the conclusion that the round trip
    time measured in the stationary frame K is (2L₀/c)⋅γ.

    Which is correct, and the same as predicted by the Lorentz transform.

    Again, he hasn't calculated the time dilation from the equation
    t' = γ (t - vx/c), but he knows that the time dilation according
    to SR is Δt' = Δt/γ. And since this IS time dilation, he gets it right.

    --------------

    So you see, Richard, when the only calculation you made is corrected,
    you have not proved that SR is inconsistent, but have given two
    calculations which confirm SR.

    So we can conclude that SR is consistent! Can't we?


    The following appears very confused.
    Are you really serious, or are you joking.



    1) Put a DIGITAL DISPLAY pointing to K origin, so it displays the time of the moving light clock tA.

    2) Now, while CALCULATING the time elapsed in the moving frame, being at the K origin, READ AND COMPARE the remote digital display.

    Two completely different values:

    - THE REAL ONE: What is observed in the digital display.

    There is no such thing as a _real_ light clock. Of obvious reasons!
    And you will put a digital display on it to see what it _really_ shows!

    I hope for your sake that you are joking.
    (But I don't believe so!)


    - THE PSEUDO-SCIENTIFIC calculation: What the observer at rest in K origin get, when applying Lorentz.

    REALITY VS. MYSTICISM.

    Now tell me, Paul, what the FUCK is the value of the Lorentz's results in the real world? Do you dispute the reading of the digital display?

    Of course, you do. Your credence is in danger and you have to write a tirade of shitty, retorted reasons to defend your posture.

    But electronics KILLS relativity. Try something for your unpleasant butthurt.


    Electronics KILLS thought experiments!

    One of your better! :-D

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Sun Nov 12 09:47:57 2023
    On Sunday, 12 November 2023 at 15:13:30 UTC+1, Paul B. Andersen wrote:


    So we can conclude that SR is consistent! Can't we?

    Oh, of course you can, nothing else is expected from
    a fanatic worshipper idiot. But the proof that it isn't
    was presented on this NG many times.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Paul B. Andersen on Sun Nov 12 14:12:19 2023
    On Sunday, November 12, 2023 at 11:13:30 AM UTC-3, Paul B. Andersen wrote:
    Den 11.11.2023 17:30, skrev Richard Hertz:

    <snip>

    So we can conclude that SR is consistent! Can't we?

    NO, doctrine-blinded and religion-clothed-brain-arteries, NO!

    SR is a deceptive pseudo-science, which FORCES YOU TO BELIEVE OR ELSE.

    The time registered in the moving frame by anything (human, ghost or instruments) IS IMMUNE to your stupid Lorentz equations. Time flows normally there.

    Throw away the light clock and use a hydrogen maser atomic clock instead. Don't use the fucking giant digital display.
    Use a 1-way microwave link to transmit to the origin the DIGITAL READOUT of the moving clock, up to picoseconds resolution.

    At origin of K compare the output of the encoded data with the LOCAL CLOCK tK: THEY ARE THE SAME!

    It's the STUPID LORENTZ EQUATION THAT FORCES YOU TO BELIEVE THAT THEY ARE DIFFERENT, BECAUSE YOU ARE FORCED TO BELIEVE!

    That's the tragedy of this shitty pseudo-science: Took a mind like yours, that COULD HAVE BEEN useful before SR absorption of your reasoning,
    and converted it in something small, with fewer capabilities than the brain OF A FUCKING PARROT!

    I feel sorry for your wasted life. Now it's too late for you. Deal with it.





    The following appears very confused.
    Are you really serious, or are you joking.

    1) Put a DIGITAL DISPLAY pointing to K origin, so it displays the time of the moving light clock tA.

    2) Now, while CALCULATING the time elapsed in the moving frame, being at the K origin, READ AND COMPARE the remote digital display.

    Two completely different values:

    - THE REAL ONE: What is observed in the digital display.
    There is no such thing as a _real_ light clock. Of obvious reasons!
    And you will put a digital display on it to see what it _really_ shows!

    I hope for your sake that you are joking.
    (But I don't believe so!)


    - THE PSEUDO-SCIENTIFIC calculation: What the observer at rest in K origin get, when applying Lorentz.

    REALITY VS. MYSTICISM.

    Now tell me, Paul, what the FUCK is the value of the Lorentz's results in the real world? Do you dispute the reading of the digital display?

    Of course, you do. Your credence is in danger and you have to write a tirade of shitty, retorted reasons to defend your posture.

    But electronics KILLS relativity. Try something for your unpleasant butthurt.

    Electronics KILLS thought experiments!

    One of your better! :-D

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Sun Nov 12 16:07:42 2023
    On Sunday, November 12, 2023 at 5:12:21 PM UTC-5, Richard Hertz wrote:
    On Sunday, November 12, 2023 at 11:13:30 AM UTC-3, Paul B. Andersen wrote:

    So we can conclude that SR is consistent! Can't we?
    NO, doctrine-blinded and religion-clothed-brain-arteries, NO!

    Then show us what step, what calculation was wrong.
    He (and I) showed you in very simple algebra steps what SR predicts.
    And all you can say is "NO, doctrine-blinded and religion-clothed-brain-arteries, NO! " ?
    You cant point out what step was wrong... you only rant.

    SR is a deceptive pseudo-science, which FORCES YOU TO BELIEVE OR ELSE.

    More rants. No counterarguments.

    The time registered in the moving frame by anything (human, ghost or instruments)
    IS IMMUNE to your stupid Lorentz equations. Time flows normally there.

    So? Again, point out which calculation was wrong.


    Throw away the light clock and use a hydrogen maser atomic clock instead.

    But YOU invoked the light clock. See your OP and title!!

    Don't use the fucking giant digital display.

    But YOU invoked it !!

    Use a 1-way microwave link to transmit to the origin the DIGITAL READOUT of the moving clock,
    up to picoseconds resolution.

    Such exps are routinely done. The conclusions (values obtained) are the same as SR's predictions.
    Are you now a reality denier?

    At origin of K compare the output of the encoded data with the LOCAL CLOCK tK: THEY ARE THE SAME!

    No they are not. Such exps are routinely done and the results are that tk & image are different.

    It's the STUPID LORENTZ EQUATION THAT FORCES YOU TO BELIEVE THAT THEY ARE DIFFERENT,

    No. SR makes the predictions. The actual exps "force" us to believe.

    <rest of rants and empirics denying snipped>

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to rotchm on Sun Nov 12 23:03:53 2023
    On Monday, 13 November 2023 at 01:07:44 UTC+1, rotchm wrote:
    On Sunday, November 12, 2023 at 5:12:21 PM UTC-5, Richard Hertz wrote:
    On Sunday, November 12, 2023 at 11:13:30 AM UTC-3, Paul B. Andersen wrote:

    So we can conclude that SR is consistent! Can't we?
    NO, doctrine-blinded and religion-clothed-brain-arteries, NO!
    Then show us what step, what calculation was wrong.
    He (and I) showed you in very simple algebra steps what SR predicts.

    What your Shit predicted was inconsistent, could be anything.


    No. SR makes the predictions. The actual exps "force" us to believe.

    In the meantime in the real world, however, forbidden
    by your insane bunch "improper" clocks keep measuring t'=t,
    just like all serious clocks always did.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Mon Nov 13 11:08:36 2023
    Den 12.11.2023 23:12, skrev Richard Hertz:
    On Sunday, November 12, 2023 at 11:13:30 AM UTC-3, Paul B. Andersen wrote:
    Den 11.11.2023 17:30, skrev Richard Hertz:
    On Saturday, November 11, 2023 at 9:48:27 AM UTC-3, Paul B. Andersen wrote:

    So back to the issue of the thread shown in the subject line:
    According to Richard Hertz there are "Conflicts in SR when
    using horizontal light clocks in the moving frame."

    Richard Hertz claims that SR can predict two different values
    for the round trip time in the "stationary frame".

    Let's see how he did it:

    Richards starts with the equation x' = γ(x - vt) and claims that
    LENGTH CONTRACTION leads to the conclusion that the round trip time measured (He uses "perceived") in the stationary frame K is (2L₀/c)/γ,
    which means that the light clock is perceived to run fast, not slow.

    He hasn't calculated the length contraction, though. You can't do that
    from the equation x' = γ(x - vt) alone. But he knows that according
    to SR, the Lorentz contraction is L'= L₀/γ.

    He has made the very naive calculation that since the length is contracted by 1/γ in K, then the round trip time in K must be (2L₀/γ)/c.
    This is horribly wrong, because the mirrors are moving in K.
    (And this is the only calculation he has made!)

    Here is the correct calculation of the round trip time based
    on the correct Lorentz contraction L' = L₀/γ:

    In the following is tf the transit time from A to B,
    and tb is the transit time from B to A.

    |<--------------c⋅tf---------------->|
    |<----------L'------------->|<-v⋅tf->|

    c⋅tf = L' + v⋅tf => tf = L'/(c-v)

    |<-----------L'------------>|
    |<--------c⋅tb----->|<-v⋅tb->|

    L' = c⋅tb + v⋅tb => tb = L'/(c+v)

    t₁ = tf + tb = 2L'⋅c/(c² + v²) = (2L'/c)⋅γ² = (2L₀/c)⋅γ

    Which is correct, and the same as predicted by the Lorentz transform.

    -------------------

    Then he starts with the equation t' = γ (t - vx/c)
    and claim that TIME DILATION leads to the conclusion that the round trip time measured in the stationary frame K is (2L₀/c)⋅γ.

    Which is correct, and the same as predicted by the Lorentz transform.

    Again, he hasn't calculated the time dilation from the equation
    t' = γ (t - vx/c), but he knows that the time dilation according
    to SR is Δt' = Δt/γ. And since this IS time dilation, he gets it right. >>
    So we can conclude that SR is consistent! Can't we?


    NO, doctrine-blinded and religion-clothed-brain-arteries, NO!

    SR is a deceptive pseudo-science, which FORCES YOU TO BELIEVE OR ELSE.

    May I remind you: Your opinion of SR is irrelevant.

    The issue is if SR is inconsistent.
    You believed you had proved SR inconsistent, but as I have shown
    above, you only demonstrated your poor mathematical skills.

    SR is a consistent theory, and the only way you can falsify it
    is by performing an experiments which prove its predictions wrong.

    But you have to PERFORM the experiment in the real word.

    Claiming that the experiment below MUST show what you think
    it will show is pathetic.

    And a little funny. :-D


    The time registered in the moving frame by anything (human, ghost or instruments) IS IMMUNE to your stupid Lorentz equations. Time flows normally there.

    Throw away the light clock and use a hydrogen maser atomic clock instead. Don't use the fucking giant digital display.
    Use a 1-way microwave link to transmit to the origin the DIGITAL READOUT of the moving clock, up to picoseconds resolution.

    At origin of K compare the output of the encoded data with the LOCAL CLOCK tK: THEY ARE THE SAME!

    So there is no delay in the microwave link?
    Or will you compensate for the unknown distance and
    unknown speed of the moving clock?


    It's the STUPID LORENTZ EQUATION THAT FORCES YOU TO BELIEVE THAT THEY ARE DIFFERENT, BECAUSE YOU ARE FORCED TO BELIEVE!

    Real several experiments with atomic clock are performed.
    The designers of the experiments were smarter that you,
    so the experiments worked.

    https://paulba.no/paper/Ives_Stilwell.pdf https://paulba.no/paper/Hafele_Keating.pdf
    https://paulba.no/paper/Alley.pdf
    see pages 708-716 https://paulba.no/paper/Initial_results_of_GPS_satellite_1977.pdf https://paulba.no/paper/Vessot.pdf

    Even you know what these experiment show.
    You can, and will, kick and scream and claim that
    the experiments are faked.

    It will only make you look ignorant and pathetic.


    That's the tragedy of this shitty pseudo-science: Took a mind like yours, that COULD HAVE BEEN useful before SR absorption of your reasoning,
    and converted it in something small, with fewer capabilities than the brain OF A FUCKING PARROT!

    I feel sorry for your wasted life. Now it's too late for you. Deal with it.

    Richard, you are not shouting loud enough.
    Use more capitals, and more profanities.
    One FUCKING PARROT won't do!

    Are you getting weak in your old days?

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Mon Nov 13 02:36:45 2023
    On Monday, 13 November 2023 at 11:06:52 UTC+1, Paul B. Andersen wrote:
    Den 12.11.2023 23:12, skrev Richard Hertz:
    On Sunday, November 12, 2023 at 11:13:30 AM UTC-3, Paul B. Andersen wrote:
    Den 11.11.2023 17:30, skrev Richard Hertz:
    On Saturday, November 11, 2023 at 9:48:27 AM UTC-3, Paul B. Andersen wrote:

    So back to the issue of the thread shown in the subject line:
    According to Richard Hertz there are "Conflicts in SR when
    using horizontal light clocks in the moving frame."

    Richard Hertz claims that SR can predict two different values
    for the round trip time in the "stationary frame".

    Let's see how he did it:

    Richards starts with the equation x' = γ(x - vt) and claims that
    LENGTH CONTRACTION leads to the conclusion that the round trip time measured (He uses "perceived") in the stationary frame K is (2L₀/c)/γ,
    which means that the light clock is perceived to run fast, not slow.

    He hasn't calculated the length contraction, though. You can't do that
    from the equation x' = γ(x - vt) alone. But he knows that according
    to SR, the Lorentz contraction is L'= L₀/γ.

    He has made the very naive calculation that since the length is contracted by 1/γ in K, then the round trip time in K must be (2L₀/γ)/c.
    This is horribly wrong, because the mirrors are moving in K.
    (And this is the only calculation he has made!)

    Here is the correct calculation of the round trip time based
    on the correct Lorentz contraction L' = L₀/γ:

    In the following is tf the transit time from A to B,
    and tb is the transit time from B to A.

    |<--------------c⋅tf---------------->|
    |<----------L'------------->|<-v⋅tf->|

    c⋅tf = L' + v⋅tf => tf = L'/(c-v)

    |<-----------L'------------>|
    |<--------c⋅tb----->|<-v⋅tb->|

    L' = c⋅tb + v⋅tb => tb = L'/(c+v)

    t₁ = tf + tb = 2L'⋅c/(c² + v²) = (2L'/c)⋅γ² = (2L₀/c)⋅γ

    Which is correct, and the same as predicted by the Lorentz transform.

    -------------------

    Then he starts with the equation t' = γ (t - vx/c)
    and claim that TIME DILATION leads to the conclusion that the round trip time measured in the stationary frame K is (2L₀/c)⋅γ.

    Which is correct, and the same as predicted by the Lorentz transform.

    Again, he hasn't calculated the time dilation from the equation
    t' = γ (t - vx/c), but he knows that the time dilation according
    to SR is Δt' = Δt/γ. And since this IS time dilation, he gets it right.

    So we can conclude that SR is consistent! Can't we?


    NO, doctrine-blinded and religion-clothed-brain-arteries, NO!

    SR is a deceptive pseudo-science, which FORCES YOU TO BELIEVE OR ELSE.
    May I remind you: Your opinion of SR is irrelevant.

    The issue is if SR is inconsistent.
    You believed you had proved SR inconsistent, but as I have shown
    above, you only demonstrated your poor mathematical skills.

    SR is a consistent theory,

    No, it is not, the proof was demonstrated here
    many times.


    and the only way you can falsify it
    is by performing an experiments which prove its predictions wrong.

    And in the meantime in the real world, forbidden
    by your bunch of idiots "improper" clocks keep
    measuring t'=t, just like all serious clocks
    always did.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lou@21:1/5 to Paul B. Andersen on Mon Nov 13 05:36:20 2023
    On Monday, 13 November 2023 at 10:06:52 UTC, Paul B. Andersen wrote:
    Den 12.11.2023 23:12, skrev Richard Hertz:
    On Sunday, November 12, 2023 at 11:13:30 AM UTC-3, Paul B. Andersen wrote:
    Den 11.11.2023 17:30, skrev Richard Hertz:
    On Saturday, November 11, 2023 at 9:48:27 AM UTC-3, Paul B. Andersen wrote:

    So back to the issue of the thread shown in the subject line:
    According to Richard Hertz there are "Conflicts in SR when
    using horizontal light clocks in the moving frame."

    Richard Hertz claims that SR can predict two different values
    for the round trip time in the "stationary frame".

    Let's see how he did it:

    Richards starts with the equation x' = γ(x - vt) and claims that
    LENGTH CONTRACTION leads to the conclusion that the round trip time measured (He uses "perceived") in the stationary frame K is (2L₀/c)/γ,
    which means that the light clock is perceived to run fast, not slow.

    He hasn't calculated the length contraction, though. You can't do that
    from the equation x' = γ(x - vt) alone. But he knows that according
    to SR, the Lorentz contraction is L'= L₀/γ.

    He has made the very naive calculation that since the length is contracted by 1/γ in K, then the round trip time in K must be (2L₀/γ)/c.
    This is horribly wrong, because the mirrors are moving in K.
    (And this is the only calculation he has made!)

    Here is the correct calculation of the round trip time based
    on the correct Lorentz contraction L' = L₀/γ:

    In the following is tf the transit time from A to B,
    and tb is the transit time from B to A.

    |<--------------c⋅tf---------------->|
    |<----------L'------------->|<-v⋅tf->|

    c⋅tf = L' + v⋅tf => tf = L'/(c-v)

    |<-----------L'------------>|
    |<--------c⋅tb----->|<-v⋅tb->|

    L' = c⋅tb + v⋅tb => tb = L'/(c+v)

    t₁ = tf + tb = 2L'⋅c/(c² + v²) = (2L'/c)⋅γ² = (2L₀/c)⋅γ

    Which is correct, and the same as predicted by the Lorentz transform.

    -------------------

    Then he starts with the equation t' = γ (t - vx/c)
    and claim that TIME DILATION leads to the conclusion that the round trip time measured in the stationary frame K is (2L₀/c)⋅γ.

    Which is correct, and the same as predicted by the Lorentz transform.

    Again, he hasn't calculated the time dilation from the equation
    t' = γ (t - vx/c), but he knows that the time dilation according
    to SR is Δt' = Δt/γ. And since this IS time dilation, he gets it right.

    So we can conclude that SR is consistent! Can't we?


    NO, doctrine-blinded and religion-clothed-brain-arteries, NO!

    SR is a deceptive pseudo-science, which FORCES YOU TO BELIEVE OR ELSE.
    May I remind you: Your opinion of SR is irrelevant.

    The issue is if SR is inconsistent.
    You believed you had proved SR inconsistent, but as I have shown
    above, you only demonstrated your poor mathematical skills.

    SR is a consistent theory, and the only way you can falsify it
    is by performing an experiments which prove its predictions wrong.

    But you have to PERFORM the experiment in the real word.

    Claiming that the experiment below MUST show what you think
    it will show is pathetic.

    And a little funny. :-D

    The time registered in the moving frame by anything (human, ghost or instruments) IS IMMUNE to your stupid Lorentz equations. Time flows normally there.

    Throw away the light clock and use a hydrogen maser atomic clock instead. Don't use the fucking giant digital display.
    Use a 1-way microwave link to transmit to the origin the DIGITAL READOUT of the moving clock, up to picoseconds resolution.

    At origin of K compare the output of the encoded data with the LOCAL CLOCK tK: THEY ARE THE SAME!
    So there is no delay in the microwave link?
    Or will you compensate for the unknown distance and
    unknown speed of the moving clock?

    It's the STUPID LORENTZ EQUATION THAT FORCES YOU TO BELIEVE THAT THEY ARE DIFFERENT, BECAUSE YOU ARE FORCED TO BELIEVE!
    Real several experiments with atomic clock are performed.
    The designers of the experiments were smarter that you,
    so the experiments worked.

    https://paulba.no/paper/Ives_Stilwell.pdf https://paulba.no/paper/Hafele_Keating.pdf
    https://paulba.no/paper/Alley.pdf
    see pages 708-716 https://paulba.no/paper/Initial_results_of_GPS_satellite_1977.pdf https://paulba.no/paper/Vessot.pdf

    Even you know what these experiment show.
    You can, and will, kick and scream and claim that
    the experiments are faked.

    It will only make you look ignorant and pathetic.

    That's the tragedy of this shitty pseudo-science: Took a mind like yours, that COULD HAVE BEEN useful before SR absorption of your reasoning,
    and converted it in something small, with fewer capabilities than the brain OF A FUCKING PARROT!

    I feel sorry for your wasted life. Now it's too late for you. Deal with it.
    Richard, you are not shouting loud enough.
    Use more capitals, and more profanities.
    One FUCKING PARROT won't do!

    Are you getting weak in your old days?


    In your website table you have the following data.

    r rate
    ----------------------
    10R 1.000000000626
    9R 1.000000000618
    8R 1.000000000608
    7R 1.000000000596
    6R 1.000000000579
    5R 1.000000000556
    4R 1.000000000522
    3R 1.000000000464
    2R 1.000000000348
    1R 1.000000000000

    https://paulba.no/temp/ClockRate.pdf

    Is that picoseconds gained per second?
    How would you calculate what frequency the rest frame
    (1R) c-133 atom frequency of 9192661770 hz would be at 2R?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Mon Nov 13 10:55:54 2023
    On Monday, 13 November 2023 at 19:36:49 UTC+1, Paul B. Andersen wrote:

    the cesium-133 atom is 9192631770 Hz by definition.
    Everywhere. Always.
    Fact! Nothing to discuss.

    Everywhere, always in your gedankenwelt, poor
    halfbrain. Anyone can check GPS, outside
    your moronic church this definition is pissed at,
    Everywhere, always, the fact, nothing to discuss.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Mon Nov 13 19:38:32 2023
    Den 13.11.2023 14:36, skrev Lou:

    In your website table you have the following data.

    r rate
    ----------------------
    10R 1.000000000626
    9R 1.000000000618
    8R 1.000000000608
    7R 1.000000000596
    6R 1.000000000579
    5R 1.000000000556
    4R 1.000000000522
    3R 1.000000000464
    2R 1.000000000348
    1R 1.000000000000

    https://paulba.no/temp/ClockRate.pdf

    Is that picoseconds gained per second?

    Read the statement above the table:
    “r" is the distance from the clock to the centre of the Earth.
    "R" is the radius of the Earth.
    The clock transmits a frequency 1 Hz,
    "rate" is the frequency received on the ground.

    Gravitational Doppler shift, Gravitational blue shift.

    How would you calculate what frequency the rest frame
    (1R) c-133 atom frequency of 9192661770 hz would be at 2R?

    It can't be "calculated".
    The frequency of the photon associated with
    the ground-state hyperfine transition of
    the cesium-133 atom is 9192631770 Hz by definition.
    Everywhere. Always.

    Fact! Nothing to discuss.

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Lou on Mon Nov 13 11:59:42 2023
    On Monday, 13 November 2023 at 20:36:42 UTC+1, Lou wrote:
    On Monday, 13 November 2023 at 18:36:49 UTC, Paul B. Andersen wrote:
    Den 13.11.2023 14:36, skrev Lou:

    In your website table you have the following data.

    r rate
    ----------------------
    10R 1.000000000626
    9R 1.000000000618
    8R 1.000000000608
    7R 1.000000000596
    6R 1.000000000579
    5R 1.000000000556
    4R 1.000000000522
    3R 1.000000000464
    2R 1.000000000348
    1R 1.000000000000

    https://paulba.no/temp/ClockRate.pdf

    Is that picoseconds gained per second?
    Read the statement above the table:
    “r" is the distance from the clock to the centre of the Earth.
    "R" is the radius of the Earth.
    The clock transmits a frequency 1 Hz,
    "rate" is the frequency received on the ground.

    Gravitational Doppler shift, Gravitational blue shift.
    How would you calculate what frequency the rest frame
    (1R) c-133 atom frequency of 9192661770 hz would be at 2R?
    It can't be "calculated".
    The frequency of the photon associated with
    the ground-state hyperfine transition of
    the cesium-133 atom is 9192631770 Hz by definition.
    Everywhere. Always.

    Fact! Nothing to discuss.

    Yes I realise that under GR the rule is c-133 frequency never changes.
    Under GR its always everywhere the same. But

    But a relativistic idiot can't understand that GPS
    is ruled by common sense (this collection of prejudices),
    not by Giant Guru and his minions.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lou@21:1/5 to Paul B. Andersen on Mon Nov 13 11:36:40 2023
    On Monday, 13 November 2023 at 18:36:49 UTC, Paul B. Andersen wrote:
    Den 13.11.2023 14:36, skrev Lou:

    In your website table you have the following data.

    r rate
    ----------------------
    10R 1.000000000626
    9R 1.000000000618
    8R 1.000000000608
    7R 1.000000000596
    6R 1.000000000579
    5R 1.000000000556
    4R 1.000000000522
    3R 1.000000000464
    2R 1.000000000348
    1R 1.000000000000

    https://paulba.no/temp/ClockRate.pdf

    Is that picoseconds gained per second?
    Read the statement above the table:
    “r" is the distance from the clock to the centre of the Earth.
    "R" is the radius of the Earth.
    The clock transmits a frequency 1 Hz,
    "rate" is the frequency received on the ground.

    Gravitational Doppler shift, Gravitational blue shift.
    How would you calculate what frequency the rest frame
    (1R) c-133 atom frequency of 9192661770 hz would be at 2R?
    It can't be "calculated".
    The frequency of the photon associated with
    the ground-state hyperfine transition of
    the cesium-133 atom is 9192631770 Hz by definition.
    Everywhere. Always.

    Fact! Nothing to discuss.

    Yes I realise that under GR the rule is c-133 frequency never changes.
    Under GR its always everywhere the same. But you say a broadcast
    frequency can appear to be blueshifted to an observer on the ground
    and I’m trying to find out what that blueshifted f would be to an
    earth ground observer.
    So if it were possible to observe, from the ground, a clock orbiting at 2R. What frequency would 9192631770 Hz on a clock at 2R be blueshifted to
    an observer on the ground be? Would it appear to a ground observer
    to be 9192631773.48hz ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Paul B. Andersen on Mon Nov 13 21:10:13 2023
    On Monday, November 13, 2023 at 3:36:49 PM UTC-3, Paul B. Andersen wrote:
    Den 13.11.2023 14:36, skrev Lou:

    In your website table you have the following data.

    r rate
    ----------------------
    10R 1.000000000626
    9R 1.000000000618
    8R 1.000000000608
    7R 1.000000000596
    6R 1.000000000579
    5R 1.000000000556
    4R 1.000000000522
    3R 1.000000000464
    2R 1.000000000348
    1R 1.000000000000

    https://paulba.no/temp/ClockRate.pdf

    Is that picoseconds gained per second?
    Read the statement above the table:
    “r" is the distance from the clock to the centre of the Earth.
    "R" is the radius of the Earth.
    The clock transmits a frequency 1 Hz,
    "rate" is the frequency received on the ground.

    Gravitational Doppler shift, Gravitational blue shift.
    How would you calculate what frequency the rest frame
    (1R) c-133 atom frequency of 9192661770 hz would be at 2R?
    It can't be "calculated".
    The frequency of the photon associated with
    the ground-state hyperfine transition of
    the cesium-133 atom is 9192631770 Hz by definition.
    Everywhere. Always.

    Fact! Nothing to discuss.

    --
    Paul

    https://paulba.no/


    You are full of crap, as always.

    First, you pollute this thread arguing nonsense around my OP.

    Now you introduce more crap, playing with Einstein's 1911 crap. Why don't you take a rest?

    You introduce gravitational time dilation playing with 1911 Einstein's shit:

    Δf/f = ΔT/T = Δɸ/c = -GMₑ/c² (1/r - 1/rₑ) = - 4.4350E-03 ((1/r - 1/6378136.55)

    Then, normalize (for r = rₑ), ΔT/T = 1.00000000, instead of 0.000000, and call it 1 SECOND.

    Finally, you ASSERT THAT time dilation (without ANY PROOF) occurs as the clock raises N. rₑ units from above Earth's surface:

    ΔT(N) = Δɸ/c =1.000000000 - GMₑ/rₑc² (1/N - 1)

    What generates

    Te +ΔT(1) = 1.00000000000000 sec
    Te +ΔT(2) = 1.00000000034767 sec
    Te +ΔT(3) = 1.00000000046357 sec
    Te +ΔT(4) = 1.00000000052151 sec
    Te +ΔT(5) = 1.00000000055628 sec
    Te +ΔT(6) = 1.00000000057946 sec
    Te +ΔT(7) = 1.00000000059601 sec
    Te +ΔT(8) = 1.00000000060843 sec
    Te +ΔT(9) = 1.00000000061809 sec
    Te +ΔT(10) = 1.00000000062581 sec


    Your manipulation of the 1911 Einstein's STUPID FORMULA to express gravitational time dilation is, to the least, disgusting and repulsive.

    Another proof that you are a very sick, deceitful relativist, who only can live by disseminating crappy and FALSE assertions about relativity.

    Retire now from this SERIOUS

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Tue Nov 14 12:02:33 2023
    Den 13.11.2023 20:36, skrev Lou:
    On Monday, 13 November 2023 at 18:36:49 UTC, Paul B. Andersen wrote:
    Den 13.11.2023 14:36, skrev Lou:

    In your website table you have the following data.

    r rate
    ----------------------
    10R 1.000000000626
    9R 1.000000000618
    8R 1.000000000608
    7R 1.000000000596
    6R 1.000000000579
    5R 1.000000000556
    4R 1.000000000522
    3R 1.000000000464
    2R 1.000000000348
    1R 1.000000000000

    https://paulba.no/temp/ClockRate.pdf

    The headline:
    Gravitational blue shift of EM radiation from a stationary
    clock in the non rotating Earth centred frame of reference.

    Read the statement above the table:

    Read it again:

    “r" is the distance from the clock to the centre of the Earth.
    "R" is the radius of the Earth.
    The clock transmits a frequency 1 Hz,
    "rate" is the frequency received on the ground.

    Gravitational Doppler shift, Gravitational blue shift.

    How would you calculate what frequency the rest frame
    (1R) c-133 atom frequency of 9192661770 hz would be at 2R?

    It can't be "calculated".
    The frequency of the photon associated with
    the ground-state hyperfine transition of
    the cesium-133 atom is 9192631770 Hz by definition.
    Everywhere. Always.

    Fact! Nothing to discuss.


    Yes I realise that under GR the rule is c-133 frequency never changes.
    Under GR its always everywhere the same.

    Not "under GR". In the real world. Everywhere. Always. By definition!

    But you say a broadcast
    frequency can appear to be blueshifted to an observer on the ground
    and I’m trying to find out what that blueshifted f would be to an
    earth ground observer.

    Not "can appear to be". IS blue shifted. Measured in the real world.

    https://paulba.no/paper/Pound&Rebka.pdf

    If the receiver is above the sender, it is gravitational red shift.

    So if it were possible to observe, from the ground, a clock orbiting at 2R.

    Not orbiting! Stationary in the ECI frame at 2R.

    What frequency would 9192631770 Hz on a clock at 2R be blueshifted to
    an observer on the ground be? Would it appear to a ground observer
    to be 9192631773.48hz ?

    The frequency of the received signal on the ground would
    be gravitational blue shifted. That's a kind of Doppler shift.

    That you hear the train-whistle change frequency when
    the train passes you doesn't mean that the emitted
    frequency has changed.

    f_received = 1.000000000348⋅f_transmitted = 9192631773.1990 Hz

    BECAUSE f_transmitted = 9192631770 Hz.

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Tue Nov 14 03:46:43 2023
    On Tuesday, 14 November 2023 at 12:00:48 UTC+1, Paul B. Andersen wrote:

    Yes I realise that under GR the rule is c-133 frequency never changes. Under GR its always everywhere the same.
    Not "under GR". In the real world. Everywhere. Always. By definition!

    Do you think sharks will start eating grass
    if some idiot (just like you) define a shark as
    4-leg grass eater? Definitions have a power,
    indeed, but not that power, poor halfbrain,
    sorry.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lou@21:1/5 to All on Tue Nov 14 06:01:55 2023
    Yes I realise that under GR the rule is c-133 frequency never changes. Under GR its always everywhere the same.
    Not "under GR". In the real world. Everywhere. Always. By definition!
    But you say a broadcast
    frequency can appear to be blueshifted to an observer on the ground
    and I’m trying to find out what that blueshifted f would be to an
    earth ground observer.
    Not "can appear to be". IS blue shifted. Measured in the real world.

    https://paulba.no/paper/Pound&Rebka.pdf

    If the receiver is above the sender, it is gravitational red shift.
    So if it were possible to observe, from the ground, a clock orbiting at 2R.
    Not orbiting! Stationary in the ECI frame at 2R.
    What frequency would 9192631770 Hz on a clock at 2R be blueshifted to
    an observer on the ground be? Would it appear to a ground observer
    to be 9192631773.48hz ?
    The frequency of the received signal on the ground would
    be gravitational blue shifted. That's a kind of Doppler shift.

    That you hear the train-whistle change frequency when
    the train passes you doesn't mean that the emitted
    frequency has changed.

    f_received = 1.000000000348⋅f_transmitted = 9192631773.1990 Hz

    BECAUSE f_transmitted = 9192631770 Hz.


    Interesting thanks. But are you sure it’s correct to convert the gps signal frequency gain of 348 pico seconds at 10.23 Mhz to the gain of 3.19 Hz
    for the recieved C-133 frequency using that method?

    Because if I try your same formula for the transmitted f of 10.23MHz, I
    get the following:
    f_received = 1.000000000348 x 10.23Mhz =10230000.0036 hz
    I would have thought it should be 10230000.0038 hz.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From rotchm@21:1/5 to Richard Hertz on Tue Nov 14 05:38:12 2023
    On Tuesday, November 14, 2023 at 12:10:16 AM UTC-5, Richard Hertz wrote:
    On Monday, November 13, 2023 at 3:36:49 PM UTC-3, Paul B. Andersen wrote:

    First, you pollute this thread arguing nonsense around my OP.
    Now you introduce more crap, playing with Einstein's 1911 crap. Why don't you take a rest?
    You introduce gravitational time dilation playing with 1911 Einstein's shit:

    Off topic.

    Stick to the OP topic.
    Oh, true, you ran away from it. We have cornered you and you havent presented any counterargument whatsoever.
    You havent answered one question psoed to you and havent answered one clarification posed to you.
    You just run away or change subject. Now, isn't that the behavior of a crank? Yes...you realize now you have become one...
    Perhaps old age has crept up on you, but something is definitely wrong with you.
    Even if you dont believe it, look into it.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dono.@21:1/5 to Richard Hertz on Tue Nov 14 12:04:55 2023
    On Monday, November 13, 2023 at 9:10:16 PM UTC-8, Richard Hertz wrote:
    snip fresh imbecilities

    Do you need a shovel?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to Who on Tue Nov 14 20:35:45 2023
    Den 14.11.2023 15:01, skrev Lou:

    Who wrote what? DON'T SNIP THE ATTRIBUTIONS!

    Yes I realise that under GR the rule is c-133 frequency never changes.
    Under GR its always everywhere the same.

    Not "under GR". In the real world. Everywhere. Always. By definition!

    But you say a broadcast
    frequency can appear to be blueshifted to an observer on the ground
    and I’m trying to find out what that blueshifted f would be to an
    earth ground observer.

    Not "can appear to be". IS blue shifted. Measured in the real world.

    https://paulba.no/paper/Pound&Rebka.pdf

    If the receiver is above the sender, it is gravitational red shift.

    So if it were possible to observe, from the ground, a clock orbiting at 2R. >> Not orbiting! Stationary in the ECI frame at 2R.
    What frequency would 9192631770 Hz on a clock at 2R be blueshifted to
    an observer on the ground be? Would it appear to a ground observer
    to be 9192631773.48hz ?

    The frequency of the received signal on the ground would
    be gravitational blue shifted. That's a kind of Doppler shift.

    That you hear the train-whistle change frequency when
    the train passes you doesn't mean that the emitted
    frequency has changed.

    f_received = 1.000000000348⋅f_transmitted = 9192631773.1990 Hz

    BECAUSE f_transmitted = 9192631770 Hz.


    Interesting thanks. But are you sure it’s correct to convert the gps signal frequency gain of 348 pico seconds at 10.23 Mhz to the gain of 3.19 Hz
    for the recieved C-133 frequency using that method?

    This statement is meaningless.

    A GPS satellite is at r = 4.187883R
    and is moving in the ECI frame at the speed 3.874 km/s.

    https://paulba.no/pdf/GPS_clock_rate.pdf


    Because if I try your same formula for the transmitted f of 10.23MHz, I
    get the following:
    f_received = 1.000000000348 x 10.23Mhz =10230000.0036 hz

    A more precise value is:
    f_received = 1.000000000347674 x 10.23Mhz = 10230000.0035567 Hz

    I would have thought it should be 10230000.0038 hz.

    OK, so that's what you believe.

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to rotchm on Tue Nov 14 12:38:36 2023
    On Tuesday, 14 November 2023 at 14:38:15 UTC+1, rotchm wrote:

    Oh, true, you ran away from it. We have cornered you and you havent presented any counterargument whatsoever.
    You havent answered one question psoed to you and havent answered one clarification posed to you.
    You just run away or change subject. Now, isn't that the behavior of a crank?

    Sure it is! Relativistic idiots behave exactly the
    same way.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lou@21:1/5 to Paul B. Andersen on Wed Nov 15 05:29:00 2023
    On Tuesday, 14 November 2023 at 19:33:59 UTC, Paul B. Andersen wrote:
    Den 14.11.2023 15:01, skrev Lou:

    Who wrote what? DON'T SNIP THE ATTRIBUTIONS!
    Yes I realise that under GR the rule is c-133 frequency never changes. >>> Under GR its always everywhere the same.

    Not "under GR". In the real world. Everywhere. Always. By definition!

    But you say a broadcast
    frequency can appear to be blueshifted to an observer on the ground
    and I’m trying to find out what that blueshifted f would be to an
    earth ground observer.

    Not "can appear to be". IS blue shifted. Measured in the real world.

    https://paulba.no/paper/Pound&Rebka.pdf

    If the receiver is above the sender, it is gravitational red shift.

    So if it were possible to observe, from the ground, a clock orbiting at 2R.
    Not orbiting! Stationary in the ECI frame at 2R.
    What frequency would 9192631770 Hz on a clock at 2R be blueshifted to >>> an observer on the ground be? Would it appear to a ground observer
    to be 9192631773.48hz ?

    The frequency of the received signal on the ground would
    be gravitational blue shifted. That's a kind of Doppler shift.

    That you hear the train-whistle change frequency when
    the train passes you doesn't mean that the emitted
    frequency has changed.

    f_received = 1.000000000348⋅f_transmitted = 9192631773.1990 Hz

    BECAUSE f_transmitted = 9192631770 Hz.


    Interesting thanks. But are you sure it’s correct to convert the gps signal
    frequency gain of 348 pico seconds at 10.23 Mhz to the gain of 3.19 Hz
    for the recieved C-133 frequency using that method?
    This statement is meaningless.

    A GPS satellite is at r = 4.187883R
    and is moving in the ECI frame at the speed 3.874 km/s.

    https://paulba.no/pdf/GPS_clock_rate.pdf

    Because if I try your same formula for the transmitted f of 10.23MHz, I get the following:
    f_received = 1.000000000348 x 10.23Mhz =10230000.0036 hz
    A more precise value is:
    f_received = 1.000000000347674 x 10.23Mhz = 10230000.0035567 Hz
    I would have thought it should be 10230000.0038 hz.
    OK, so that's what you believe.

    That was a typo. It should have been 10230000.00348hz.
    But you have clarified that point thanks. It is as you
    say10230000.0035567 Hz

    Using your formula I get approximately 10230000.0054hz
    recieved on earth for a gps signal of 10.23 Mhz from 4.12 R.
    I can’t find any reference to confirm this. Do you know if that
    approx frequency is observed at earth ground stations?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Wed Nov 15 19:22:15 2023
    Den 15.11.2023 14:29, skrev Lou:
    On Tuesday, 14 November 2023 at 19:33:59 UTC, Paul B. Andersen wrote:

    A GPS satellite is at r = 4.187883R
    and is moving in the ECI frame at the speed 3.874 km/s.

    You can find the answer to your question below here.

    https://paulba.no/pdf/GPS_clock_rate.pdf


    Using your formula I get approximately 10230000.0054hz
    recieved on earth for a gps signal of 10.23 Mhz from 4.12 R.
    I can’t find any reference to confirm this. Do you know if that
    approx frequency is observed at earth ground stations?

    The received frequency from a stationary satellite
    at GPS altitude which transmits the frequency 10.23 MHz
    would be 10.230000005408 MHz.
    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.

    It is however impossible to directly measure this
    frequency on the ground, because the Doppler shift due
    to the orbital speed of the satellite is order of
    magnitudes greater than the shift due to GR, and it
    is changing all the time.

    But the ground stations can read what the satellite clock shows,
    and can compare it to clocks on the ground (GPS-time, UTC).
    The difference will increase with time.

    This was done in the first GPS-satellite with a clock
    which was not corrected for relativistic effects.

    https://paulba.no/paper/Initial_results_of_GPS_satellite_1977.pdf

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Richard Hertz@21:1/5 to Paul B. Andersen on Wed Nov 15 12:53:22 2023
    On Wednesday, November 15, 2023 at 3:20:28 PM UTC-3, Paul B. Andersen wrote:

    <snip>

    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.

    It is however impossible to directly measure this frequency on the ground, because the Doppler shift due
    to the orbital speed of the satellite is order of magnitudes greater than the shift due to GR, and it
    is changing all the time.

    But the ground stations can read what the satellite clock shows, and can compare it to clocks on the ground (GPS-time, UTC).
    The difference will increase with time.

    <snip>

    Relativist, you are so full of shit that it's extremely disgusting.

    So, relativistic effects can't be measured in any way because Doppler effect bury them 1,000 times under its values.

    But EVERYONE have to trust you about the readings of the ground clock, because YOU HAD A JOB measuring it.

    LIAR, DECEIVER, HYPOCRITE!

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Wed Nov 15 22:34:28 2023
    Den 15.11.2023 21:53, skrev Richard Hertz:
    On Wednesday, November 15, 2023 at 3:20:28 PM UTC-3, Paul B. Andersen wrote:

    <snip>

    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.

    It is however impossible to directly measure this frequency on the ground, because the Doppler shift due
    to the orbital speed of the satellite is order of magnitudes greater than the shift due to GR, and it
    is changing all the time.

    But the ground stations can read what the satellite clock shows, and can compare it to clocks on the ground (GPS-time, UTC).
    The difference will increase with time.

    https://paulba.no/pdf/GPS_clock_rate.pdf



    Relativist, you are so full of shit that it's extremely disgusting.

    So, relativistic effects can't be measured in any way because Doppler effect bury them 1,000 times under its values.

    The satellite is moving, the ground is moving, so the Doppler
    shift of the carrier signals from a satellite will be anything
    in the range (1 ± 1E-7). The receiver will obviously not measure
    this frequency. Why should it?
    The bandwidth of the receiver is bigger that that.
    Receivers can receive the signals of up to 12 satellites at
    the same time, and all the signals will be differently Doppler shifted.
    They are separated by their PRN code. Phase locked loops.

    Didn't you know this, Richard?
    Did you believe that the receiver could measure the frequency
    to a precision of 1E-12?


    But EVERYONE have to trust you about the readings of the ground clock, because YOU HAD A JOB measuring it.

    LIAR, DECEIVER, HYPOCRITE!


    Mind the blood pressure, Richard. :-D

    --
    Paul, enjoying Richard's helpless rage

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Wed Nov 15 22:40:42 2023
    Den 15.11.2023 22:34, skrev Paul B. Andersen:
    Den 15.11.2023 21:53, skrev Richard Hertz:
    On Wednesday, November 15, 2023 at 3:20:28 PM UTC-3, Paul B. Andersen
    wrote:

    <snip>

    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.

    It is however impossible to directly measure this frequency on the
    ground, because the Doppler shift due
    to the orbital speed of the satellite is order of magnitudes greater
    than the shift due to GR, and it
    is changing all the time.

    But the ground stations can read what the satellite clock shows, and
    can compare it to clocks on the ground (GPS-time, UTC).
    The difference will increase with time.

    This was the link I meant to send:

    https://paulba.no/paper/Initial_results_of_GPS_satellite_1977.pdf




    Relativist, you are so full of shit that it's extremely disgusting.

    So, relativistic effects can't be measured in any way because Doppler
    effect bury them 1,000 times under its values.

    The satellite is moving, the ground is moving, so the Doppler
    shift of the carrier signals from a satellite will be anything
    in the range (1 ± 1E-7). The receiver will obviously not measure
     this frequency. Why should it?
    The bandwidth of the receiver is bigger that that.
    Receivers can receive the signals of up to 12 satellites at
    the same time, and all the signals will be differently Doppler shifted.
    They are separated by their PRN code. Phase locked loops.

    Didn't you know this, Richard?
    Did you believe that the receiver could measure the frequency
    to a precision of 1E-12?


    But EVERYONE have to trust you about the readings of the ground clock,
    because YOU HAD A JOB measuring it.

    LIAR, DECEIVER, HYPOCRITE!


    Mind the blood pressure, Richard. :-D


    --
    Paul, still enjoying Richard's helpless rage

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Wed Nov 15 21:53:27 2023
    On Wednesday, 15 November 2023 at 19:20:28 UTC+1, Paul B. Andersen wrote:

    This was done in the first GPS-satellite with a clock
    which was not corrected for relativistic effects.

    Of course, Paul is a piece of lying shit and this
    first GPS satellite was made perfectly proper way,
    exactly as it should be according to The Shit.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lou@21:1/5 to Paul B. Andersen on Thu Nov 16 04:58:33 2023
    On Wednesday, 15 November 2023 at 18:20:28 UTC, Paul B. Andersen wrote:
    Den 15.11.2023 14:29, skrev Lou:
    On Tuesday, 14 November 2023 at 19:33:59 UTC, Paul B. Andersen wrote:

    A GPS satellite is at r = 4.187883R
    and is moving in the ECI frame at the speed 3.874 km/s.
    You can find the answer to your question below here.

    https://paulba.no/pdf/GPS_clock_rate.pdf

    Using your formula I get approximately 10230000.0054hz
    recieved on earth for a gps signal of 10.23 Mhz from 4.12 R.
    I can’t find any reference to confirm this. Do you know if that
    approx frequency is observed at earth ground stations?
    The received frequency from a stationary satellite
    at GPS altitude which transmits the frequency 10.23 MHz
    would be 10.230000005408 MHz.
    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.

    It is however impossible to directly measure this
    frequency on the ground, because the Doppler shift due
    to the orbital speed of the satellite is order of
    magnitudes greater than the shift due to GR, and it
    is changing all the time.

    But the ground stations can read what the satellite clock shows,
    and can compare it to clocks on the ground (GPS-time, UTC).
    The difference will increase with time.

    This was done in the first GPS-satellite with a clock
    which was not corrected for relativistic effects.

    https://paulba.no/paper/Initial_results_of_GPS_satellite_1977.pdf


    Interesting facts thanks for clarifying things. Still a bit of discrepancy though.The current NIST reference says the gps sat clock f is designated
    as 10229999.99543Hz.
    If I assume gps at 4.12R ** then it should have an approx picosecond gain
    of 1.000000000542s
    So using your formula I get:
    10229999.99543 × 1.000000000542 = 10230000.001hz.
    Small error but maybe still significant.
    To get exactly 10.23 Mhz for GR clock gains at receiver I need a calculation using closer to a 3R altitude clock gain of only 450 picoseconds.
    Not 542 picoseconds

    10229999.99543 × 1.00000000045 = 10.23 Mhz.

    That’s equivelent to one whole radius r distance based on your table
    below

    As you can see below the sat clock f setting isn’t
    matching GR predictions. Is that because the sat f
    also has to take account the various Doppler speeds
    you mentioned? I would have thought that the average
    Doppler shift over time would be zero seeing as 1/2 the
    time it’s(gps sat) coming towards reciever, 1/2 time away.

    **
    10R 1.000000000626 0.0100
    9R 1.000000000618 0.0123
    8R 1.000000000608 0.0156
    7R 1.000000000596 0.0204
    6R 1.000000000579 0.0278
    5R 1.000000000556 0.0400
    4.12 1.000000000542. *
    4R 1.000000000522 0.0625
    3R 1.000000000464 0.1111 *
    2R 1.000000000348 0.2500
    1R 1.000000000000 1.0000
    https://paulba.no/temp/ClockRate.pdf

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Thu Nov 16 20:20:59 2023
    Den 16.11.2023 13:58, skrev Lou:
    On Wednesday, 15 November 2023 at 18:20:28 UTC, Paul B. Andersen wrote:
    Den 15.11.2023 14:29, skrev Lou:

    Using your formula I get approximately 10230000.0054hz
    recieved on earth for a gps signal of 10.23 Mhz from 4.12 R.
    I can’t find any reference to confirm this. Do you know if that
    approx frequency is observed at earth ground stations?

    The received frequency from a stationary satellite
    at GPS altitude which transmits the frequency 10.23 MHz
    would be 10.230000005408 MHz.

    As I told you and you have ignored:
    THE SATELLITE IS MOVING IN THE ECI-FRAME ========================================
    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.

    Note that I didn't say a GPS satellite, I said a satellite
    in GPS orbit which transmits a 10.23 Mhz signal.
    Then the signal received on the ground would be:
    f = (1 + 4.4647E-10)⋅10.23 MHz = 10.230000004567389 MHz


    Interesting facts thanks for clarifying things. Still a bit of discrepancy though.The current NIST reference says the gps sat clock f is designated
    as 10229999.99543Hz.

    Yes, the GPS satellite is NOT transmitting a 10.23 MHz signal.
    The frequency is adjusted (the famous "GR-correction") to:
    f₀ = (1 - 4.4647E-10)⋅10.23 MHz = 10.229999995432612 MHz

    This frequency would observed on the ground be:
    f₁ = (1 + 4.4647E-10)⋅10.229999995432612 MHz = 10.2300000000000000 MHz

    (The frequency f₀ isn't transmitted at all, but it is used as reference
    for the satellite clock, to make it stay in sync with GPS-time (UTC).)


    If I assume gps at 4.12R ** then it should have an approx picosecond gain
    of 1.000000000542s
    So using your formula I get:
    10229999.99543 × 1.000000000542 = 10230000.001hz.

    The satellite is moving!!!!
    https://paulba.no/pdf/GPS_clock_rate.pdf
    equation (8)

    Read it!

    Small error but maybe still significant.
    To get exactly 10.23 Mhz for GR clock gains at receiver I need a calculation using closer to a 3R altitude clock gain of only 450 picoseconds.
    Not 542 picoseconds

    10229999.99543 × 1.00000000045 = 10.23 Mhz.

    That’s equivelent to one whole radius r distance based on your table
    below

    As you can see below the sat clock f setting isn’t
    matching GR predictions. Is that because the sat f
    also has to take account the various Doppler speeds
    you mentioned? I would have thought that the average
    Doppler shift over time would be zero seeing as 1/2 the
    time it’s(gps sat) coming towards reciever, 1/2 time away.

    **
    10R 1.000000000626 0.0100
    9R 1.000000000618 0.0123
    8R 1.000000000608 0.0156
    7R 1.000000000596 0.0204
    6R 1.000000000579 0.0278
    5R 1.000000000556 0.0400
    4.12 1.000000000542. *
    4R 1.000000000522 0.0625
    3R 1.000000000464 0.1111 *
    2R 1.000000000348 0.2500
    1R 1.000000000000 1.0000
    https://paulba.no/temp/ClockRate.pdf

    The GPS-satellites are moving!
    ================================

    Got it now?

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lou@21:1/5 to Paul B. Andersen on Thu Nov 16 12:16:43 2023
    On Thursday, 16 November 2023 at 19:19:09 UTC, Paul B. Andersen wrote:
    Den 16.11.2023 13:58, skrev Lou:
    On Wednesday, 15 November 2023 at 18:20:28 UTC, Paul B. Andersen wrote:
    Den 15.11.2023 14:29, skrev Lou:

    Using your formula I get approximately 10230000.0054hz
    recieved on earth for a gps signal of 10.23 Mhz from 4.12 R.
    I can’t find any reference to confirm this. Do you know if that
    approx frequency is observed at earth ground stations?

    The received frequency from a stationary satellite
    at GPS altitude which transmits the frequency 10.23 MHz
    would be 10.230000005408 MHz.
    As I told you and you have ignored:
    THE SATELLITE IS MOVING IN THE ECI-FRAME ========================================
    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.
    Note that I didn't say a GPS satellite, I said a satellite
    in GPS orbit which transmits a 10.23 Mhz signal.
    Then the signal received on the ground would be:
    f = (1 + 4.4647E-10)⋅10.23 MHz = 10.230000004567389 MHz

    Interesting facts thanks for clarifying things. Still a bit of discrepancy though.The current NIST reference says the gps sat clock f is designated as 10229999.99543Hz.
    Yes, the GPS satellite is NOT transmitting a 10.23 MHz signal.

    Yes. I just told you it was 10.229999995432612 MHz I got that from NIST.

    The frequency is adjusted (the famous "GR-correction") to:
    f₀ = (1 - 4.4647E-10)⋅10.23 MHz = 10.229999995432612 MHz

    This frequency would observed on the ground be:
    f₁ = (1 + 4.4647E-10)⋅10.229999995432612 MHz = 10.23 Mhz

    Where did you get 1 + 4.4647E-10 ?
    That’s only 3R in your table.
    According to you and your table if the gps satellite is at 4.12 R, then
    your “famous correction” from broadcast to receive should include approx 5.42 Not 4.46. At 4.12 R the correction formula should be, *according
    to you*:
    f₁ = (1 + 5.52E-10)⋅10.229999995432612 MHz = 10230000.001hz
    Notice it doesn’t work. There shouldn’t be an extra .001Hz
    To correct that one needs to assume the satelitte is only at 3R to use
    4.46 in your equation.
    Which it isn’t. It’s at 4R.
    You say that the reason why you pretend the satelitte is at 3 R is
    “Because it is moving in the ECI frame”
    Are you referring to kinematic velocity SR etc reducing the
    total picoseconds gained from GR?

    (The frequency f₀ isn't transmitted at all, but it is used as reference for the satellite clock, to make it stay in sync with GPS-time (UTC).)
    If I assume gps at 4.12R ** then it should have an approx picosecond gain of 1.000000000542s
    So using your formula I get:
    10229999.99543 × 1.000000000542 = 10230000.001hz.
    The satellite is moving!!!!
    https://paulba.no/pdf/GPS_clock_rate.pdf
    equation (8)

    Read it!
    Small error but maybe still significant.
    To get exactly 10.23 Mhz for GR clock gains at receiver I need a calculation
    using closer to a 3R altitude clock gain of only 450 picoseconds.
    Not 542 picoseconds

    10229999.99543 × 1.00000000045 = 10.23 Mhz.

    That’s equivelent to one whole radius r distance based on your table below

    As you can see below the sat clock f setting isn’t
    matching GR predictions. Is that because the sat f
    also has to take account the various Doppler speeds
    you mentioned? I would have thought that the average
    Doppler shift over time would be zero seeing as 1/2 the
    time it’s(gps sat) coming towards reciever, 1/2 time away.

    **
    10R 1.000000000626 0.0100
    9R 1.000000000618 0.0123
    8R 1.000000000608 0.0156
    7R 1.000000000596 0.0204
    6R 1.000000000579 0.0278
    5R 1.000000000556 0.0400
    4.12 1.000000000542. *
    4R 1.000000000522 0.0625
    3R 1.000000000464 0.1111 *
    2R 1.000000000348 0.2500
    1R 1.000000000000 1.0000
    https://paulba.no/temp/ClockRate.pdf
    The GPS-satellites are moving!
    ================================
    Yes OK
    “They are moving”. Could you elaborate.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Thu Nov 16 13:58:29 2023
    On Thursday, 16 November 2023 at 20:19:09 UTC+1, Paul B. Andersen wrote:
    Den 16.11.2023 13:58, skrev Lou:
    On Wednesday, 15 November 2023 at 18:20:28 UTC, Paul B. Andersen wrote:
    Den 15.11.2023 14:29, skrev Lou:

    Using your formula I get approximately 10230000.0054hz
    recieved on earth for a gps signal of 10.23 Mhz from 4.12 R.
    I can’t find any reference to confirm this. Do you know if that
    approx frequency is observed at earth ground stations?

    The received frequency from a stationary satellite
    at GPS altitude which transmits the frequency 10.23 MHz
    would be 10.230000005408 MHz.
    As I told you and you have ignored:
    THE SATELLITE IS MOVING IN THE ECI-FRAME ========================================
    But a GPS satellite is moving, so the frequency received from
    a satellite in GPS orbit which transmits the frequency 10.23 MHz
    would be 10.230000004567 MHz.
    Note that I didn't say a GPS satellite, I said a satellite
    in GPS orbit which transmits a 10.23 Mhz signal.

    You didn't say but it is, measured both by
    ground and satellite clocks.



    The satellite is moving!!!!

    Was sure that you don't even believe this rrelative
    motion idiocies.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul B. Andersen@21:1/5 to All on Fri Nov 17 12:11:54 2023
    Den 16.11.2023 21:16, skrev Lou:
    On Thursday, 16 November 2023 at 19:19:09 UTC, Paul B. Andersen wrote:
    Den 16.11.2023 13:58, skrev Lou:

    Interesting facts thanks for clarifying things. Still a bit of discrepancy >>> though.The current NIST reference says the gps sat clock f is designated >>> as 10229999.99543Hz.

    Yes, the GPS satellite is NOT transmitting a 10.23 MHz signal.

    Yes. I just told you it was 10.229999995432612 MHz I got that from NIST.


    The frequency is adjusted (the famous "GR-correction") to:
    f₀ = (1 - 4.4647E-10)⋅10.23 MHz = 10.229999995432612 MHz

    This frequency would observed on the ground be:
    f₁ = (1 + 4.4647E-10)⋅10.229999995432612 MHz = 10.23 Mhz


    Where did you get 1 + 4.4647E-10 ?

    The correction is (1 - 4.4647E-10)
    so f₁ = (1/(1 - 4.4647E-10))⋅f₀ ≈ (1 + 4.4647E-10)⋅f₀

    The correction is specified in the
    "INTERFACE SPECIFICATION DOCUMENT" for GPS:

    https://www.gps.gov/technical/icwg/IS-GPS-200N.pdf

    From 3.3.1.1 Frequency Plan:
    "The carrier frequencies for the L1 and L2 signals shall be
    coherently derived from a common frequency source within the SV.
    The nominal frequency of this source -- as it appears to an observer
    on the ground -- is 10.23 MHz. The SV carrier frequency and clock
    rates -- as they would appear to an observer located in the SV --
    are offset to compensate for relativistic effects. The clock rates
    are offset by Δf/f = -4.4647E-10, equivalent to a change in the
    P-code chipping rate of 10.23 MHz offset by a Δf = -4.5674E-3 Hz.
    This is equal to 10.2299999954326 MHz."

    SV = space vehicle, satellite.

    <snip>


    The GPS-satellites are moving!
    ================================

    Got it now?

    Obviously not!

    “They are moving”. Could you elaborate.

    I have given this link several times now: https://paulba.no/pdf/GPS_clock_rate.pdf

    The blue shift observed on the ground is given in equation (8).
    READ IT!

    Equation (8) is of the form:
    dτ₂/dτ₁ = 1 + gravitational term + kinematic term

    You keep ignoring the kinematic term.

    --
    Paul

    https://paulba.no/

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Paul B. Andersen on Fri Nov 17 11:14:56 2023
    On Friday, 17 November 2023 at 12:10:04 UTC+1, Paul B. Andersen wrote:
    Den 16.11.2023 21:16, skrev Lou:
    On Thursday, 16 November 2023 at 19:19:09 UTC, Paul B. Andersen wrote:
    Den 16.11.2023 13:58, skrev Lou:

    Interesting facts thanks for clarifying things. Still a bit of discrepancy
    though.The current NIST reference says the gps sat clock f is designated >>> as 10229999.99543Hz.

    Yes, the GPS satellite is NOT transmitting a 10.23 MHz signal.

    Yes. I just told you it was 10.229999995432612 MHz I got that from NIST.


    The frequency is adjusted (the famous "GR-correction") to:
    f₀ = (1 - 4.4647E-10)⋅10.23 MHz = 10.229999995432612 MHz

    This frequency would observed on the ground be:
    f₁ = (1 + 4.4647E-10)⋅10.229999995432612 MHz = 10.23 Mhz


    Where did you get 1 + 4.4647E-10 ?
    The correction is (1 - 4.4647E-10)
    so f₁ = (1/(1 - 4.4647E-10))⋅f₀ ≈ (1 + 4.4647E-10)⋅f₀

    The correction is specified in the
    "INTERFACE SPECIFICATION DOCUMENT" for GPS:

    https://www.gps.gov/technical/icwg/IS-GPS-200N.pdf

    From 3.3.1.1 Frequency Plan:
    "The carrier frequencies for the L1 and L2 signals shall be
    coherently derived from a common frequency source within the SV.
    The nominal frequency of this source -- as it appears to an observer
    on the ground -- is 10.23 MHz. The SV carrier frequency and clock
    rates -- as they would appear to an observer located in the SV --

    Paul, poor halfbrain, who cares what "would appear" to a
    non-existing gedanken person? It's the measurement result
    that counts, andthis is 10.23, both measured with
    ground or satellite clock.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From carl eto@21:1/5 to All on Sun Nov 19 10:20:44 2023
    t' = γ (t - vx/c)


    The relativistic velocity v is not constant.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Volney@21:1/5 to Maciej Wozniak on Sun Nov 19 13:49:46 2023
    On 11/17/2023 2:14 PM, Maciej Wozniak wrote:
    On Friday, 17 November 2023 at 12:10:04 UTC+1, Paul B. Andersen wrote:
    Den 16.11.2023 21:16, skrev Lou:
    On Thursday, 16 November 2023 at 19:19:09 UTC, Paul B. Andersen wrote:
    Den 16.11.2023 13:58, skrev Lou:

    Interesting facts thanks for clarifying things. Still a bit of discrepancy
    though.The current NIST reference says the gps sat clock f is designated >>>>> as 10229999.99543Hz.

    Yes, the GPS satellite is NOT transmitting a 10.23 MHz signal.

    Yes. I just told you it was 10.229999995432612 MHz I got that from NIST. >>>

    The frequency is adjusted (the famous "GR-correction") to:
    f₀ = (1 - 4.4647E-10)⋅10.23 MHz = 10.229999995432612 MHz

    This frequency would observed on the ground be:
    f₁ = (1 + 4.4647E-10)⋅10.229999995432612 MHz = 10.23 Mhz


    Where did you get 1 + 4.4647E-10 ?
    The correction is (1 - 4.4647E-10)
    so f₁ = (1/(1 - 4.4647E-10))⋅f₀ ≈ (1 + 4.4647E-10)⋅f₀

    The correction is specified in the
    "INTERFACE SPECIFICATION DOCUMENT" for GPS:

    https://www.gps.gov/technical/icwg/IS-GPS-200N.pdf

    From 3.3.1.1 Frequency Plan:
    "The carrier frequencies for the L1 and L2 signals shall be
    coherently derived from a common frequency source within the SV.
    The nominal frequency of this source -- as it appears to an observer
    on the ground -- is 10.23 MHz. The SV carrier frequency and clock
    rates -- as they would appear to an observer located in the SV --

    Paul, poor halfbrain, who cares what "would appear" to a
    non-existing gedanken person?

    NIST does, obviously, since they wrote that. They use "would appear"
    since nobody is going to send an astronaut up to check, especially since
    it was already set to 10.229999995432612 MHz on the ground before launch.

    It's the measurement result
    that counts, andthis is 10.23, both measured with
    ground or satellite clock.

    So now it is you invoking the "would appear" since you are talking about
    the satellite clock without an astronaut checking. But regardless of
    whether there is an astronaut there or not, it still runs at
    10.229999995432612 MHz because that is what it was set to run.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Maciej Wozniak@21:1/5 to Volney on Sun Nov 19 11:49:55 2023
    On Sunday, 19 November 2023 at 19:49:53 UTC+1, Volney wrote:
    On 11/17/2023 2:14 PM, Maciej Wozniak wrote:
    On Friday, 17 November 2023 at 12:10:04 UTC+1, Paul B. Andersen wrote:
    Den 16.11.2023 21:16, skrev Lou:
    On Thursday, 16 November 2023 at 19:19:09 UTC, Paul B. Andersen wrote: >>>> Den 16.11.2023 13:58, skrev Lou:

    Interesting facts thanks for clarifying things. Still a bit of discrepancy
    though.The current NIST reference says the gps sat clock f is designated
    as 10229999.99543Hz.

    Yes, the GPS satellite is NOT transmitting a 10.23 MHz signal.

    Yes. I just told you it was 10.229999995432612 MHz I got that from NIST. >>>

    The frequency is adjusted (the famous "GR-correction") to:
    f₀ = (1 - 4.4647E-10)⋅10.23 MHz = 10.229999995432612 MHz

    This frequency would observed on the ground be:
    f₁ = (1 + 4.4647E-10)⋅10.229999995432612 MHz = 10.23 Mhz


    Where did you get 1 + 4.4647E-10 ?
    The correction is (1 - 4.4647E-10)
    so f₁ = (1/(1 - 4.4647E-10))⋅f₀ ≈ (1 + 4.4647E-10)⋅f₀

    The correction is specified in the
    "INTERFACE SPECIFICATION DOCUMENT" for GPS:

    https://www.gps.gov/technical/icwg/IS-GPS-200N.pdf

    From 3.3.1.1 Frequency Plan:
    "The carrier frequencies for the L1 and L2 signals shall be
    coherently derived from a common frequency source within the SV.
    The nominal frequency of this source -- as it appears to an observer
    on the ground -- is 10.23 MHz. The SV carrier frequency and clock
    rates -- as they would appear to an observer located in the SV --

    Paul, poor halfbrain, who cares what "would appear" to a
    non-existing gedanken person?
    NIST does, obviously, since they wrote that.

    Too bad for NIST, stupid Mike.
    Anyway, the measurement result gives a different number.

    It's the measurement result
    that counts, andthis is 10.23, both measured with
    ground or satellite clock.
    So now it is you invoking the "would appear" since you are talking about
    the satellite clock without an astronaut checking. But regardless of
    whether there is an astronaut there or not, it still runs at 10.229999995432612 MHz

    No, stupid Mike, it isn't,. I know it's the prediction of yourr
    moronic Shit, but the measurement gives a different
    result.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)