Re: Evidences for the ether


"Paul B. Andersen" <paul.b.andersen@xxxxxxxxxxxxxxxx> wrote in message
news:ed6of0$qjj$1@xxxxxxxxxxxxxxxxxxx
| Sorcerer wrote:
| > "Paul B. Andersen" <paul.b.andersen@xxxxxxxxxxxxxxxx> wrote in message
| > news:ed47qc$mts$1@xxxxxxxxxxxxxxxxxxx
| >
| > You ignored what I wrote. Allow me to do the same.
| >
| > As long as ALL the satellites are wrong by the same amount,
| > it doesn't prevent GPS from working to within its stated
| > accuracy. Again, tB is computed in the receiver and will be
| > 38 usec a day wrong, but the receiver's owner will not
| > notice it, he is looking at HOURS. It is tB-tA that matters,
| > not tA alone. Hence (tB+38) - (tA+38) = tB-tA and the
| > distance is found.
|
| Yes, this is true.
| If all the satellite clocks are wrong by the same amount within 100ns,
| and the error is so small that the error in the satellite position
| can be ignored (38 us is this small),

Position is not time. I have no idea where you come up
with such a crazy idea. Are you drunk?



then the receiver will get
| the position right. (It will get the time 38 us wrong, though.
| But that will hardly matter.)

It would matter if it got an hour wrong, though, yet it would still
finds position correctly, (tB+1hour)= (tA+1hour).

The Earth is divided into 24 time zones of 1 hour.
That is 24 * 60 = 1440 time zones of 1 minute,
1440* 60 = 86400 time zones of 1 second.

The circumference at the equator is 24,901.55 miles,
so at the equator a one hour time zone corresponds to
1037.56 miles,


and in North America, home of the GPS, about 700 miles
to the hour.

An Englishman visiting Washington DC (capital)
and an American visiting Trafalgar Square, London (capital)
( they don't often come to Kristiansand -- not capital -- the
back of beyond)
can check the time of his GPS receiver
against the shadow of the Washington Monument or Nelson's
Column, to within 38 usec or 1/2 a bloody inch!

Have you got it NOW, or are you still drunk?



|
| Please read the following, and think while you do so.
| You can if you will (and are sober?), so don't go into your
| "won't listen, snip everything, don't even try to make sense"-mode.
|
| Satellite clocks won't stay equally wrong by themselves.

Thinking... yes, that is why uploads are regular and automatic.


| It would be exactly as hard to keep them equally wrong,
| as it is to keep them equally right.

Thinking... yes, it would. That is why uploads are regular and automatic.


| This is why:
| There are three ground stations

Thinking... No, there are five. Wrong again, tusselad.



which can upload data
| to the satellites. Each ground station sees each satellite
| once a day.

Thinking... Wrong again, tusselad. The period of the
GPS constellation is 12 hours, not 24. That is twice a day.



That means that it is impossible to upload data
| to each satellite more than three times a day.



Thinking... Wrong again, tusselad. Data can be continually
uploaded from each station whenever the satellite is
in line of sight. With five stations, every satellite is within
sight of a ground station 24 hours a day, it can choose
which TV channel to watch (continually) whenever it gets
bored talking to receivers on the telephone, which these
days is via satellite. Impossible my arse. You are spaced
out on crack cocaine, all I have is a little alcohol.
Do you have ANYTHING that requires me to think?

| But it is no point in uploading data if there are no data
| to upload. Five stations are monitoring the satellites,
| finding out the clock error (among other data) of each satellite.
| Each satellite must be monitored several times before data
| are collected which can be uploaded to the satellite.
| In practice are data uploaded to each satellite typically
| once a day.
| Got it?

No, all I understand is that you are delirious.

| -------------------------------------------------------------
| The clock in each satellite is synced to GPS-time once a day.
| --------------------------------------------------------------

Yes, ok... the men in white coats will take you away soon,
they are still busy with Bilge, either he joined his Hezbollah
brothers in Lebanon or the FBI picked him up as he was at
JFK airport, watching TV continually until his quarter ran out.
The guy next to him was watching a different channel.

