From Stuart Presnell · 1996-04-06 23:21 · #65456 in HAM
Hello Thomas! 27 Mar 96 19:02, Thomas Morley wrote to Andy Smith: AS>>>> Episode: Cause and Effect. TM>>> Here goes: They were wrong. The other ship, the Bozeman, TM>>> had not been in the loop for 80 years. So where /had/ they been for the rest of the intervening time? TM> Well, they couldn't have been, as the loop didn't begin until TM> Data 'first' made the mistake of using the tractor beam (or was TM> it the shuttle bay?), thus causing the explosion. Ha, you fool! :) You're thinking in terms of linear cause and effect! The title of the episode is a clue - the whole point is the the effect can precede the cause. You are reasoning that they can't have been trapped in the loop before the explosion was set off. By since this was a temporal anomaly, the cause (ie the explosion) can come after the effect (the Enterprise being trapped in the time loop). See? TM> (We know that the explosion caused the loop, because they got out of it by TM> preventing the explosion.) Does that make sense? Seems to make pretty good sense. Now, to explain the discrepancy between the two times: a) The Bozeman had been through the loop more often than the Enterprise. This seems imposible, since after each loop the two ships meet and collide - so surely each one goes around the same nmumber of times? But what if it is the /same/ Enterprise the Bozeman meets on several occasions? So the Enterprise may have met several incarnations of the Bozeman all at once; if the "different" Bozemans were identical (since they were exact repeats of each other), they might be considered to be the same thing... I'll admit, this explanation seems a little hootchie. b) Each loop of the Bozeman lasted longer than a loop of the Enterprise. Although it was the same Cause acting on each, they might have suffered different Effects, and so the Bozeman might have been in a longer time loop than the Enty. If the figures are correct, the Bozeman's loop would be about 1800 times as long (in duration) as the Enty's. TM>>> Just be glad you didn't ask for my explanation of the error TM>>> in Brothers.... AS>> Go on then..... [ <cut> Data says one thing but the computer displays another ] So what's /your/ explanation for it? Perhaps an inbuilt system in the computer to throw up random errors in the display to throw off anyone trying to read the code over your shoulder? :) SmP --- GEcho 1.00 * Origin: SmP's Point off Pacific Lightning BBS (2:440/7.46)