SEARCH · Engineering Papers
Search indexed NASA NTRS and DOE OSTI research on propulsion, heat transfer, battery materials and energy systems. Follow report and document links to the original sources.
Quote a phrase for an exact phrase match. Source license links do not imply unrestricted reuse.
The Science Activity Planner (SAP), currently under development by our group at the Jet Propulsion Laboratory, will be the primary tool used for science data assessment and science activity planning during the Mars Exploration Rover (MER) mission.
In this paper we describe a multiuser collaboration infrastructure that enables multiple mission scientists to remotely and collaboratively interact with visualization and planning software, using wireless networked personal digital assistants(PDAs) and other mobile devices. During ground operations of planetary rover and lander missions, scientists need to meet daily to review downlinked data and plan science activities. For example, scientists use the Science Activity Planner (SAP) in the Mars Exploration Rover (MER) mission to visualize downlinked data and plan rover activities during the science meetings [1]. Computer displays are projected onto large screens in the meeting room to enable the scientists to view and discuss downlinked images and data displayed by SAP and other software applications. However, only one person can interact with the software applications because input to the computer is limited to a single mouse and keyboard. As a result, the scientists have to verbally express their intentions, such as selecting a target at a particular location on the Mars terrain image, to that person in order to interact with the applications. This constrains communication and limits the returns of science planning. Furthermore, ground operations for Mars missions are fundamentally constrained by the short turnaround time for science and engineering teams to process and analyze data, plan the next uplink, generate command sequences, and transmit the uplink to the vehicle [2]. Therefore, improving ground operations is crucial to the success of Mars missions. The multiuser collaboration infrastructure enables users to control software applications remotely and collaboratively using mobile devices. The infrastructure includes (1) human-computer interaction techniques to provide natural, fast, and accurate inputs, (2) a communications protocol to ensure reliable and efficient coordination of the input devices and host computers, (3) an application-independent middleware that maintains the states, sessions, and interactions of individual users of the software applications, (4) an application programming interface to enable tight integration of applications and the middleware. The infrastructure is able to support any software applications running under the Windows or Unix platforms. The resulting technologies not only are applicable to NASA mission operations, but also useful in other situations such as design reviews, brainstorming sessions, and business meetings, as they can benefit from having the participants concurrently interact with the software applications (e.g., presentation applications and CAD design tools) to illustrate their ideas and provide inputs.
To support the distributed and complex operational scheduling required for future National Aeronautics and Space Administration (NASA) missions, a formal, textual language, the Scheduling Applications Interface Language (SAIL), has been developed. Increased geographic dispersion of investigators is leading to distributed mission and science activity planning, scheduling, and operations. SAIL is an innovation which supports the effective and efficient communication of scheduling information among physically dispersed applications in distributed scheduling environments. SAIL offers a clear, concise, unambiguous expression of scheduling information in a readable, hardware independent format. The language concept, syntax, and semantics incorporate language features found useful during five years of research and prototyping with scheduling languages in physically distributed environments. SAIL allows concise specification of mission and science activity plans in a format which promotes repetition and reuse.
The science activity planning process for the 2003 Mars Exploration Rover (MER) mission was exercised in a ten day terrestrial rover field test in August 2002. A version of the MER mission Science Activity Planner (SAP) tool was used for downlink data visualization and uplink plan generation.
Most major global satellite surveyors of climate-relevant trace gases have relatively coarse spatial resolution or temporal sampling. While these data can be supplemented by fine-pointing satellites and aircraft, the spatial and temporal resolutions available from crewed aircraft is not sufficient to observe stochastic, ephemeral events that take place between observations. Emerging High Altitude Long Endurance (HALE) Uncrewed Aerial Systems (UAS) can operate for months at a time and loiter over targets to provide continuous daylight geostationary-like observations, allowing these new platforms to be integrated with existing satellites as part of a New Observing Strategy (NOS).To aid in the planning of future NOS missions, NASA is developing the Intelligent Long Endurance Observing System (ILEOS), a science activity planning system. ILEOS will help scientists build plans to improve spatio-temporal resolution of climate-relevant gases by fusing coarse-grained sensor data from satellites and other sources(e.g., terrain, forecasts), and plan HALE UAS flights to obtain finer-grain (high spatio-temporal) data. ILEOS will also enable observations for longer periods and of environments not accessible through in-situ observations and crewed aircraft field campaigns.
A decomposition of the Apollo 17 mission extravehicular activities (EVA) tasks can be used to prepare for Artemis and future Mars missions. A categorized minute by minute breakdown of the astronauts’ activites could be used to plan future EVAs and determine which scientific tasks or equipment may be prioritized. This is especially relevant in this critical stage for the upcoming Atemis missions and science activity planning. The infographics generated from the decomposition provide a higher level view of actual EVAs and could aid in making future EVAs more efficient and successful.
This factsheet briefly describes the role of the LADEE Activity Scheduling System (LASS) software in science activity planning for theLunar Atmosphere And Dust Environment Explorer (LADEE) mission.
An intensive science and mission planning effort has been underway for several years to develop the next logical candidate mission to the outer planets following the Mariner Jupiter/Saturn 1977 Mission. The highest priority candidate that emerges from this effort is the launch of a MJS-derived Mariner spacecraft to Uranus during the 1979 Jupiter/Uranus opportunity. Since 1972 when the Outer Planets Science Advisory Group recommended MJU79 to follow MJS77, four other science groups have addressed this issue and arrived at the same recommendation. Currently, the planning effort is most intensive and the paper will report the past and present determinations of the various science and mission planning activities, emphasizing science value, technical factors and fiscal constraints.
Planetary surface exploration missions present considerable operational challenges in the form of substantial communication delays, limited communication windows, and limited communication bandwidth. A 3D visualization software was developed and delivered to the 2008 Phoenix Mars Lander (PML) mission. The components of the system include an interactive 3D visualization environment called Mercator, terrain reconstruction software called the Ames Stereo Pipeline, and a server providing distributed access to terrain models. The software was successfully utilized during the mission for science analysis, site understanding, and science operations activity planning. A terrain server was implemented that provided distribution of terrain models from a central repository to clients running the Mercator software. The Ames Stereo Pipeline generates accurate, high-resolution, texture-mapped, 3D terrain models from stereo image pairs. These terrain models can then be visualized within the Mercator environment. The central cross-cutting goal for these tools is to provide an easy-to-use, high-quality, full-featured visualization environment that enhances the mission science team s ability to develop low-risk productive science activity plans. In addition, for the Mercator and Viz visualization environments, extensibility and adaptability to different missions and application areas are key design goals.
The Rover Sequencing and Visualization Program (RSVP) is the software tool for use in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight-code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover-predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (IDD) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities. Thus, RSVP, being highly data driven, may be tailored to other missions with minimal effort. In addition, RSVP uses a distributed, message-passing architecture to allow multitasking, and collaborative visualization and sequence development by scattered team members.
The Rover Sequencing and Visualization Program (RSVP) has been updated. RSVP was reported in Rover Sequencing and Visualization Program (NPO-30845), NASA Tech Briefs, Vol. 29, No. 4 (April 2005), page 38. To recapitulate: The Rover Sequencing and Visualization Program (RSVP) is the software tool to be used in the Mars Exploration Rover (MER) mission for planning rover operations and generating command sequences for accomplishing those operations. RSVP combines three-dimensional (3D) visualization for immersive exploration of the operations area, stereoscopic image display for high-resolution examination of the downlinked imagery, and a sophisticated command-sequence editing tool for analysis and completion of the sequences. RSVP is linked with actual flight code modules for operations rehearsal to provide feedback on the expected behavior of the rover prior to committing to a particular sequence. Playback tools allow for review of both rehearsed rover behavior and downlinked results of actual rover operations. These can be displayed simultaneously for comparison of rehearsed and actual activities for verification. The primary inputs to RSVP are downlink data products from the Operations Storage Server (OSS) and activity plans generated by the science team. The activity plans are high-level goals for the next day s activities. The downlink data products include imagery, terrain models, and telemetered engineering data on rover activities and state. The Rover Sequence Editor (RoSE) component of RSVP performs activity expansion to command sequences, command creation and editing with setting of command parameters, and viewing and management of rover resources. The HyperDrive component of RSVP performs 2D and 3D visualization of the rover s environment, graphical and animated review of rover predicted and telemetered state, and creation and editing of command sequences related to mobility and Instrument Deployment Device (robotic arm) operations. Additionally, RoSE and HyperDrive together evaluate command sequences for potential violations of flight and safety rules. The products of RSVP include command sequences for uplink that are stored in the Distributed Object Manager (DOM) and predicted rover state histories stored in the OSS for comparison and validation of downlinked telemetry. The majority of components comprising RSVP utilize the MER command and activity dictionaries to automatically customize the system for MER activities.
The NASA-ISRO Synthetic Aperture Radar, or NISAR, mission is an Earth-mapping radar observatory to be launched from Sriharikota (India) in 2022. This mission is a collaboration between the National Aeronautics and Space Administration (NASA) and the Indian Space Research Organization (ISRO). This spacecraft will carry two instruments that will operate at radar wavelengths (L and Sband) and will provide data for understanding changes in the Earth’s land surface. The scientific data from this mission will revolutionize our understanding of the causes and consequences of land surface changes on Earth, ranging from Solid Earth Deformation in the form of natural hazards like earthquakes, volcanic eruptions and landslides, to ecosystem disturbances, to changes in the cryosphere (measurements of polar ice caps, ice sheets and sea ice). A nominal Reference Observation Plan, that repeats roughly every 12-24 days, developed prior to launch by the NISAR Mission Planning team, in consultation with the Science Team, will form the basis of science data collection by the payload instruments onboard the NISAR observatory after launch. Scheduling of science observations for the mission requires accounting for limited spacecraft resources like onboard data storage, downlink capacity, energy/power, thermal limits and instrument duty cycles. In addition to nominal science data collection, the project has a Level 1 requirement to respond to requests for urgent data acquisition over disaster sites (natural or anthropogenic) by scheduling new acquisitions within 24 hrs of notification and delivering science data within 5 hours of data acquisition. This capability is to be exercised on a ‘best-efforts basis’. While the definition of what constitutes an ‘urgent request’, and how such requests would be submitted to the project, is within the domain of the Science Team, the Mission System team is responsible for developing the baseline operations concept and implementation approach for responding to such requests. Given the ‘best-efforts’ nature of this requirement, a few highlevel guidelines have been developed to help guide the formulation of the operations concept, and are presented in this paper. Requests for urgent response data will be accommodated following the guiding principle of minimal to no impact on nominal science and planned engineering activities. No change in satellite orbit or attitude will be made for urgent response. Restricting response approaches to only changing the downlink and/or ground processing priority for existing observations, and adding new observations only in areas where NISAR will not be nominally imaging, allows for minimal impact on the Reference science Observation Plan. No instrument mode changes will be allowed for urgent response (except for high-priority requests), and no new observations that impact either planned science or engineering activities will be scheduled. Additionally, data requests must fit within the available project resource margins (both spacecraft and ground resources are to be evaluated). Both JPL and ISRO will be involved at various steps of the implementation, irrespective of whether the urgent request is for L-SAR (NASA instrument) or S-SAR (ISRO instrument) or a joint dataset.
The design of the science planning process for a space science mission needs to find a balance between operational and resource constraints and scientific decision-making. Science planning has previously been characterized as either predictive or reactive. Predictive science planning is needed when constraints drive science activities to be planned far in advance. For example, a combination of long one-way light time plus high-stakes science decisions drove the Cassini-Huygens mission to Saturn to have an extremely predictive planning process. On the other extreme, reactive science planning is needed when constraints drive science activities to be planned based on the results of the previous plan. For example, the Mars Exploration Rover mission interacted with the surface of Mars, and so the planning team needed to know the state of the rover at the end of each planning cycle before starting the next cycle. Operational and resource constraints that require management on intermediate timescales has led to the development of a science planning process between these two extremes. For example, the Mars Science Laboratory is a technically complex rover and has a parallel predictive process that allows the operations team to manage engineering constraints several days in advance while maintaining the reactive tactical planning process similar to that of MER. The Mars 2020 Perseverance rover is a technically complex rover in the MSL style, but has an added layer of science complexity: it is tasked with collecting a returnable cache of scientifically valuable samples of Mars within prime mission. Thus, the science planning process also needs to accommodate high-stakes longer-term science decisions in the style of Cassini. In order to balance the push-pull of these constraints, we have developed a science campaign-focused operational paradigm for Mars 2020 Perseverance that allows for both predictive planning to accommodate technological complexity and high-stakes science decisions as well as reactive planning to accommodate the realities of interacting with the martian surface. This paradigm influenced the design of operational processes and operational tools.
Objectives were listed for four areas: engineering science, reliability physics, module development, and module performance and failure analysis. The engineering science efforts are to develop module design requirements for large-scale photovoltaic (PV) applications and to develop generic module and array design and construction technology to meet the needed performance, safety, reliability, and system interfaces. The reliability physics effort is to develop the technology for 30-year life modules. The module development efforts are to transfer new technology to PV manufacturers and their products, and to evaluate these advanced modules. The module performance and failure analysis efforts are to determine PV module performance, to identify needed development, and to assess suitability for large-scale use.
The Science Activity Planner (SAP) is the science planning tool used for the Mars Exploration Rover (MER) mission. This paper begins with an overview of the software developed for MER and how it was used for science downlink analysis and activity planning.
The Galileo mission operations concept is undergoing substantial redesign, necessitated by the deployment failure of the High Gain Antenna, while the spacecraft is on its way to Jupiter. The new design applies state-of-the-art technology and processes to increase the telemetry rate available through the Low Gain Antenna and to increase the information density of the telemetry. This paper describes the mission planning process being developed as part of this redesign. Principal topics include a brief description of the new mission concept and anticipated science return (these have been covered more extensively in earlier papers), identification of key drivers on the mission planning process, a description of the process and its implementation schedule, a discussion of the application of automated mission planning tool to the process, and a status report on mission planning work to date. Galileo enhancements include extensive reprogramming of on-board computers and substantial hard ware and software upgrades for the Deep Space Network (DSN). The principal mode of operation will be onboard recording of science data followed by extended playback periods. A variety of techniques will be used to compress and edit the data both before recording and during playback. A highly-compressed real-time science data stream will also be important. The telemetry rate will be increased using advanced coding techniques and advanced receivers. Galileo mission planning for orbital operations now involves partitioning of several scarce resources. Particularly difficult are division of the telemetry among the many users (eleven instruments, radio science, engineering monitoring, and navigation) and allocation of space on the tape recorder at each of the ten satellite encounters. The planning process is complicated by uncertainty in forecast performance of the DSN modifications and the non-deterministic nature of the new data compression schemes. Key mission planning steps include quantifying resource or capabilities to be allocated, prioritizing science observations and estimating resource needs for each, working inter-and intra-orbit trades of these resources among the Project elements, and planning real-time science activity. The first major mission planning activity, a high level, orbit-by-orbit allocation of resources among science objectives, has already been completed; and results are illustrated in the paper. To make efficient use of limited resources, Galileo mission planning will rely on automated mission planning tools capable of dealing with interactions among time-varying downlink capability, real-time science and engineering data transmission, and playback of recorded data. A new generic mission planning tool is being adapted for this purpose.
Life sciences activities being planned for Space Station Freedom (SSF) as of Fall 1992 are discussed. Planning for these activities is ongoing. Therefore, this description should be viewed as indicative of the prevailing ideas at one particular time in the SSF development cycle. The proposed contributions of the Canadian Space Agency (CSN) the European Space Agency (ESA), Japan, and the United States are all discussed in detail. In each case, the life sciences goals, and the way in which each partner proposes to achieve their goals, are reviewed.
SURE (Science User Resource Expert) is one of three components that compose the SURPASS (Science User Resource Planning and Scheduling System). This system is a planning and scheduling tool which supports distributed planning and scheduling, based on resource allocation and optimization. Currently SURE is being used within the SURPASS by the UARS (Upper Atmospheric Research Satellite) SOLSTICE instrument to build a daily science plan and activity schedule and in a prototyping effort with NASA GSFC to demonstrate distributed planning and scheduling for the SOLSTICE II instrument on the EOS platform. For the SOLSTICE application the SURE utilizes a rule-based system. Development of a rule-based program using Ada CLIPS as opposed to using conventional programming, allows for capture of the science planning and scheduling heuristics in rules and provides flexibility in inserting or removing rules as the scientific objectives and mission constraints change. The SURE system's role as a component in the SURPASS, the purpose of the SURE planning and scheduling tool, the SURE knowledge base, and the software architecture of the SURE component are described.