Rocksolid Light

Welcome to novaBBS (click a section below)

mail  files  register  newsreader  groups  login

Message-ID:  

You will be successful in your work.


tech / sci.physics.relativity / Writing the History of a Spacetime Event

SubjectAuthor
* Writing the History of a Spacetime Eventpatdolan
+- Re: Writing the History of a Spacetime EventWerner Soldati
+- Re: Writing the History of a Spacetime Eventpatdolan
+* Re: Writing the History of a Spacetime EventTrevor Lange
|+* Re: Writing the History of a Spacetime Eventpatdolan
||`* Re: Writing the History of a Spacetime EventTrevor Lange
|| `- Re: Writing the History of a Spacetime Eventpatdolan
|`* Re: Writing the History of a Spacetime Eventpatdolan
| `* Re: Writing the History of a Spacetime EventTrevor Lange
|  `* Re: Writing the History of a Spacetime Eventpatdolan
|   `* Re: Writing the History of a Spacetime EventTrevor Lange
|    +- Re: Writing the History of a Spacetime Eventpatdolan
|    `* Re: Writing the History of a Spacetime Eventpatdolan
|     `* Re: Writing the History of a Spacetime EventTrevor Lange
|      +- Re: Writing the History of a Spacetime Eventpatdolan
|      `* Re: Writing the History of a Spacetime EventTrevor Lange
|       `* Re: Writing the History of a Spacetime Eventpatdolan
|        `* Re: Writing the History of a Spacetime EventTrevor Lange
|         `* Re: Writing the History of a Spacetime Eventpatdolan
|          `* Re: Writing the History of a Spacetime EventTrevor Lange
|           `* Re: Writing the History of a Spacetime Eventpatdolan
|            `* Re: Writing the History of a Spacetime EventTrevor Lange
|             `* Re: Writing the History of a Spacetime Eventpatdolan
|              `* Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime Eventmitchr...@gmail.com
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventmitchr...@gmail.com
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime Eventgehan.am...@gmail.com
|               +- Re: Writing the History of a Spacetime Eventpatdolan
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               +- Re: Writing the History of a Spacetime EventTrevor Lange
|               `- Re: Writing the History of a Spacetime Eventpatdolan
`- Re: Writing the History of a Spacetime Eventgehan.am...@gmail.com

Pages:123
Writing the History of a Spacetime Event

<774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:5e54:0:b0:3ef:3243:2851 with SMTP id i20-20020ac85e54000000b003ef32432851mr128206qtx.3.1683126843563;
Wed, 03 May 2023 08:14:03 -0700 (PDT)
X-Received: by 2002:a37:f51a:0:b0:74d:dcc:c9ba with SMTP id
l26-20020a37f51a000000b0074d0dccc9bamr2761797qkk.0.1683126843401; Wed, 03 May
2023 08:14:03 -0700 (PDT)
Path: i2pn2.org!rocksolid2!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 3 May 2023 08:14:03 -0700 (PDT)
Injection-Info: google-groups.googlegroups.com; posting-host=2600:100f:b06a:9c46:10ea:e043:3f45:6f2d;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2600:100f:b06a:9c46:10ea:e043:3f45:6f2d
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
Subject: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Wed, 03 May 2023 15:14:03 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 19
 by: patdolan - Wed, 3 May 2023 15:14 UTC

A very typical atmospheric muon simultaneously comes to rest and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. Let's explore the history of this spacetime event. The muon's trajectory was normal to the surface of the earth.

The muon's velocity relative to the earth was measured to be 0.867c which results in gamma = 2. The muon's clock showed an elapsed proper time of 2..2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.

1) What did the muon calculate its proper altitude above the earth to be at the spacetime event corresponding to its creation?

2) What did the scientists in the scintillator lab calculate the muon's altitude to be at the spacetime event corresponding to the muon's creation?

3) What did the lab scientist read on the scintillator lab's clock at the spacetime event corresponding to the muon's creation?

Re: Writing the History of a Spacetime Event

<u2tui5$1b28b$1@dont-email.me>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity sci.physics sci.math
Path: i2pn2.org!i2pn.org!eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail
From: tdn...@tnlernad.rs (Werner Soldati)
Newsgroups: sci.physics.relativity,sci.physics,sci.math
Subject: Re: Writing the History of a Spacetime Event
Date: Wed, 3 May 2023 15:28:06 -0000 (UTC)
Organization: A noiseless patient Spider
Lines: 23
Message-ID: <u2tui5$1b28b$1@dont-email.me>
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Injection-Date: Wed, 3 May 2023 15:28:06 -0000 (UTC)
Injection-Info: dont-email.me; posting-host="7076e6c15ff16fce2b63627c5a3284d0";
logging-data="1411339"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/WmfBsfoqmZAAbwV+gvFSb"
User-Agent: MesNews/1.08.06.00-gb
Cancel-Lock: sha1:g7790Mo+eqSHtDKE8eAjrDKe3Tk=
Face: iVBORw0KGgoAAAANSUhEUgAAADAAAAAwBAMAAAClLOS0AAAAGFBMVEWPj6QoIiHQ
gofRZDrhvnV4QCLRz7pnYmjESovaAAACYUlEQVQ4jXXTwW7bMAwAUC1D0WuVwei
1o5Tl2kl2c1dZ7+xorK9DJuicOPD0+yPtNHUxTECDVE+URIZSRcZIWt8f1fswj6
r0Yxm1rk66X4B/VCd90pXWutP6+AF4bgIe9//A25gnh/RwhU4+TvNe23ObYAai0
umKOn2nFIBBzIFvRbqfbrznu92pcRNbhgPDSBMMLYz6/nZfbJuYJA8ZAJBDo/W5
FMSEiP6o+jdIodNxN+A0nneKympXjhM0HQ0u2CfE8FJUeW0PZQBoE25HsuBqBjS
9KhCwDAPwMkN9Qm+NnEGqhGS3YCdoXjNifYGhNTXYzFcBoDazGMt/jbLBYPgmgB
BzzsmYmm+1URh8PlhemAL85IgEtJ8Bf7dBlgM88B6YzRinPBKXQE72njgbya0ni
7VXGbnK/H9DpCYIvnNYO5WTPUwLCdRKvmA4nYMTwB/Amz9HATkFv+6N9wJbWQiO
wUc5/mXtjEAoZ9mA4YaIhjZzsEDYUpRcIaib+F1PYHkrrnbpuVYNR3yqNj1XJ5B
1njPneOcb4sNvI8+1DCBgSFN/7jpy6raWlNrUXKCrOKiTnnpKzqLFxgl4kqaiqd
me8sZJFRwYteYI7rnd1J01bqITMEbpM0lbz2+AmsiXAJIIXUnjVvMTGCnSF2fI2
e2l269AO777EuYXsKF+9JzTBcbrmzEdxXe4e39In0mAqK4FFk9vRdX/oPcCtg7q
7eXN0PRyBEcAAywh8rSAZ1gvYMPABbLcJXq518oIVIR1LQBLoBlagT8L4AM0RbR
JYPh1hWf5yaLnphFYfYBI3mOAv9K23xPxjD2rAAAAAElFTkSuQmCC
X-Face: ;&at>V@0:+M}FU*@&$GK{Do?i=l7=[RX%~-eRWk-cp.l3/2*7e^X?WpsUdJ|cR<H
ePY-jy,u&;+b~:;XY]l@f*vABn~q(D'Gl7R&y9_p0e+`i\BGg0qoIR+zn\SS%azg]U}(9{"
H>_U#E|GjNN9YBe\V=p8(>Qn!|)Rh*P)JDDr7d^)`_&H\v`X6WWP@AEgkrlsel|k0yw}q-2
^hB(U1<5Y}T(,X=MAD:(uXVZHQ^5Z]BS$.\fVngxS)/v_rRM_QsUs6&PG$>L:)^O%PzBvX}
3U8HojH^2CpDJfStZn#D"zMj/'Gm/{AA>]
 by: Werner Soldati - Wed, 3 May 2023 15:28 UTC

