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 2 of 11 — ← Prev page 1 [2] 3 4 … 11 Next page →
| From | jaymoseley@hotmail.com |
|---|---|
| Date | 2016-12-26 11:12 -0800 |
| Message-ID | <9a4eb2d3-b010-4705-9a56-bbbba92369b2@googlegroups.com> |
| In reply to | #402991 |
What , like you assuming an incorrect calculation for c+v in Ives Stillwell for classical? Or you pretending you knew how many total detections in each LIGO detector when in fact you didn't know and later unwittingly admitted you didn't know? Or how about you pretending light isn't invariant in the MMX lab frame? Just to rule out classical theory. Sounds like you are fantasist, not me. I stick with the facts.
[toc] | [prev] | [next] | [standalone]
| From | Rafael Valls Hidalgo-Gato <rvalls162@gmail.com> |
|---|---|
| Date | 2016-12-22 13:42 -0800 |
| Message-ID | <461ded3a-8834-4b88-98f8-ba21dc1c475c@googlegroups.com> |
| In reply to | #402686 |
El jueves, 22 de diciembre de 2016, 3:39:08 (UTC-5), mlwo...@wp.pl escribió:
> W dniu czwartek, 22 grudnia 2016 05:32:10 UTC+1 użytkownik Prokaryotic Caspase Homolog napisał:
>
> > To detect time dilation, information has to be interchanged between clocks.
>
> You're absolutely right, poor idiot. Time dilation is the
> matter of information interchanged.
> You can't detect your idiocy just by observing muons:(
> You have to have clocks interchanging information.
>
> You have such clocks on GPS. And, quite unfortunately,
> information interchanged between them gives - t'=t.
> Welcome to real world.
The information interchanged that you refer corresponds to an operative GPS
with ALL the clocks already synchronized according to the 1905 Einstein's
relative time definition to the GPS ECI stationary system (of Cartesian
coordinates with Euclidean geometry) in which Newtonian equations hold good
(center of mass ones). ALL operative clocks (already adjusted to correct
velocity and gravitational potential effects) are then always showing
simultaneously the same ECI relative time t.
All GPS receptors are resolving every instant (since already almost 4 decades)
the following Newtonian system of equations:
(x-x_i)^2+ (y-y_i)^2+ (z-z_i)^2= (ct-ct_i)^2
where (x, y, z) is the position of the receptor at the same reception instant t
of signals transmitted from i different satellites (at least 4 ones) with
position (x_i, y_i, z_i) at time t_i.
The operative GPS represents then HUGE experimental evidence supporting the
1905R Einstein's Relativity theory, including the two original postulates; the
same laws of electrodynamics and optics holding good jointly with the mechanics
ones (proving the ether at absolute rest superfluous), and always the same
vacuum light speed c independent on the source one in all stationary systems.
RVHG (Rafael Valls Hidalgo-Gato)
[toc] | [prev] | [next] | [standalone]
| From | Ed Lake <detect@newsguy.com> |
|---|---|
| Date | 2016-12-25 11:00 -0800 |
| Message-ID | <5bd360a6-1be0-4d78-9b2b-c2ba6cb9ca78@googlegroups.com> |
| In reply to | #402686 |
All you need if you want to detect time dilation is two very accurate atomic clocks. If you set them side by side you can see and verify that they tick at the same rate because the are the same distance from the center of the Earth's mass. If you then RAISE one of the clocks, you will see that the clock that was raised to a higher level now ticks FASTER than the lower clock because it is farther from the center of Earth's mass. The National Institute of Standards and Technology demonstrated that they can measure gravitational time dilation by raising one clock by just 1 foot (33 centimeters). https://www.nist.gov/news-events/news/2010/09/nist-pair-aluminum-atomic-clocks-reveal-einsteins-relativity-personal-scale http://tf.boulder.nist.gov/general/pdf/2447.pdf
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-25 13:34 -0800 |
| Message-ID | <26e8382b-999f-41ef-9154-945fc3cc490e@googlegroups.com> |
| In reply to | #402975 |
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:(
[toc] | [prev] | [next] | [standalone]
| From | bartekltg@gmail.com |
|---|---|
| Date | 2016-12-25 13:57 -0800 |
| Message-ID | <3c683573-0ff0-4395-afcb-aff1efe73c97@googlegroups.com> |
| In reply to | #402986 |
W dniu niedziela, 25 grudnia 2016 22:34:04 UTC+1 użytkownik mlwo...@wp.pl napisał: > 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:( 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 See 3.2.1.1 " Frequency plan The nominal frequency of this source -- as it appears to an observer on the ground -- is 10.23 MHz. The SV carrier frequency and clock rates -- as they would appear to an observer located in the SV -- are offset to compensate for relativistic effects. The clock rates are offset by Δf/f = - 4.4647E-10, equivalent to a change in the I5 and Q5-code chipping rate of 10.23 MHz offset by a Δf = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz. " bartekltg
[toc] | [prev] | [next] | [standalone]
| From | Ed Lake <detect@newsguy.com> |
|---|---|
| Date | 2016-12-26 08:16 -0800 |
| Message-ID | <c0fedb58-5f4a-477d-ac14-858227830a51@googlegroups.com> |
| In reply to | #402986 |
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. As a result, every day the clocks on all 30 GPS satellites have to be adjusted by 38 microseconds (45 - 7 = 38) or the system would be worthless in a matter of days. Ed
[toc] | [prev] | [next] | [standalone]
| From | Demetrice Barren <teercere@tmerunin.tme> |
|---|---|
| Date | 2016-12-26 16:53 +0000 |
| Message-ID | <o3rhup$ur2$1@gioia.aioe.org> |
| In reply to | #403023 |
Ed Lake wrote: > As a result, every day the clocks on all 30 GPS satellites have to be > adjusted by 38 microseconds (45 - 7 = 38) or the system would be > worthless in a matter of days. Adjusted how exactly. Do you have the schematics diagram, the PCB layout diagram, Function Block diagram, Class diagram, or any other diagrams?? No, you dont have anything. You just move your lips.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-26 19:21 +0000 |
| Message-ID | <o3rqjj$3a5$1@pcls7.std.com> |
| In reply to | #403028 |
The nymshifting troll posting as Demetrice Barren <teercere@tmerunin.tme> writes: >Ed Lake wrote: >> As a result, every day the clocks on all 30 GPS satellites have to be >> adjusted by 38 microseconds (45 - 7 = 38) or the system would be >> worthless in a matter of days. >Adjusted how exactly. Do you have the schematics diagram, the PCB layout >diagram, Function Block diagram, Class diagram, or any other diagrams?? >No, you dont have anything. You just move your lips. We have the design specifications for the GPS system, which explicitly state the SV clock is adjusted by 38 microseconds/day to adjust for GR. Links have been posted many, many times. With further digging, I'm sure you can find schematics etc. for the SV frequency synthesizer should you want that level of detail.
[toc] | [prev] | [next] | [standalone]
| From | Demetrice Barren <teercere@tmerunin.tme> |
|---|---|
| Date | 2016-12-26 21:49 +0000 |
| Message-ID | <o3s3a7$1q8q$1@gioia.aioe.org> |
| In reply to | #403040 |
Michael Moroney wrote: >>Adjusted how exactly. Do you have the schematics diagram, the PCB layout >>diagram, Function Block diagram, Class diagram, or any other diagrams?? >>No, you dont have anything. You just move your lips. > > We have the design specifications for the GPS system, which explicitly > state the SV clock is adjusted by 38 microseconds/day to adjust for GR. > Links have been posted many, many times. With further digging, I'm sure > you can find schematics etc. for the SV frequency synthesizer should you > want that level of detail. I bet you cant find anything. They just move their lips, in order for people like you to have something to believe. Learn this basic thing in Physics, moroney. Receiver/Slave need specifications are completely different from Host/Master implementation specification. The Host/Master is something you dont need to know.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-27 03:29 +0000 |
| Message-ID | <o3sn6c$phr$1@pcls7.std.com> |
| In reply to | #403049 |
The nymshifting troll posting as Demetrice Barren <teercere@tmerunin.tme> writes: >Michael Moroney wrote: >> We have the design specifications for the GPS system, which explicitly >> state the SV clock is adjusted by 38 microseconds/day to adjust for GR. >> Links have been posted many, many times. With further digging, I'm sure >> you can find schematics etc. for the SV frequency synthesizer should you >> want that level of detail. >I bet you cant find anything. It's up to you to find it. Pointers have been posted here very many times discussing how the satellite transmitter clocks are adjusted to compensate for GR. >Learn this basic thing in Physics, moroney. Receiver/Slave need >specifications are completely different from Host/Master implementation >specification. The Host/Master is something you dont need to know. That's the space vehicle (satellite) transmitters which have their clocks adjusted to run slow by 38 microseconds per day, so that the receivers on earth receive the correct timing signals.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-26 23:34 -0800 |
| Message-ID | <49279606-d209-474c-9b56-b76d14c24817@googlegroups.com> |
| In reply to | #403064 |
W dniu wtorek, 27 grudnia 2016 04:29:20 UTC+1 użytkownik Michael Moroney napisał: > It's up to you to find it. Pointers have been posted here very many > times discussing how the satellite transmitter clocks are adjusted to > compensate for GR. And that's a lie, unfortunately. Your Shit's MAIN assumption is, that clocks are proper without any adjustment to compensate anything.
[toc] | [prev] | [next] | [standalone]
| From | Demetrice Barren <teercere@tmerunin.tme> |
|---|---|
| Date | 2016-12-27 20:33 +0000 |
| Message-ID | <o3uj6i$1l3g$1@gioia.aioe.org> |
| In reply to | #403064 |
Michael Moroney wrote: >>Learn this basic thing in Physics, moroney. Receiver/Slave need >>specifications are completely different from Host/Master implementation >>specification. The Host/Master is something you dont need to know. > > That's the space vehicle (satellite) transmitters which have their > clocks adjusted to run slow by 38 microseconds per day, so that the > receivers on earth receive the correct timing signals. Hmm, so their rates are "adjusted", because of Relativity, THEN again, have those clock adjusted once a day, in order to make sure :) Huh?? Do you even know what "timing signals", moroney. You use things in wrong context. Cant avoid to remark. Timing is something else, has nothing to with anything, in here.
[toc] | [prev] | [next] | [standalone]
| From | moroney@world.std.spaamtrap.com (Michael Moroney) |
|---|---|
| Date | 2016-12-30 01:24 +0000 |
| Message-ID | <o44d10$n4m$2@pcls7.std.com> |
| In reply to | #403148 |
The nymshifting troll, pretending to be Demetrice Barren, writes: >Michael Moroney wrote: >>>Learn this basic thing in Physics, moroney. Receiver/Slave need >>>specifications are completely different from Host/Master implementation >>>specification. The Host/Master is something you dont need to know. >> >> That's the space vehicle (satellite) transmitters which have their >> clocks adjusted to run slow by 38 microseconds per day, so that the >> receivers on earth receive the correct timing signals. >Hmm, so their rates are "adjusted", because of Relativity, THEN again, >have those clock adjusted once a day, in order to make sure :) Huh?? There is the fixed builtin adjustment for GR effects of 38 microseconds per day. This never changes. There are additional smaller adjustments for things like small changes in orbit due to the moon or whatever. Usually in the nanosecond range. >Do you even know what "timing signals", moroney. You use things in wrong >context. Cant avoid to remark. Timing is something else, has nothing to >with anything, in here. English please, nymshifter.
[toc] | [prev] | [next] | [standalone]
| From | bartekltg@gmail.com |
|---|---|
| Date | 2016-12-27 11:05 -0800 |
| Message-ID | <3f25a778-4f0d-465e-b798-e45df0d88c7a@googlegroups.com> |
| In reply to | #403028 |
W dniu poniedziałek, 26 grudnia 2016 17:53:48 UTC+1 użytkownik Demetrice Barren napisał: > Ed Lake wrote: > > > As a result, every day the clocks on all 30 GPS satellites have to be > > adjusted by 38 microseconds (45 - 7 = 38) or the system would be > > worthless in a matter of days. > > Adjusted how exactly. Do you have the schematics diagram, the PCB layout > diagram, Function Block diagram, Class diagram, or any other diagrams?? > No, you dont have anything. You just move your lips. Frequency change isn't a big problem. Do you want to know precisely? read documentation. Oh, you asked about docs... Do you even read the thread? 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 A good start is here, from the middle one: "The requirements specified in this document shall pertain to the signal contained within a 24 MHz band centered about the L5 nominal frequency. The carrier frequencies for the L1, L2 and L5 signals shall be coherently derived from a common frequency source within the SV. The nominal frequency of this source -- as it appears to an observer on the ground -- is 10.23 MHz. The SV carrier frequency and clock rates -- as they would appear to an observer located in the SV -- are offset to compensate for relativistic effects. The clock rates are offset by Δf/f = - 4.4647E-10, equivalent to a change in the I5 and Q5-code chipping rate of 10.23 MHz offset by a Δf = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz. The nominal carrier frequency (f0) -- as it appears to an observer on the ground - shall be 1176.45 MHz, or 115 times 10.23 MHz." bartekltg
[toc] | [prev] | [next] | [standalone]
| From | Demetrice Barren <teercere@tmerunin.tme> |
|---|---|
| Date | 2016-12-27 20:43 +0000 |
| Message-ID | <o3ujov$1m5g$1@gioia.aioe.org> |
| In reply to | #403137 |
bartekltg wrote: >> Adjusted how exactly. Do you have the schematics diagram, the PCB >> layout diagram, Function Block diagram, Class diagram, or any other >> diagrams?? No, you dont have anything. You just move your lips. > > Frequency change isn't a big problem. > Do you want to know precisely? read documentation. > Oh, you asked about docs... Do you even read the thread? Asked about diagrams, blueprints, in order to see the exact HOST/MASTER implementation. But I am talking to a moron, which come back with the specification needed to implement the clients/slaves. Last time I read it was a military business, not in public domain. Crucial difference. But even without being a military business. Pure basics in Science and Physics, you get for instance an RF chip (a lot of Function Blocks) and about two hundreds pages datasheet specification. But the proper internal embedded specification you dont get. Never will get, and is something you do NOT need know. AND, if it were to get it, then NOT without agreements of NON-DISCLOSURE. Hopefully you, and alot of half-engineers around here, just learned something about GPS, they never will forget.
[toc] | [prev] | [next] | [standalone]
| From | Ed Lake <detect@newsguy.com> |
|---|---|
| Date | 2016-12-27 13:30 -0800 |
| Message-ID | <db8539f0-8881-46ac-8e37-4844e6f9df61@googlegroups.com> |
| In reply to | #403137 |
On Tuesday, December 27, 2016 at 1:05:20 PM UTC-6, bart...@gmail.com wrote: > W dniu poniedziałek, 26 grudnia 2016 17:53:48 UTC+1 użytkownik Demetrice Barren napisał: > > Ed Lake wrote: > > > > > As a result, every day the clocks on all 30 GPS satellites have to be > > > adjusted by 38 microseconds (45 - 7 = 38) or the system would be > > > worthless in a matter of days. > > > > Adjusted how exactly. Do you have the schematics diagram, the PCB layout > > diagram, Function Block diagram, Class diagram, or any other diagrams?? > > No, you dont have anything. You just move your lips. > > Frequency change isn't a big problem. > Do you want to know precisely? read documentation. > Oh, you asked about docs... Do you even read the thread? > > 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 > > A good start is here, from the middle one: > "The requirements specified in this document shall pertain to the signal contained within a 24 > MHz band centered about the L5 nominal frequency. The carrier frequencies for the L1, L2 and > L5 signals shall be coherently derived from a common frequency source within the SV. The > nominal frequency of this source -- as it appears to an observer on the ground -- is 10.23 MHz. > The SV carrier frequency and clock rates -- as they would appear to an observer located in the > SV -- are offset to compensate for relativistic effects. The clock rates are offset by Δf/f = - > 4.4647E-10, equivalent to a change in the I5 and Q5-code chipping rate of 10.23 MHz offset by a > Δf = -4.5674E-3 Hz. This is equal to 10.2299999954326 MHz. The nominal carrier frequency > (f0) -- as it appears to an observer on the ground - shall be 1176.45 MHz, or 115 times 10.23 > MHz." > > bartekltg Sorry. I was just talking generalities. I don't plan to build and launch my own GPS satellite. Also, I've only been on this forum for three days. I'm just responding to the latest posts that mention time dilation. Ed
[toc] | [prev] | [next] | [standalone]
| From | paparios <paparios@gmail.com> |
|---|---|
| Date | 2016-12-26 10:00 -0800 |
| Message-ID | <37979172-5075-4133-9110-625bb822769a@googlegroups.com> |
| In reply to | #403023 |
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. > As a result, every day the clocks on all 30 GPS satellites have to be adjusted by 38 microseconds (45 - 7 = 38) or the system would be worthless in a matter of days. > > Ed
[toc] | [prev] | [next] | [standalone]
| From | Demetrice Barren <teercere@tmerunin.tme> |
|---|---|
| Date | 2016-12-26 18:06 +0000 |
| Message-ID | <o3rm6o$15bq$2@gioia.aioe.org> |
| In reply to | #403034 |
paparios wrote: > This is incorrect. GPS atomic clocks tick always at the same rate (the > rate they had before the launching). Yes, observed LOCALLY. > What changes is the observation > rates of those clocks, from the point of view of the GPS receiver. No, but the observations performed NON-LOCALLY. Excellent post. Thank you.
[toc] | [prev] | [next] | [standalone]
| From | mlwozniak@wp.pl |
|---|---|
| Date | 2016-12-26 11:48 -0800 |
| Message-ID | <811759ff-2fdb-48f4-9733-ba3cab91f9a6@googlegroups.com> |
| In reply to | #403034 |
W dniu poniedziałek, 26 grudnia 2016 19:00:06 UTC+1 użytkownik paparios napisał: > This is incorrect. GPS atomic clocks tick always at the same rate (the rate they had before the launching). If they did, they wouldn't keep synchronization, poor idiot.
[toc] | [prev] | [next] | [standalone]
| From | Ed Lake <detect@newsguy.com> |
|---|---|
| Date | 2016-12-26 13:28 -0800 |
| Message-ID | <ec20e09a-692b-47c3-bdc4-8d0a20eebcdc@googlegroups.com> |
| In reply to | #403034 |
On Monday, December 26, 2016 at 12:00:06 PM UTC-6, paparios wrote: > > > 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. > "The engineers who designed the GPS system included these relativistic effects when they designed and deployed the system. For example, to counteract the General Relativistic effect once on orbit, they slowed down the ticking frequency of the atomic clocks before they were launched so that once they were in their proper orbit stations their clocks would appear to tick at the correct rate as compared to the reference atomic clocks at the GPS ground stations. Further, each GPS receiver has built into it a microcomputer that, in addition to performing the calculation of position using 3D trilateration, will also compute any additional special relativistic timing calculations required." source: http://www.astronomy.ohio-state.edu/~pogge/Ast162/Unit5/gps.html So, they do not make corrections daily. I was wrong about that. They knew before launching what time dilation corrections would be required, so they automated the correcting process. Either way, time dilation DOES affect the GPS satellite clocks. They just built in the correction process so that it does no harm.
[toc] | [prev] | [next] | [standalone]
Page 2 of 11 — ← Prev page 1 [2] 3 4 … 11 Next page →
Back to top | Article view | sci.physics.relativity
csiph-web