2008
DOI: 10.1029/2007je003051
|View full text |Cite
|
Sign up to set email alerts
|

Phoenix surface mission operations processes

Abstract: [1] We present an overview of Phoenix Mars Scout Mission (Phoenix) surface operations process design with an emphasis on the science portion of the process. We describe the drivers and constraints on Phoenix operations and the resulting choices that the development team made to accommodate these constraints. The two most important drivers on Phoenix operations are the choice of orbiter relay only for data and the limited amount of data storage on the lander. These two combine to regulate the amount of data the… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

2
18
0

Year Published

2012
2012
2017
2017

Publication Types

Select...
6

Relationship

0
6

Authors

Journals

citations
Cited by 11 publications
(20 citation statements)
references
References 1 publication
2
18
0
Order By: Relevance
“…This allows scientists to use these tools to efficiently maximize science return. For example, Mars Exploration Rovers (MER) science operations strategies were designed Contents lists available at ScienceDirect journal homepage: www.elsevier.com/locate/actaastro to accommodate the latency in communications between Earth and Mars, a delay that required separating sciencedriven decisions based on analysis of the surroundings, from the actual execution of remote field activities [1][2][3][4][5]. A science support team (the "science backroom") determined science priorities and observations to be executed by the rover the following Martian day, or "sol"; these observations, along with other necessary activities, were planned and executed by the rover engineers.…”
Section: Introductionmentioning
confidence: 99%
“…This allows scientists to use these tools to efficiently maximize science return. For example, Mars Exploration Rovers (MER) science operations strategies were designed Contents lists available at ScienceDirect journal homepage: www.elsevier.com/locate/actaastro to accommodate the latency in communications between Earth and Mars, a delay that required separating sciencedriven decisions based on analysis of the surroundings, from the actual execution of remote field activities [1][2][3][4][5]. A science support team (the "science backroom") determined science priorities and observations to be executed by the rover the following Martian day, or "sol"; these observations, along with other necessary activities, were planned and executed by the rover engineers.…”
Section: Introductionmentioning
confidence: 99%
“…There are a total of six separate processes which were present during the Phoenix Mission, three of which were explicitly described by the Operations Concept Document (Eagles, 2008) and in descriptions of the surface mission operations process (Bass and Talley, 2008). These are (1) Tactical Planning and its low-level follow-on counterpart, (2) Sequencing as well as a separate (3) Since the size, experience and time for training were all limited for the volunteer team available for ILSR Mission Control, it was necessary to reorganize these processes.…”
Section: Processesmentioning
confidence: 99%
“…Bass and Talley [16] defined strategic processes as including, ''ythe generation of midterm and also longterm 'strategic' science plan that describes the possible lander actions from 4 to 11 sols in the future.'' Consequently, the strategic science operations process for MarsPhoenix involved an analysis of high-level science objectives that would be decomposed into more detailed activities.…”
Section: Mars-phoenix Missionmentioning
confidence: 99%
“…Although not a rover mission, the Mars-Phoenix Mission Team built its operations approach on lessons learned in the Mars Exploration Rover mission [16]. A critical factor in Mars-Phoenix mission operations was managing data return from the surface within a limited return data budget, which drove the Mars-Phoenix team to operate essentially two planning processes: (1) a tactical process that dealt exclusively with those science activities whose commands were up-linked to the spacecraft each Martian day, and (2) a strategic process that considered those science activities that would be executed over the longer planning horizon of the total mission duration [16]. The requirement for teams to operate under different planning horizons was a function of mission duration.…”
Section: Mars-phoenix Missionmentioning
confidence: 99%
See 1 more Smart Citation