patdolan wrote:

> 1) What did the muon calculate its proper altitude above the earth to be
> at the spacetime event corresponding to its creation?

*_Ukraine_preparing_sabotage_raid_on_neighbor_* – RT Russian source
Kiev has gathered up to 4,000 troops to storm an ammunition depot in
Transnistria, the source claims
https://%72%74.com/%72%75%73sia/575712-transnistria-ukraine-raid-russia/

Ukraine has been a terrorist state since the US backed 2014 coup, when
they overthrew an elected government and installed a slovenly, debased
puppet.

Just heard Alex Christoforou's first report today wherein he said that
Ukraine NAZIS decide who is civilized and who isn't in the world from a
delusional Uke leadership spokesman! Looks like you give us money and arms
to make the US world controllers, you're civilized!

Now, is NATO going to help Ukraine's neighbor fight Ukraine? Hmm, Lol.
Typical evil, illegal Obama strategy spinning out of control and
backfiring.

Re: Writing the History of a Spacetime Event

<7d34b267-8073-48cd-a91c-5ee94dee4dccn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:255:b0:3ec:8ffc:e232 with SMTP id c21-20020a05622a025500b003ec8ffce232mr575053qtx.7.1683157027580;
Wed, 03 May 2023 16:37:07 -0700 (PDT)
X-Received: by 2002:ad4:57ad:0:b0:5ef:512f:ffe1 with SMTP id
g13-20020ad457ad000000b005ef512fffe1mr1699526qvx.1.1683157027389; Wed, 03 May
2023 16:37:07 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 3 May 2023 16:37:07 -0700 (PDT)
In-Reply-To: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:a929:a40c:f0b3:62d4;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:a929:a40c:f0b3:62d4
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <7d34b267-8073-48cd-a91c-5ee94dee4dccn@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Wed, 03 May 2023 23:37:07 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 2678
 by: patdolan - Wed, 3 May 2023 23:37 UTC

On Wednesday, May 3, 2023 at 8:14:04 AM UTC-7, patdolan wrote:
> A very typical atmospheric muon simultaneously comes to rest and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. Let's explore the history of this spacetime event. The muon's trajectory was normal to the surface of the earth.
>
> The muon's velocity relative to the earth was measured to be 0.867c which results in gamma = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
>
> 1) What did the muon calculate its proper altitude above the earth to be at the spacetime event corresponding to its creation?
>
> 2) What did the scientists in the scintillator lab calculate the muon's altitude to be at the spacetime event corresponding to the muon's creation?
>
> 3) What did the lab scientist read on the scintillator lab's clock at the spacetime event corresponding to the muon's creation?
One thing you can say for Eponymous: when he sets up the chess board, it's always a one move checkmate. I give relativists credit for recognizing this. But I also condemn them for their cowardice when it comes to takin' their whupin' for their error-filled beliefs.

Re: Writing the History of a Spacetime Event

<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:16:b0:3e3:db7d:da45 with SMTP id x22-20020a05622a001600b003e3db7dda45mr734875qtw.2.1683161801463;
Wed, 03 May 2023 17:56:41 -0700 (PDT)
X-Received: by 2002:a05:6214:4a48:b0:61a:facb:3618 with SMTP id
ph8-20020a0562144a4800b0061afacb3618mr1729931qvb.9.1683161801269; Wed, 03 May
2023 17:56:41 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!border-1.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 3 May 2023 17:56:41 -0700 (PDT)
In-Reply-To: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:250e:814:315f:73b7;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:250e:814:315f:73b7
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Thu, 04 May 2023 00:56:41 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 44
 by: Trevor Lange - Thu, 4 May 2023 00:56 UTC

On Wednesday, May 3, 2023 at 8:14:04 AM UTC-7, patdolan wrote:
> Let's explore the history of this spacetime event.

A spacetime event doesn't have a history, it is simply a specific "point" in spacetime. Of course, the causal past of an event consists of the entirety of the past light cone and its interior.

> A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.

Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) that you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2.

> 1) What did the muon calculate its proper altitude above the earth to be at the spacetime event corresponding to its creation?

Muon's don't calculate things, and even if they did, it would be irrelevant.. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.

> 2) What did the scientists in the scintillator lab calculate the muon's altitude to be at the spacetime event corresponding to the muon's creation?

As noted above, in terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds.

> 3) What did the lab scientist read on the scintillator lab's clock at the spacetime event corresponding to the muon's creation?

In terms of S, the lab clock read -D/v at event e2. Of course, it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.

Re: Writing the History of a Spacetime Event

<ccce72a0-983b-4425-ac0c-af41704b9d80n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:152c:b0:74d:f7d0:6a48 with SMTP id n12-20020a05620a152c00b0074df7d06a48mr3001220qkk.9.1683168451595;
Wed, 03 May 2023 19:47:31 -0700 (PDT)
X-Received: by 2002:ae9:c007:0:b0:74d:fb3d:536 with SMTP id
u7-20020ae9c007000000b0074dfb3d0536mr4081800qkk.13.1683168451372; Wed, 03 May
2023 19:47:31 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!border-1.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 3 May 2023 19:47:31 -0700 (PDT)
In-Reply-To: <e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:a929:a40c:f0b3:62d4;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:a929:a40c:f0b3:62d4
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com> <e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <ccce72a0-983b-4425-ac0c-af41704b9d80n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Thu, 04 May 2023 02:47:31 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 60
 by: patdolan - Thu, 4 May 2023 02:47 UTC

On Wednesday, May 3, 2023 at 5:56:42 PM UTC-7, Trevor Lange wrote:
> On Wednesday, May 3, 2023 at 8:14:04 AM UTC-7, patdolan wrote:
> > Let's explore the history of this spacetime event.
> A spacetime event doesn't have a history, it is simply a specific "point" in spacetime. Of course, the causal past of an event consists of the entirety of the past light cone and its interior.
>
> > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
>
> Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) that you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.

A point of clarification please. Your e4 is simultaneous is in both your S and your S'. Correct? I will take the liberty of anticipating your answering in the affirmative and go on to cast this fact in terms of my own narrative, which most will agree is far more informative, heuristic, natural, numerical and entertaining than your own style of composure, Legion Lange. To wit:

The lab clock reads 0.00 at the moment of the muon's disintegration in the scintillator. And the muon's egg-timer-to-disintegration has ticked down from 2.2 usec (which the anthropomorphized muon set when it was formed high in the atmosphere) to 0.00 usec at the moment of its disintegration in the scintillator. So both the lab clock and the muon's egg timer read 0.00 usec at the moment of disintegration. This is your e4 and it is the END OF THE BRIEF HISTORY OF MURRAY THE MUON.

From here Legion, we can examine Murray's life history in both your S and your S'.

In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2.
> > 1) What did the muon calculate its proper altitude above the earth to be at the spacetime event corresponding to its creation?
> Muon's don't calculate things, and even if they did, it would be irrelevant. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > 2) What did the scientists in the scintillator lab calculate the muon's altitude to be at the spacetime event corresponding to the muon's creation?
> As noted above, in terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds.
> > 3) What did the lab scientist read on the scintillator lab's clock at the spacetime event corresponding to the muon's creation?
> In terms of S, the lab clock read -D/v at event e2. Of course, it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.

Re: Writing the History of a Spacetime Event

<e964cf6f-58b1-4dd6-9989-0ea505ca7d1bn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:1a09:b0:3ef:3ead:149 with SMTP id f9-20020a05622a1a0900b003ef3ead0149mr749973qtb.13.1683169526684;
Wed, 03 May 2023 20:05:26 -0700 (PDT)
X-Received: by 2002:ac8:5a12:0:b0:3f0:abe7:24a7 with SMTP id
n18-20020ac85a12000000b003f0abe724a7mr771776qta.6.1683169526452; Wed, 03 May
2023 20:05:26 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 3 May 2023 20:05:26 -0700 (PDT)
In-Reply-To: <ccce72a0-983b-4425-ac0c-af41704b9d80n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:250e:814:315f:73b7;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:250e:814:315f:73b7
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <ccce72a0-983b-4425-ac0c-af41704b9d80n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e964cf6f-58b1-4dd6-9989-0ea505ca7d1bn@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Thu, 04 May 2023 03:05:26 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3276
 by: Trevor Lange - Thu, 4 May 2023 03:05 UTC

