5 ms·
I'm surprised that's not already an thing in that ops center. Maybe being an outsider I've built up an unrealistic aura of awe around NASA/JPL type environments
by dylan604 3y ago
I'm surprised that's not already an thing in that ops center. Maybe being an outsider I've built up an unrealistic aura of awe around NASA/JPL type environments where those places would be quiet as a church unless something like landing or some other epic accomplishment where everyone was cheering. Otherwise, I'd expect everyone to know that when the shit hits the fan, everyone is hunkered down doing what needs to be done. Does the long lag between issuing commands kind of break that?
- foobarbecue 3y agoThere's a well-choreographed dance of meetings (with polls, e.g. go / no go) and head-down sequence writing. Meetings have a pretty rigid structure and there are zero off-topic comments. But the time for getting the actual sequencing done often has chatter with varying amounts of on-topic-ness. Generally, people are really great at not distracting each other-- I've only occasionally had an issue and when I bring it up, chatter ends. It's just that having a term for it would make it easier to bring up. "Socialize with your colleagues" is actually an item on one of our checklists!
- deleted 3y ago[deleted]
- dylan604 3y agoDo you feel that something as long running as Curiosity that things become a little more lax as everyone gets to a level of complacency? I could see where that might happen, but at the same time the concept of I'm controlling something on the surface of another planet is hard to forget. Basically, super curious about the day to day of a job I'm very jealous of in a very respectful way
- foobarbecue 3y agoInteresting question about complacency. Hard for me to speak objectively on this since I'm too close to it to be unbiased, but I'll try. I actually think the level of acceptable risk is gradually dropping. Each time something goes wrong, we add procedures. It's much easier to add rules than to remove them. I do think the risk tolerance of individuals on the project does tend to gradually increase with experience, but we have fairly high turnover. It's common for MSL roles to have a year or more of training before certification during which you spend a lot of time focusing on what can go wrong, so new people definitely trend cautious.
- dylan604 3y agoThat makes sense. Thanks for taking the time to answer my curiosity about your Curiosity
- deleted 3y ago[deleted]
- masklinn 3y ago> Does the long lag between issuing commands kind of break that? That would be my assumption. For earth operations everyone would be focused and ready (especially if that involves people). With Mars there’s several minutes of comm lag, by the time you get an emergency signal it’s resolved one way or the other.
- foobarbecue 3y agoSignal travel time isn't really a significant delay in the planning cycle. What matters is waiting for orbiters to fly overhead for downlink, DSN scheduling, and the 6 to 8 hours it takes to write a typically 1 to 4 sol plan (set of commands). Also constraints of getting it done during regular work hours, ish.
- foobarbecue 3y agoI should say, the above response is with respect to ops for landed Mars missions, during the surface phase. I haven't been involved with ops for missions in deep space orbit or coast (& Entry Descent and Landing), lunar missions, etc. in which more of a real-time-ish paradigm is possible, so I don't know how that works.
- deleted 3y ago[deleted]