On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:

> > Excuse me, stupid Mike, are GPS clocks
> > set to your 9 192 631 770 ISO idiocy?
> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> frequency (9192631774.1)

So, for a relativistic idiot setting it
to 9192631774.1 is an indirect
way of setting it to 9 192 631 770.
Isn't it sweet?
That's what The Shit's brainwashing
is doing with the brains of its victims.

El viernes, 15 de septiembre de 2023 a las 9:00:40 UTC-3, Maciej Wozniak escribió:
> On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
>
> > > Excuse me, stupid Mike, are GPS clocks
> > > set to your 9 192 631 770 ISO idiocy?
> > Yes, poor quarterbrain. But indirectly, of course. They are set to a
> > frequency (9192631774.1)
>
> So, for a relativistic idiot setting it
> to 9192631774.1 is an indirect
> way of setting it to 9 192 631 770.
> Isn't it sweet?
> That's what The Shit's brainwashing
> is doing with the brains of its victims.

GPS clocks are set to tick, in orbit, at 10.2299999954326 MHz (see document IS-GPS-200M, section 3.3.1.1). Those signals are received on the ground at 10.23 MHz.

On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
>
>>> Excuse me, stupid Mike, are GPS clocks
>>> set to your 9 192 631 770 ISO idiocy?
>> Yes, poor quarterbrain. But indirectly, of course. They are set to a
>> frequency (9192631774.1)
>
> So, for a relativistic idiot setting it
> to 9192631774.1 is an indirect
> way of setting it to 9 192 631 770.
> Isn't it sweet?

Exactly, to compensate for GR.

Just like if, for some reason, you wanted the horn of an approaching
train to be heard in the station at a musical tone of "B♭", the train's
horn must sound at, perhaps "A", to compensate for the Doppler Effect.

On Friday, 15 September 2023 at 16:12:46 UTC+2, Paparios wrote:
> El viernes, 15 de septiembre de 2023 a las 9:00:40 UTC-3, Maciej Wozniak escribió:
> > On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> >
> > > > Excuse me, stupid Mike, are GPS clocks
> > > > set to your 9 192 631 770 ISO idiocy?
> > > Yes, poor quarterbrain. But indirectly, of course. They are set to a
> > > frequency (9192631774.1)
> >
> > So, for a relativistic idiot setting it
> > to 9192631774.1 is an indirect
> > way of setting it to 9 192 631 770.
> > Isn't it sweet?
> > That's what The Shit's brainwashing
> > is doing with the brains of its victims.
> GPS clocks are set to tick, in orbit, at

Clocks, poor halfbrain, generally are to
indicate time. GPS clocks are indicating
GPS time. See your precious documentation.

On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
> On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> > On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> >
> >>> Excuse me, stupid Mike, are GPS clocks
> >>> set to your 9 192 631 770 ISO idiocy?
> >> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> >> frequency (9192631774.1)
> >
> > So, for a relativistic idiot setting it
> > to 9192631774.1 is an indirect
> > way of setting it to 9 192 631 770.
> > Isn't it sweet?
> Exactly

Exactly. Setting to 9192631774.1 is
setting to 9 192 631 770.
Exactly, that's whatr The Shit's brainwashing
is doing to the brains of its victims.

El viernes, 15 de septiembre de 2023 a las 12:14:25 UTC-3, Maciej Wozniak escribió:
> On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
> > On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> > > On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> > >
> > >>> Excuse me, stupid Mike, are GPS clocks
> > >>> set to your 9 192 631 770 ISO idiocy?
> > >> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> > >> frequency (9192631774.1)
> > >
> > > So, for a relativistic idiot setting it
> > > to 9192631774.1 is an indirect
> > > way of setting it to 9 192 631 770.
> > > Isn't it sweet?
> > Exactly
> Exactly. Setting to 9192631774.1 is
> setting to 9 192 631 770.
> Exactly, that's whatr The Shit's brainwashing
> is doing to the brains of its victims.

Wrong!!! A Cesium atomic clock can't be made to tick at 9192631774.1 since its operation only work at the 9192631770 Hz frequency (the clock resonance frequency of Cesium).

GPS use download counters to set the ticking frequency from 9192631770 Hz to 10.2299999954326 MHz

On 9/15/2023 11:14 AM, Maciej Wozniak wrote:
> On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
>> On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
>>> On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
>>>
>>>>> Excuse me, stupid Mike, are GPS clocks
>>>>> set to your 9 192 631 770 ISO idiocy?

>>>> Yes, poor quarterbrain. But indirectly, of course. They are set to a
>>>> frequency (9192631774.1)
>>>
>>> So, for a relativistic idiot setting it
>>> to 9192631774.1 is an indirect
>>> way of setting it to 9 192 631 770.
>>> Isn't it sweet?