On Wednesday, May 3, 2023 at 7:47:32 PM UTC-7, patdolan wrote:
> > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> >
> > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) that you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.
>
> Your e4 is simultaneous is in both your S and your S'. Correct?

Simultaneous with what? Event e4 is the collision event. It is not simultaneous with any of the other events in terms of any standard system of inertial coordinates.

Again, in terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v at event e2. Of course, it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.

Re: Writing the History of a Spacetime Event

<5e12bb0e-c1a7-4c16-9fb4-a485efc0b783n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ad4:48d0:0:b0:61a:bbd9:2c6d with SMTP id v16-20020ad448d0000000b0061abbd92c6dmr1912955qvx.6.1683173191564;
Wed, 03 May 2023 21:06:31 -0700 (PDT)
X-Received: by 2002:a05:620a:15d6:b0:74e:9036:34f3 with SMTP id
o22-20020a05620a15d600b0074e903634f3mr4158520qkm.15.1683173191400; Wed, 03
May 2023 21:06:31 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Wed, 3 May 2023 21:06:31 -0700 (PDT)
In-Reply-To: <e964cf6f-58b1-4dd6-9989-0ea505ca7d1bn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:a929:a40c:f0b3:62d4;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:a929:a40c:f0b3:62d4
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <ccce72a0-983b-4425-ac0c-af41704b9d80n@googlegroups.com>
<e964cf6f-58b1-4dd6-9989-0ea505ca7d1bn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5e12bb0e-c1a7-4c16-9fb4-a485efc0b783n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Thu, 04 May 2023 04:06:31 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4055
 by: patdolan - Thu, 4 May 2023 04:06 UTC

On Wednesday, May 3, 2023 at 8:05:27 PM UTC-7, Trevor Lange wrote:
> On Wednesday, May 3, 2023 at 7:47:32 PM UTC-7, patdolan wrote:
> > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > >
> > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) that you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.
> >
> > Your e4 is simultaneous is in both your S and your S'. Correct?
> Simultaneous with what? Event e4 is the collision event. It is not simultaneous with any of the other events in terms of any standard system of inertial coordinates.

Just checking Legion, just checking. You are known to be a slippery fellow who delights in introducing your own notation for purposes of obfuscation. Everybody says so.

As you can see out your window, twilight is almost over in Seattle. The Night is falling fast. Ross is probably tucked up in his bed already and is reading hizself to sleep with the CRC Standard Mathematical Tables--you'll notice he never records his YouTube videos at night. I am a bit tire too. If I wake up between now and dawn I may continue the bifurcated and inconsistent histories of Murray the muon. For sure tomorrow.
>
> Again, in terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v at event e2. Of course, it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.

Re: Writing the History of a Spacetime Event

<229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:318f:b0:74e:437f:e942 with SMTP id bi15-20020a05620a318f00b0074e437fe942mr254556qkb.8.1683227902872;
Thu, 04 May 2023 12:18:22 -0700 (PDT)
X-Received: by 2002:a05:620a:1792:b0:74e:362b:2f96 with SMTP id
ay18-20020a05620a179200b0074e362b2f96mr307369qkb.2.1683227902706; Thu, 04 May
2023 12:18:22 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!3.eu.feeder.erje.net!feeder.erje.net!npeer.as286.net!npeer-ng0.as286.net!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer02.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 4 May 2023 12:18:22 -0700 (PDT)
In-Reply-To: <e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:20f1:9eb3:450a:5059;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:20f1:9eb3:450a:5059
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com> <e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Thu, 04 May 2023 19:18:22 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4898
 by: patdolan - Thu, 4 May 2023 19:18 UTC

On Wednesday, May 3, 2023 at 5:56:42 PM UTC-7, Trevor Lange wrote:
> On Wednesday, May 3, 2023 at 8:14:04 AM UTC-7, patdolan wrote:
> > Let's explore the history of this spacetime event.
> A spacetime event doesn't have a history, it is simply a specific "point" in spacetime. Of course, the causal past of an event consists of the entirety of the past light cone and its interior.
>
> > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
>
> Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) that you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2.
> > 1) What did the muon calculate its proper altitude above the earth to be at the spacetime event corresponding to its creation?
> Muon's don't calculate things, and even if they did, it would be irrelevant. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > 2) What did the scientists in the scintillator lab calculate the muon's altitude to be at the spacetime event corresponding to the muon's creation?
> As noted above, in terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds.
> > 3) What did the lab scientist read on the scintillator lab's clock at the spacetime event corresponding to the muon's creation?
> In terms of S, the lab clock read -D/v at event e2. Of course, it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.
No, no, no Legion! This simply won't do. All you have done is copied out the schema of the standard Minkowski treatment of spacetime while avoiding my numerical values like a vampire avoids a garlic smeared crucifix. Do you not realize that you must sink your hands into the numerical calculations up to the elbows in order for me to trap you and Einstein in foolhardy inconsistency. You want the spacetime event e1 (the creation of Murray the muon) to not be simultaneous in the lab frame S and Murray's frame S'. Fine, I'm down with that. In fact it is essential to my demonstration. You want the attitudes of Murray's nativity to have different values in each frame too. Good! This is also vital to my demonstration. Go ahead. Put numbers to these things. Then watch me show how we lose all hope of ever demonstrating that Murray's egg timer and the lab clock each correspond to 0.0 usec at e4 (the disintegration of Murray in the lab).

Re: Writing the History of a Spacetime Event

<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:424c:b0:74d:fb3d:536 with SMTP id w12-20020a05620a424c00b0074dfb3d0536mr552897qko.13.1683245378213;
Thu, 04 May 2023 17:09:38 -0700 (PDT)
X-Received: by 2002:a05:620a:1a20:b0:74e:5103:2c9c with SMTP id
bk32-20020a05620a1a2000b0074e51032c9cmr599486qkb.12.1683245378044; Thu, 04
May 2023 17:09:38 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer02.ams1!peer.ams1.xlned.com!news.xlned.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 4 May 2023 17:09:37 -0700 (PDT)
In-Reply-To: <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:80b8:87a7:2408:8b87;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:80b8:87a7:2408:8b87
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Fri, 05 May 2023 00:09:38 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3892
 by: Trevor Lange - Fri, 5 May 2023 00:09 UTC

On Wednesday, May 3, 2023 at 7:47:32 PM UTC-7, patdolan wrote:
> A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.

Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.

In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v at event e2, and it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.

> You want the spacetime event e1 (the creation of the muon) to not be simultaneous
> in the lab frame S and in the muon's frame S'.

Simultaneous with what? Again, e1 is simultaneous with e2 in terms of S, and it is simultaneous with e3 in terms of S'.

> Watch me show how we lose all hope of ever demonstrating that the muon's egg timer
> and the lab clock each correspond to 0.0 usec at e4 (the disintegration of the muon in the lab).

Again, the elapsed proper time of the muon from creation to collision is 2.2 usec, so if it's co-moving clock to reads zero at the collision, it read -2.2 usec at its creation. Likewise if the lab clock reads zero at the collision, it must read -D/v at event e2, and -D/(vg^2) at event e3. This was all covered (twice) up above.

Re: Writing the History of a Spacetime Event