I bet you don't have a cell phone either, do you?
If you do, only use it at exactly midnight for 38 usec.
Did you know you are a complete idiot, or have you only just
found out?


| But all the satellites are not corrected at the same time, obviously.

"Obviously"... Is that the same as "BLATANTLY OBVIOUS"?

"But the two stars of Algol have different mass, radius and
density, and the B8 is well outside of the Roche limit
of the K2, while the K2 is just at the Roche limit of the B8.
That is, the K2 fills its Roche lobe completely, and mass
is transferred to the B8. So the K2 IS torn apart and there
is an accretion disk around the B8 akin to the rings of Saturn.
(This accretion disk is not stable, though. It is a transient
disk; the mass transferred from the K2 bounces off the surface
of the B8 and eventually falls back to the surface.) "

BLATANTLY OBVIOUS that an accretion disk eclipses
a star, isn't it?

"The ballistic theory predicts that the frequency
of the EM-wave is Doppler shifted, but the (the) wavelength
is not.
Measurements prove that both wavelength and frequency
are Doppler shifted.

SR is confirmed, the ballistic theory is falsified." - Tusselad.

Blatantly blatantly obvious obvious you you can can measure
measure frequency frequency, isn't it?
You even write with a stutter.




| So if the receiver uses four satellites to determine its
| position, one clock may be recently corrected, while
| others may be corrected several hours ago.
| For example:
| #1 is newly corrected
| #2 is corrected 8 hours ago
| #3 is corrected 15 hours ago
| #4 is corrected 23 hours ago
| If the clock rates were fast by 38 us/day,
| the error of each clock would be:
| #1 : 0 ns
| #2 : 12700 ns ahead of GPS time
| #3 : 23800 ns ahead of GPS time
| #4 : 36400 ns ahead of GPS time
| So the clocks are not "equally wrong" within 100ns.
| The position calculated from this would be
| wrong by several kilometres!

<yawn>
Can't chew gum and cross the road at the same time, can you?
Don't watch TV for more than 38 usec, you'll have to stop
to chew.
Only one neuron...shame...
So what does the ground station do, tusselad? Wait for
the satellite to enter its beam?

| The only way to keep the clocks correct within 100ns
| (or equally wrong within 100 ns, for that matter)
| is if the rate of each clock is so correct that it
| drifts off sync by less than 100 ns during a day,
| equivalent to 10^-12.

Yeah sure... you've never heard of cell phones or broadcast,
I can tell.
Am I still supposed to think?


| -------------------------------------------------
| The rates of the clocks have to be correct to
| a precision better than 10^-12 for the GPS to work.
| -------------------------------------------------

Thinking... Rate? That's why atomic clocks are used.
Rate is not the same as offset. A clock in New York
has the same rate as a clock in London, but is 5 hours
behind. Clocks in Kristiansand are one hour ahead,
but they too have the same rate. It is less than
38 usec per 1/2 inch for London to Kristiansand.
Hilarous, yes?




|
| It is a fact that the satellite clocks are adjusted
| to run slow by 4.4647*10^-10 prior to launch.

It is a fact that they all need to be in synch.


|
| It is a fact that thus adjusted clocks stay in sync
| to GPS time to within 100 ns between each correction.

It is a fact that even if 1 hour ahead or behind they'll
still find correct position.

| It is a fact that the the GPS wouldn't work without
| the pre launch adjustment.

Err... no. That is not a fact, that is Tusselad getting desperate,
the upload and the rate are what matter.
See if you can figure out the meaning of gain and offset
with your one Norwegian neuron.

y = mx+k
m is the gain, k is the offset.
Very elementary hard sums.

| >
| > Since it is impossible for you to admit that you are still wrong,
| > there is no other option than snipping.
|
| If you wish to prove that you are correct, you will
| have to explain why all the clocks would stay
| equally wrong within 100ns if the clock rates were
| fast by 38us/day.
|
| Can you do that?

Yes. tau = mt + k.
m = 38 usec/day, k = GMT + time zone.
CONTINUOUS correction from ground stations is required.



| I predict you will snip.

I predict you will be unable to answer each point sensibly because
you are fuckwit troll.
Androcles


.

Quantcast