>> Exactly[, to compensate for GR.

>> Just like if, for some reason, you wanted the horn of an approaching train to be heard in the station at a musical tone of "B♭", the train's horn must sound at, perhaps "A", to compensate for the Doppler Effect.]

Naughty boy, janitor, snipping important quoted material. No toilets for
you to lick tonight!
>
> Exactly. Setting to 9192631774.1

In other words, like the train horn honking at "A"

> is setting to 9 192 631 770.

In other words, like the horn being heard at the station at "B♭".

The only difference is the cause of the change in frequencies, Doppler
effect for the train horn and GR for the GPS system.

On Friday, 15 September 2023 at 19:22:16 UTC+2, Paparios wrote:
> El viernes, 15 de septiembre de 2023 a las 12:14:25 UTC-3, Maciej Wozniak escribió:
> > On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
> > > On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> > > > On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> > > >
> > > >>> Excuse me, stupid Mike, are GPS clocks
> > > >>> set to your 9 192 631 770 ISO idiocy?
> > > >> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> > > >> frequency (9192631774.1)
> > > >
> > > > So, for a relativistic idiot setting it
> > > > to 9192631774.1 is an indirect
> > > > way of setting it to 9 192 631 770.
> > > > Isn't it sweet?
> > > Exactly
> > Exactly. Setting to 9192631774.1 is
> > setting to 9 192 631 770.
> > Exactly, that's whatr The Shit's brainwashing
> > is doing to the brains of its victims.
> Wrong!!! A Cesium atomic clock can't be made to tick at 9192631774.1

Surely wrong; what GPS crew did is a mortal
sin and for sure Giant Guru will banish them
for that from the relativistic eden.

On Friday, 15 September 2023 at 19:23:56 UTC+2, Volney wrote:
> On 9/15/2023 11:14 AM, Maciej Wozniak wrote:
> > On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
> >> On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> >>> On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> >>>
> >>>>> Excuse me, stupid Mike, are GPS clocks
> >>>>> set to your 9 192 631 770 ISO idiocy?
>
> >>>> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> >>>> frequency (9192631774.1)
> >>>
> >>> So, for a relativistic idiot setting it
> >>> to 9192631774.1 is an indirect
> >>> way of setting it to 9 192 631 770.
> >>> Isn't it sweet?
> >> Exactly[, to compensate for GR.
>
> >> Just like if, for some reason, you wanted the horn of an approaching train to be heard in the station at a musical tone of "B♭", the train's horn must sound at, perhaps "A", to compensate for the Doppler Effect.]
>
> Naughty boy, janitor, snipping important quoted material.

No, stupid Mike, you only imagine it
was important; as you're a delususional
idiot your opinion doesn't matter.

> > Exactly. Setting to 9192631774.1
>
> In other words

And In THESE words - I asked you
whether the clocks were sedt to 9192631770
and your answer was - of course they were because
they were set to 9192631774.
That's what The Shit's brainwashiong is making
to the brains of its victims.

On Friday, September 15, 2023 at 2:23:56 PM UTC-3, Volney wrote:
> On 9/15/2023 11:14 AM, Maciej Wozniak wrote:
> > On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
> >> On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> >>> On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> >>>
> >>>>> Excuse me, stupid Mike, are GPS clocks
> >>>>> set to your 9 192 631 770 ISO idiocy?
>
> >>>> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> >>>> frequency (9192631774.1)
> >>>
> >>> So, for a relativistic idiot setting it
> >>> to 9192631774.1 is an indirect
> >>> way of setting it to 9 192 631 770.
> >>> Isn't it sweet?
> >> Exactly[, to compensate for GR.
>
> >> Just like if, for some reason, you wanted the horn of an approaching train to be heard in the station at a musical tone of "B♭", the train's horn must sound at, perhaps "A", to compensate for the Doppler Effect.]
>
> Naughty boy, janitor, snipping important quoted material. No toilets for
> you to lick tonight!
> >
> > Exactly. Setting to 9192631774.1
>
> In other words, like the train horn honking at "A"
> > is setting to 9 192 631 770.
> In other words, like the horn being heard at the station at "B♭".
>
> The only difference is the cause of the change in frequencies, Doppler
> effect for the train horn and GR for the GPS system.

Volney, seriously, stop talking nonsense and start to study how GPS works, but do it thoroughly using many references.

You are so mentally frozen with Schwarzschild's solution being used in THE REAL WORLD, that you have lost (COMPLETELY)
how ANY GNSS constellation really works.

To cite few mistakes:

1) By Sept 2023, there are 31 GPS SV in activity, and ONLY ONE use cesium clocks for civilian applications. The other 30 use rubidium.

2) The master clock at each SV works at 10.230000000 Mhz to compute GPS Week Time and ANY OTHER frequency used in the SV.

3) The master clock at each SV delivers the onboard GPS Time every 12.5 minutes, with the complete almanac (ephemeris, data clock
correction parameters, etc.). Each GPS receiver store the whole almanac for every SV every 12.5 minutes, to compute solution on Earth.

1 Superframe = 25 Frames x 5 Subframes --> 10 x 30 x 5 x 25 bits = 37500 bits for a complete almanac (transmitted at 50 bps)

4) Every SV mantains the GPS Time within 1 nanosecond error in the constellation (civilian apps), as it's uploaded from Earth Control
Stations no less than THREE TIMES A DAY.

5) Any relativistic correction, if it's desired, HAS TO BE COMPUTED ON THE GPS RECEIVER, not in every SV (GPS satellite).

6) In commercial GPS receivers, the MOST IMPORTANT FACTOR to be corrected is the RECEIVER GPS Time, which is the source of
most errors. The errors in the transmitted GPS Time, every 12.5 minutes, are so small that they can be ignored. This allows to
calculate the true distance satellite-user (pseudoranging ρ).

If there were no errors or degradation, ρ = c (GPS Timeʳᵉᶜ - GPS Timeˢᵛ), but errors in GPS Timeʳᵉᶜ and ECEF xyz user coordinates (not
known initially) requires that the GPS receiver make an iterative procedure to obtain the corrected GPS Timeʳᵉᶜ and ECEF coordinates.

The receiver resolves error around +/- 10% of initial ECEF coordinates in less than 10 loops (almost instantaneous computation), and
then translate ECEF to latitude-longitude-altitude on a map.

Relativity HAS ZERO ACCOUNTABILITY for this procedure and IS IGNORED in most articles, lectures or books that deal with
GNSS positioning.

So, have A LITTLE BIT OF SHAME, start studying the GNSS positioning problem from MODERN SOURCES (not before 2005), and
stop talking about Schwarzschild and GR as if it HAS A ROLE in GNSS. Grow up!

And, above all, stop talking idiocies about cesium or rubidium fundamental frequencies, as they are IRRELEVANT IN GPS. What
matters is that GPS Time is sustained by atomic clocks, and synchronized from Earth every 8 hour or less per day.

And the above is ONLY for single frequency ranging in civilian applications, like in your smartphone (CER < 7 meters). In other
fields, CER < 10 cm with much more complex receivers and 2 or three SV frequencies.