<a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:4723:b0:74e:a66:30f5 with SMTP id bs35-20020a05620a472300b0074e0a6630f5mr542137qkb.5.1683248799272;
Thu, 04 May 2023 18:06:39 -0700 (PDT)
X-Received: by 2002:a05:622a:2595:b0:3f3:62cc:a0fe with SMTP id
cj21-20020a05622a259500b003f362cca0femr1504004qtb.3.1683248799074; Thu, 04
May 2023 18:06:39 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!feeder1.feed.usenet.farm!feed.usenet.farm!peer02.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 4 May 2023 18:06:38 -0700 (PDT)
In-Reply-To: <6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:18de:f3f0:e3ec:af92;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:18de:f3f0:e3ec:af92
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Fri, 05 May 2023 01:06:39 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 5011
 by: patdolan - Fri, 5 May 2023 01:06 UTC

On Thursday, May 4, 2023 at 5:09:40 PM UTC-7, Trevor Lange wrote:
> On Wednesday, May 3, 2023 at 7:47:32 PM UTC-7, patdolan wrote:
> > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.
>
> In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v at event e2, and it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.
>
> > You want the spacetime event e1 (the creation of the muon) to not be simultaneous
> > in the lab frame S and in the muon's frame S'.
>
> Simultaneous with what? Again, e1 is simultaneous with e2 in terms of S, and it is simultaneous with e3 in terms of S'.
>
> > Watch me show how we lose all hope of ever demonstrating that the muon's egg timer
> > and the lab clock each correspond to 0.0 usec at e4 (the disintegration of the muon in the lab).
>
> Again, the elapsed proper time of the muon from creation to collision is 2.2 usec, so if it's co-moving clock to reads zero at the collision, it read -2.2 usec at its creation. Likewise if the lab clock reads zero at the collision, it must read -D/v at event e2, and -D/(vg^2) at event e3. This was all covered (twice) up above.

Legion, do you understand what you are doing? Do you even understand the fallacious style of argumentation that you are using? Here is your *argument*

1) You make the claim to this forum that the Theory of Special Relativity is true.
2) Then you write down the Theory of Special Relativity.
3) After this you reach the conclusion that the Theory of Special Relativity is true.

In order to be scientific, Legion, a theory must be a) falsifiable, and b) must make predictions.
I have provided a specific experiment along the lines of Smith-Frisch, to test the predictions made by SR. First apply the theory of SR to the numbers I have provided to obtain a result. Then I will apply the theory of SR to the same number to arrive at an equally valid result, but completely at odds with the first result. This will demonstrate the inconsistency of SR and thereby falsify it. That is my program here.

Re: Writing the History of a Spacetime Event

<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:5f0b:0:b0:3e1:3cc8:98b0 with SMTP id x11-20020ac85f0b000000b003e13cc898b0mr72093qta.3.1683252490695;
Thu, 04 May 2023 19:08:10 -0700 (PDT)
X-Received: by 2002:a05:620a:458a:b0:74d:fd99:ab3e with SMTP id
bp10-20020a05620a458a00b0074dfd99ab3emr649449qkb.9.1683252490507; Thu, 04 May
2023 19:08:10 -0700 (PDT)
Path: i2pn2.org!i2pn.org!news.neodome.net!feeder1.feed.usenet.farm!feed.usenet.farm!peer03.ams4!peer.am4.highwinds-media.com!peer01.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 4 May 2023 19:08:10 -0700 (PDT)
In-Reply-To: <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:80b8:87a7:2408:8b87;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:80b8:87a7:2408:8b87
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Fri, 05 May 2023 02:08:10 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4233
 by: Trevor Lange - Fri, 5 May 2023 02:08 UTC

On Thursday, May 4, 2023 at 6:06:40 PM UTC-7, patdolan wrote:
> > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.
> >
> > In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2.. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v at event e2, and it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.
> >
> > > Watch me show how we lose all hope of ever demonstrating that the muon's egg timer
> > > and the lab clock each correspond to 0.0 usec at e4 (the disintegration of the muon in the lab).
> >
> > Again, the elapsed proper time of the muon from creation to collision is 2.2 usec, so if it's co-moving clock to reads zero at the collision, it read -2.2 usec at its creation. Likewise if the lab clock reads zero at the collision, it must read -D/v at event e2, and -D/(vg^2) at event e3. This was all covered (twice) up above.
>
> I have provided a specific experiment to test the predictions made by SR. First
> apply the theory of SR to the numbers I have provided to obtain a result.

Done. See above, i.e., the lab clock reads -4.4 usec at e2 and -1.1 usec at e3. We covered this before.

> Then I will...

Rather than constantly making grand announcements about what you are about to do, it would be more interesting if you would actually do it.

Re: Writing the History of a Spacetime Event

<9b73dae6-bde1-49bb-857f-0b5d3d81d186n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:1a27:b0:3ef:3af7:1c40 with SMTP id f39-20020a05622a1a2700b003ef3af71c40mr93067qtb.3.1683255096879;
Thu, 04 May 2023 19:51:36 -0700 (PDT)
X-Received: by 2002:ad4:4d51:0:b0:618:ab80:7619 with SMTP id
m17-20020ad44d51000000b00618ab807619mr14616qvm.3.1683255096697; Thu, 04 May
2023 19:51:36 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!1.us.feeder.erje.net!feeder.erje.net!border-1.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Thu, 4 May 2023 19:51:36 -0700 (PDT)
In-Reply-To: <e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:34ad:b2ba:f0e6:b659;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:34ad:b2ba:f0e6:b659
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <9b73dae6-bde1-49bb-857f-0b5d3d81d186n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Fri, 05 May 2023 02:51:36 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 49
 by: patdolan - Fri, 5 May 2023 02:51 UTC

On Thursday, May 4, 2023 at 7:08:11 PM UTC-7, Trevor Lange wrote:
> On Thursday, May 4, 2023 at 6:06:40 PM UTC-7, patdolan wrote:
> > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.
> > >
> > > In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v at event e2, and it reads -D/(vg^2) at event e3. The elapsed proper time in the lab between e2 and e3 is Dv.
> > >
> > > > Watch me show how we lose all hope of ever demonstrating that the muon's egg timer
> > > > and the lab clock each correspond to 0.0 usec at e4 (the disintegration of the muon in the lab).
> > >
> > > Again, the elapsed proper time of the muon from creation to collision is 2.2 usec, so if it's co-moving clock to reads zero at the collision, it read -2.2 usec at its creation. Likewise if the lab clock reads zero at the collision, it must read -D/v at event e2, and -D/(vg^2) at event e3. This was all covered (twice) up above.
> >
> > I have provided a specific experiment to test the predictions made by SR. First
> > apply the theory of SR to the numbers I have provided to obtain a result.
> Done. See above, i.e., the lab clock reads -4.4 usec at e2 and -1.1 usec at e3. We covered this before.
>
> > Then I will...
>
> Rather than constantly making grand announcements about what you are about to do, it would be more interesting if you would actually do it.
I'm watching the Kraken game. I'll write something tomorrow. Channel 99 CBUT from Vancouver, Ross.

Re: Writing the History of a Spacetime Event

<6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:6214:1911:b0:61b:5d80:384a with SMTP id er17-20020a056214191100b0061b5d80384amr999961qvb.0.1683399492046;
Sat, 06 May 2023 11:58:12 -0700 (PDT)
X-Received: by 2002:a05:620a:2802:b0:74e:2de8:c802 with SMTP id
f2-20020a05620a280200b0074e2de8c802mr1883752qkp.9.1683399491902; Sat, 06 May
2023 11:58:11 -0700 (PDT)
Path: i2pn2.org!i2pn.org!news.1d4.us!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 11:58:11 -0700 (PDT)
In-Reply-To: <e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:9cae:9147:1da:aeb1;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:9cae:9147:1da:aeb1
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sat, 06 May 2023 18:58:12 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4523
 by: patdolan - Sat, 6 May 2023 18:58 UTC

On Thursday, May 4, 2023 at 7:08:11 PM UTC-7, Trevor Lange wrote:
> On Thursday, May 4, 2023 at 6:06:40 PM UTC-7, patdolan wrote:
> > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.
> > >
> > > In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g.

Which is equal to 2.2v

This is the magnitude of the interval from e1 to e3. In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock read -D/v

