• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

The Fly Within

Metryq

Fleet Captain
Fleet Captain
Upon reviewing Cronenberg's 1986 "remake" of The Fly, I realized there is more to the perennial discussion of how the Star Trek transporter works than is dreamt of in our philosophy. The 1958 version followed the original story very closely, including the "disappearance" of the cat to wander somewhere in the ether like a ghost. The matter transmitter was likened to TV and radio, and produced "magical" end results, such as the radical re-scaling of body parts between the different subjects—and having them remain viable when spliced in this way. (And Asimov did his best to correct the sins of the movie script when he novelized Fantastic Voyage.)

So, one of the things the 1986 movie did was "correct" the physics a bit by catering to our worldview and biases. That is, we view the world as a mechanical composite of atoms, and the remake added in a computer to analyze and buffer the state of each of these particles. The transformation into a fly also invoked another information buffer known as DNA, thus making the scenario more "credible." Copy the state of each "switch" from start to finish, and you have a teleporter!

Unfortunately, reality threw us curve balls in the form of quantum mechanics, epigenetic code, and artificial "intelligence." Quantum mechanics as a model isn't perfect, but is the currently accepted form of interpreting the bizarre behaviors observed in the atomic and sub-atomic realm. In short, it ain't the predictable, cause-and-effect billiard ball world imagined by earlier "natural philosophers." Nor is DNA the rigid and predictable code that computer binary is. Exact clones can look very different from each other, and have radically different behaviors (like CC the cat). This led to the discovery of the "epigenetic code," a vast repository of if-then statements that can alter a viable and existing organism—and leave effects on progeny for generations. I guess all that "junk" code ain't junk. But where did all that information come from?

Then there's the matter of AI (artificial intelligence). What we have today is basically pattern recognition, not self-awareness. The vaunted "Turing test" does not test the machine for self-awareness. Rather, it tests the gullibility of humans to distinguish another sentience vs a simulation. Some of the simulations are very good, although some experts deny that the unpredictable and creative behaviors of living creatures can ever emerge from the rigid, binary calculations of computers as they currently are. Something more is needed, something quantum mechanical and epigenetic.

I, Robot "Ghosts in the Machine"
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

The materialistic worldview constrains our science. In the 1986 The Fly the computer turned its first living subject (a baboon) "inside out" because it did not "understand" the poetry of life. (The scene was spoofed in Galaxy Quest.) Simply copying the state of particles from transmitter to receiver failed to reproduce the baboon because there was "more to life" than the mechanical worldview. So, the inventor set about teaching the computer the needed poetry—only to have it backfire on him when the computer got "confused" by two life-forms in the transmitter, and resolved the dilemma by fusing them at the molecular-genetic level. (See James P. Hogan's excellent novel The Two Faces of Tomorrow where scientists are confronted by "thinking" machines that nevertheless do not have "judgment.") In the Trek episode "The Enemy Within" the transporter was in a similarly confused state and produced a Jekyll and Hyde Kirk in the process.

It may be a long while before we understand how sentience ties in to matter, and if that sentience can be "teleported" with its matter.
 
So, one of the things the 1986 movie did was "correct" the physics a bit by catering to our worldview and biases. That is, we view the world as a mechanical composite of atoms, and the remake added in a computer to analyze and buffer the state of each of these particles. The transformation into a fly also invoked another information buffer known as DNA, thus making the scenario more "credible." Copy the state of each "switch" from start to finish, and you have a teleporter!
When Seth Brundle's 1980s computer goes about noting the state of atomic fly particles, there might be yet another "information buffer" issue coming his way: the accuracy of floating point operations.

I think most of us assume that computers are perfectly accurate at arithmetic. Nope. I just ran into this video:
To view this content we will need your consent to set third party cookies.
For more detailed information, see our cookies page.

Turns out, trouble starts to brew when a number has too many zeroes after the decimal point. Different computers gave different answers for the math in those days!

NEC chips would round off "subnormals" to zero, but Intel invented a way to get tough on these tiny numbers— but doing so destroyed CPU performance on certain functions such as audio fading. And possibly teleporting.

The industry adopted the IEEE 754 standard to get everybody's machines to compute the same answers, but they did so in 1985, and it's not clear that Brundle's hardware was that new. Could be a problem; I'm not getting in that thing until I know how the FLOPs are being computed.
 
(Forgive me for posting twice in a row.)
the accuracy of floating point operations.
I ran into this situation in another field: 3D animation rendering. When your projects become big enough, you may resort to a "render farm" where more than one machine is employed to render the frames of your animation. If you are using any "particle effects," you may run into snags with a render farm due to different processors, or even the same processor "rounding" numbers slightly differently.

A particle effect might be smoke, or water, or a horde of Starship Trooper bugs. The smoke was not rendered smoke particle by smoke particle, but in "cotton balls" textured to look like smoke. In a vast crowd, one did not see the individual balls/particles, but a roiling cloud of smoke. To avoid the problems of multi-machine rendering, you would "bake" the particle effect before sending the file to each machine. The "baked" file nailed down the position of each ball/particle, and each machine did the grunt work of rendering the texture. Without baking, the smoke would randomly twitch from the different particle positions.

And this brings up another sci-fi trope: the so-called butterfly effect, which is not a concern in the physical world, but only in computers. It cropped up when a simulation ran from, say, frames 1 through 200. Unfortunately, the sim had to be interrupted, but was picked up again starting with the numbers calculated for frame 150. From that point forward, there was greater and greater divergence from frame 150 up to 200 already calculated. But if the sim was re-run all the way from the beginning, all the frames remained the same! Oh, my gosh! Time travelers and dinosaurs, and...

Not so fast. The reason for the divergence was the rounding of numbers between those recorded and those in RAM and CPU. So, this "butterfly effect" only happened in the artificial and arbitrary world of computing. There is no way to test it in reality (quantum effects), nor is it known if "time travel" is even possible. Another flaw with the concept in time travel stories is that it treats tiny effects (like a butterfly flapping its wings in China) with the major divergence of a slightly off-target ballistic (raining in San Francisco). Other, larger effects would surely overwhelm the flapping butterfly. For example, if you pushed your finger into the edge of a river, would you expect an entire row of flowing water droplets all the way across the river to be displaced, or only a local displacement of swirls around your finger?

("A Sound of Thunder" also invokes numerous paradoxes, which cannot logically happen. Since no one has—or can—time travel, we must fall back on logic. Eliminate that, and you are writing fantasy, not sci-fi.)
 
Star Fleet should have had the inverter from “The High Ground.”


Finn should have THE FLY type transporter tech…each use messing him up a bit more—VHS copy style.

Star Trek transporter’s have have previous copy-plans, but I always guessed there was a cascade where it didn’t quite have to re-build you…more like “pouring” a still-connected chain out of a container…or something
 
I always preferred Andre Delambre's Transportation experiment and the result. It was definitely more emotional and exciting. Plus the terrifying ending remained with me for years.
I always wondered why McCoy had such a grievance against the transporter unless it was a recently discovered technology but as we learnt in The Menagerie it was around at least two decades before.
JB
 
Andre worked with metric, but was forced to use some English components. And he didn't do the conversions right. It became the fly in the displacement.
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top