El viernes, 15 de septiembre de 2023 a las 15:26:19 UTC-3, Richard Hertz escribió:
> On Friday, September 15, 2023 at 2:23:56 PM UTC-3, Volney wrote:
> > On 9/15/2023 11:14 AM, Maciej Wozniak wrote:
> > > On Friday, 15 September 2023 at 16:44:08 UTC+2, Volney wrote:
> > >> On 9/15/2023 8:00 AM, Maciej Wozniak wrote:
> > >>> On Friday, 15 September 2023 at 00:13:53 UTC+2, Volney wrote:
> > >>>
> > >>>>> Excuse me, stupid Mike, are GPS clocks
> > >>>>> set to your 9 192 631 770 ISO idiocy?
> >
> > >>>> Yes, poor quarterbrain. But indirectly, of course. They are set to a
> > >>>> frequency (9192631774.1)
> > >>>
> > >>> So, for a relativistic idiot setting it
> > >>> to 9192631774.1 is an indirect
> > >>> way of setting it to 9 192 631 770.
> > >>> Isn't it sweet?
> > >> Exactly[, to compensate for GR.
> >
> > >> Just like if, for some reason, you wanted the horn of an approaching train to be heard in the station at a musical tone of "B♭", the train's horn must sound at, perhaps "A", to compensate for the Doppler Effect..]
> >
> > Naughty boy, janitor, snipping important quoted material. No toilets for
> > you to lick tonight!
> > >
> > > Exactly. Setting to 9192631774.1
> >
> > In other words, like the train horn honking at "A"
> > > is setting to 9 192 631 770.
> > In other words, like the horn being heard at the station at "B♭".
> >
> > The only difference is the cause of the change in frequencies, Doppler
> > effect for the train horn and GR for the GPS system.
> Volney, seriously, stop talking nonsense and start to study how GPS works, but do it thoroughly using many references.
>
> You are so mentally frozen with Schwarzschild's solution being used in THE REAL WORLD, that you have lost (COMPLETELY)
> how ANY GNSS constellation really works.
>
> To cite few mistakes:
>
> 1) By Sept 2023, there are 31 GPS SV in activity, and ONLY ONE use cesium clocks for civilian applications. The other 30 use rubidium.
>
> 2) The master clock at each SV works at 10.230000000 Mhz to compute GPS Week Time and ANY OTHER frequency used in the SV.
>
> 3) The master clock at each SV delivers the onboard GPS Time every 12.5 minutes, with the complete almanac (ephemeris, data clock
> correction parameters, etc.). Each GPS receiver store the whole almanac for every SV every 12.5 minutes, to compute solution on Earth.
>
> 1 Superframe = 25 Frames x 5 Subframes --> 10 x 30 x 5 x 25 bits = 37500 bits for a complete almanac (transmitted at 50 bps)
>
> 4) Every SV mantains the GPS Time within 1 nanosecond error in the constellation (civilian apps), as it's uploaded from Earth Control
> Stations no less than THREE TIMES A DAY.
>
> 5) Any relativistic correction, if it's desired, HAS TO BE COMPUTED ON THE GPS RECEIVER, not in every SV (GPS satellite).
>
> 6) In commercial GPS receivers, the MOST IMPORTANT FACTOR to be corrected is the RECEIVER GPS Time, which is the source of
> most errors. The errors in the transmitted GPS Time, every 12.5 minutes, are so small that they can be ignored. This allows to
> calculate the true distance satellite-user (pseudoranging ρ).
>
> If there were no errors or degradation, ρ = c (GPS Timeʳᵉᶜ - GPS Timeˢᵛ), but errors in GPS Timeʳᵉᶜ and ECEF xyz user coordinates (not
> known initially) requires that the GPS receiver make an iterative procedure to obtain the corrected GPS Timeʳᵉᶜ and ECEF coordinates.
>
> The receiver resolves error around +/- 10% of initial ECEF coordinates in less than 10 loops (almost instantaneous computation), and
> then translate ECEF to latitude-longitude-altitude on a map.
>
> Relativity HAS ZERO ACCOUNTABILITY for this procedure and IS IGNORED in most articles, lectures or books that deal with
> GNSS positioning.
>
> So, have A LITTLE BIT OF SHAME, start studying the GNSS positioning problem from MODERN SOURCES (not before 2005), and
> stop talking about Schwarzschild and GR as if it HAS A ROLE in GNSS. Grow up!
>
> And, above all, stop talking idiocies about cesium or rubidium fundamental frequencies, as they are IRRELEVANT IN GPS. What
> matters is that GPS Time is sustained by atomic clocks, and synchronized from Earth every 8 hour or less per day.
>
> And the above is ONLY for single frequency ranging in civilian applications, like in your smartphone (CER < 7 meters). In other
> fields, CER < 10 cm with much more complex receivers and 2 or three SV frequencies.

Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1

On Friday, September 15, 2023 at 7:23:47 PM UTC-3, Paparios wrote:

<snip>

> Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1

As usual, Miguelito, you're full of shit and ignorance. Read (STUDY) these sections. Don't fool yourself like in your thesis, 40 years ago.

3.3.1.1 Frequency Plan (legacy point since 1993)

3.3.4 GPS Time and SV Z-Count

20.3.3.3.3.1 User Algorithm for SV Clock Correction (here states that is up to the GPS receiver to use these corrections)

20.3.3.5.2.2 Almanac Reference Time
20.3.3.5.2.3 Almanac Time Parameters
20.3.3.5.2.4 Coordinated Universal Time (UTC)

30.3.3.2.3 User Algorithms for SV Clock Correction Data

30.3.3.6.2 UTC and GPS Time

Now, study all of the above plus this tutorial. Then come back here and write opinions, not shitty indoctrination.

https://indico.ictp.it/event/a12180/session/21/contribution/12/material/0/0..pdf

Calculation of GPS PNT Solution
Dr. John F. Raquet
Air Force Institute of Technology
Advanced Navigation Technology (ANT) Center

QUESTION FOR YOU: Do you have, after reading all of the above, understand how your smartphone GNSS HW/SW compute your location?

If NOT, go back to study deeper and thoroughly. But maybe you can't. Aging sucks

On 9/15/2023 2:26 PM, Richard Hertz wrote:

> Volney, seriously, stop talking nonsense and start to study how GPS works, but do it thoroughly using many references.

In particular, the oficial GPS document (IS-GPS-200M), as Paparios
points out.
>
> You are so mentally frozen with Schwarzschild's solution being used in THE REAL WORLD, that you have lost (COMPLETELY)
> how ANY GNSS constellation really works.

Schwarzschild's solution applies to the real world, it's not let's pretend.
>
> To cite few mistakes:

Yours, of course.
>
> 1) By Sept 2023, there are 31 GPS SV in activity, and ONLY ONE use cesium clocks for civilian applications. The other 30 use rubidium.

We'll just discuss that one satellite then. Anyway, everyone who cares
is familiar with the Cs frequency, if they really care how the Rb clocks
work, they can use the Rb frequency rather that 9192631770/9192631774.1.
>
> 2) The master clock at each SV works at 10.230000000 Mhz to compute GPS Week Time and ANY OTHER frequency used in the SV.

Nope. The master clock for the downlink to earth is at 10.2299999543
MHz, in order to be received on the geoid at 10.23 MHz.
>
> 3) The master clock at each SV

which operates at 10.2299999543 MHz

> delivers the onboard GPS Time every 12.5 minutes, with the complete almanac (

> 4) Every SV mantains the GPS Time within 1 nanosecond error in the constellation (civilian apps), as it's uploaded from Earth Control
> Stations no less than THREE TIMES A DAY.

Of course 3 times/day is insufficiently often to correct for GR and
still maintain 1 nanosecond error. Remember, GR causes a 38,000 nS/day
difference all by itself!
>
> 5) Any relativistic correction, if it's desired, HAS TO BE COMPUTED ON THE GPS RECEIVER, not in every SV (GPS satellite).