Which is equal to -2.2g = -4.4 usec. [ okay ]

at event e2, and it reads -D/(vg^2) [ huh? ]

Which is equal to -2.2/g = -1.1 usec.

at event e3.

Question: why is there an extra gamma in the denominator at e3?

The elapsed proper time in the lab between e2 and e3 is Dv.
> > >
> > > > Watch me show how we lose all hope of ever demonstrating that the muon's egg timer
> > > > and the lab clock each correspond to 0.0 usec at e4 (the disintegration of the muon in the lab).
> > >
> > > Again, the elapsed proper time of the muon from creation to collision is 2.2 usec, so if it's co-moving clock to reads zero at the collision, it read -2.2 usec at its creation. Likewise if the lab clock reads zero at the collision, it must read -D/v at event e2, and -D/(vg^2) at event e3. This was all covered (twice) up above.
> >
> > I have provided a specific experiment to test the predictions made by SR. First
> > apply the theory of SR to the numbers I have provided to obtain a result.
> Done. See above, i.e., the lab clock reads -4.4 usec at e2 and -1.1 usec at e3. We covered this before.
>
> > Then I will...
>
> Rather than constantly making grand announcements about what you are about to do, it would be more interesting if you would actually do it.

Re: Writing the History of a Spacetime Event

<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:408:b0:3f3:8459:956c with SMTP id n8-20020a05622a040800b003f38459956cmr889045qtx.3.1683402410958;
Sat, 06 May 2023 12:46:50 -0700 (PDT)
X-Received: by 2002:a05:620a:258d:b0:74e:3f85:9a37 with SMTP id
x13-20020a05620a258d00b0074e3f859a37mr1582789qko.10.1683402410778; Sat, 06
May 2023 12:46:50 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 12:46:50 -0700 (PDT)
In-Reply-To: <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:9a5:bb7b:2284:6c85;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:9a5:bb7b:2284:6c85
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Sat, 06 May 2023 19:46:50 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3832
 by: Trevor Lange - Sat, 6 May 2023 19:46 UTC

On Saturday, May 6, 2023 at 11:58:13 AM UTC-7, patdolan wrote:
> > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> >
> > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
>
> Which is equal to 2.2v

Right! Bravo!

> > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
>
> Which is equal to -2.2g = -4.4 usec. [ okay ]

Right again! You're on fire.

> > and it reads -D/(vg^2) = -1.1 usec at event e3.
>
> Why is there an extra gamma in the denominator at e3?

It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D(vg^2) at event e3, which is simultaneous with e1 in terms of S'.

Re: Writing the History of a Spacetime Event

<3839a43b-c3d9-4a85-b21c-51d9b461fdeen@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:134a:b0:3ef:499a:dd95 with SMTP id w10-20020a05622a134a00b003ef499add95mr2029093qtk.7.1683406601223;
Sat, 06 May 2023 13:56:41 -0700 (PDT)
X-Received: by 2002:a05:622a:4c7:b0:3ef:2db1:6e59 with SMTP id
q7-20020a05622a04c700b003ef2db16e59mr2214621qtx.9.1683406601080; Sat, 06 May
2023 13:56:41 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 13:56:40 -0700 (PDT)
In-Reply-To: <a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:9cae:9147:1da:aeb1;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:9cae:9147:1da:aeb1
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3839a43b-c3d9-4a85-b21c-51d9b461fdeen@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sat, 06 May 2023 20:56:41 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 52
 by: patdolan - Sat, 6 May 2023 20:56 UTC

On Saturday, May 6, 2023 at 12:46:52 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 11:58:13 AM UTC-7, patdolan wrote:
> > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > >
> > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> >
> > Which is equal to 2.2v
> Right! Bravo!
>
> > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> >
> > Which is equal to -2.2g = -4.4 usec. [ okay ]
> Right again! You're on fire.
>
> > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> >
> > Why is there an extra gamma in the denominator at e3?
>
> It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D(vg^2) at event e3, which is simultaneous with e1 in terms of S'.

Let me write out those ( space, time ) coordinates you just gave in S:
e1: 0, 0
e2: 2.2vg, 0
e3: 2.2vg, 2.2(v^2)g
e4: 2.2vg, 2.2g

Also, do you realize that D(vg^2) = 2.2( v^2 )( g^3 )

D/v - Dv = Show me

Re: Writing the History of a Spacetime Event

<5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:598c:0:b0:3f0:abe7:24a2 with SMTP id e12-20020ac8598c000000b003f0abe724a2mr2236096qte.10.1683407364002;
Sat, 06 May 2023 14:09:24 -0700 (PDT)
X-Received: by 2002:a05:622a:19a9:b0:3f3:6708:c7ca with SMTP id
u41-20020a05622a19a900b003f36708c7camr2179929qtc.2.1683407363852; Sat, 06 May
2023 14:09:23 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer01.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 14:09:23 -0700 (PDT)
In-Reply-To: <a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:9a5:bb7b:2284:6c85;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:9a5:bb7b:2284:6c85
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Sat, 06 May 2023 21:09:23 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4251
 by: Trevor Lange - Sat, 6 May 2023 21:09 UTC

