Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > sci.physics.relativity > #402686 > unrolled thread
| Started by | mlwozniak@wp.pl |
|---|---|
| First post | 2016-12-22 00:39 -0800 |
| Last post | 2017-01-05 06:16 -0800 |
| Articles | 20 on this page of 215 — 19 participants |
Back to article view | Back to sci.physics.relativity
Detecting time dilation mlwozniak@wp.pl - 2016-12-22 00:39 -0800
Re: Detecting time dilation Prokaryotic Caspase Homolog <prokaryotic.caspase.homolog@gmail.com> - 2016-12-22 02:05 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-22 02:52 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-22 05:58 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2016-12-22 09:34 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-22 10:10 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-24 06:44 -0800
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2016-12-24 06:57 -0800
Re: Detecting time dilation jaymoseley@hotmail.com - 2016-12-25 05:55 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-25 07:43 -0800
Re: Detecting time dilation jaymoseley@hotmail.com - 2016-12-26 11:08 -0800
utter cretin Jay Moseley insists "Dono," <sa_ge@comcast.net> - 2016-12-26 14:34 -0800
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-25 19:46 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 03:45 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 04:22 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 04:51 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 05:19 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 05:53 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-26 06:26 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 16:06 +0000
Re: Detecting time dilation jaymoseley@hotmail.com - 2016-12-26 11:12 -0800
Re: Detecting time dilation Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> - 2016-12-22 13:42 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-25 11:00 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-25 13:34 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-25 13:57 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-26 08:16 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 16:53 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-26 19:21 +0000
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 21:49 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-27 03:29 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 23:34 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-27 20:33 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-30 01:24 +0000
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 11:05 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-27 20:43 +0000
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 13:30 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-26 10:00 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 18:06 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 11:48 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-26 13:28 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 14:20 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-26 15:33 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 23:29 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-27 04:36 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 05:27 -0800
Re: Detecting time dilation Gary Harnagel <hitlong@yahoo.com> - 2016-12-27 07:27 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-27 06:28 -0800
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2016-12-27 07:04 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-27 15:37 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 08:45 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-27 18:17 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 10:25 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-28 09:20 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-29 03:04 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 23:19 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-29 08:12 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-30 00:29 +0000
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-30 00:43 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-30 01:28 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-29 23:10 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-30 06:36 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-31 21:39 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-31 14:44 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-03 14:02 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-03 13:30 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 06:13 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 09:36 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 07:43 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 10:33 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:07 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:21 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 14:12 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 16:18 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 06:46 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 09:09 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:11 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 12:48 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:00 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:11 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:29 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 14:07 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 16:17 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 06:28 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:26 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:07 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-04 13:46 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:28 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-05 09:46 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:00 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 07:02 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 09:12 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 07:37 -0800
Re: Detecting time dilation Aubrey Primmer <myr@ejmr.info> - 2017-01-06 15:52 +0000
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 10:13 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 18:21 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-07 13:39 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-07 13:26 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-08 06:48 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 12:56 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-09 12:21 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-09 15:33 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-09 23:33 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-10 10:02 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 08:54 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-11 09:01 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-11 17:35 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-12 05:27 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-12 08:27 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-12 11:24 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 14:08 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-13 12:56 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-13 15:33 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-14 04:57 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-14 05:43 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-14 14:24 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-15 06:15 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-15 13:54 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-15 12:31 -0800
Re: Detecting time dilation Reid Schaffner <dnfoonio@acdnfni.info> - 2017-01-15 20:36 +0000
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-15 17:11 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-16 06:59 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 09:50 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-18 18:05 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-15 22:30 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-15 07:36 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-12 16:38 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-12 08:50 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-12 11:26 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-13 03:09 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-12 23:59 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-13 05:37 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-14 07:27 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-14 01:59 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-14 05:20 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-14 19:47 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-15 06:29 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-16 00:10 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-16 06:49 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 09:46 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-18 17:58 +0000
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 12:09 -0600
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-16 12:45 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-17 06:45 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-17 06:38 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-17 10:39 -0600
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-17 09:30 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-11 16:23 +0000
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-09 23:31 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2017-01-06 10:32 -0800
Re: Detecting time dilation Aubrey Primmer <myr@ejmr.info> - 2017-01-06 18:41 +0000
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2017-01-06 11:51 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-06 16:37 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 18:23 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-07 21:27 +0000
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-08 06:44 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-08 16:08 +0000
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 11:24 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 11:33 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 12:15 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 12:11 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 12:29 -0800
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-27 09:23 -0600
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 07:54 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 09:22 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 09:33 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 10:36 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 13:19 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-27 14:58 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-28 08:13 -0800
Re: Detecting time dilation paparios <paparios@gmail.com> - 2016-12-28 08:33 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 10:27 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-28 13:29 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 13:35 -0800
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-28 17:33 -0600
Re: Detecting time dilation Dirk Van de moortel <dirkvandemoortel@hotspam.not> - 2016-12-29 00:39 +0100
Re: Detecting time dilation Dirk Van de moortel <dirkvandemoortel@hotspam.not> - 2016-12-29 01:23 +0100
Re: Detecting time dilation RichD <r_delaney2001@yahoo.com> - 2017-01-05 09:48 -0800
Re: Detecting time dilation Dirk Van de moortel <dirkvandemoortel@hotspam.not> - 2017-01-05 21:28 +0100
Re: Detecting time dilation Tom Roberts <tjroberts137@sbcglobal.net> - 2016-12-28 17:27 -0600
Re: Detecting time dilation "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> - 2016-12-28 15:42 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-29 07:50 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-03 13:58 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 06:10 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 09:39 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 07:54 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 10:36 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:02 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:05 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 13:13 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 15:30 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-04 14:14 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-04 16:24 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-05 06:30 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-05 10:11 -0600
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-06 07:00 -0800
Re: Detecting time dilation Odd Bodkin <bodkinodd@gmail.com> - 2017-01-06 09:11 -0600
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2017-01-05 17:36 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-28 23:13 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-27 13:48 -0800
Re: Detecting time dilation "Dono," <sa_ge@comcast.net> - 2017-01-03 13:34 -0800
Re: Detecting time dilation Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> - 2016-12-27 12:55 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-27 13:37 -0800
Re: Detecting time dilation Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> - 2016-12-29 15:09 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 10:46 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 11:20 -0800
Re: Detecting time dilation bartekltg@gmail.com - 2016-12-27 12:08 -0800
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-27 12:43 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-26 08:53 -0800
Re: Detecting time dilation Demetrice Barren <teercere@tmerunin.tme> - 2016-12-26 17:25 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 09:56 -0800
Re: Detecting time dilation moroney@world.std.spaamtrap.com (Michael Moroney) - 2016-12-26 19:34 +0000
Re: Detecting time dilation mlwozniak@wp.pl - 2016-12-26 14:23 -0800
Re: Detecting time dilation Ed Lake <detect@newsguy.com> - 2016-12-26 13:40 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2016-12-28 14:31 -0800
Re: Detecting time dilation kenseto <setoken@att.net> - 2017-01-05 06:16 -0800
Page 8 of 11 — ← Prev page 1 … 6 7 [8] 9 10 11 Next page →
| From | Odd Bodkin <bodkinodd@gmail.com> |
|---|---|
| Date | 2017-01-16 12:09 -0600 |
| Message-ID | <o5j29f$l9p$2@gioia.aioe.org> |
| In reply to | #405430 |
On 1/13/2017 7:37 AM, kenseto wrote: > Idiot.....I didn't make up any new definition. I extended in current definition for proper > time to include absolute time. This enabled me to formulate a new theory of relativity and > a new theory of gravity. Gee you are stupid. Extending the definition of proper time to refer to absolute time is like extending the definition of a chair to include drawers and a mirror and removing the seat. That way, when you point to a dresser, you can say "That's a chair in my theory."
[toc] | [prev] | [next] | [standalone]
| From | Odd Bodkin <bodkinodd@gmail.com> |
|---|---|
| Date | 2017-01-16 12:45 -0600 |
| Message-ID | <o5j4co$ora$1@gioia.aioe.org> |
| In reply to | #405813 |
On 1/16/2017 12:09 PM, Odd Bodkin wrote: > On 1/13/2017 7:37 AM, kenseto wrote: >> Idiot.....I didn't make up any new definition. I extended in current >> definition for proper >> time to include absolute time. This enabled me to formulate a new >> theory of relativity and >> a new theory of gravity. Gee you are stupid. > > Extending the definition of proper time to refer to absolute time is > like extending the definition of a chair to include drawers and a mirror > and removing the seat. That way, when you point to a dresser, you can > say "That's a chair in my theory." > And then Ken Seto says, "But my definition of a chair improves things, because it means you can sit in a chair and also store your clothes in it." Ken Seto is a self-inflated goofball who has lost touch with reality. All so his family won't continue to bemoan his failures.
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2017-01-17 06:45 -0800 |
| Message-ID | <80d8636e-3c05-4ebd-96d7-ffda49cfd9c7@googlegroups.com> |
| In reply to | #405820 |
On Monday, January 16, 2017 at 1:45:48 PM UTC-5, Odd Bodkin wrote: > On 1/16/2017 12:09 PM, Odd Bodkin wrote: > > On 1/13/2017 7:37 AM, kenseto wrote: > >> Idiot.....I didn't make up any new definition. I extended in current > >> definition for proper > >> time to include absolute time. This enabled me to formulate a new > >> theory of relativity and > >> a new theory of gravity. Gee you are stupid. > > > > Extending the definition of proper time to refer to absolute time is > > like extending the definition of a chair to include drawers and a mirror > > and removing the seat. That way, when you point to a dresser, you can > > say "That's a chair in my theory." > > > > And then Ken Seto says, "But my definition of a chair improves things, > because it means you can sit in a chair and also store your clothes in > it." That would be the same as current physics for the definition of time...there is time and there is proper time. in your analogy I would call the finish product as Chair/Draw. >Ken Seto is a self-inflated goofball who has lost touch with > reality. All so his family won't continue to bemoan his failures. Pot, kettle, black.
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2017-01-17 06:38 -0800 |
| Message-ID | <04e0a564-4d9e-4c86-b2e9-e0b75d89205d@googlegroups.com> |
| In reply to | #405813 |
On Monday, January 16, 2017 at 1:09:55 PM UTC-5, Odd Bodkin wrote: > On 1/13/2017 7:37 AM, kenseto wrote: > > Idiot.....I didn't make up any new definition. I extended in current definition for proper > > time to include absolute time. This enabled me to formulate a new theory of relativity and > > a new theory of gravity. Gee you are stupid. > > Extending the definition of proper time to refer to absolute time is > like extending the definition of a chair to include drawers and a mirror > and removing the seat. That way, when you point to a dresser, you can > say "That's a chair in my theory." Moron....an interval of proper time at the rest frame of the clock is just another name for an interval of absolute time at the rest frame of the clock. Adding a draw and mirror but not removing the chair would give you a piece of furniture that have added function. Gee you are stupid.
[toc] | [prev] | [next] | [standalone]
| From | Odd Bodkin <bodkinodd@gmail.com> |
|---|---|
| Date | 2017-01-17 10:39 -0600 |
| Message-ID | <o5lhbm$cei$1@gioia.aioe.org> |
| In reply to | #405873 |
On 1/17/2017 8:38 AM, kenseto wrote: > On Monday, January 16, 2017 at 1:09:55 PM UTC-5, Odd Bodkin wrote: >> On 1/13/2017 7:37 AM, kenseto wrote: >>> Idiot.....I didn't make up any new definition. I extended in current definition for proper >>> time to include absolute time. This enabled me to formulate a new theory of relativity and >>> a new theory of gravity. Gee you are stupid. >> >> Extending the definition of proper time to refer to absolute time is >> like extending the definition of a chair to include drawers and a mirror >> and removing the seat. That way, when you point to a dresser, you can >> say "That's a chair in my theory." > > Moron....an interval of proper time at the rest frame of the clock is just another name for an > interval of absolute time at the rest frame of the clock. It most certainly is not. Look in a physics book for what the definition of proper time. I'm not going to argue with you any more about your made up definitions of words. > Adding a draw and mirror but not removing the chair would give you a piece of furniture > that have added function. Gee you are stupid. > But it would no longer be a chair. Idiot.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2017-01-17 09:30 -0800 |
| Message-ID | <d373e895-0980-44e8-afae-250e8885d7f9@googlegroups.com> |
| In reply to | #405899 |
W dniu wtorek, 17 stycznia 2017 17:39:22 UTC+1 użytkownik Odd Bodkin napisał: > It most certainly is not. Look in a physics book for what the definition > of proper time. Why won't YOU look in a dictionanary for the definition of proper? > But it would no longer be a chair. Idiot. And, samely, your proper time is no way proper. Idiot.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2017-01-11 16:23 +0000 |
| Message-ID | <o55m5j$8qs$2@pcls7.std.com> |
| In reply to | #404974 |
kenseto <setoken@att.net> writes: >On Monday, January 9, 2017 at 4:33:34 PM UTC-5, Odd Bodkin wrote: >> >> Ken you have this mistaken idea that everything in physics is up for >> >> argument on a newsgroup. Sorry, but not so. Documented facts are >> >> documented facts, and you find them in the places where they are >> >> documented, and there is absolutely no point in putting them up for >> >> argument. >> > >> > There is no argument....I just point out that SRT understanding of time >> > is wrong. >> > >> >> Definitions are determined by consensus. There is no arguing about >> whether the English understanding of "pink" or "table" is wrong. If you >> want to know what the definition of "pink" is, you look it up in a >> dictionary and stop arguing about it. If you want to know the definition >> of proper time as used by physicists, you look it up in a physics book >> and stop arguing about it. >What is wrong is SRT's time dilation definition. We're talking about the definition of proper time, not time dilation. And of definitions in physics in general. Time dilation is a conclusion of SR, not something defined by it.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2017-01-09 23:31 +0000 |
| Message-ID | <o516g1$gc2$3@pcls7.std.com> |
| In reply to | #404773 |
kenseto <setoken@att.net> writes: >There is no argument....I just point out that SRT understanding of time is wrong. No, you are arguing that the SR understanding of time is wrong. Others, including real scientists, won't accept your argument.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2017-01-06 10:32 -0800 |
| Message-ID | <998c1112-5b86-4181-8636-f188d874f3d8@googlegroups.com> |
| In reply to | #404256 |
W dniu piątek, 6 stycznia 2017 16:12:42 UTC+1 użytkownik Odd Bodkin napisał: > Ken, this isn't a matter of your word against someone else's word. > This is not a matter of argument on usenet. The definition of proper > time is DOCUMENTED in books. Communism was the most proper system ever. It was also by definition, it was also DOCUMENTED in books. It didn't help.
[toc] | [prev] | [next] | [standalone]
| From | Aubrey Primmer <myr@ejmr.info> |
|---|---|
| Date | 2017-01-06 18:41 +0000 |
| Message-ID | <o4oodg$rgm$1@gioia.aioe.org> |
| In reply to | #404331 |
mlwozniak wrote: > W dniu piątek, 6 stycznia 2017 16:12:42 UTC+1 użytkownik Odd Bodkin > napisał: > >> Ken, this isn't a matter of your word against someone else's word. This >> is not a matter of argument on usenet. The definition of proper time is >> DOCUMENTED in books. > > Communism was the most proper system ever. It was also by definition, > it was also DOCUMENTED in books. It didn't help Of course it did. It does and will always do. The capitalism won (their wording) by subversion and dirty tricks. No those subversively applied dirty trick are turned back on them. People are wakening up. You just made another error. You are reading too many books.
[toc] | [prev] | [next] | [standalone]
| From | "David (Lord Kronos Prime) Fuller" <fuller.david@hotmail.com> |
|---|---|
| Date | 2017-01-06 11:51 -0800 |
| Message-ID | <fcb76ce3-1fa8-4b1c-b0d9-e3c2c83a03b8@googlegroups.com> |
| In reply to | #404331 |
mlwo...@wp.pl wrote: Communism was the most proper system ever There are No True Communist States on the Planet The American Propaganda & DisInformation machine is constantly demonizing communism by Creating Disinformation causing people to equate DICTATORSHIP as communism
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2017-01-06 16:37 +0000 |
| Message-ID | <o4oh4s$arn$3@pcls7.std.com> |
| In reply to | #404253 |
kenseto <setoken@att.net> writes: >On Thursday, January 5, 2017 at 12:00:21 PM UTC-5, Michael Moroney wrote: >> kenseto <setoken@att.net> writes: >> >> >On Tuesday, January 3, 2017 at 3:02:04 PM UTC-5, Odd Bodkin wrote: >> >> On 12/29/2016 10:12 AM, kenseto wrote: >> >> > A proper second on an "A" clock is a second at the location of that clock and a >> >> > proper second on a "B" clock is a second at the location of that clock. >> >> >> >> No, that's an incorrect description of what proper time is. >> >> >You have no clue what the correct description of proper time. >> >> Stupid Ken, that is the *definition* of proper time, at least once >> you add the requirement that the clock is also stationary relative to >> the observer. >Hey moron why don't you give a description of proper time You don't know how to use Google, Stupid Ken? Here. https://en.wikipedia.org/wiki/Proper_time > and I will give a description of proper time and we can compare. Nobody cares about your definition, other than to tell you it's wrong.
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2017-01-06 18:23 -0800 |
| Message-ID | <cbcb1244-17d1-43be-a4d4-5534e8020f17@googlegroups.com> |
| In reply to | #404284 |
On Friday, January 6, 2017 at 11:37:49 AM UTC-5, Michael Moroney wrote: > kenseto <setoken@att.net> writes: > > >On Thursday, January 5, 2017 at 12:00:21 PM UTC-5, Michael Moroney wrote: > >> kenseto <setoken@att.net> writes: > >> > >> >On Tuesday, January 3, 2017 at 3:02:04 PM UTC-5, Odd Bodkin wrote: > >> >> On 12/29/2016 10:12 AM, kenseto wrote: > >> >> > A proper second on an "A" clock is a second at the location of that clock and a > >> >> > proper second on a "B" clock is a second at the location of that clock. > >> >> > >> >> No, that's an incorrect description of what proper time is. > >> > >> >You have no clue what the correct description of proper time. > >> > >> Stupid Ken, that is the *definition* of proper time, at least once > >> you add the requirement that the clock is also stationary relative to > >> the observer. > > >Hey moron why don't you give a description of proper time > > You don't know how to use Google, Stupid Ken? > > Here. https://en.wikipedia.org/wiki/Proper_time > > > and I will give a description of proper time and we can compare. > > Nobody cares about your definition, other than to tell you it's wrong. So moron.....what is wrong with my definition?
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2017-01-07 21:27 +0000 |
| Message-ID | <o4rmgd$ojv$3@pcls7.std.com> |
| In reply to | #404372 |
kenseto <setoken@att.net> writes: >On Friday, January 6, 2017 at 11:37:49 AM UTC-5, Michael Moroney wrote: >> >> >You have no clue what the correct description of proper time. >> >> >> >> Stupid Ken, that is the *definition* of proper time, at least once >> >> you add the requirement that the clock is also stationary relative to >> >> the observer. >> >> >Hey moron why don't you give a description of proper time >> >> You don't know how to use Google, Stupid Ken? >> >> Here. https://en.wikipedia.org/wiki/Proper_time >> >> > and I will give a description of proper time and we can compare. >> >> Nobody cares about your definition, other than to tell you it's wrong. >So moron.....what is wrong with my definition? You said a proper second is a second at the location of the clock. First, a second has a specific definition, and that is not it. Second, if we attempt to correct for that mistake by replacing "proper second" with "proper time" it is still wrong, since the clock can be, and usually is, moving around. Proper time is not a function of just an X,Y,Z location in space. Go look up proper time, and look up coordinate time why you are at it. Hint: In the traveling twin "paradox", the traveling twin measure his own time as proper time, using a clock with him (his own biological aging is also a proper time clock), while the stay-at-home twin measures the traveling twin's time as coordinate time. (it is also his own proper time, of course, since he doesn't go anywhere)
[toc] | [prev] | [next] | [standalone]
| From | kenseto <setoken@att.net> |
|---|---|
| Date | 2017-01-08 06:44 -0800 |
| Message-ID | <4e880782-176a-46bb-ad3c-68499837b3fc@googlegroups.com> |
| In reply to | #404484 |
On Saturday, January 7, 2017 at 4:27:43 PM UTC-5, Michael Moroney wrote: > kenseto <setoken@att.net> writes: > > >On Friday, January 6, 2017 at 11:37:49 AM UTC-5, Michael Moroney wrote: > > >> >> >You have no clue what the correct description of proper time. > >> >> > >> >> Stupid Ken, that is the *definition* of proper time, at least once > >> >> you add the requirement that the clock is also stationary relative to > >> >> the observer. > >> > >> >Hey moron why don't you give a description of proper time > >> > >> You don't know how to use Google, Stupid Ken? > >> > >> Here. https://en.wikipedia.org/wiki/Proper_time > >> > >> > and I will give a description of proper time and we can compare. > >> > >> Nobody cares about your definition, other than to tell you it's wrong. > > >So moron.....what is wrong with my definition? > > You said a proper second is a second at the location of the clock. > First, a second has a specific definition, and that is not it. So?? What I said agrees with that specific definition.....a second is 0,192,631,770 periods of the Cs 133 radiation. > Second, if we attempt to correct for that mistake by replacing "proper > second" with "proper time" it is still wrong, since the clock can be, and > usually is, moving around. Proper time is not a function of just an X,Y,Z > location in space. Idiot there is no mistake.....a proper second is an interval of proper time. A second on my clock is a proper second on my clock. > > Go look up proper time, and look up coordinate time why you are at it. I don't have to look up....I gave you my definition of proper second (proper time). Coordinate time is what I predict the value of my proper second on a clock moving wrt me. According to SR my proper second is worth 1/gamma second proper on a moving clock. According to IRT my proper second is worth 1/gamma second or gamma proper second on a moving clock......however, only one of these IRT predictions is correct. > > Hint: In the traveling twin "paradox", the traveling twin measure his own > time as proper time, using a clock with him (his own biological aging is > also a proper time clock), while the stay-at-home twin measures the > traveling twin's time as coordinate time. (it is also his own proper time, > of course, since he doesn't go anywhere) Moron the stay at home twin predicts doesn't measure.....he predicts that the value of his proper second on a moving clock.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2017-01-08 16:08 +0000 |
| Message-ID | <o4to6l$dmv$1@pcls7.std.com> |
| In reply to | #404563 |
kenseto <setoken@att.net> writes: >On Saturday, January 7, 2017 at 4:27:43 PM UTC-5, Michael Moroney wrote: >> kenseto <setoken@att.net> writes: >> >> >On Friday, January 6, 2017 at 11:37:49 AM UTC-5, Michael Moroney wrote: >> >> kenseto <setoken@att.net> writes: >> >> >Hey moron why don't you give a description of proper time >> >> You don't know how to use Google, Stupid Ken? >> >> >> >> Here. https://en.wikipedia.org/wiki/Proper_time >> >> > and I will give a description of proper time and we can compare. >> >> Nobody cares about your definition, other than to tell you it's wrong. >> >So moron.....what is wrong with my definition? >> You said a proper second is a second at the location of the clock. >> First, a second has a specific definition, and that is not it. >So?? What I said agrees with that specific definition.....a second is >0,192,631,770 periods of the Cs 133 radiation. You said "proper second". Science doesn't use that phrase, so it is something you made up, and to science is meaningless. >> Second, if we attempt to correct for that mistake by replacing "proper >> second" with "proper time" it is still wrong, since the clock can be, and >> usually is, moving around. Proper time is not a function of just an X,Y,Z >> location in space. >Idiot there is no mistake.....a proper second is an interval of proper time. >A second on my clock is a proper second on my clock. The made up phrase "proper second" is meaningless to science. >> Go look up proper time, and look up coordinate time why you are at it. >I don't have to look up.... That's your problem, Stupid Ken. You refuse to look up what words and phrases mean to science so you make up your own meanings. In addition, you also refuse to read what SR says, so again, you make up your own definitions for what SR states, which are usually wrong, and then you start arguing with people who try to correct you. >I gave you my definition of proper second (proper time). Nobody cares what your definition is. Especially when your definitions are part of IRT/Model Mechanics, since they are complete, utter, total, absolute failures. > Coordinate time is what I predict the value of my proper second on a >clock moving wrt me. You got it backwards, Stupid Ken. Go look up the science definitions of proper time and coordinate time. The wikipedia articles are good enough. > According to SR my proper second is worth 1/gamma second proper SR says nothing of the sort, and you know that. > According to IRT my proper second is worth Nobody cares what the failure known as IRT says. >> Hint: In the traveling twin "paradox", the traveling twin measure his own >> time as proper time, using a clock with him (his own biological aging is >> also a proper time clock), while the stay-at-home twin measures the >> traveling twin's time as coordinate time. (it is also his own proper time, >> of course, since he doesn't go anywhere) >Moron the stay at home twin predicts doesn't measure..... Stupid Ken, the stay-at-home twin definitely measures. He records the time his twin's rocket ship leaves and he records the time when his twin returns on his (inertial) clock, and subtracts to find the difference. That is a measurement. Why are you trying to involve fortune telling here? >he predicts that the value of his proper second on a moving clock. Gibberish.
[toc] | [prev] | [next] | [standalone]
| From | bartekltg@gmail.com |
|---|---|
| Date | 2016-12-27 11:24 -0800 |
| Message-ID | <20760f20-da94-4dad-9ff0-4a990a8fbe16@googlegroups.com> |
| In reply to | #403034 |
W dniu poniedziałek, 26 grudnia 2016 19:00:06 UTC+1 użytkownik paparios napisał: > El lunes, 26 de diciembre de 2016, 13:17:01 (UTC-3), Ed Lake escribió: > > On Sunday, December 25, 2016 at 3:34:04 PM UTC-6, mlwo...@wp.pl wrote: > > > W dniu niedziela, 25 grudnia 2016 20:00:16 UTC+1 użytkownik Ed Lake napisał: > > > > All you need if you want to detect time dilation is two very accurate atomic clocks. > > > > > > Check at GPS - when set accurately, clocks show no > > > dilation:( > > > > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on earth every day due to the speed at which the satellites travel. The clocks on GPS satellites tick 45 microseconds FASTER than clocks on Earth every day due to the difference in gravitation due to the difference in distance from the center of the Earth. > > > > This is incorrect. GPS atomic clocks tick always at the same rate (the rate they had before the launching). What changes is the observation rates of those clocks, from the point of view of the GPS receiver. No, it is true. Atomic clock on the satelite tick as nature tell it :) So, yes, the second is 9 192 631 770 periods connected to transition of two particular states, but you do not send ticks, but seconds. On Earth you divide it by 9192631770. On the GPS satellite we want to send a signal, that get us a second on Earth's surface. So we divide ticks by different number. For more technical version, see for example here: http://www.gps.gov/technical/icwg/IS-GPS-200H.pdf http://www.gps.gov/technical/icwg/IS-GPS-705D.pdf http://www.gps.gov/technical/icwg/IS-GPS-800D.pdf (yes, it is third time I post it in this htread) Chapter 'frequency plan'. There are small differences batween pdfs. bartekltg
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-27 11:33 -0800 |
| Message-ID | <e9637d09-a2a0-4f81-a23d-50be44e9bfb1@googlegroups.com> |
| In reply to | #403140 |
W dniu wtorek, 27 grudnia 2016 20:24:04 UTC+1 użytkownik bart...@gmail.com napisał: > No, it is true. Atomic clock on the satelite tick as nature tell it :) Another idiot hearing The Voice Of The Universe. > So, yes, the second is 9 192 631 770 periods connected to transition > of two particular states A lie, as expected from a fanatic idiot. During a second counted on GPS satellite by the local clock present on that satellite - Cs atom ticks a different number of periods. You know it well.
[toc] | [prev] | [next] | [standalone]
| From | bartekltg@gmail.com |
|---|---|
| Date | 2016-12-27 12:15 -0800 |
| Message-ID | <f6f14d78-d4f6-40ff-a4e7-bbd01289cb43@googlegroups.com> |
| In reply to | #403141 |
W dniu wtorek, 27 grudnia 2016 20:33:40 UTC+1 użytkownik mlwo...@wp.pl napisał: > W dniu wtorek, 27 grudnia 2016 20:24:04 UTC+1 użytkownik bart...@gmail.com napisał: > > > No, it is true. Atomic clock on the satelite tick as nature tell it :) > > Another idiot hearing The Voice Of The Universe. I'm offended:-) We are posting on polish newsgroups for a decade. I on the side of eggheads, you on the side of crackpots. And now you pretend you do not recognize me? Shame:-) bartekltg
[toc] | [prev] | [next] | [standalone]
| From | paparios <paparios@gmail.com> |
|---|---|
| Date | 2016-12-27 12:11 -0800 |
| Message-ID | <a43ebfcb-7432-4666-8362-4c5cf115ee2e@googlegroups.com> |
| In reply to | #403140 |
El martes, 27 de diciembre de 2016, 16:24:04 (UTC-3), bart...@gmail.com escribió: > W dniu poniedziałek, 26 grudnia 2016 19:00:06 UTC+1 użytkownik paparios napisał: > > El lunes, 26 de diciembre de 2016, 13:17:01 (UTC-3), Ed Lake escribió: > > > On Sunday, December 25, 2016 at 3:34:04 PM UTC-6, mlwo...@wp.pl wrote: > > > > W dniu niedziela, 25 grudnia 2016 20:00:16 UTC+1 użytkownik Ed Lake napisał: > > > > > All you need if you want to detect time dilation is two very accurate atomic clocks. > > > > > > > > Check at GPS - when set accurately, clocks show no > > > > dilation:( > > > > > > The clocks on GPS satellites tick 7 microseconds SLOWER than clocks on earth every day due to the speed at which the satellites travel. The clocks on GPS satellites tick 45 microseconds FASTER than clocks on Earth every day due to the difference in gravitation due to the difference in distance from the center of the Earth. > > > > > > > This is incorrect. GPS atomic clocks tick always at the same rate (the rate they had before the launching). What changes is the observation rates of those clocks, from the point of view of the GPS receiver. > > > No, it is true. Atomic clock on the satelite tick as nature tell it :) > So, yes, the second is 9 192 631 770 periods connected to transition > of two particular states, but you do not send ticks, but seconds. > On Earth you divide it by 9192631770. > On the GPS satellite we want to send a signal, that get us a second > on Earth's surface. So we divide ticks by different number. > Well it is not. You copied above the precise quotation from IS-GPS-200H.pdf, but read it careful again: "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." So, the received signal frequency AT THE GROUND should be 10.23 MHz. The satellite frequency IN ORBIT has to be 10.2299999954326 MHz, which is precisely the frequency which the atomic clock is set before launching.
[toc] | [prev] | [next] | [standalone]
Page 8 of 11 — ← Prev page 1 … 6 7 [8] 9 10 11 Next page →
Back to top | Article view | sci.physics.relativity
csiph-web