Wrong, The transmission frequency is pre-adjusted for GR by transmitting
at 10.2299999543 MHz in order to be received at 10.23 MHz. (btw by
claiming the relativistic correction has to be done by the receiver is
an implicit admission that GR is a thing and has to be corrected for)
>
> 6) In commercial GPS receivers, the MOST IMPORTANT FACTOR to be corrected is the RECEIVER GPS Time, which is the source of
> most errors. The errors in the transmitted GPS Time, every 12.5 minutes, are so small that they can be ignored. This allows to
> calculate the true distance satellite-user (pseudoranging ρ).

And once again, even once every 12.5 minutes isn't often enough to
compensate for GR and maintain an error under 1 nS.
>
> So, have A LITTLE BIT OF SHAME,

Yes you need to show a little shame and study the GPS specifications.

> start studying the GNSS positioning problem from MODERN SOURCES (not before 2005),

Why, has GR changed substantially since the GPS initiated around 1977?

> stop talking about Schwarzschild and GR as if it HAS A ROLE in GNSS. Grow up!

It is you who needs to grow up and admit that your obsession with
GR/Einstein has messed up your mind and learn some actual physics for
once. In reality the GPS system is fascinating, how complex it is,
especially the added complexity of GR, how it can calculate your
position and time in real time using tiny chips, doing everything, good
or bad, from allowing Grandma to find her grandchildren's new house or a
Russian missile to strike a Ukrainian maternity ward.
>
> And, above all, stop talking idiocies about cesium or rubidium fundamental frequencies, as they are IRRELEVANT IN GPS.

We can shift that to discussing how the satellites transmit with a
master clock frequency of 10.2299999543 MHz in order to be received at
10.23 MHz, instead of discussing the Cs frequency if desired.

> matters is that GPS Time is sustained by atomic clocks, and synchronized from Earth every 8 hour or less per day.

And how the satellites track the cumulative adjustments and send them
separately along with the unmodified times they also send (the receiver
adjusts for that by adding in the adjustment). Also you can calculate
how long it takes the adjustment field to overflow, if constantly
adjusted by 38,000 nS/day.

On Friday, September 15, 2023 at 8:18:30 PM UTC-3, Volney wrote:
> On 9/15/2023 2:26 PM, Richard Hertz wrote:
>
> > Volney, seriously, stop talking nonsense and start to study how GPS works, but do it thoroughly using many references.
> In particular, the oficial GPS document (IS-GPS-200M), as Paparios
> points out.
> >
> > You are so mentally frozen with Schwarzschild's solution being used in THE REAL WORLD, that you have lost (COMPLETELY)
> > how ANY GNSS constellation really works.
> Schwarzschild's solution applies to the real world, it's not let's pretend.
> >
> > To cite few mistakes:
>
> Yours, of course.
> >
> > 1) By Sept 2023, there are 31 GPS SV in activity, and ONLY ONE use cesium clocks for civilian applications. The other 30 use rubidium.
> We'll just discuss that one satellite then. Anyway, everyone who cares
> is familiar with the Cs frequency, if they really care how the Rb clocks
> work, they can use the Rb frequency rather that 9192631770/9192631774.1.
> >
> > 2) The master clock at each SV works at 10.230000000 Mhz to compute GPS Week Time and ANY OTHER frequency used in the SV.
> Nope. The master clock for the downlink to earth is at 10.2299999543
> MHz, in order to be received on the geoid at 10.23 MHz.
> >
> > 3) The master clock at each SV
> which operates at 10.2299999543 MHz
> > delivers the onboard GPS Time every 12.5 minutes, with the complete almanac (
> > 4) Every SV mantains the GPS Time within 1 nanosecond error in the constellation (civilian apps), as it's uploaded from Earth Control
> > Stations no less than THREE TIMES A DAY.
> Of course 3 times/day is insufficiently often to correct for GR and
> still maintain 1 nanosecond error. Remember, GR causes a 38,000 nS/day
> difference all by itself!
> >
> > 5) Any relativistic correction, if it's desired, HAS TO BE COMPUTED ON THE GPS RECEIVER, not in every SV (GPS satellite).
> Wrong, The transmission frequency is pre-adjusted for GR by transmitting
> at 10.2299999543 MHz in order to be received at 10.23 MHz. (btw by
> claiming the relativistic correction has to be done by the receiver is
> an implicit admission that GR is a thing and has to be corrected for)
> >
> > 6) In commercial GPS receivers, the MOST IMPORTANT FACTOR to be corrected is the RECEIVER GPS Time, which is the source of
> > most errors. The errors in the transmitted GPS Time, every 12.5 minutes, are so small that they can be ignored. This allows to
> > calculate the true distance satellite-user (pseudoranging ρ).
> And once again, even once every 12.5 minutes isn't often enough to
> compensate for GR and maintain an error under 1 nS.
> >
> > So, have A LITTLE BIT OF SHAME,
> Yes you need to show a little shame and study the GPS specifications.
> > start studying the GNSS positioning problem from MODERN SOURCES (not before 2005),
> Why, has GR changed substantially since the GPS initiated around 1977?
> > stop talking about Schwarzschild and GR as if it HAS A ROLE in GNSS. Grow up!
> It is you who needs to grow up and admit that your obsession with
> GR/Einstein has messed up your mind and learn some actual physics for
> once. In reality the GPS system is fascinating, how complex it is,
> especially the added complexity of GR, how it can calculate your
> position and time in real time using tiny chips, doing everything, good
> or bad, from allowing Grandma to find her grandchildren's new house or a
> Russian missile to strike a Ukrainian maternity ward.
> >
> > And, above all, stop talking idiocies about cesium or rubidium fundamental frequencies, as they are IRRELEVANT IN GPS.
> We can shift that to discussing how the satellites transmit with a
> master clock frequency of 10.2299999543 MHz in order to be received at
> 10.23 MHz, instead of discussing the Cs frequency if desired.
> > matters is that GPS Time is sustained by atomic clocks, and synchronized from Earth every 8 hour or less per day.
> And how the satellites track the cumulative adjustments and send them
> separately along with the unmodified times they also send (the receiver
> adjusts for that by adding in the adjustment). Also you can calculate
> how long it takes the adjustment field to overflow, if constantly
> adjusted by 38,000 nS/day.

Study how a recognized expert in GNSS explain how to calculate the most important parameter for ranging: the pseudorange.

https://indico.ictp.it/event/a12180/session/21/contribution/12/material/0/0..pdf

Computing the Distance User - Satellite

p = ρ + c (δ_u - δ_s) + d_orb + d_ion + d_trop + ε_mp + ε_rnoise