On Saturday, May 6, 2023 at 12:46:52 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 11:58:13 AM UTC-7, patdolan wrote:
> > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > >
> > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> >
> > Which is equal to 2.2v
> Right! Bravo!
>
> > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> >
> > Which is equal to -2.2g = -4.4 usec. [ okay ]
> Right again! You're on fire.
>
> > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> >
> > Why is there an extra gamma in the denominator at e3?
>
> It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D/(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D/(vg^2) at event e3, which is simultaneous with e1 in terms of S'.

Fixed the obvious typo, in agreement with what has been typed for you a hundred times before (including the very expression that you quoted).

Re: Writing the History of a Spacetime Event

<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:170e:b0:3f3:6708:c7c1 with SMTP id h14-20020a05622a170e00b003f36708c7c1mr2129868qtk.0.1683408866818;
Sat, 06 May 2023 14:34:26 -0700 (PDT)
X-Received: by 2002:a05:6214:a85:b0:61a:3ac7:11c3 with SMTP id
ev5-20020a0562140a8500b0061a3ac711c3mr1185009qvb.5.1683408866669; Sat, 06 May
2023 14:34:26 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!peer03.ams1!peer.ams1.xlned.com!news.xlned.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 14:34:26 -0700 (PDT)
In-Reply-To: <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:9cae:9147:1da:aeb1;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:9cae:9147:1da:aeb1
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sat, 06 May 2023 21:34:26 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 4533
 by: patdolan - Sat, 6 May 2023 21:34 UTC

On Saturday, May 6, 2023 at 2:09:25 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 12:46:52 PM UTC-7, Trevor Lange wrote:
> > On Saturday, May 6, 2023 at 11:58:13 AM UTC-7, patdolan wrote:
> > > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > >
> > > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4.. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > >
> > > Which is equal to 2.2v
> > Right! Bravo!
> >
> > > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> > >
> > > Which is equal to -2.2g = -4.4 usec. [ okay ]
> > Right again! You're on fire.
> >
> > > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> > >
> > > Why is there an extra gamma in the denominator at e3?
> >
> > It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D/(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D/(vg^2) at event e3, which is simultaneous with e1 in terms of S'.
>
> Fixed the obvious typo, in agreement with what has been typed for you a hundred times before (including the very expression that you quoted).

Ha! I caught you, Legion Lange. I don't give a damn about the minus sign typo.

Re: Writing the History of a Spacetime Event

<4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:4ce:b0:3f3:641b:85f with SMTP id q14-20020a05622a04ce00b003f3641b085fmr2080590qtx.10.1683409418050;
Sat, 06 May 2023 14:43:38 -0700 (PDT)
X-Received: by 2002:a05:622a:15c4:b0:3bf:b9d9:6759 with SMTP id
d4-20020a05622a15c400b003bfb9d96759mr2312049qty.8.1683409417853; Sat, 06 May
2023 14:43:37 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 14:43:37 -0700 (PDT)
In-Reply-To: <b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:9a5:bb7b:2284:6c85;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:9a5:bb7b:2284:6c85
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Sat, 06 May 2023 21:43:38 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 54
 by: Trevor Lange - Sat, 6 May 2023 21:43 UTC

On Saturday, May 6, 2023 at 2:34:28 PM UTC-7, patdolan wrote:
> On Saturday, May 6, 2023 at 2:09:25 PM UTC-7, Trevor Lange wrote:
> > On Saturday, May 6, 2023 at 12:46:52 PM UTC-7, Trevor Lange wrote:
> > > On Saturday, May 6, 2023 at 11:58:13 AM UTC-7, patdolan wrote:
> > > > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > > >
> > > > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2.. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > > >
> > > > Which is equal to 2.2v
> > > Right! Bravo!
> > >
> > > > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> > > >
> > > > Which is equal to -2.2g = -4.4 usec. [ okay ]
> > > Right again! You're on fire.
> > >
> > > > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> > > >
> > > > Why is there an extra gamma in the denominator at e3?
> > >
> > > It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D/(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D/(vg^2) at event e3, which is simultaneous with e1 in terms of S'.
> >
> > Fixed the obvious typo, in agreement with what has been typed for you a hundred times before (including the very expression that you quoted).
> Ha! I caught you, Legion Lange. I don't give a damn about the minus sign typo.

Huh? There was no minus sign typo. The typo was the missing division ( / ) symbol. So, is anything still unclear to you?

Re: Writing the History of a Spacetime Event

<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:1a20:b0:74e:4f4e:2fe2 with SMTP id bk32-20020a05620a1a2000b0074e4f4e2fe2mr1643294qkb.9.1683412122899;
Sat, 06 May 2023 15:28:42 -0700 (PDT)
X-Received: by 2002:a05:6214:2f8a:b0:5ef:4436:ef38 with SMTP id
ob10-20020a0562142f8a00b005ef4436ef38mr3203532qvb.4.1683412122712; Sat, 06
May 2023 15:28:42 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 15:28:42 -0700 (PDT)
In-Reply-To: <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:9cae:9147:1da:aeb1;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:9cae:9147:1da:aeb1
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sat, 06 May 2023 22:28:42 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 5099
 by: patdolan - Sat, 6 May 2023 22:28 UTC

On Saturday, May 6, 2023 at 2:43:38 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 2:34:28 PM UTC-7, patdolan wrote:
> > On Saturday, May 6, 2023 at 2:09:25 PM UTC-7, Trevor Lange wrote:
> > > On Saturday, May 6, 2023 at 12:46:52 PM UTC-7, Trevor Lange wrote:
> > > > On Saturday, May 6, 2023 at 11:58:13 AM UTC-7, patdolan wrote:
> > > > > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > > > >
> > > > > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > > > >
> > > > > Which is equal to 2.2v
> > > > Right! Bravo!
> > > >
> > > > > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> > > > >
> > > > > Which is equal to -2.2g = -4.4 usec. [ okay ]
> > > > Right again! You're on fire.
> > > >
> > > > > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> > > > >
> > > > > Why is there an extra gamma in the denominator at e3?
> > > >
> > > > It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D/(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D/(vg^2) at event e3, which is simultaneous with e1 in terms of S'.
> > >
> > > Fixed the obvious typo, in agreement with what has been typed for you a hundred times before (including the very expression that you quoted).
> > Ha! I caught you, Legion Lange. I don't give a damn about the minus sign typo.
> Huh? There was no minus sign typo. The typo was the missing division ( / ) symbol. So, is anything still unclear to you?

Yes. D/v - Dv = D/(vg^2) is still very unclear to me.

D/(vg^2) = 2.2 usec/2 = 1.1 usec

4.4 usec - (4.4 usec)v^2 = 1.1 usec ??

Show me!

Re: Writing the History of a Spacetime Event

<927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:410d:b0:74e:37dd:6197 with SMTP id j13-20020a05620a410d00b0074e37dd6197mr2068772qko.8.1683413089924;
Sat, 06 May 2023 15:44:49 -0700 (PDT)
X-Received: by 2002:a05:620a:3715:b0:74e:324:d6f0 with SMTP id
de21-20020a05620a371500b0074e0324d6f0mr1647037qkb.7.1683413089752; Sat, 06
May 2023 15:44:49 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!feeder1.feed.usenet.farm!feed.usenet.farm!peer03.ams4!peer.am4.highwinds-media.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 15:44:49 -0700 (PDT)
In-Reply-To: <d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:9a5:bb7b:2284:6c85;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:9a5:bb7b:2284:6c85
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Sat, 06 May 2023 22:44:49 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 5031
 by: Trevor Lange - Sat, 6 May 2023 22:44 UTC

On Saturday, May 6, 2023 at 3:28:44 PM UTC-7, patdolan wrote:
> > > > > > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > > > > >
> > > > > > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > > > > >
> > > > > > Which is equal to 2.2v
> > > > > Right! Bravo!
> > > > >
> > > > > > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> > > > > >
> > > > > > Which is equal to -2.2g = -4.4 usec. [ okay ]
> > > > > Right again! You're on fire.
> > > > >
> > > > > > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> > > > > >
> > > > > > Why is there an extra gamma in the denominator at e3?
> > > > >
> > > > > It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D/(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D/(vg^2) at event e3, which is simultaneous with e1 in terms of S'. Is anything still unclear to you?
>
> Yes. D/v - Dv = D/(vg^2) is still very unclear to me.

Well, D/v - Dv = D(1/v - v) = D((1-v^2)/v) = D/(v g^2). Remember, g=1/sqrt(1-v^2). This is just simple algebra. What part is unclear?
> D/(vg^2) = 2.2 usec/2 = 1.1 usec

Right! That's the elapsed lab time from e3 to e4, and since you stipulated the clock reads 0.0 at e4, it read -1.1 usec at e3. Likewise the lab clock reads -4.4 usec at e2. The muon clock reads -2.2 usec at e1 and 0.0 at e4. We covered all this before (several times). Is anything still unclear to you?

Re: Writing the History of a Spacetime Event

<fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:6214:911:b0:61b:5c7c:af11 with SMTP id dj17-20020a056214091100b0061b5c7caf11mr1319872qvb.7.1683427825429;
Sat, 06 May 2023 19:50:25 -0700 (PDT)
X-Received: by 2002:a05:622a:1a06:b0:3f0:a9a0:45e3 with SMTP id
f6-20020a05622a1a0600b003f0a9a045e3mr2633776qtb.12.1683427825270; Sat, 06 May
2023 19:50:25 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 19:50:24 -0700 (PDT)
In-Reply-To: <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:bda1:83e3:aa60:eff6;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:bda1:83e3:aa60:eff6
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com> <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sun, 07 May 2023 02:50:25 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 59
 by: patdolan - Sun, 7 May 2023 02:50 UTC

On Saturday, May 6, 2023 at 3:44:51 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 3:28:44 PM UTC-7, patdolan wrote:
> > > > > > > > > A muon simultaneously [sic] comes to rest [sic] and disintegrates in a laboratory scintillator on the surface of the earth just as the laboratory clock strikes 0.000 hours. The muon's trajectory was normal to the surface of the earth. The muon's velocity relative to the earth [sic] was measured to be [v=]0.867c which results in g = 2. The muon's clock showed an elapsed proper time of 2.2 microseconds between the spacetime event corresponding to its creation and the spacetime event corresponding to its disintegration in the lab scintillator.
> > > > > > > >
> > > > > > > > Letting S and S' denote standard inertial coordinate systems in which the lab and the muon in flight are at rest, respectively, four relevant events (among infinitely many) you might be interested in are the muon's creation event e1, the lab event e2 simultaneous with e1 in terms of S, the lab event e3 simultaneous with e1 in terms of S', and the collision event e4. In terms of S the height of the muon at creation is D = (2.2)(vg) where g = 1/sqrt(1-v^2). This is the magnitude of the interval from e1 to e2. In terms of S', the spatial distance between the muon and the lab at the time of the muon's creation is D/g. This is the magnitude of the interval from e1 to e3.
> > > > > > >
> > > > > > > Which is equal to 2.2v
> > > > > > Right! Bravo!
> > > > > >
> > > > > > > > In terms of S, the altitude of the muon's creation event is D, which in your example is 2.2(vg) light microseconds. In terms of S, the lab clock reads -D/v at event e2 ...
> > > > > > >
> > > > > > > Which is equal to -2.2g = -4.4 usec. [ okay ]
> > > > > > Right again! You're on fire.
> > > > > >
> > > > > > > > and it reads -D/(vg^2) = -1.1 usec at event e3.
> > > > > > >
> > > > > > > Why is there an extra gamma in the denominator at e3?
> > > > > >
> > > > > > It isn't an "extra" factor. For convenience, place the origin of S at the muon creation event, so the events e1, e2, e3, and e4 have the coordinates (0,0), (D,0), (D,Dv), and (D,D/v) respectively. So the elapsed time in the lab from e3 to e4 is D/v - Dv, which equals D/(vg^2). Thus for the clock to read 0.0 at the collision, it must read -D/(vg^2) at event e3, which is simultaneous with e1 in terms of S'. Is anything still unclear to you?
> >
> > Yes. D/v - Dv = D/(vg^2) is still very unclear to me.
> Well, D/v - Dv = D(1/v - v) = D((1-v^2)/v) = D/(v g^2). Remember, g=1/sqrt(1-v^2). This is just simple algebra. What part is unclear?
> > D/(vg^2) = 2.2 usec/2 = 1.1 usec
> Right! That's the elapsed lab time from e3 to e4, and since you stipulated the clock reads 0.0 at e4, it read -1.1 usec at e3. Likewise the lab clock reads -4.4 usec at e2. The muon clock reads -2.2 usec at e1 and 0.0 at e4.. We covered all this before (several times). Is anything still unclear to you?
At laboratory event e2, which is simultaneous with e1 in the lab's frame, the scientist start's the lab's one and only stopwatch.

At laboratory event e3, which is simultaneous with e1 in the muon's frame, the scientist starts the lab's one and only stopwatch.

What does that stopwatch read at the muon's disintegration at e4?

Re: Writing the History of a Spacetime Event

<79e3d358-35fc-434f-841b-54868e6b87c8n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:622a:170e:b0:3f3:6708:c7c1 with SMTP id h14-20020a05622a170e00b003f36708c7c1mr2430948qtk.0.1683428856546;
Sat, 06 May 2023 20:07:36 -0700 (PDT)
X-Received: by 2002:a05:620a:470c:b0:74e:1ca7:3716 with SMTP id
bs12-20020a05620a470c00b0074e1ca73716mr2436766qkb.6.1683428856401; Sat, 06
May 2023 20:07:36 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 20:07:36 -0700 (PDT)
In-Reply-To: <fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:9a5:bb7b:2284:6c85;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:9a5:bb7b:2284:6c85
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com> <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
<fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <79e3d358-35fc-434f-841b-54868e6b87c8n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Sun, 07 May 2023 03:07:36 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 21
 by: Trevor Lange - Sun, 7 May 2023 03:07 UTC

On Saturday, May 6, 2023 at 7:50:26 PM UTC-7, patdolan wrote:
> At laboratory event e2, which is simultaneous with e1 in the lab's frame,
> the scientist start's the lab's one and only stopwatch.

So, at e2 the lab guy initializes his stopwatch to 0.0 and lets it run.

> At laboratory event e3, which is simultaneous with e1 in the muon's frame,
> the scientist starts the lab's one and only stopwatch.

So, by the time he reaches e3, the stopwatch will have ticked off 3.3 usec, and you are saying at this point he re-initializes the stop watch to 0.0 and lets it run.
> What does that stopwatch read at the muon's disintegration at e4?

It reads 1.1 usec, consistent with the fact that the elapsed proper time from e2 to e3 is 3.3 usec, and the elapsed proper time from e3 to e4 is 1.1 usec, and the total elapsed proper time from e2 to e4 is 4.4 usec. Also, the elapsed proper time on the muon's clock from e1 to e4 is 2.2 usec. Is anything still unclear to you?

Re: Writing the History of a Spacetime Event

<22668a7c-5356-4ad3-a894-939ec4a08ae8n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:a05:620a:414a:b0:74d:f7af:b238 with SMTP id k10-20020a05620a414a00b0074df7afb238mr2386584qko.14.1683429587238;
Sat, 06 May 2023 20:19:47 -0700 (PDT)
X-Received: by 2002:a05:6214:1774:b0:61b:68e0:53d6 with SMTP id
et20-20020a056214177400b0061b68e053d6mr1367056qvb.1.1683429587102; Sat, 06
May 2023 20:19:47 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!news.misty.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 20:19:46 -0700 (PDT)
In-Reply-To: <79e3d358-35fc-434f-841b-54868e6b87c8n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:bda1:83e3:aa60:eff6;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:bda1:83e3:aa60:eff6
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com> <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
<fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com> <79e3d358-35fc-434f-841b-54868e6b87c8n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <22668a7c-5356-4ad3-a894-939ec4a08ae8n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sun, 07 May 2023 03:19:47 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 23
 by: patdolan - Sun, 7 May 2023 03:19 UTC

On Saturday, May 6, 2023 at 8:07:37 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 7:50:26 PM UTC-7, patdolan wrote:
> > At laboratory event e2, which is simultaneous with e1 in the lab's frame,
> > the scientist start's the lab's one and only stopwatch.
> So, at e2 the lab guy initializes his stopwatch to 0.0 and lets it run.
> > At laboratory event e3, which is simultaneous with e1 in the muon's frame,
> > the scientist starts the lab's one and only stopwatch.
> So, by the time he reaches e3, the stopwatch will have ticked off 3.3 usec, and you are saying at this point he re-initializes the stop watch to 0.0 and lets it run.
> > What does that stopwatch read at the muon's disintegration at e4?
> It reads 1.1 usec, consistent with the fact that the elapsed proper time from e2 to e3 is 3.3 usec, and the elapsed proper time from e3 to e4 is 1.1 usec, and the total elapsed proper time from e2 to e4 is 4.4 usec. Also, the elapsed proper time on the muon's clock from e1 to e4 is 2.2 usec. Is anything still unclear to you?

Yes Legion. Teach me the "many worlds" interpretation of SR which you have just propounded. This is the weakness of your "four event formula" that Roberts, Bodkin and Paul Anderson wouldn't even take the time to study. But I DID take the time. And now I present you with it's flaw. Is this unclear to you?

Re: Writing the History of a Spacetime Event

<8c906f12-6576-4daf-aefa-c045f7c4da06n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:584d:0:b0:3e9:9419:b153 with SMTP id h13-20020ac8584d000000b003e99419b153mr2560181qth.0.1683430377845;
Sat, 06 May 2023 20:32:57 -0700 (PDT)
X-Received: by 2002:a05:620a:4405:b0:757:6d26:55fe with SMTP id
v5-20020a05620a440500b007576d2655femr1198882qkp.12.1683430377657; Sat, 06 May
2023 20:32:57 -0700 (PDT)
Path: i2pn2.org!i2pn.org!usenet.blueworldhosting.com!diablo1.usenet.blueworldhosting.com!peer03.iad!feed-me.highwinds-media.com!news.highwinds-media.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 20:32:57 -0700 (PDT)
In-Reply-To: <22668a7c-5356-4ad3-a894-939ec4a08ae8n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:601:1700:7df0:9a5:bb7b:2284:6c85;
posting-account=B2MNBQoAAADtgq_pZTEECSkLIDJGrDSJ
NNTP-Posting-Host: 2601:601:1700:7df0:9a5:bb7b:2284:6c85
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com> <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
<fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com> <79e3d358-35fc-434f-841b-54868e6b87c8n@googlegroups.com>
<22668a7c-5356-4ad3-a894-939ec4a08ae8n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <8c906f12-6576-4daf-aefa-c045f7c4da06n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: trevorla...@gmail.com (Trevor Lange)
Injection-Date: Sun, 07 May 2023 03:32:57 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Received-Bytes: 3878
 by: Trevor Lange - Sun, 7 May 2023 03:32 UTC

On Saturday, May 6, 2023 at 8:19:48 PM UTC-7, patdolan wrote:
> > > At laboratory event e2, which is simultaneous with e1 in the lab's frame,
> > > the scientist start's the lab's one and only stopwatch.
> > So, at e2 the lab guy initializes his stopwatch to 0.0 and lets it run.
> > > At laboratory event e3, which is simultaneous with e1 in the muon's frame,
> > > the scientist starts the lab's one and only stopwatch.
> > So, by the time he reaches e3, the stopwatch will have ticked off 3.3 usec, and you are saying at this point he re-initializes the stop watch to 0..0 and lets it run.
> > > What does that stopwatch read at the muon's disintegration at e4?
> > It reads 1.1 usec, consistent with the fact that the elapsed proper time from e2 to e3 is 3.3 usec, and the elapsed proper time from e3 to e4 is 1..1 usec, and the total elapsed proper time from e2 to e4 is 4.4 usec. Also, the elapsed proper time on the muon's clock from e1 to e4 is 2.2 usec. Is anything still unclear to you?
>
> Yes. Please teach me the "many worlds" interpretation of SR which you have just propounded.

There is no "many worlds" interpretation of special relativity, and I obviously have not propounded any such thing. What specifically is unclear to you about the spatio-temporal relations in the above scenario?

> And now I present you with it's flaw: [then.... crickets]

Apparently your message was truncated at this crucial point, just as you were about to point out a flaw in the simple and clear explanation of the scenario. Could you try posting again, and this time be sure to actually present the flaw?

[I know, I know... you'll get to it tomorrow... as always. yawn]

Re: Writing the History of a Spacetime Event

<3cf33964-efd2-499a-b3d4-9e0749e28ce6n@googlegroups.com>

  copy mid

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

  copy link   Newsgroups: sci.physics.relativity
X-Received: by 2002:ac8:5b0a:0:b0:3f3:7a7a:7943 with SMTP id m10-20020ac85b0a000000b003f37a7a7943mr2552658qtw.5.1683431685593;
Sat, 06 May 2023 20:54:45 -0700 (PDT)
X-Received: by 2002:a05:622a:1814:b0:3f0:a7ba:74a with SMTP id
t20-20020a05622a181400b003f0a7ba074amr2651643qtc.4.1683431685355; Sat, 06 May
2023 20:54:45 -0700 (PDT)
Path: i2pn2.org!i2pn.org!weretis.net!feeder6.news.weretis.net!1.us.feeder.erje.net!feeder.erje.net!border-1.nntp.ord.giganews.com!border-2.nntp.ord.giganews.com!nntp.giganews.com!news-out.google.com!nntp.google.com!postnews.google.com!google-groups.googlegroups.com!not-for-mail
Newsgroups: sci.physics.relativity
Date: Sat, 6 May 2023 20:54:45 -0700 (PDT)
In-Reply-To: <8c906f12-6576-4daf-aefa-c045f7c4da06n@googlegroups.com>
Injection-Info: google-groups.googlegroups.com; posting-host=2601:602:9b00:7c40:bda1:83e3:aa60:eff6;
posting-account=9sfziQoAAAD_UD5NP4mC4DjcYPHqoIUc
NNTP-Posting-Host: 2601:602:9b00:7c40:bda1:83e3:aa60:eff6
References: <774006aa-5668-4e27-8fe4-eccabc9fa6f7n@googlegroups.com>
<e5b7df3f-011f-4ccf-a8c4-94b26820c445n@googlegroups.com> <229ab722-facd-4639-b3c0-fd8e6316d51bn@googlegroups.com>
<6ef34e01-091f-4cba-8cea-9905d32f3f23n@googlegroups.com> <a34ea6f4-b57b-4c6b-8292-29349d55de9an@googlegroups.com>
<e3fa0968-90db-4b76-86ec-49e4b095c027n@googlegroups.com> <6ab8f969-9b34-44b6-a126-798f0562dc79n@googlegroups.com>
<a3a8e521-2ba9-4c73-96fb-6ee3eb098a34n@googlegroups.com> <5485754a-49d5-421c-8afb-2b6f09695959n@googlegroups.com>
<b70a672f-7f7c-4a12-8567-5175c2fefff4n@googlegroups.com> <4da71acc-9d77-4442-a2aa-832c9e3cda3an@googlegroups.com>
<d4e41c83-e1f3-4ca5-82c7-fd4e6e2576d5n@googlegroups.com> <927ebcb2-a34e-4bae-ae3f-eb4312930022n@googlegroups.com>
<fd7d228b-ed81-4993-8462-7c715f328330n@googlegroups.com> <79e3d358-35fc-434f-841b-54868e6b87c8n@googlegroups.com>
<22668a7c-5356-4ad3-a894-939ec4a08ae8n@googlegroups.com> <8c906f12-6576-4daf-aefa-c045f7c4da06n@googlegroups.com>
User-Agent: G2/1.0
MIME-Version: 1.0
Message-ID: <3cf33964-efd2-499a-b3d4-9e0749e28ce6n@googlegroups.com>
Subject: Re: Writing the History of a Spacetime Event
From: patdo...@comcast.net (patdolan)
Injection-Date: Sun, 07 May 2023 03:54:45 +0000
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Lines: 41
 by: patdolan - Sun, 7 May 2023 03:54 UTC

On Saturday, May 6, 2023 at 8:32:58 PM UTC-7, Trevor Lange wrote:
> On Saturday, May 6, 2023 at 8:19:48 PM UTC-7, patdolan wrote:
> > > > At laboratory event e2, which is simultaneous with e1 in the lab's frame,
> > > > the scientist start's the lab's one and only stopwatch.
> > > So, at e2 the lab guy initializes his stopwatch to 0.0 and lets it run.
> > > > At laboratory event e3, which is simultaneous with e1 in the muon's frame,
> > > > the scientist starts the lab's one and only stopwatch.
> > > So, by the time he reaches e3, the stopwatch will have ticked off 3.3 usec, and you are saying at this point he re-initializes the stop watch to 0.0 and lets it run.
> > > > What does that stopwatch read at the muon's disintegration at e4?
> > > It reads 1.1 usec, consistent with the fact that the elapsed proper time from e2 to e3 is 3.3 usec, and the elapsed proper time from e3 to e4 is 1.1 usec, and the total elapsed proper time from e2 to e4 is 4.4 usec. Also, the elapsed proper time on the muon's clock from e1 to e4 is 2.2 usec. Is anything still unclear to you?
> >
> > Yes. Please teach me the "many worlds" interpretation of SR which you have just propounded.
>
> There is no "many worlds" interpretation of special relativity, and I obviously have not propounded any such thing. What specifically is unclear to you about the spatio-temporal relations in the above scenario?
>
> > And now I present you with it's flaw: [then.... crickets]
>
> Apparently your message was truncated at this crucial point, just as you were about to point out a flaw in the simple and clear explanation of the scenario. Could you try posting again, and this time be sure to actually present the flaw?
>
> [I know, I know... you'll get to it tomorrow... as always. yawn]
Rest up Legion. You'll have a big day ahead of you Monday...maybe Sunday night. I'm headed to the Hen in Green Lake to hear music that is too old played by a band that is too young. Come up from Renton if you like. It will only take you 20 minutes this time of night. You will recognize me instantly. You too Ross. I'll buy you guys a drink. But nothing fancy. I only buy well.

Pages:123
server_pubkey.txt

rocksolid light 0.9.8
clearnet tor