Re: Why TWLS= 0 <> OWLS in any ONE Frame.
- From: "JanPB" <filmart@xxxxxxxxx>
- Date: 29 Jan 2006 18:31:29 -0800
Hexenmeister wrote:
> "JanPB" <filmart@xxxxxxxxx> wrote in message
> news:1138582423.455005.238750@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
> > Henri Wilson wrote:
> >> On 28 Jan 2006 22:27:58 -0800, "JanPB" <filmart@xxxxxxxxx> wrote:
> >>
> >> >Now imagine A and B and the rod accelerate a bit (fire rocket engines
> >> >for a minute). After the acceleration is turned off again, will their
> >> >clocks be still in sync (according to the procedure above)?
> >>
> >> They should be, but if they were physically affected by the acceleration
> >> they
> >> can easily be resynched with the above method.
> >
> > Well, it's not an absolute sync then.
> >
> > --
> > Jan Bielawski
>
> Yep.
Nop.
> [300,000 + (-300,000)]/2 = 300,000/1 -- Wilson and Einstein.
He said "They should be, but if they were physically affected by the
acceleration they can easily be resynched" - which means they could go
out of sync.
--
Jan Bielawski
.
- Follow-Ups:
- Re: Why TWLS= 0 <> OWLS in any ONE Frame.
- From: Hexenmeister
- Re: Why TWLS= 0 <> OWLS in any ONE Frame.
- References:
- Re: Why TWLS=OWLS=c in any ONE Frame.
- From: JanPB
- Re: Why TWLS=OWLS=c in any ONE Frame.
- From: JanPB
- Re: Why TWLS= 0 <> OWLS in any ONE Frame.
- From: Hexenmeister
- Re: Why TWLS=OWLS=c in any ONE Frame.
- Prev by Date: Re: What is LET?
- Next by Date: Re: What is LET?
- Previous by thread: Re: Why TWLS= 0 <> OWLS in any ONE Frame.
- Next by thread: Re: Why TWLS= 0 <> OWLS in any ONE Frame.
- Index(es):
Relevant Pages
|
|