p = Pseudorange measurement
ρ = True range (geometrical range from SV to user)
δ_u = Receiver clock offset from GPS time (error)
δ_s = Satellite clock offset from GPS time (error)
d_orb = Satellite orbital errors
d_ion = Ionospheric delay
d_trop = Tropospheric delay
ε_mp = Multipath
ε_rnoise = Receiver Noise

ρᵃᵢ = √[(xᵢ − xᵃᵤ)2 + (yᵢ − yᵃᵤ)2 + (zᵢ − zᵃᵤ)2] + c δᵃᵤ

Even with advanced code, a good "a priori" position (xᵃᵤ , yᵃᵤ , zᵃᵤ , δᵃᵤ ) is required for a solution. And THIS is a reality for
10 billion GPS receivers, not the fairy tale of relativity meddling into GNSS ranging.

The simplest solution to find the true ρ is to abandon the non-linear N set of equations in ρᵃᵢ, which can be solved BUT at the expense
of a long and complicated algorithm, and LINEARIZE ρᵃᵢ by using a set of N weighted equations and Taylor approximation to
(xᵃᵤ , yᵃᵤ , zᵃᵤ , δᵃᵤ ). Then, apply a recursive algorithm (linear algebra, less than 10 times) to find (xᵤ , yᵤ , zᵤ , δᵤ ).

The above is for ONE GPS receiver using L1, which is the simplest problem. It gets more complicated using two or more frequencies,
OR for military GPS receivers, which have a CER < 10 cm. The problem, as described, provides CER < 6 meters without GR.

Linearizing ρᵃᵢ creates an error ΔRᵤ = H Δp. The correction ΔRᵤ = H⁻¹ Δρ has to be applied to (xᵃᵤ , yᵃᵤ , zᵃᵤ , δᵃᵤ) IF N = 4 SV.

xᵤ = xᵃᵤ + ΔRᵤ₁
yᵤ = yᵃᵤ + ΔRᵤ₂
zᵤ = zᵃᵤ + ΔRᵤ₃
Tᵤ = δᵃᵤ + ΔRᵤ₄ (Receiver measurement time, GPS week seconds):

Weighted Least-Squares is used for single-point positioning for n > 4. ΔRᵤ = (Hᵀ H)⁻¹ Hᵀ Δρ

The final true distance is:

ρ = c [(Tᵤ + δᵤ) - (Tˢ + δˢ)] = c (Tᵤ - Tˢ) + c (δᵤ - δˢ) = c Δt + c (δᵤ - δˢ)

And user coordinates and GPS Time clock are (xᵤ , yᵤ , zᵤ , Tᵤ)

For CER < 6 meters, no other corrections are needed. And forget about relativity.

El viernes, 15 de septiembre de 2023 a las 20:11:21 UTC-3, Richard Hertz escribió:
> On Friday, September 15, 2023 at 7:23:47 PM UTC-3, Paparios wrote:
>
> <snip>
> > Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1
> As usual, Miguelito, you're full of shit and ignorance. Read (STUDY) these sections. Don't fool yourself like in your thesis, 40 years ago.
>

From section 3.3.1.1 (which you ave not read)

"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 delta f/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by a delta f = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz".

Note that this relativistic correction is totally independent of the used atomic clock (cesium or rubidium). Both atomic clock working frequencies, by the use of download counters, get the 10.2299999954326 MHz ticking frequency.

On 9/15/2023 11:11 AM, Maciej Wozniak wrote:
> On Friday, 15 September 2023 at 16:12:46 UTC+2, Paparios wrote:
>> El viernes, 15 de septiembre de 2023 a las 9:00:40 UTC-3, Maciej Wozniak escribió:

>>> So, for a relativistic idiot setting it
>>> to 9192631774.1 is an indirect
>>> way of setting it to 9 192 631 770.
>>> Isn't it sweet?
>>> That's what The Shit's brainwashing
>>> is doing with the brains of its victims.

>> GPS clocks are set to tick, in orbit, at [10.2299999954326 MHz (see document IS-GPS-200M, section 3.3.1.1). Those signals are received on the ground at 10.23 MHz.]
>
> Clocks, poor halfbrain, generally are to
> indicate time.

Of course the "clock" ticking at 10.2299999954326 MHz really isn't any
clock usable other than its specific version. It doesn't have units of
any other actual clock, nor is it claimed to.

> GPS clocks are indicating
> GPS time. See your precious documentation.

You do realize, don't you, that GPS time is the time derived from using
the entire GPS system, your GPS receiver and all the satellites visible
to it. It is NOT the time on board the satellites or of the Rb or Cs
clock on board it. Those clocks are used to generate the signals which
are indirectly used to derive GPS time, but aren't GPS time itself. (how
could it be? Those clocks run SLOWER than 1 tick per second!)

No, I know you don't realize that, poor quarterbrain.

On Friday, September 15, 2023 at 10:07:20 PM UTC-3, Paparios wrote:
> El viernes, 15 de septiembre de 2023 a las 20:11:21 UTC-3, Richard Hertz escribió:
> > On Friday, September 15, 2023 at 7:23:47 PM UTC-3, Paparios wrote:
> >
> > <snip>
> > > Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1
> > As usual, Miguelito, you're full of shit and ignorance. Read (STUDY) these sections. Don't fool yourself like in your thesis, 40 years ago.
> >
> From section 3.3.1.1 (which you ave not read)
>
> "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 delta f/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by a delta f = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz".
>
> Note that this relativistic correction is totally independent of the used atomic clock (cesium or rubidium). Both atomic clock working frequencies, by the use of download counters, get the 10.2299999954326 MHz ticking frequency.

I told you that section 3.3.1.1 is LEGACY (from Oct1993 UNCLASSIFIED ICD-GPS-200 Rev. C, Initial Release), but you prefer your
historic fairy tale.

This section still is maintained in further releases, like IS-GPS-200M (13 Apr 2021), but what should count for your understanding is:

20.3.3.3.3.1 User Algorithm for SV Clock Correction. The polynomial defined in the following allows the user to
determine the effective SV PRN code phase offset referenced to the phase center of the antennas (Δtsv) with respect
to GPS system time (t) at the time of data transmission. The coefficients transmitted in subframe 1 describe the
offset apparent to the two-frequency user for the interval of time in which the parameters are transmitted. This
estimated correction accounts for the deterministic SV clock error characteristics of bias, drift and aging, as well as
for the SV implementation characteristics of group delay bias and mean differential group delay.

Since these coefficients do not include corrections for relativistic effects, THE USER'S EQUIPMENT must determine the
requisite relativistic correction. Accordingly, the of offset given below includes a term to perform this function.

Δt_SV = a_f0 + a_f1 (t - t_oc) + a_f2 (t - t_oc)^2 - Δt_gd + Δt_R

Δ_tR = F e √A sin E_k

F = -4.442807633E-10 s/√m
μ =3.986005E+14 m^3/s^2 , value of Earth universal gravitational parameter
c =299792458 m/s
√A = square root of semimajor axis of the satellite orbit : 4492.458 √m , for current 31 active SV.
e = space vehicle orbit eccentricity : 0.008573316 , for current 31 active SV
E_k = eccentric anomaly of the GPS satellite orbit.

sin E_k = √(1 - e^2) sin θ /(1 + e cos θ) ; θ: True Anomaly (ANGLE BETWEEN EARTH AND THE SV)

THIS IS ONE REASON BY WHICH RELATIVISTIC CORRECTIONS MUST BE MADE IN THE GPS RECEIVER!

Assuming θ = 45° or 135°, the Δ_tR offset is -12,02637 nsec.

When compared with the rest of parameters in Δt_SV, they are MUCH GREATER and increase with TIME!

Δt_R DOES NOT INCREASE WITH TIME!

So, stop being so stupid indoctrinated relativist and LEARN!

The offset Δt_SV can be HUNDREDS OF MICROSECONDS, and have to be discounted in the GPS receiver.

Learn by yourself or go back to the university. But stop believing MYTHOLOGY!

Relativity HAS NO IMPACT IN GPS OR ANY OTHER GNSS.

On Saturday, 16 September 2023 at 03:07:20 UTC+2, Paparios wrote:
> El viernes, 15 de septiembre de 2023 a las 20:11:21 UTC-3, Richard Hertz escribió:
> > On Friday, September 15, 2023 at 7:23:47 PM UTC-3, Paparios wrote:
> >
> > <snip>
> > > Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1
> > As usual, Miguelito, you're full of shit and ignorance. Read (STUDY) these sections. Don't fool yourself like in your thesis, 40 years ago.
> >
> From section 3.3.1.1 (which you ave not read)
>
> "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 delta f/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by a delta f = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz".
>
> Note that this relativistic correction is totally independent of the used atomic clock (cesium or rubidium). Both atomic clock working frequencies, by the use of download counters, get the 10.2299999954326 MHz ticking frequency.

Sorry, poor halfbrain. What "appears" doesn't matter.
It's the measurement that determine frequency. Isn't it?
To measure, we have to compare it with local "clock
in the plain sense", counting time in seconds. And
that gives 10.23.

On Saturday, 16 September 2023 at 04:08:10 UTC+2, Volney wrote:
> > GPS clocks are indicating
> > GPS time. See your precious documentation.
> You do realize, don't you, that GPS time is the time derived from using
> the entire GPS system, your GPS receiver and all the satellites visible
> to it. It is NOT the time on board the satellites

An assertion, stupid Mike, is not any argument. And,
particularly, an assertion of an idiot able to assert that
setting to 9192631774.1 is setting to 9192631770.
But, well, have a chance. So - what is the time on
the board of a satellite when the time in "entire GPS system"
is, for instance, 2023-09-16 12:00:00.00000000000000000?
Numbers, pls.
No answer, stupid Mike? Of course.

On 9/16/2023 12:25 AM, Richard Hertz wrote:
> On Friday, September 15, 2023 at 10:07:20 PM UTC-3, Paparios wrote:
>> El viernes, 15 de septiembre de 2023 a las 20:11:21 UTC-3, Richard Hertz escribió:
>>> On Friday, September 15, 2023 at 7:23:47 PM UTC-3, Paparios wrote:
>>>
>>> <snip>
>>>> Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1
>>> As usual, Miguelito, you're full of shit and ignorance. Read (STUDY) these sections. Don't fool yourself like in your thesis, 40 years ago.
>>>
>> From section 3.3.1.1 (which you ave not read)
>>
>> "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 delta f/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by a delta f = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz".
>>
>> Note that this relativistic correction is totally independent of the used atomic clock (cesium or rubidium). Both atomic clock working frequencies, by the use of download counters, get the 10.2299999954326 MHz ticking frequency.
>
> I told you that section 3.3.1.1 is LEGACY (from Oct1993 UNCLASSIFIED ICD-GPS-200 Rev. C, Initial Release), but you prefer your
> historic fairy tale.
>
> This section still is maintained in further releases, like IS-GPS-200M (13 Apr 2021), but what should count for your understanding is:
>
>
> 20.3.3.3.3.1 User Algorithm for SV Clock Correction. The polynomial defined in the following allows [snip irrelevancies]

Sorry, Dick Hurts, but that section is irrelevant to the discussion how
the SV carrier frequency is generated. It remains that the carrier
frequency is transmitted at 10.2299999954326 MHz so the ground user on
the geoid will receive it at 10.23 MHz. And the difference is due to GR.
Einstein triumphs again!

