Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

Avoid the Gates of Hell. Use Linux -- unknown source


tech / sci.physics.relativity / Re: Conflicts in SR when using horizontal light clocks in the moving frame.

SubjectAuthor
* Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
+* Re: Conflicts in SR when using horizontal light clocks in the movingTom Roberts
|`* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
| +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Tom Roberts
| |+- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
| |`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
| `* Re: Conflicts in SR when using horizontal light clocks in the movingVolney
|  `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
|   `- Re: Conflicts in SR when using horizontal light clocks in the movingVolney
+* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|+* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
||`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
+* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|`* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
| `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|  `- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
+* Crank Richard Hertz fails relativity 101Dono.
|+- Re: Crank Richard Hertz fails relativity 101Prokaryotic Capase Homolog
|`- Re: Crank Richard Hertz fails relativity 101Richard Hertz
+* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|`* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
| +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
| |+* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
| ||`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
| |`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
| `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|  `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
|   +* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |`* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
|   | +- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Paparios
|   | +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|   | |`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   | `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |  +- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |  `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
|   |   +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|   |   |`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |   `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |    +- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |    `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Lou
|   |     `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      +- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Lou
|   |      |+- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      |`* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      | +- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      | `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Lou
|   |      |  +- Re: Conflicts in SR when using horizontal light clocks in the movingHuey Baidzhanov
|   |      |  +- Re: Conflicts in SR when using horizontal light clocks in the movingOrlando Shamburkin
|   |      |  `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      |   `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Lou
|   |      |    `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      |     +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
|   |      |     |`* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      |     | `- Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      |     +- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      |     `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Lou
|   |      |      `* Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      |       +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Lou
|   |      |       |+- Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |      |       |`* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      |       | +- Re: Conflicts in SR when using horizontal light clocks in the movingVolney
|   |      |       | `- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      |       `- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |      `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.Richard Hertz
|   |       +- Re: Conflicts in SR when using horizontal light clocks in the movingPaul B. Andersen
|   |       +* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|   |       |`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Maciej Wozniak
|   |       `- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Dono.
|   `* Re: Conflicts in SR when using horizontal light clocks in the moving frame.rotchm
|    `- Re: Conflicts in SR when using horizontal light clocks in the movingJerry Yahse Michurin
+- Re: Conflicts in SR when using horizontal light clocks in the moving frame.Laurence Clark Crossen
`- Re: Conflicts in SR when using horizontal light clocks in the moving frame.carl eto

Pages:123
Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<wrI4N.74304$ydda.66481@fx13.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127861&group=sci.physics.relativity#127861

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!news.chmurka.net!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx13.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
Content-Language: en-GB
From: relativ...@paulba.no (Paul B. Andersen)
In-Reply-To: <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 88
Message-ID: <wrI4N.74304$ydda.66481@fx13.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Tue, 14 Nov 2023 11:00:44 UTC
Organization: Eweka Internet Services
Date: Tue, 14 Nov 2023 12:02:33 +0100
X-Received-Bytes: 4060
 by: Paul B. Andersen - Tue, 14 Nov 2023 11:02 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<8f233614-7fe1-4e1b-95e9-1caca2debb0fn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127862&group=sci.physics.relativity#127862

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ae9:e413:0:b0:77b:e0a6:e38c with SMTP id q19-20020ae9e413000000b0077be0a6e38cmr42279qkc.11.1699962404512;
Tue, 14 Nov 2023 03:46:44 -0800 (PST)
X-Received: by 2002:a65:4201:0:b0:5bd:9c1e:c557 with SMTP id
c1-20020a654201000000b005bd9c1ec557mr441509pgq.3.1699962404276; Tue, 14 Nov
2023 03:46:44 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Tue, 14 Nov 2023 03:46:43 -0800 (PST)
In-Reply-To: <wrI4N.74304$ydda.66481@fx13.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=83.21.204.13; posting-account=I3DWzAoAAACOmZUdDcZ-C0PqAZGVsbW0
NNTP-Posting-Host: 83.21.204.13
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <8f233614-7fe1-4e1b-95e9-1caca2debb0fn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: maluwozn...@gmail.com (Maciej Wozniak)
Injection-Date: Tue, 14 Nov 2023 11:46:44 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2215
 by: Maciej Wozniak - Tue, 14 Nov 2023 11:46 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<e4991d41-f430-45e4-bf21-f50d1dad56cbn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127865&group=sci.physics.relativity#127865

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:6214:48a:b0:677:91b7:b35 with SMTP id pt10-20020a056214048a00b0067791b70b35mr74750qvb.13.1699969094025;
Tue, 14 Nov 2023 05:38:14 -0800 (PST)
X-Received: by 2002:a05:6a00:8912:b0:6be:aed:7ad0 with SMTP id
hw18-20020a056a00891200b006be0aed7ad0mr2567038pfb.2.1699969093617; Tue, 14
Nov 2023 05:38:13 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Tue, 14 Nov 2023 05:38:12 -0800 (PST)
In-Reply-To: <fa985245-de4a-4202-b8e6-b062efae5465n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=184.160.32.227; posting-account=BHsbrQoAAAANJj6HqXJ987nOEDAC1EsJ
NNTP-Posting-Host: 184.160.32.227
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <fa985245-de4a-4202-b8e6-b062efae5465n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e4991d41-f430-45e4-bf21-f50d1dad56cbn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: rot...@gmail.com (rotchm)
Injection-Date: Tue, 14 Nov 2023 13:38:14 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2727
 by: rotchm - Tue, 14 Nov 2023 13:38 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127866&group=sci.physics.relativity#127866

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:c4e:b0:77b:9ebc:f9eb with SMTP id u14-20020a05620a0c4e00b0077b9ebcf9ebmr66605qki.9.1699970516430;
Tue, 14 Nov 2023 06:01:56 -0800 (PST)
X-Received: by 2002:a17:90b:350e:b0:26d:a6b:9a47 with SMTP id
ls14-20020a17090b350e00b0026d0a6b9a47mr2905823pjb.2.1699970515830; Tue, 14
Nov 2023 06:01:55 -0800 (PST)
Path: i2pn2.org!i2pn.org!paganini.bofh.team!2.eu.feeder.erje.net!feeder.erje.net!proxad.net!feeder1-2.proxad.net!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Tue, 14 Nov 2023 06:01:55 -0800 (PST)
In-Reply-To: <wrI4N.74304$ydda.66481@fx13.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=92.23.58.23; posting-account=l0YVUwoAAACvUnQCooL-PCAznCzJnJho
NNTP-Posting-Host: 92.23.58.23
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: noelturn...@live.co.uk (Lou)
Injection-Date: Tue, 14 Nov 2023 14:01:56 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
 by: Lou - Tue, 14 Nov 2023 14:01 UTC

> > 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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<uj05p6$3cu40$1@paganini.bofh.team>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127868&group=sci.physics.relativity#127868

  copy link   Newsgroups: sci.physics.relativity sci.physics sci.math
Followup: sci.physics.relativity,sci.physics,sci.math
Path: i2pn2.org!i2pn.org!paganini.bofh.team!not-for-mail
From: aau...@hohuyvbv.ie (Huey Baidzhanov)
Newsgroups: sci.physics.relativity,sci.physics,sci.math
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Followup-To: sci.physics.relativity,sci.physics,sci.math
Date: Tue, 14 Nov 2023 16:03:50 -0000 (UTC)
Organization: To protect and to server
Message-ID: <uj05p6$3cu40$1@paganini.bofh.team>
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 14 Nov 2023 16:03:50 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="3569792"; posting-host="ncD5mYLSvmSC3ESTAw5XRA.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: iPhone Mail (12H143)
Cancel-Lock: sha256:gXcek7Tg50AsL9LuaZxKkVfReVQSgnmcQ7j3dm3TeGA=
X-Face: #pDFvv:BiBdRQH-B0D:wdA9?usWP|G3!LXLDw;69a=a9bzTgCRl/6/pUM`1)RjuP
Ol>8.b2U=TC@7+d0FEe*nJyZri%C$+|_#g_{*!Y?{ECEfQ&RbNP&J=l{I.]@JRH83O'KfyC
t[3#=RO,\i"zbG^@ntOMjSLoK;stk.,bM^6B<60/FY><),xqXbYiR}JH:/Jw!(h*:rf%!bG
}],iDm>SN*;Z,{t>pM4q]}52v;PyA*|S0>I3VHAK{qc_lUb|WT~*Y`8l>ui^,Ks"JXLhDyf l
X-Notice: Filtered by postfilter v. 0.9.3
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAElBMVEXIyMphYlyZ
W1etk38gHiBZLC+3FvN+AAACUUlEQVQ4jVWUUW7jMAxE6agHWFrR/yZu/0WrPYA
B6gCqxftfpUPJ6WIN1C74zOGQlEP8/xXLvISugM1HeV08QXz8i4+b8CuDywVkQB
5g5QjtCYQ3v/FLitcyKwtuTxem1JgbpyEVg/wWJLGWarKhFSUxpwtQ0F7NkkVXB
OD2nIAWtWrdoPd9isvGAQpRMjWLKfUWUcOTzBrBCbtWlKaWAztji3nY7ahxhmac
Q/MmVsgMgMx0UrSVliOLeUOZ7hA1/H9SSUyh5QVl4HE0CE05SbjkpeGBF208B2D
an1sOkQLcJqvkkrC+wHjZowMvnyrdHEgM7MYj3IT4BaAUbIwbjW4h/CHCQhDvSr
lNgFAIf+mu6tK9UoYZcVkfTiHVHDCUfhDKFol4MW8ZOoAPDNIOmhsiiSvAzoAwy
70Rn8MuZoO/kOI++kPno7/Gmzj0syPJl1OIU4OHtpbHc5y0tXxhCc1PIhL1LLG8
136EbSsBM8WsUMqsln3Nt66ZAhqCd8UG4SE1DCrT54FB4RlE4CrK2BKha5+IZ2A
z6DyCwj35m5nmBS3P0MozErYZD+4Hw06KdvztwGUC4QGkaxyBMsWCj8IwbMHax4
auCiXhYFaAgpMYc7nCnmDmi4KiavuNU7lXbHaApNXP5Cvhru0CyDxau4hYPcW0T
tAK9jbIcte6BXVAsNsoPPrhrSiWvFGfwFB7fyLvFMVVt/ypx3BlHd/w/lGbTkBv
A7x+Qh5au4PvTDcHu3+tJ8DHCKsBEMD4fSgOygXcxDtGAlLxcXnKAL0CvB0/Y8i
jMctyop0AAAAASUVORK5CYII=
 by: Huey Baidzhanov - Tue, 14 Nov 2023 16:03 UTC

Lou wrote:

> 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.

that .0038 makes no sense. Ie, a photon with a frequency of 1 Hz, would
have a wavelength of 3E8 m, long radiowave already. GPS sats are closer
than this distance. (3E8/.0038 ~ 79E9). Please reconsider. Think on size
and accuracy of the antenna.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<uj06ks$3d3k0$1@paganini.bofh.team>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127869&group=sci.physics.relativity#127869

  copy link   Newsgroups: sci.physics.relativity sci.physics sci.math
Followup: sci.physics.relativity,sci.physics,sci.math
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!paganini.bofh.team!not-for-mail
From: kna...@anurasoo.id (Orlando Shamburkin)
Newsgroups: sci.physics.relativity,sci.physics,sci.math
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Followup-To: sci.physics.relativity,sci.physics,sci.math
Date: Tue, 14 Nov 2023 16:18:37 -0000 (UTC)
Organization: To protect and to server
Message-ID: <uj06ks$3d3k0$1@paganini.bofh.team>
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Tue, 14 Nov 2023 16:18:37 -0000 (UTC)
Injection-Info: paganini.bofh.team; logging-data="3575424"; posting-host="DDidBw00V/VYlZwHU+eEGQ.user.paganini.bofh.team"; mail-complaints-to="usenet@bofh.team"; posting-account="9dIQLXBM7WM9KzA+yjdR4A";
User-Agent: MesNews/1.08.06.00-gb
Cancel-Lock: sha256:cy8xP+Ne/e7qFlhM1ni365t2KtGw6JCUYAjHEhgR2ho=
X-Face: &q^c+BYW"[Q)4)0`,L5aY/eU=*-ae('ffX\A|(vS48NDwPi<quUZZR&t3.\hW2nM
dQ&<g]p>Q!QA6@5kmr?"lgwoW0)G";Znjt0!1n?U_;^(0ao()/7^QM~(a,(O4U:ORaFNX(H
f?NZ9tPwXM1rtRlAI!a+0I;g%v+*33)%Lr=~6(A3!s[4db%+idVW/${GM4%U+7Hf>dXpz*)
f~]]c8,%X7p=<kmDOnSAB?ZUUe[E*1@(h5>$)D^@+a1Y:n-(z./NURMepaC0I$x2NOg$0z>
W[Wq9/o{9fRcs!(7.pI2#"9qE=yw4p+uI9:&PAWGx
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEXp1dddQjMV
HCbBs5x6h5tpa3GyuMO0eX7ekqDpAAACdklEQVQ4jU3UwZLaMAwAUHWyTc/O4uk
5bpm90pqQayF29mxiLdfQsO61NJvm9yvZga1nmAl6SHJsDRDSykNeqcfvau239q
xoQYr3eX+5qq5QsrtYrxQeIVxaBsiroxJKueby/KK+6G8EpmUIVy5QyvEydcdN9
oeBpIf6yLBe7cJ02uuaShlaAXLHcSV8W+Fsx6pM0MJrGcH5weLp0BVPCWy/j/ES
WzPJ6aDUE5i4XmIHtZbtFiUSrCO0hp8jhGGSp5/8ghEu1qZS0hjEz+cbmGCwKHh
TkuL4d7qDMe4o/F4JNBZxrBfw9JEC+3NRIqWIOXvPsA5t/0E6KmRc9w6WK/QPcu
8JqhtYCjJALtEb9L/Gj0uG9bzJBmD16LxEPT7codnaJgA0zXklsRthAaQTwh8AE
PJXauI3cLhlaGs3wCszzrsfcGTgxo1t+ghwKEu3AjoFoB0Z39gWMs1QSlG5FxXB
Gz+Yvh41VctFad/s1wW2TQiVKEfNUBRbL9OuvN6FQRTiMaMhKov1Fvn+waLf0by
5Qjzl1KNtYIv71Bx5eq4Ey8by5vU/+CREnV6F1rCADyF+D3c53iFWGe6wv0NMyb
TWqcv1HTglm+c5QVWUDNQ98E+z6/w7HWUtEjRh0FwmW2CoilgKuwigoebEPOja8
bET7DhBb7J67BcogC/Q61hK6+q0gzzXusYilvK7Beb5LUAgmBxIRBqGW1zTeQZ+
coA8ownqed7RwXB2PYGPo5gy9Egt0tYnsDyIt1p0ZeEG6NHR9Dd05wvoBRBdsTb
4PEfRKa7rCEJ5j6d5oQUcQ1nIZxqwe3gz1CDoRQT9u3SaGt1OALT+B3OR/gh5g+
03AAAAAElFTkSuQmCC
X-Notice: Filtered by postfilter v. 0.9.3
 by: Orlando Shamburkin - Tue, 14 Nov 2023 16:18 UTC

Lou wrote:

> 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.

that .0038 makes no sense. Ie, a photon with a frequency of 1 Hz, would
have a wavelength of 3E8 m, long radiowave already. GPS sats are closer
than this distance. (3E8/.0038 ~ 79E9). Please reconsider. Think on size
and accuracy of the antenna.

Anal-lena Baerbock's Grandfather was 𝗮 𝗡𝗮𝘇𝗶 𝗰𝗼𝗺𝗽𝗹𝗶𝗰𝗶𝘁 𝗶𝗻 𝗸𝗶𝗹𝗹𝗶𝗻𝗴 𝗥𝘂𝘀𝘀𝗶𝗮𝗻 𝗖𝗶𝘃𝗶𝗹𝗶𝗮𝗻𝘀
and she wants to go to war against Russia again - this nasty Slattern
should read some history and find out what Russian Soldiers 𝗱𝗶𝗱 𝘁𝗼 𝗽𝗲𝗼𝗽𝗹𝗲
𝗹𝗶𝗸𝗲 𝗵𝗲𝗿.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<EYP4N.33839$84ya.16368@fx10.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127871&group=sci.physics.relativity#127871

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!paganini.bofh.team!2.eu.feeder.erje.net!feeder.erje.net!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx10.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
Content-Language: en-US
From: relativ...@paulba.no (Paul B. Andersen)
In-Reply-To: <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 66
Message-ID: <EYP4N.33839$84ya.16368@fx10.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Tue, 14 Nov 2023 19:33:56 UTC
Organization: Eweka Internet Services
Date: Tue, 14 Nov 2023 20:35:45 +0100
X-Received-Bytes: 3590
 by: Paul B. Andersen - Tue, 14 Nov 2023 19:35 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<70a46df2-58b6-4832-a845-2daba63ba683n@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127872&group=sci.physics.relativity#127872

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:6214:1874:b0:66d:1371:f7e2 with SMTP id eh20-20020a056214187400b0066d1371f7e2mr67839qvb.6.1699992296727;
Tue, 14 Nov 2023 12:04:56 -0800 (PST)
X-Received: by 2002:a17:903:2583:b0:1cc:478b:ef1 with SMTP id
jb3-20020a170903258300b001cc478b0ef1mr871963plb.13.1699992296332; Tue, 14 Nov
2023 12:04:56 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Tue, 14 Nov 2023 12:04:55 -0800 (PST)
In-Reply-To: <fa985245-de4a-4202-b8e6-b062efae5465n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=69.181.75.9; posting-account=vma-PgoAAABrctSmMdefNKZ-c5S8buvP
NNTP-Posting-Host: 69.181.75.9
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <fa985245-de4a-4202-b8e6-b062efae5465n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <70a46df2-58b6-4832-a845-2daba63ba683n@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: eggy2001...@gmail.com (Dono.)
Injection-Date: Tue, 14 Nov 2023 20:04:56 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 1908
 by: Dono. - Tue, 14 Nov 2023 20:04 UTC

On Monday, November 13, 2023 at 9:10:16 PM UTC-8, Richard Hertz wrote:
> snip fresh imbecilities

Do you need a shovel?

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<21ed882a-4554-4965-9da5-2d8fc338e8f9n@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127874&group=sci.physics.relativity#127874

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:1016:0:b0:412:1bc3:10f3 with SMTP id z22-20020ac81016000000b004121bc310f3mr65195qti.13.1699994317950;
Tue, 14 Nov 2023 12:38:37 -0800 (PST)
X-Received: by 2002:a17:902:efc2:b0:1cc:70f2:c1d5 with SMTP id
ja2-20020a170902efc200b001cc70f2c1d5mr855771plb.11.1699994317628; Tue, 14 Nov
2023 12:38:37 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Tue, 14 Nov 2023 12:38:36 -0800 (PST)
In-Reply-To: <e4991d41-f430-45e4-bf21-f50d1dad56cbn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=83.21.204.13; posting-account=I3DWzAoAAACOmZUdDcZ-C0PqAZGVsbW0
NNTP-Posting-Host: 83.21.204.13
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <fa985245-de4a-4202-b8e6-b062efae5465n@googlegroups.com>
<e4991d41-f430-45e4-bf21-f50d1dad56cbn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <21ed882a-4554-4965-9da5-2d8fc338e8f9n@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: maluwozn...@gmail.com (Maciej Wozniak)
Injection-Date: Tue, 14 Nov 2023 20:38:37 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2219
 by: Maciej Wozniak - Tue, 14 Nov 2023 20:38 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127884&group=sci.physics.relativity#127884

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:3995:b0:77a:4aa:5502 with SMTP id ro21-20020a05620a399500b0077a04aa5502mr97309qkn.2.1700054941020;
Wed, 15 Nov 2023 05:29:01 -0800 (PST)
X-Received: by 2002:a63:fd06:0:b0:5bd:fe41:194e with SMTP id
d6-20020a63fd06000000b005bdfe41194emr1273534pgh.11.1700054940714; Wed, 15 Nov
2023 05:29:00 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 15 Nov 2023 05:29:00 -0800 (PST)
In-Reply-To: <EYP4N.33839$84ya.16368@fx10.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=92.23.58.23; posting-account=l0YVUwoAAACvUnQCooL-PCAznCzJnJho
NNTP-Posting-Host: 92.23.58.23
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: noelturn...@live.co.uk (Lou)
Injection-Date: Wed, 15 Nov 2023 13:29:01 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4760
 by: Lou - Wed, 15 Nov 2023 13:29 UTC

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?

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<IZ75N.59141$Wkza.55257@fx14.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127887&group=sci.physics.relativity#127887

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx14.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
From: relativ...@paulba.no (Paul B. Andersen)
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
Content-Language: en-GB
In-Reply-To: <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 43
Message-ID: <IZ75N.59141$Wkza.55257@fx14.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Wed, 15 Nov 2023 18:20:24 UTC
Organization: Eweka Internet Services
Date: Wed, 15 Nov 2023 19:22:15 +0100
X-Received-Bytes: 3105
 by: Paul B. Andersen - Wed, 15 Nov 2023 18:22 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<3cec9ffd-5d06-4715-a707-11171ccdd4ddn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127890&group=sci.physics.relativity#127890

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:479b:b0:774:2ad1:b816 with SMTP id dt27-20020a05620a479b00b007742ad1b816mr133600qkb.4.1700081603912;
Wed, 15 Nov 2023 12:53:23 -0800 (PST)
X-Received: by 2002:a17:90a:7e88:b0:280:2609:6d5d with SMTP id
j8-20020a17090a7e8800b0028026096d5dmr3392006pjl.4.1700081603651; Wed, 15 Nov
2023 12:53:23 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 15 Nov 2023 12:53:22 -0800 (PST)
In-Reply-To: <IZ75N.59141$Wkza.55257@fx14.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=181.84.181.162; posting-account=blnzJwoAAAA-82jKM1F-uNmKbbRkrU6D
NNTP-Posting-Host: 181.84.181.162
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3cec9ffd-5d06-4715-a707-11171ccdd4ddn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: hertz...@gmail.com (Richard Hertz)
Injection-Date: Wed, 15 Nov 2023 20:53:23 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3060
 by: Richard Hertz - Wed, 15 Nov 2023 20:53 UTC

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!

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<VNa5N.96996$D%n3.51991@fx01.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127892&group=sci.physics.relativity#127892

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!usenet.goja.nl.eu.org!3.eu.feeder.erje.net!feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx01.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
<3cec9ffd-5d06-4715-a707-11171ccdd4ddn@googlegroups.com>
Content-Language: en-US
From: relativ...@paulba.no (Paul B. Andersen)
In-Reply-To: <3cec9ffd-5d06-4715-a707-11171ccdd4ddn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 50
Message-ID: <VNa5N.96996$D%n3.51991@fx01.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Wed, 15 Nov 2023 21:32:37 UTC
Organization: Eweka Internet Services
Date: Wed, 15 Nov 2023 22:34:28 +0100
X-Received-Bytes: 3558
 by: Paul B. Andersen - Wed, 15 Nov 2023 21:34 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<LTa5N.148576$LJv3.122920@fx02.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127893&group=sci.physics.relativity#127893

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!feeder1.feed.usenet.farm!feed.usenet.farm!peer03.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx02.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Content-Language: en-US
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
<3cec9ffd-5d06-4715-a707-11171ccdd4ddn@googlegroups.com>
<VNa5N.96996$D%n3.51991@fx01.ams4>
From: relativ...@paulba.no (Paul B. Andersen)
In-Reply-To: <VNa5N.96996$D%n3.51991@fx01.ams4>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 61
Message-ID: <LTa5N.148576$LJv3.122920@fx02.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Wed, 15 Nov 2023 21:38:51 UTC
Organization: Eweka Internet Services
Date: Wed, 15 Nov 2023 22:40:42 +0100
X-Received-Bytes: 3692
 by: Paul B. Andersen - Wed, 15 Nov 2023 21:40 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<a2be0f76-b7d9-43c9-8c93-db7d5a61b7f4n@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127895&group=sci.physics.relativity#127895

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:4b50:0:b0:417:b53e:c659 with SMTP id e16-20020ac84b50000000b00417b53ec659mr155342qts.13.1700114008685;
Wed, 15 Nov 2023 21:53:28 -0800 (PST)
X-Received: by 2002:a17:902:a9c9:b0:1cc:cc77:94ed with SMTP id
b9-20020a170902a9c900b001cccc7794edmr2022897plr.10.1700114008409; Wed, 15 Nov
2023 21:53:28 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 15 Nov 2023 21:53:27 -0800 (PST)
In-Reply-To: <IZ75N.59141$Wkza.55257@fx14.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=83.21.204.13; posting-account=I3DWzAoAAACOmZUdDcZ-C0PqAZGVsbW0
NNTP-Posting-Host: 83.21.204.13
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <a2be0f76-b7d9-43c9-8c93-db7d5a61b7f4n@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: maluwozn...@gmail.com (Maciej Wozniak)
Injection-Date: Thu, 16 Nov 2023 05:53:28 +0000
Content-Type: text/plain; charset="UTF-8"
X-Received-Bytes: 2278
 by: Maciej Wozniak - Thu, 16 Nov 2023 05:53 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127897&group=sci.physics.relativity#127897

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:6214:1d28:b0:670:754b:2e6d with SMTP id f8-20020a0562141d2800b00670754b2e6dmr268989qvd.7.1700139514325;
Thu, 16 Nov 2023 04:58:34 -0800 (PST)
X-Received: by 2002:a17:902:ef93:b0:1cc:5d23:2792 with SMTP id
iz19-20020a170902ef9300b001cc5d232792mr2085541plb.7.1700139513898; Thu, 16
Nov 2023 04:58:33 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 16 Nov 2023 04:58:33 -0800 (PST)
In-Reply-To: <IZ75N.59141$Wkza.55257@fx14.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=92.23.58.23; posting-account=l0YVUwoAAACvUnQCooL-PCAznCzJnJho
NNTP-Posting-Host: 92.23.58.23
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: noelturn...@live.co.uk (Lou)
Injection-Date: Thu, 16 Nov 2023 12:58:34 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 5117
 by: Lou - Thu, 16 Nov 2023 12:58 UTC

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

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<JWt5N.235069$tzR.22315@fx05.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127900&group=sci.physics.relativity#127900

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx05.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
<eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
Content-Language: en-US
From: relativ...@paulba.no (Paul B. Andersen)
In-Reply-To: <eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 93
Message-ID: <JWt5N.235069$tzR.22315@fx05.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Thu, 16 Nov 2023 19:19:05 UTC
Organization: Eweka Internet Services
Date: Thu, 16 Nov 2023 20:20:59 +0100
X-Received-Bytes: 4911
 by: Paul B. Andersen - Thu, 16 Nov 2023 19:20 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127901&group=sci.physics.relativity#127901

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:7ec8:0:b0:421:c2a4:8647 with SMTP id x8-20020ac87ec8000000b00421c2a48647mr167232qtj.9.1700165804633;
Thu, 16 Nov 2023 12:16:44 -0800 (PST)
X-Received: by 2002:a63:1017:0:b0:589:5235:b3cb with SMTP id
f23-20020a631017000000b005895235b3cbmr519684pgl.3.1700165803896; Thu, 16 Nov
2023 12:16:43 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 16 Nov 2023 12:16:43 -0800 (PST)
In-Reply-To: <JWt5N.235069$tzR.22315@fx05.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=92.23.58.23; posting-account=l0YVUwoAAACvUnQCooL-PCAznCzJnJho
NNTP-Posting-Host: 92.23.58.23
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4> <eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
<JWt5N.235069$tzR.22315@fx05.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: noelturn...@live.co.uk (Lou)
Injection-Date: Thu, 16 Nov 2023 20:16:44 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 6837
 by: Lou - Thu, 16 Nov 2023 20:16 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<2faaf292-ea75-4f0a-b98d-09463f5072f6n@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127902&group=sci.physics.relativity#127902

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:22aa:b0:774:143e:f9a1 with SMTP id p10-20020a05620a22aa00b00774143ef9a1mr198934qkh.11.1700171910733;
Thu, 16 Nov 2023 13:58:30 -0800 (PST)
X-Received: by 2002:a17:903:4101:b0:1c9:f267:1661 with SMTP id
r1-20020a170903410100b001c9f2671661mr750304pld.2.1700171910432; Thu, 16 Nov
2023 13:58:30 -0800 (PST)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 16 Nov 2023 13:58:29 -0800 (PST)
In-Reply-To: <JWt5N.235069$tzR.22315@fx05.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=83.21.204.13; posting-account=I3DWzAoAAACOmZUdDcZ-C0PqAZGVsbW0
NNTP-Posting-Host: 83.21.204.13
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4> <eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
<JWt5N.235069$tzR.22315@fx05.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <2faaf292-ea75-4f0a-b98d-09463f5072f6n@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: maluwozn...@gmail.com (Maciej Wozniak)
Injection-Date: Thu, 16 Nov 2023 21:58:30 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3486
 by: Maciej Wozniak - Thu, 16 Nov 2023 21:58 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<bSH5N.74382$Wkza.49371@fx14.ams4>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127912&group=sci.physics.relativity#127912

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!paganini.bofh.team!2.eu.feeder.erje.net!feeder.erje.net!newsreader4.netcologne.de!news.netcologne.de!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.ams4!peer.am4.highwinds-media.com!news.highwinds-media.com!fx14.ams4.POSTED!not-for-mail
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Newsgroups: sci.physics.relativity
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4>
<19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
<eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
<JWt5N.235069$tzR.22315@fx05.ams4>
<d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>
Content-Language: en-US
From: relativ...@paulba.no (Paul B. Andersen)
In-Reply-To: <d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 71
Message-ID: <bSH5N.74382$Wkza.49371@fx14.ams4>
X-Complaints-To: abuse@eweka.nl
NNTP-Posting-Date: Fri, 17 Nov 2023 11:09:59 UTC
Organization: Eweka Internet Services
Date: Fri, 17 Nov 2023 12:11:54 +0100
X-Received-Bytes: 3989
 by: Paul B. Andersen - Fri, 17 Nov 2023 11:11 UTC

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/

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<9668c19d-3786-4940-9c99-1b1f96e0de2en@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127916&group=sci.physics.relativity#127916

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a0c:e5cb:0:b0:677:9fb9:29b3 with SMTP id u11-20020a0ce5cb000000b006779fb929b3mr184282qvm.5.1700248497263;
Fri, 17 Nov 2023 11:14:57 -0800 (PST)
X-Received: by 2002:a63:f602:0:b0:5bd:9b7f:b08d with SMTP id
m2-20020a63f602000000b005bd9b7fb08dmr11701pgh.0.1700248496650; Fri, 17 Nov
2023 11:14:56 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!feeder1.cambriumusenet.nl!feed.tweak.nl!209.85.160.216.MISMATCH!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Fri, 17 Nov 2023 11:14:56 -0800 (PST)
In-Reply-To: <bSH5N.74382$Wkza.49371@fx14.ams4>
Injection-Info: google-groups.googlegroups.com; posting-host=83.21.204.13; posting-account=I3DWzAoAAACOmZUdDcZ-C0PqAZGVsbW0
NNTP-Posting-Host: 83.21.204.13
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<N8b3N.3912$2E8a.3592@fx07.ams4> <19c81692-6566-42c5-ba36-5fe483a2c56fn@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4> <eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
<JWt5N.235069$tzR.22315@fx05.ams4> <d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>
<bSH5N.74382$Wkza.49371@fx14.ams4>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9668c19d-3786-4940-9c99-1b1f96e0de2en@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: maluwozn...@gmail.com (Maciej Wozniak)
Injection-Date: Fri, 17 Nov 2023 19:14:57 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4138
 by: Maciej Wozniak - Fri, 17 Nov 2023 19:14 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<2f9534d6-b7ce-4ba2-aaa9-a9cad0f6f13fn@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127969&group=sci.physics.relativity#127969

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:6214:2a87:b0:66d:260:d0ed with SMTP id jr7-20020a0562142a8700b0066d0260d0edmr114508qvb.8.1700418045176;
Sun, 19 Nov 2023 10:20:45 -0800 (PST)
X-Received: by 2002:a17:902:d345:b0:1cc:3355:9fa9 with SMTP id
l5-20020a170902d34500b001cc33559fa9mr1484360plk.10.1700418044915; Sun, 19 Nov
2023 10:20:44 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sun, 19 Nov 2023 10:20:44 -0800 (PST)
In-Reply-To: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=137.150.105.150; posting-account=AYxSsgoAAABJAl_IKPpFpkhDa-pp32Mm
NNTP-Posting-Host: 137.150.105.150
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <2f9534d6-b7ce-4ba2-aaa9-a9cad0f6f13fn@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: carleto4...@gmail.com (carl eto)
Injection-Date: Sun, 19 Nov 2023 18:20:45 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 1307
 by: carl eto - Sun, 19 Nov 2023 18:20 UTC

> t' = γ (t - vx/c)

The relativistic velocity v is not constant.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<ujdlcd$3tq96$1@dont-email.me>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127970&group=sci.physics.relativity#127970

  copy link   Newsgroups: sci.physics.relativity
Path: i2pn2.org!i2pn.org!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: vol...@invalid.invalid (Volney)
Newsgroups: sci.physics.relativity
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving
frame.
Date: Sun, 19 Nov 2023 13:49:46 -0500
Organization: A noiseless patient Spider
Lines: 53
Message-ID: <ujdlcd$3tq96$1@dont-email.me>
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4>
<fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4>
<8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4>
<2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4>
<c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4>
<2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4>
<5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4>
<04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4>
<eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
<JWt5N.235069$tzR.22315@fx05.ams4>
<d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>
<bSH5N.74382$Wkza.49371@fx14.ams4>
<9668c19d-3786-4940-9c99-1b1f96e0de2en@googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Injection-Date: Sun, 19 Nov 2023 18:49:49 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="a324ea2b9e88b1f583f435e91827e464";
logging-data="4122918"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1+FOpRYd3v8xRAwfkgl7wbE"
User-Agent: Mozilla Thunderbird
Cancel-Lock: sha1:H6572lrdTLj/rgvMKiz94xGWW2U=
Content-Language: en-US
In-Reply-To: <9668c19d-3786-4940-9c99-1b1f96e0de2en@googlegroups.com>
 by: Volney - Sun, 19 Nov 2023 18:49 UTC

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.

Re: Conflicts in SR when using horizontal light clocks in the moving frame.

<96b16576-9efe-4777-9783-87573ae7c233n@googlegroups.com>

  copy mid

https://www.novabbs.com/tech/article-flat.php?id=127973&group=sci.physics.relativity#127973

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:22a8:b0:421:ac6a:39c6 with SMTP id ay40-20020a05622a22a800b00421ac6a39c6mr153949qtb.1.1700423396121;
Sun, 19 Nov 2023 11:49:56 -0800 (PST)
X-Received: by 2002:a17:902:728d:b0:1ca:8e79:53b7 with SMTP id
d13-20020a170902728d00b001ca8e7953b7mr1609248pll.9.1700423395819; Sun, 19 Nov
2023 11:49:55 -0800 (PST)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sun, 19 Nov 2023 11:49:55 -0800 (PST)
In-Reply-To: <ujdlcd$3tq96$1@dont-email.me>
Injection-Info: google-groups.googlegroups.com; posting-host=83.21.156.250; posting-account=I3DWzAoAAACOmZUdDcZ-C0PqAZGVsbW0
NNTP-Posting-Host: 83.21.156.250
References: <5dd8497a-ccd5-43b3-9b4c-f3a8d7e7a3b0n@googlegroups.com>
<XJv3N.13208$Wkza.7052@fx14.ams4> <fe20fc3c-3f29-4f25-a327-97d76b164ba3n@googlegroups.com>
<sKK3N.34843$tzR.17852@fx05.ams4> <8a4acd1a-497b-468f-b7ef-ee6321f9933cn@googlegroups.com>
<a454N.65646$OPFb.14853@fx15.ams4> <2eb125ef-069d-40d6-bc4d-ad56e884c99en@googlegroups.com>
<Yym4N.93802$OPFb.29638@fx15.ams4> <c91e0c40-807e-4e45-ac5c-c80971e091abn@googlegroups.com>
<11u4N.81971$96D1.79021@fx04.ams4> <2a8e836a-34ca-4645-b0f5-07e180b8f876n@googlegroups.com>
<wrI4N.74304$ydda.66481@fx13.ams4> <5a2ce75b-0af9-499c-9016-2ab5b07c94ccn@googlegroups.com>
<EYP4N.33839$84ya.16368@fx10.ams4> <04e38ed6-a7f0-4f45-9dbd-f5e04febb54fn@googlegroups.com>
<IZ75N.59141$Wkza.55257@fx14.ams4> <eb72535a-3eac-4db4-9b43-28f2805f8315n@googlegroups.com>
<JWt5N.235069$tzR.22315@fx05.ams4> <d8b4eaed-50a4-4c3e-b551-2a5f8a12612fn@googlegroups.com>
<bSH5N.74382$Wkza.49371@fx14.ams4> <9668c19d-3786-4940-9c99-1b1f96e0de2en@googlegroups.com>
<ujdlcd$3tq96$1@dont-email.me>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <96b16576-9efe-4777-9783-87573ae7c233n@googlegroups.com>
Subject: Re: Conflicts in SR when using horizontal light clocks in the moving frame.
From: maluwozn...@gmail.com (Maciej Wozniak)
Injection-Date: Sun, 19 Nov 2023 19:49:56 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4946
 by: Maciej Wozniak - Sun, 19 Nov 2023 19:49 UTC

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.

Pages:123
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor