Search NASA⌕ Search

Engineering topics

Ko, A.

Publications and source records attributed to Ko, A..

7 records
All sourcesNASA NTRSDOE OSTI
NASA NTRS2014

The U.S. Rosetta Project: Preparations for Prime Mission, 2014

In 2014, the International Rosetta mission will place a spacecraft in orbit around comet 67P/Churyumov-Gerasimenko and deliver a lander to the comet's surface. The National Aeronautics and Space Administration's (NASA) contribution to the International Rosetta mission, designated the U.S. Rosetta Project, includes several instruments, tracking support, and science support for some non-US payloads. In July 2011 the spacecraft was placed in a long-duration hibernation mode planned to last approximately 37 months to conserve electrical power. Rosetta will rendezvous with 67P/Churyumov-Gerasimenko in 2014. On the eve of the mission's arrival at its target, this paper highlights three issues related to Rosetta's looming prime mission: (A) measures taken in 2009 to prepare the US Rosetta Project for the long-duration hibernation mode; (B) risk reviews conducted in 2013 to prepare the US Rosetta Project for exit from hibernation; (C) ESA and NASA preparations for use of NASA Deep Space Network (DSN) assets related to keyword files.

hibernation↗
NASA NTRS2003

Mission interactive scenarion studio for autonomous spacecraft

We propose building a Studio enabling the use of diverse existing mission activity and scenario patterns, the creation of new ones, and the modeling of their effects using existing modeling tools. The core of the Studio is a component-based Type Library, which captures years of mission adaptation patterns in various forms. The Studio works as a content server to capture the developed adaptation knowledge for reuse and provides bridging into different mission uplink implementations, including the Mission Data System [l] (MDS) state/goal machinery. Various activities can be coordinated, controlled, and reused through the Studio's component interface to establish and model a mission scenario. A special component Factory mechanism will be in place to facilitate the adaptation of projects into the Studio. The architecture of the Studio reflects and enforces a division of knowledge and actions into three parts: Model, Controller, Viewer. The Model contains information about (a proposed version of) the spacecraft and mission. The Controller contains logic for constructing scenarios of mission activities. The information in the Model and Controller is principally in the form of reusable patterns. A Viewer can be a simple or complex software system. For example, Apgen [2,3] is one possible viewer, MDS is another. A 3-tiered infrastructure is used for the Studio, reflecting the Model, Controller, Viewer architecture [4,5]. The Studio is useful in pre-phase A of a project by enabling spacecraft design options to be played against desired mission scenarios. In later design phases of a project, the construction and modeling of more detailed scenarios is supported by the Studio.

autonomous spacecraft↗
NASA NTRS1999

A Process for Verifying and Validating Requirements for Fault Tolerant Systems Using Model Checking

Model checking is shown to be an effective tool in validating the behavior of a fault tolerant embedded spacecraft controller. The case study presented here shows that by judiciously abstracting away extraneous complexity, the state space of the model could be exhaustively searched allowing critical functional requirement to be validated down to the design level.

model checking fault tolerant embedded spacecraft ↗