Search NASASearch

SEARCH · Search NASA

Results for “mission sequencing”

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.

At least 19 records

The evolution of the Voyager mission sequence software and trends for future mission sequence software systems

The historical background of the spacecraft sequence generation process as it is represented by the Voyager mission to the outer planets is discussed. Present plans for future sequencing methods are examined, including the emphasis on cutting costs and the contrast between the centralized and distributed systems for sequencing. The use of artificial intelligence in mission sequencing is addressed.

Brooks, Robert N., Jr.

Irreducible Tests for Space Mission Sequencing Software

As missions extend further into space, the modeling and simulation of their every action and instruction becomes critical. The greater the distance between Earth and the spacecraft, the smaller the window for communication becomes. Therefore, through modeling and simulating the planned operations, the most efficient sequence of commands can be sent to the spacecraft. The Space Mission Sequencing Software is being developed as the next generation of sequencing software to ensure the most efficient communication to interplanetary and deep space mission spacecraft. Aside from efficiency, the software also checks to make sure that communication during a specified time is even possible, meaning that there is not a planet or moon preventing reception of a signal from Earth or that two opposing commands are being given simultaneously. In this way, the software not only models the proposed instructions to the spacecraft, but also validates the commands as well.To ensure that all spacecraft communications are sequenced properly, a timeline is used to structure the data. The created timelines are immutable and once data is as-signed to a timeline, it shall never be deleted nor renamed. This is to prevent the need for storing and filing the timelines for use by other programs. Several types of timelines can be created to accommodate different types of communications (activities, measurements, commands, states, events). Each of these timeline types requires specific parameters and all have options for additional parameters if needed. With so many combinations of parameters available, the robustness and stability of the software is a necessity. Therefore a baseline must be established to ensure the full functionality of the software and it is here where the irreducible tests come into use.

sequencing test

PLAN-IT - Knowledge-based mission sequencing

PLAN-IT (Plan-Integrated Timelines), a knowledge-based approach to assist in mission sequencing, is discussed. PLAN-IT uses a large set of scheduling techniques known as strategies to develop and maintain a mission sequence. The approach implemented by PLAN-IT and the current applications of PLAN-IT for sequencing at NASA are reported.

Biefeld, Eric W.

Multi-mission sequencing software

This paper describes the architecture of the JPL multi-mission sequencing system and demonstrates many of the benefits of the core/adaptation format of the sequencing software.

sequencing multi-mission

Cassini Mission Sequence Subsystem (MSS)

This paper describes my work with the Cassini Mission Sequence Subsystem (MSS) team during the summer of 2011. It gives some background on the motivation for this project and describes the expected benefit to the Cassini program. It then introduces the two tasks that I worked on - an automatic system auditing tool and a series of corrections to the Cassini Sequence Generator (SEQ_GEN) - and the specific objectives these tasks were to accomplish. Next, it details the approach I took to meet these objectives and the results of this approach, followed by a discussion of how the outcome of the project compares with my initial expectations. The paper concludes with a summary of my experience working on this project, lists what the next steps are, and acknowledges the help of my Cassini colleagues.

solstice mission

Viking adaptive mission sequence and control operations

Viking mission operations were required to provide an adaptive sequencing capability in which future observations could be influenced by the latest information about Mars as it was obtained and analyzed. The mission operations strategy that was developed met this requirement and provided the capability to respond smoothly and efficiently to spacecraft subsystem anomalies with minimum impact on the science data gathering process. A description of the major elements of this adaptive man-in-the-loop control system is provided. Specific cases showing how it was utilized to enhance scientific return and to respond to spacecraft anomalies are also provided.

Larman, B. T.

Mariner 9 extended mission sequence design optimization

This paper discusses the Mariner 9 science sequence design during the extended mission including science objectives, and mission operation and spacecraft constraints. The primary objectives of the extended mission were to complete 100% mapping of the planet, photograph special interest targets, obtain high resolution coverage of prospective Viking landing sites, and to function through the superior conjunction period. The optimization of planet viewing characteristics by moving to different celestial reference stars, and the techniques used to efficiently allocate science links to data taking days are described.

Reichert, R. J.

Lessons Learned Implementing Multi-Mission Sequencing Software

This paper will describe the software and its uses to provide context for its criticality. The different approaches that have been taken to implement the software in a multi-mission format will be outlined. The advantages and disadvantages as well as the lessons learned during development and maintenance of these different architectures will be discussed, Finally. the use of multi-mission software in operations and the lessons learned from using it will be discussed.This paper will provide valuable information to organizations exploring the use of multi-mission software. regardless of whether the change is to minimize spacecraft ground software development time or cost reduction. Similarly. the paper will provide insight into some of the steps that can be taken during software development and operational use that will minimize difficulty later.

software

MSFC Skylab mission sequence evaluation

Planned and actual major Skylab sequences are presented. Off-nominal events are highlighted. Differences between planned and actual events are discussed.

Hoverkamp, J. D.

Satellite services system analysis study. Volume 3A: Service equipment requirements, appendix

Spacecraft descriptions and mission sequences, mission and servicing operations functional analyses, servicing requirements, and servicing equipment are discussed for five reference satellites: the X-ray Timing Explorer, the Upper Atmospheric Research Satellite, the Advanced X-ray Astrophysics Facility, the Earth Gravity Field Survey Mission, and the Orbiting Astronomical Observatory.

Source record

Techniques and software for optimum and efficient mission science sequence development

Highly successful mission operations require efficient and cost-effective science sequence development. Of key importance is the Science Planning and Operations Team's (SPOT's) ability to complete science observation design and integration early in the sequence development process (i.e., before the sequence enters into a formal change control process). Once under formal change control, careful change paper documentation, Flight Team checks, and mission software checks make sequence changes more labor-intensive. This paper discusses team organization, strategies, scheduling, and software employed by the Voyager and Galileo SPOT's to complete science observation design and integration early in the sequence development process.

Bliss, David A.