Daystrom Institute
Welcome to Daystrom Institute!
Serious, in-depth discussion about Star Trek from both in-universe and real world perspectives.
Read more about how to comment at Daystrom.
Rules
1. Explain your reasoning
All threads and comments submitted to the Daystrom Institute must contain an explanation of the reasoning put forth.
2. No whinging, jokes, memes, and other shallow content.
This entire community has a “serious tag” on it. Shitposts are encouraged in Risa.
3. Be diplomatic.
Participate in a courteous, objective, and open-minded fashion. Be nice to other posters and the people who make Star Trek. Disagree respectfully and don’t gatekeep.
4. Assume good faith.
Assume good faith. Give other posters the benefit of the doubt, but report them if you genuinely believe they are trolling. Don’t whine about “politics.”
5. Tag spoilers.
Historically Daystrom has not had a spoiler policy, so you may encounter untagged spoilers here. Ultimately, avoiding online discussion until you are caught up is the only certain way to avoid spoilers.
6. Stay on-topic.
Threads must discuss Star Trek. Comments must discuss the topic raised in the original post.
Episode Guides
The /r/DaystromInstitute wiki held a number of popular Star Trek watch guides. We have rehosted them here:
- Kraetos’ guide to Star Trek (the original series)
- Algernon_Asimov’s guide to Star Trek: The Animated Series
- Algernon_Asimov’s guide to Star Trek: The Next Generation
- Algernon_Asimov’s guide to Star Trek: Deep Space Nine
- Darth_Rasputin32898’s guide to Star Trek: Deep Space Nine
- OpticalData’s guide to Star Trek: Voyager
- petrus4’s guide to Star Trek: Voyager
view the rest of the comments
Whats the difference between a transporter and a replicator? Once you've gotten the pattern of a tomato why can't you just keep copying it? Presumably a human is too complicated to do that regularly but why not a tomato?
I mean, on a molecular level there is no difference. I feel like they even did the whole ship of Theseus thing several times. And the obvious one is the 2nd Riker. Enterprise (the series, not the ship) saw the addition of transporters to starships and they talked about it a lot in that episode. Bones in the original refused to use them because he understood the science of it and knew people were essentially being killed and reassembled every time they were transported.
I always got the impressions that people who said non-replicated food tasted better were either deluding themselves or that extra flavor they attribute to the food is like, non food things in it. Leftover dirt, mold starting to grow.... Kind of like how completely filtered water is tasteless when the minerals and other fine particulates are removed. Transporters, as a side effect of how they work, remove illnesses from the body (Except when it needs to not for plot reasons. And don't get me started on the billions of bacteria that exist in our body all the time that are necessary for life that wouldn't count as "you"). So presumably, they would remove all those tiny things in food if transported, and obviously wouldn't create them in the first place if replicated.
That's something I hadn't considered about replicated food. As a gardener, I can attest that the dirt it's grown in can have a pretty big impact on taste. It could be that.
Could also be, like, you order your replicated tomato, and they're giving you Tomato variety number 7, as is standard for replicators, and you just don't care for that variety. Kinda like how banana candy doesn't taste like bananas, because it actually tastes like a variety of banana you can't get anymore, so no one thinks it tastes real anymore.
Doctor McCoy used the transporter very frequently with minimal complaining; the only complaint I can recall is from TMP and followed a horrific and unexpected transporter accident.
As for transporters in Enterprise, two things are especially noteworthy: one, they explicitly refuted the idea that the transporter creates a "some sort of weird copy" of the person or object transported, and two, those human-safe transporters were contemporary with very primitive replicator equivalents called protein resequencers. Clearly transporters aren't building humans atom-by-atom from data alone if they can't figure out how to do more than resequence protein molecules in any other context.
Transporters don't do anything to affect the matter they are transporting unless explicitly intended to: by the 24th century they are programmed to filter out recognizeable pathogens, and can be used to deactivate weapons or occasionally monkey with the genes of a person in mid-transport, but things routinely pass through the transporter without issue which are either totally unknown or explicitly non-replicatable. None of this makes sense if the sequence is scan -> destroy -> rebuild, but makes total sense if the transporter is shifting the transportee into subspace (with some tweaks to allow them to exist there) and then back out of subspace at the destination.
Thomas Riker (and now William Boimler) is the one big exception. Both occured under a very specific and extremely rare weather condition, and the first time this happened the Chief Engineer on the flagship of the Enterprise was shocked that such a thing was even possible. I'm much more inclined to believe that the "transporter duplicates" are actually the result of the phenomenon that duplicated Voyager in Deadlock, not the transporter actually constructing two people from the pattern and matter of only one.
@Lem453 There are cargo transporters and people transporters. The people transporters are more faithful. The replicators are more like cargo transporters. See "Heisenberg Compensator" https://memory-alpha.fandom.com/wiki/Heisenberg_compensator
A transporter is a device which takes matter, shifts it into subspace, and can do some manipulation of that matter in the process, but can't reconstruct it arbitrary. Once the transported object has been rematerialized, all the transporter has left is a record of what that matter was at a far lesser precision than what would be needed to replicate it.
A replicator is a transporter designed to shift inert matter into subspace and modify it extensively from that state. A typical replicator is less precise than a transporter and is simultaneously limited by the complexity of its recipes. It cannot produce functional living things, for example.
Transporters and replicators are frequently referred to as matter-energy conversion devices. This is technically true but somewhat deceptive. It's also a common misconception that a transporter is an advanced replicator, instead of the other way round, but we know this isn't true: a safe-for-humans Transporter was invented and used in the 22nd century, while the contemporary replicator equivalents were primitive protein resequencers.
Haven't they had multiple episodes where something is in the 'buffer' of the ship? What is the buffer? Why can't you just copy the buffer and put whatever you want into it?
First off, it's clear that the metaphor the writers initially had in mind was a computer storing data. The TNG tech manual is just vague enough to be ambiguous on this point, but very heavily implies a "scan and save a pattern -> destroy the original -> rebuild from the pattern" process. Terminology like "pattern buffer" no doubt comes out of that conception.
It's also clear that by the end of 90s Trek at least some people with decision making power felt it was really important to explicitly shoot down a lot of the "kill and clone machine" theories about how transporters work, which is why Enterprise in particular is full of counter-evidence. Of course, TNG Realm of Fear was clearly not written by someone with "kill and clone" in mind, and stands as another very strong bit of evidence against that theory. The conflicting intentions make things confusing, but they are not irreconcilable.
My preferred explanation is as follows: When they shift something into subspace, they still need to keep an accurate track of exactly where in subspace everything is (the "pattern"), in addition to preventing whatever extradimensional subspace interference whosamawhatsit from damaging the matter itself. (If you're familiar with computer programming, the pattern is functionally a huge set of "pointers", not pointing to a specific piece of computer memory, but a specific point within the non-euclidian topology of subspace.) This pattern is stored in the "pattern buffer", a computer memory storage unit with an extremely high capacity but which only retains data for a limited time. The transporter then uses this pattern to find the dematerialized transportee in subspace and rematerialize them at the target coordinates, taking great care to ensure that all these trillions of pieces are moved to the correct locations in realspace. These steps can be (and often are) accelerated, with a person beginning to materialize at the target coordinates while still dematerializing on the transporter pad (see TNG Darmok for an example off the top of my head).
The reason you can't just tell the transporter to make another copy of what's in the buffer is that although you have a lot of information about whatever you just dematerialized, you only have one copy of the matter in the buffer. If you try to materialize another one you'll be trying to pull matter from subspace where none exists: the transporter equivalent of a Segmentation Fault, to use another computer science term. If you tried to use that pattern to convert an appropriate quantity of base matter into a copy of whatever was in the buffer, you'll still be missing any information about the transported material which can't be gleamed exclusively from a mapping of where each piece was: you won't necessarily know exactly what every piece was, at a precision necessary to recreate it. Especially if the diffusion of material into subspace is sufficiently predictable that the pattern doesn't need a pointer for every individual subatomic particle, but can capture a a cluster of particles with each one.
We know from the existence of "transporter traces" that the transport process does leave behind some persistent information about a person who was transported. We also know that it is possible for the transporter operator to identify and deactivate weapons mid-transport. It makes sense that a mapping of pointers could be extrapolated out to get a lot of data about the matter being transported (such as detailed information on a subject's cellular makeup, or if there's a device capable of discharging a dangerous amount of energy) while still falling far short of the data required to make an exact copy.