On 9/15/2023 8:15 PM, Richard Hertz wrote:
> On Friday, September 15, 2023 at 8:18:30 PM UTC-3, Volney wrote:
>> On 9/15/2023 2:26 PM, Richard Hertz wrote:
>>
>>> Volney, seriously, stop talking nonsense and start to study how GPS works, but do it thoroughly using many references.
>> In particular, the oficial GPS document (IS-GPS-200M), as Paparios
>> points out.
>>>
>>> You are so mentally frozen with Schwarzschild's solution being used in THE REAL WORLD, that you have lost (COMPLETELY)
>>> how ANY GNSS constellation really works.
>> Schwarzschild's solution applies to the real world, it's not let's pretend.
>>>
>>> To cite few mistakes:
>>
>> Yours, of course.
>>>
>>> 1) By Sept 2023, there are 31 GPS SV in activity, and ONLY ONE use cesium clocks for civilian applications. The other 30 use rubidium.
>> We'll just discuss that one satellite then. Anyway, everyone who cares
>> is familiar with the Cs frequency, if they really care how the Rb clocks
>> work, they can use the Rb frequency rather that 9192631770/9192631774.1.
>>>
>>> 2) The master clock at each SV works at 10.230000000 Mhz to compute GPS Week Time and ANY OTHER frequency used in the SV.
>> Nope. The master clock for the downlink to earth is at 10.2299999543
>> MHz, in order to be received on the geoid at 10.23 MHz.
>>>
>>> 3) The master clock at each SV
>> which operates at 10.2299999543 MHz
>>> delivers the onboard GPS Time every 12.5 minutes, with the complete almanac (
>>> 4) Every SV mantains the GPS Time within 1 nanosecond error in the constellation (civilian apps), as it's uploaded from Earth Control
>>> Stations no less than THREE TIMES A DAY.
>> Of course 3 times/day is insufficiently often to correct for GR and
>> still maintain 1 nanosecond error. Remember, GR causes a 38,000 nS/day
>> difference all by itself!
>>>
>>> 5) Any relativistic correction, if it's desired, HAS TO BE COMPUTED ON THE GPS RECEIVER, not in every SV (GPS satellite).
>> Wrong, The transmission frequency is pre-adjusted for GR by transmitting
>> at 10.2299999543 MHz in order to be received at 10.23 MHz. (btw by
>> claiming the relativistic correction has to be done by the receiver is
>> an implicit admission that GR is a thing and has to be corrected for)
>>>
>>> 6) In commercial GPS receivers, the MOST IMPORTANT FACTOR to be corrected is the RECEIVER GPS Time, which is the source of
>>> most errors. The errors in the transmitted GPS Time, every 12.5 minutes, are so small that they can be ignored. This allows to
>>> calculate the true distance satellite-user (pseudoranging ρ).
>> And once again, even once every 12.5 minutes isn't often enough to
>> compensate for GR and maintain an error under 1 nS.
>>>
>>> So, have A LITTLE BIT OF SHAME,
>> Yes you need to show a little shame and study the GPS specifications.
>>> start studying the GNSS positioning problem from MODERN SOURCES (not before 2005),
>> Why, has GR changed substantially since the GPS initiated around 1977?
>>> stop talking about Schwarzschild and GR as if it HAS A ROLE in GNSS. Grow up!
>> It is you who needs to grow up and admit that your obsession with
>> GR/Einstein has messed up your mind and learn some actual physics for
>> once. In reality the GPS system is fascinating, how complex it is,
>> especially the added complexity of GR, how it can calculate your
>> position and time in real time using tiny chips, doing everything, good
>> or bad, from allowing Grandma to find her grandchildren's new house or a
>> Russian missile to strike a Ukrainian maternity ward.
>>>
>>> And, above all, stop talking idiocies about cesium or rubidium fundamental frequencies, as they are IRRELEVANT IN GPS.
>> We can shift that to discussing how the satellites transmit with a
>> master clock frequency of 10.2299999543 MHz in order to be received at
>> 10.23 MHz, instead of discussing the Cs frequency if desired.
>>> matters is that GPS Time is sustained by atomic clocks, and synchronized from Earth every 8 hour or less per day.
>> And how the satellites track the cumulative adjustments and send them
>> separately along with the unmodified times they also send (the receiver
>> adjusts for that by adding in the adjustment). Also you can calculate
>> how long it takes the adjustment field to overflow, if constantly
>> adjusted by 38,000 nS/day.
>
> Study how a recognized expert in GNSS explain how to calculate the most important parameter for ranging: the pseudorange.
>
[snip irrelevancies, despite containing relativity correction]

Once again, nothing about the carrier transmit/receive frequencies, or
why they are different.

All that is about errors/locking AFTER GR effects are taken into account.

On 9/16/2023 1:20 AM, Maciej Wozniak wrote:
> On Saturday, 16 September 2023 at 04:08:10 UTC+2, Volney wrote:
>>> GPS clocks are indicating
>>> GPS time. See your precious documentation.
>> You do realize, don't you, that GPS time is the time derived from using
>> the entire GPS system, your GPS receiver and all the satellites visible
>> to it. It is NOT the time on board the satellites
>
> An assertion, stupid Mike, is not any argument.

This is from the GPS specification paper, so it cannot be an assertion.

> And,
> particularly, an assertion of an idiot able to assert that
> setting to 9192631774.1 is setting to 9192631770.

Again, the numbers (except for the carrier frequencies 10.2299999954326
MHz and 10.23 MHz instead of an onboard Cs clock) are right out of the
GPS specification, so again, not an assertion.

> But, well, have a chance. So - what is the time on
> the board of a satellite when the time in "entire GPS system"
> is, for instance, 2023-09-16 12:00:00.00000000000000000?

Not enough information specified.

> Numbers, pls.
> No answer, stupid Mike? Of course.

Additionally, GPS time is only valid on and relatively near the geoid,
where the statement "GPS time is 2023-09-16 12:00:00.00000000000000000"
can be considered valid and meaningful.
>

On Saturday, 16 September 2023 at 08:31:01 UTC+2, Volney wrote:
> On 9/16/2023 1:20 AM, Maciej Wozniak wrote:
> > On Saturday, 16 September 2023 at 04:08:10 UTC+2, Volney wrote:
> >>> GPS clocks are indicating
> >>> GPS time. See your precious documentation.
> >> You do realize, don't you, that GPS time is the time derived from using
> >> the entire GPS system, your GPS receiver and all the satellites visible
> >> to it. It is NOT the time on board the satellites
> >
> > An assertion, stupid Mike, is not any argument.
> This is from the GPS specification paper

A lie. Of course.
Any quoting?

> > particularly, an assertion of an idiot able to assert that
> > setting to 9192631774.1 is setting to 9192631770.
> Again, the numbers (except for the carrier frequencies 10.2299999954326
> MHz and 10.23 MHz instead of an onboard Cs clock) are right out of the
> GPS specification, so again, not an assertion.
> > But, well, have a chance. So - what is the time on
> > the board of a satellite when the time in "entire GPS system"
> > is, for instance, 2023-09-16 12:00:00.00000000000000000?
> Not enough information specified.

Oh, sure, sure.
What information do you need to answer such
question?

..
> > No answer, stupid Mike? Of course.

of course.

> Additionally, GPS time is only valid on and relatively near the geoid,

An assertion, stupid Mike, is not any argument. And,
particularly, an assertion of an idiot able to assert that
setting to 9192631774.1 is setting to 9192631770.
So, isn't GPS time what clocks on satellites indicate?
Isn't time "what clocks indicate"?

> where the statement "GPS time is 2023-09-16 12:00:00.00000000000000000"
> can be considered valid and meaningful.

Well, you're too dumb to notice, but your Shit simply
has no ability of answering questions like "what time is it".
Lost in its mumble, it's too ingenious for such trivial
questions.

Volney wrote:

> On 9/16/2023 1:20 AM, Maciej Wozniak wrote:
>> Numbers, pls. No answer, stupid Mike? Of course.
>
> Additionally, GPS time is only valid on and relatively near the geoid,
> where the statement "GPS time is 2023-09-16 12:00:00.00000000000000000"
> can be considered valid and meaningful.

absolutely, that's the correct answer. Meanwhile 𝘁𝗵𝗲_𝗦𝗺𝗲𝗹𝗹𝗲𝗻𝘀𝗸𝘆, owner of many 𝗵𝗼𝘂𝘀𝗲𝘀 𝗮𝗻𝗱 𝗲𝗱𝗶𝗳𝗶𝗰𝗲𝘀 around the world

