Movies & TV Stack Exchange is a question and answer site for movie and TV enthusiasts. It only takes a minute to sign up.
Sign up to join this community
Mark Watney was able to hack Mars Pathfinder and set up a kind of chat application to communicate with Earth.
But AFAIK there is communication delay about 30 minutes in one way! And in the movie it seems like he's getting immediate responses.
Was the delay addressed or was realism ignored for timing or other purposes?
The communication delay was in fact addressed in the movie. Here is a link to the scene with Director Ridley Scott's commentary. Around 3:25 Tim makes a sarcastic comment about the limits of the communication with Mark, including the delay.
"Are you receiving me?" "Yes. No."
[Vincent] Okay, point the camera at "yes."
[Tim] 32-minute round-trip communications time. All he can do is ask yes or no questions... and all we can do is point the camera. This won't exactly be an Algonquin Round Table of snappy repartee.
[Vincent] -Are you kidding me?
[Bruce] -Tim, Tim.
[Vincent] -Just point the camera.
[Tim] -Roger that. Pointing the camera.
I believe that after pointing it out once, creators focused on contents of the communication.
They gloss over the delay for effect, but it does show that a crowd of people at NASA headquarters and the JPL are waiting around for replies. Especially when he is live.
The Delay is addressed multiple times though. And according to the book and movie, at some points, depending on where Mars and Earth are relative to each other, the delay is only about 10 minutes (both ways), not 16 (32 both ways).
Aside from @bartuosz answer which includes the main scene from the first transmission stating 32 minutes round trip, the rest of the scene is important too. The camera in the movie spins fairly quickly, but in real life is a bit slower (minutes, not seconds) to take a panoramic 360° picture and transmit. Not instant pictures like the movie shows as well. And then because Yes and No questions are slow and limiting, Mark looks for the Ascii Table. It's not a quick communication method. And the people at the JPL fall asleep when Mark made the first ASCII transmission.
Where timestamps are used for the communication, instead of being a potty mouth, Mark is a 12 year old boy:
[11:52] WATNEY: The crops are potatoes, grown from the ones we were supposed to prepare on Thanksgiving. They’re doing great, but the available farmland isn’t enough for sustainability. I’ll run out food around Sol 900. Also: Tell the crew I’m alive! What the fuck is wrong with you?
[12:04] JPL: We’ll get botanists in to ask detailed questions and double-check your work. Your life is at stake, so we want to be sure. Sol 900 is great news. It’ll give us a lot more time to get the supply mission together. Also, please watch your language. Everything you type is being broadcast live all over the world.
[12:15] WATNEY: Look! A pair of boobs! -> (.Y.)[11:49] JPL: what we can see of your planned cut looks good. We're assuming the other side is identical. You're cleared to start drilling.
[12:07] WATNEY: That's what she said
[12:25] JPL: Seriously, Mark? Seriously?
When the Hermes crew decide to mutiny:
BRENDAN: What the hell? CAPCOM, ask them what the hell.
CAPCOM: Roger Flight. Message sent. Minimum reply time 3 minutes, 4 seconds.
When the rescue is about to start:
ANNIE: If something goes wrong, what can Mission Control do?
VINCENT Not a damned thing.
(off her look) It’s all happening twelve light-minutes away. That means it takes twenty-four minutes for them to get the answer to any question they ask. The whole launch is twelve minutes long. They’re on their own.
It's faster but doesn't change the delay. The delay is glossed over because it would ruin the timing of the film.
There is one place that really made me think they'd forgotten about the comm latency: when Mark asks about the crew's reaction to the news he's alive, he sends "RU receiving?" after he doesn't get a reply. This seems like something you'd do only if communication was real-time.
But if you watch the scene carefully (which apparently I didn't the first time), you can see that he was sitting back in his chair, and only sent that after looking at another screen to his side (presumably with a clock). They do a decent job of showing that he had been waiting a while (for the expected comm round-trip time), and didn't still have his hands on the keyboard like you would after a 10 second pause.
After Kapoor sends "we haven't told the crew...", he starts to stand up from his computer before the shot cuts away. Presumably he's going to get a drink or something while waiting for the reply, since obviously there is lots more to talk about with Mark (on other subjects).
When the reply does come, people are standing around the office like they're waiting.
So there are subtle visual cues about the time jumps in each cut between send and receive.
Having the conversation "broadcast live all over the world" is a little weird. It's not plausible that TV news stations would just show it continuously with at least 20 minutes between messages. TV and radio news would have to cut back to it for every update, which would let them take an extra couple seconds to screen it for profanity. Presumably they just meant that it's going up live on NASA's web site as it comes in.
In the commentary track for that scene, they address it directly:
Weir (author of the book): I also really appreciate you guys maintaining the communication latency. As far as I can tell, that is the hardest thing for Hollywood to do...
Goddard interjects: It's really hard.
Weir: ... is accept the fact that there's a communication latency.
Goddard (author of the screenplay): I guess it does sort of go against the nature of cinema. 'Cause you cut between one place to another and in your mind it doesn't quite make sense.
Weir: This one bit right here where he doesn't get an immediate response, so he's like "Are you receiving?". I'm like, "Well, technically he would have been waiting 20 minutes."
Goddard: All right. Let's no-prize it. He waited 20 minutes, the normal amount of time.
Weir: And there was no immediate response. And so he's like "Hey."
Goddard (joking): That's right. We shot those 20 minutes, but it was boring.
Weir: Yeah, right. You just pointed the cameras at the actors and said ...
Goddard: "Now just wait".
The three different methods of communication shown in The Martian
Answer yes/no questions by pointing the camera. Pretty terrible for proposing new ideas to Mark: No way for NASA to tell him what yes/no question to ask. Also tricky to have multiple questions in-flight because you'll get mixed up on which yes/no went with which question.
Mark->Earth: messages on boards. NASA->Mars: ASCII transmitted 4 bits at a time (hex digits as symbols). Same latency (well, higher if you include decode time), much higher bandwidth. Mark can receive messages without a round-trip to Earth. But only when standing outside watching the camera move.
Two way text (and presumably data, like email attachments). Fully asynchronous. NASA can send stuff while Mark is busy doing something else, and he can see it when he next checks the screen. Same latency, vastly higher bandwidth.
They all have the same latency (+/- manual decoding time), but there are huge increases in bandwidth with each revision. The first one is so limited that the second one (manually-decoded ASCII) is a qualitative change, not just a quantitative bandwidth improvement.
The third communication method (fully computerized) should make it much easier to deal with the large delay * bandwidth product. Multiple whole messages can be "in flight" at once in each direction.
If you've ever had a text-chat conversation with someone where you're still replying to an old message while they're starting to say something new, imagine that. You will have multiple topics of conversation happening in parallel.
Ideally each conversation in separate windows on screen. Or set it up like email, with a different thread for each topic.
(Initial contact would be something simple hacked together like shown; a threaded chat program would come later).
So instead of sitting there waiting for a reply to your last message, you'd go eat something, or alt+tab and reply to a different message. You'd be talking to botanists about your plants, talking to habitat engineers about any maintenance issues, talking to a doctor about your health, etc. etc.
It's easy to imagine that this is "what happened", even though the movie doesn't explicitly show it. Movies rarely have time for the interesting details of a lot of things.
The other thing that seemed odd was that messages appear on the receiving screen at about typing speed. Communication over that distance results in very weak signals on the receiving end, so sending a single character reliably would actually require sending a whole data packet with error-detection and correction codes. (See this short article about NASA's Deep Space Network.)
Given that the minimum round-trip time is over 3 minutes, composing a whole message and sending it would not add a significant amount of extra delay, and would make more sense (and probably would have been easier for the engineers to implement).
I guess there's plenty of bandwidth to send a whole packet for each character if we're only talking about human typing speed, though. There's no technical obstacle to implementing it that way.