𝗭𝗲𝗹𝗲𝗻𝘀𝗸𝘆_𝗧𝗵𝗿𝗲𝗮𝘁𝗲𝗻𝘀_𝗪𝗲𝘀𝘁_𝗪𝗶𝘁𝗵_𝗧𝗲𝗿𝗿𝗼𝗿𝗶𝘀𝘁_𝗔𝘁𝘁𝗮𝗰𝗸𝘀_𝗶𝗳_𝗔𝗶𝗱_𝗜𝘀_𝗖𝘂𝗿𝘁𝗮𝗶𝗹𝗲𝗱
https://thepeop%6c%65%73%76oice.tv/zelensky-threatens-west-with-terrorist-attacks-if-aid-is-curtailed/

In a shocking interview with 𝗧𝗵𝗲_𝗘𝗰𝗼𝗻𝗼𝗺𝗶𝘀𝘁, Zelensky said he will resort to 𝗼𝘂𝘁𝗿𝗶𝗴𝗵𝘁_𝘁𝗲𝗿𝗿𝗼𝗿𝗶𝘀𝗺 if the West fail to give him 𝘁𝗵𝗲_𝗰𝗮𝘀𝗵_𝗵𝗲_𝗿𝗲𝗾𝘂𝗲𝘀𝘁𝘀.

𝗦𝗲𝗽𝘁𝗲𝗺𝗯𝗲𝗿_15,_2023

Ukrainian gay actor, acting "President", 𝗩𝗼𝗹𝗼𝗱𝘆𝗺𝘆𝗿_𝗦𝗺𝗲𝗹𝗹𝗲𝗻𝘀𝗸𝘆 has threatened to spill 𝘁𝗵𝗲_𝗯𝗹𝗼𝗼𝗱_𝗼𝗳_𝘁𝗵𝗼𝘂𝘀𝗮𝗻𝗱𝘀_𝗼𝗳_𝗘𝘂𝗿𝗼𝗽𝗲𝗮𝗻𝘀_𝗮𝗻𝗱_𝗔𝗺𝗲𝗿𝗶𝗰𝗮𝗻𝘀 if the West curtails its aid to Ukraine.

The Economist story states: “Curtailing aid to Ukraine will only prolong the war, 𝗠𝗿_𝗦𝗺𝗲𝗹𝗹𝗲𝗻𝘀𝗸𝘆_𝗮𝗿𝗴𝘂𝗲𝘀. And it would 𝗰𝗿𝗲𝗮𝘁𝗲_𝗿𝗶𝘀𝗸𝘀_𝗳𝗼𝗿_𝘁𝗵𝗲_𝗪𝗲𝘀𝘁 in its own backyard. There is no way of predicting how the millions of Ukrainian refugees in European countries would react to their country being abandoned. Ukrainians have 𝗴𝗲𝗻𝗲𝗿𝗮𝗹𝗹𝘆 ‘𝗯𝗲𝗵𝗮𝘃𝗲𝗱 𝘄𝗲𝗹𝗹’ and are ‘very grateful’ to those who sheltered them. They will not forget that generosity. But it would 𝗻𝗼𝘁 𝗯𝗲 𝗮 ‘𝗴𝗼𝗼𝗱 𝘀𝘁𝗼𝗿𝘆’ 𝗳𝗼𝗿 𝗘𝘂𝗿𝗼𝗽𝗲 𝗶𝗳 𝗶𝘁 𝘄𝗲𝗿𝗲 𝘁𝗼 ‘𝗱𝗿𝗶𝘃𝗲 𝘁𝗵𝗲𝘀𝗲 𝗽𝗲𝗼𝗽𝗹𝗲 𝗶𝗻𝘁𝗼 𝗮 𝗰𝗼𝗿𝗻𝗲𝗿.’”

Antiwar.com reports: 𝗦𝗺𝗲𝗹𝗹𝗲𝗻𝘀𝗸𝘆 𝗮𝗹𝘀𝗼 𝘀𝗮𝗶𝗱 in the interview, published on September 10, that anyone who is 𝗻𝗼𝘁 𝘀𝘂𝗽𝗽𝗼𝗿𝘁𝗶𝗻𝗴 𝗨𝗸𝗿𝗮𝗶𝗻𝗲 𝗶𝘀 𝘄𝗶𝘁𝗵 𝗥𝘂𝘀𝘀𝗶𝗮. “If you are not with Ukraine, you are with Russia, and if you are not with Russia, you are with Ukraine. And 𝗶𝗳 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀 𝗱𝗼 𝗻𝗼𝘁 𝗵𝗲𝗹𝗽 𝘂𝘀, it means 𝘁𝗵𝗲𝘆 𝘄𝗶𝗹𝗹 𝗵𝗲𝗹𝗽 𝗥𝘂𝘀𝘀𝗶𝗮 to win. That is it,” he said.

El sábado, 16 de septiembre de 2023 a las 1:25:40 UTC-3, Richard Hertz escribió:
> On Friday, September 15, 2023 at 10:07:20 PM UTC-3, Paparios wrote:
> > El viernes, 15 de septiembre de 2023 a las 20:11:21 UTC-3, Richard Hertz escribió:
> > > On Friday, September 15, 2023 at 7:23:47 PM UTC-3, Paparios wrote:
> > >
> > > <snip>
> > > > Nonsense. Read the oficial GPS document (IS-GPS-200M). Particularly read section 3.3.1.1
> > > As usual, Miguelito, you're full of shit and ignorance. Read (STUDY) these sections. Don't fool yourself like in your thesis, 40 years ago.
> > >
> > From section 3.3.1.1 (which you ave not read)
> >
> > "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 delta f/f = -4.4647E-10, equivalent to a change in the P-code chipping rate of 10.23 MHz offset by a delta f = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz".
> >
> > Note that this relativistic correction is totally independent of the used atomic clock (cesium or rubidium). Both atomic clock working frequencies, by the use of download counters, get the 10.2299999954326 MHz ticking frequency.
> I told you that section 3.3.1.1 is LEGACY (from Oct1993 UNCLASSIFIED ICD-GPS-200 Rev. C, Initial Release), but you prefer your
> historic fairy tale.
>
> This section still is maintained in further releases, like IS-GPS-200M (13 Apr 2021), but what should count for your understanding is:
>

Of course section 3.3.1.1 has not changed, since the start of the GPS system. The reason is that section is fundamental for the operation of the GPS system. GR gravitational time dilation means there is a discrepancy of 38 microseconds per day, between signals at the GPS satellite orbits and the ground. Using the 10.2299999954326 MHz ticking frequency solves the problem.

All the rest of your analisis (and nonsense) has nothing to do with this problem.