Search NASA⌕ Search

SEARCH · Search NASA

Results for “mission data system”

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 343 records · Page 19

Artificial intelligence for multi-mission planetary operations

A brief introduction is given to an automated system called the Spacecraft Health Automated Reasoning Prototype (SHARP). SHARP is designed to demonstrate automated health and status analysis for multi-mission spacecraft and ground data systems operations. The SHARP system combines conventional computer science methodologies with artificial intelligence techniques to produce an effective method for detecting and analyzing potential spacecraft and ground systems problems. The system performs real-time analysis of spacecraft and other related telemetry, and is also capable of examining data in historical context. Telecommunications link analysis of the Voyager II spacecraft is the initial focus for evaluation of the prototype in a real-time operations setting during the Voyager spacecraft encounter with Neptune in August, 1989. The preliminary results of the SHARP project and plans for future application of the technology are discussed.

Atkinson, David J.↗

Orbiter data reduction complex data processing requirements for the OFT mission evaluation team (level C)

This document addresses requirements for post-test data reduction in support of the Orbital Flight Tests (OFT) mission evaluation team, specifically those which are planned to be implemented in the ODRC (Orbiter Data Reduction Complex). Only those requirements which have been previously baselined by the Data Systems and Analysis Directorate configuration control board are included. This document serves as the control document between Institutional Data Systems Division and the Integration Division for OFT mission evaluation data processing requirements, and shall be the basis for detailed design of ODRC data processing systems.

Source record↗

Architecture and Dynamics of Kepler's Multi-Transiting Planet Systems.III. Comprehensive Investigation Using All Four Years of Kepler Mission Data

We study the orbital architectures of planetary systems orbiting within ∼1 AU of their stars by analyzing the ensemble of Kepler systems having two or more planet candidates. We use data from the entire Kepler mission, and in many cases we apply improved analysis techniques (e.g., replacing histograms by top-hat Kernel Density Estimators that avoid the loss of information resulting from choosing a particular phase for the bin boundaries) to extend and enhance the studies of Lissauer et al. (2011, ApJS 197, 8) and Fabrycky et al. (2014, ApJ 790, 146).These data show ~ 1700 transiting planet candidates in > 600 multiple-planet systems, far more than were available for our previous two studies. The increased numbers and better information about planetary radii and the properties of stellar hosts made possible by Gaia DR2 allow more statistically-robust analyses of the entire ensemble of Kepler multis as well as independent analyses of subsets of the population. We are thus able to contrast the dynamical configurations of small and large planets, short-period and longer-period planets, and planets orbiting various types of host stars. We reinforce our previous findings that most pairs of planets within the same system are neither in nor near low-order mean motion resonances and that there is a substantial excess of planets having period ratios slightly larger than those of first-order mean-motion resonances. However, neglecting three systems whose planets are locked in 3- body resonances and summing over all first-order mean motion resonances, the deficit of planet pairs with period ratios just narrow of resonance is as large as the excess of planets wide of resonance (within statistical uncertainties), suggesting that overall there is no overall excess of planet pairs in the vicinity of resonance. Other aspects of our study, including estimates of the typical relative inclinations of planetary orbits and their variations as functions of orbital period, planet sizes and stellar properties, are in progress, with results expected to be available for presentation by the time of the conference.

Lissauer, Jack↗

A Space Data System Standard for Telerobotic Operations

The Telerobotics Working Group of the Mission Operations and Information Management Services Area of the Consultative Committee for Space Data Systems is drafting a document that will help bound the scope of an eventual international standard for telerobotic operations services. This paper will present the work in progress and provide background for how the international community is beginning to define standards in telerobotic operations that will help ensure the success of complex missions to explore beyond Earth orbit.

Mittman, David S.↗

Space Data Storage Systems and Technologies

A central aspect of most space missions is the acquisition from space of unique, mission-specific data and the subsequent return of these data to Earth.

data storage systems buffer data↗

Cost-Effective Telemetry and Command Ground Systems Automation Strategy for the Soil Moisture Active Passive (SMAP) Mission

Soil Moisture Active Passive (SMAP) is an Earth-orbiting, remote-sensing NASA mission slated for launch in 2014.[double dagger] The ground data system (GDS) being developed for SMAP is composed of many heterogeneous subsystems, ranging from those that support planning and sequencing to those used for real-time operations, and even further to those that enable science data exchange. A full end-to-end automation of the GDS may result in cost savings during mission operations, but it would require a significant upfront investment to develop such comprehensive automation. As demonstrated by the Jason-1 and Wide-field Infrared Survey Explorer (WISE) missions, a measure of "lights-out" automation for routine, orbital pass ground operations can still reduce mission cost through smaller staffing of operators and limited work hours. The challenge, then, for the SMAP GDS engineering team is to formulate an automated operations strategy--and corresponding system architecture--to minimize operator intervention during operations, while balancing the development cost associated with the scope and complexity of automation. This paper discusses the automated operations approach being developed for the SMAP GDS. The focus is on automating the activities involved in routine passes, which limits the scope to real-time operations. A key subsystem of the SMAP GDS--NASA's AMMOS Mission Data Processing and Control System (AMPCS)--provides a set of capabilities that enable such automation. Also discussed are the lights-out pass automations of the Jason-1 and WISE missions and how they informed the automation strategy for SMAP. The paper aims to provide insights into what is necessary in automating the GDS operations for Earth satellite missions.

remote-sensing↗

CCSDS Overview

The primary goal of Consultative Committee for Space Data Systems (CCSDS) is interoperability between communications and data systems of space agencies' vehicles, facilities, missions and programs. Of all of the technologies used in spaceflight, standardization of communications and data systems brings the most benefit to multi-agency interoperability. CCSDS Started in 1982 developing standards at the lower layers of the protocol stack. The CCSDS scope has grown to cover standards throughout the entire ISO communications stack, plus other Data Systems areas (architecture, archive, security, XML exchange formats, etc.

Kearney, Mike↗

Helios mission support

Activities of the Deep Space Network in support of the Helios project from 15 April through 15 June 1977 are reported. Information concerning Helios-2's superior conjunction period, Faraday rotation experimentation during solar conjunction, updated Mark III data system status, and other mission oriented activities is included.

Goodwin, P. S.↗

Modular Software Interfaces for Revolutionary Flexibility in Space Operations

To make revolutionary improvements in exploration, space systems need to be flexible, realtime reconfigurable, and able to trade data transparently among themselves and mission operations. Onboard operations systems, space assembly coordination and EVA systems in exploration and construction all require real-time modular reconfigurability and data sharing. But NASA's current exploration systems are still largely legacies from hastily-developed, one-off Apollo-era practices. Today's rovers, vehicles, spacesuits, space stations, and instruments are not able to plug-and-play, Lego-like: into different combinations. Point-to-point dominates - individual suit to individual vehicle, individual instrument to rover. All are locally optimized, all unique, each of the data interfaces has been recoded for each possible combination. This will be an operations and maintenance nightmare in the much larger Project Constellation system of systems. This legacy approach does not scale to the hundreds of networked space components needed for space construction and for new, space-based approaches to Earth-Moon operations. By comparison, battlefield information management systems, which are considered critical to military force projection, have long since abandoned a point-to-point approach to systems integration. From a system-of-systems viewpoint, a clean-sheet redesign of the interfaces of all exploration systems is a necessary prerequisite before designing the interfaces of the individual exploration systems. Existing communications and Global Information Grid and middleware technologies are probably sufficient for command and control and information interfaces, with some hardware and time-delay modifications for space environments. NASA's future advanced space operations must also be information and data compatible with aerospace operations and surveillance systems being developed by other US Government agencies such as the Department of Homeland Security, Federal Aviation Administration and Department of Defense. This paper discusses fundamental system-of-systems infrastructure: approaches and architectures for modular plug-and-play software interfaces for revolutionary improvements in flexibility, modularity, robustness, ease of maintenance, reconfigurability, safety and productivity. Starting with middleware, databases, and mobile communications technologies, our technical challenges will be to apply these ideas to the requirements of constellations of space systems and to implement them initially on prototype space hardware. This is necessary to demonstrate an integrated information sharing architecture and services. It is a bottom-up approach, one that solves the problem of space operations data integration. Exploration demands uniform software mechanisms for application information interchange, and the corresponding uniformly available software services to enhance these mechanisms. We will examine the issues in plug-and-play, real-time-configurable systems, including common definition and management and tracking of data and information among many different space systems. Different field test approaches are discussed, including the use of the International Space Station and terrestrial analog mission operations at field sites.

Glass, Brian↗

A proven approach for more effective software development and maintenance

Modern space flight mission operations and associated ground data systems are increasingly dependent upon reliable, quality software. Critical functions such as command load preparation, health and status monitoring, communications link scheduling and conflict resolution, and transparent gateway protocol conversion are routinely performed by software. Given budget constraints and the ever increasing capabilities of processor technology, the next generation of control centers and data systems will be even more dependent upon software across all aspects of performance. A key challenge now is to implement improved engineering, management, and assurance processes for the development and maintenance of that software; processes that cost less, yield higher quality products, and that self-correct for continual improvement evolution. The NASA Goddard Space Flight Center has a unique experience base that can be readily tapped to help solve the software challenge. Over the past eighteen years, the Software Engineering Laboratory within the code 500 Flight Dynamics Division has evolved a software development and maintenance methodology that accommodates the unique characteristics of an organization while optimizing and continually improving the organization's software capabilities. This methodology relies upon measurement, analysis, and feedback much analogous to that of control loop systems. It is an approach with a time-tested track record proven through repeated applications across a broad range of operational software development and maintenance projects. This paper describes the software improvement methodology employed by the Software Engineering Laboratory, and how it has been exploited within the Flight Dynamics Division with GSFC Code 500. Examples of specific improvement in the software itself and its processes are presented to illustrate the effectiveness of the methodology. Finally, the initial findings are given when this methodology was applied across the mission operations and ground data systems software domains throughout Code 500.

Pajerski, Rose↗

Long Duration Exposure Facility (LDEF) low-temperature heat pipe experiment package power system results

An overview of a self-contained Direct Energy Transfer Power System which was developed to provide power to the Long Duration Exposure Facility (LDEF) Low-Temperature Heat Pipe Experiment Package is presented. The power system operated successfully for the entire mission. Data recorded by the onboard recorder shows that the system operated within design specifications. Other than unanticipated overcharging of the battery, the power system operated as expected for nearly 32,000 low earth orbit cycles, and was still operational when tested after the LDEF recovery. Some physical damage was sustained by the solar array panels due to micrometeoroid hits, but there were not electrical failures.

Tiller, Smith E.↗

The 2008 Mars Phoenix Lander Thermal and Evolved Gas Analyzer (TEGA) Dataset: Placing Easily Interpretable Evolved Gas Data on the Planetary Data System (PDS)

The Phoenix Scout Lander mission investigated the north polar region of Mars in 2008 with the goal to study the history of water, assess the past/present Martian climate, search for organics, and evaluate the potential for past/present microbial habit-ability on Mars. To accomplish this goal, the Phoenix Lander’s Thermal and Evolved-Gas Analyzer (TEGA) instrument assessed the gas composition of the Martian atmosphere and evaluated the mineralogy of the Martian regolith. The TEGA instrument consisted of eight small ovens connected to a 4 channel magnetic sector mass spectrometer. The ovens heated soil samples from ambient to 1000°C where the gases (e.g., H2O, CO2, etc.) evolved from thermal decomposition of mineral phases were analyzed by the mass spectrometer. Minerals thermally decomposed at characteristic temperatures and the evolving gases indicated the presence of perchlorate, carbonate, and hydrated phases in the Phoenix landing site soils.

Garcia, A. H.↗

Tools to Support the Reuse of Software Assets for the NASA Earth Science Decadal Survey Missions

The NASA Earth Science Data Systems (ESDS) Software Reuse Working Group (SRWG) is chartered with the investigation, production, and dissemination of information related to the reuse of NASA Earth science software assets. One major current objective is to engage the NASA decadal missions in areas relevant to software reuse. In this paper we report on the current status of these activities. First, we provide some background on the SRWG in general and then discuss the group s flagship recommendation, the NASA Reuse Readiness Levels (RRLs). We continue by describing areas in which mission software may be reused in the context of NASA decadal missions. We conclude the paper with pointers to future directions.

Mattmann, Chris A.↗

Exposing the Strategies that Can Reduce the Obstacles: Improving the Science User Experience

It is now well established that pursuing generic solutions to what seem are common problems in Earth science data access and use can often lead to disappointing results for both system developers and the intended users. This presentation focuses on real-world experience of managing a large and complex data system, NASAs Earth Science Data and Information Science System (EOSDIS), whose mission is to serve both broad user communities and those in smaller niche applications of Earth science data and services. In the talk, we focus on our experiences with known data user obstacles characterizing EOSDIS approaches, including various technological techniques, for engaging and bolstering, where possible, user experiences with EOSDIS. For improving how existing and prospective users discover and access NASA data from EOSDIS we introduce our cross-archive tool: Earthdata Search. This new search and order tool further empowers users to quickly access data sets using clever and intuitive features. The Worldview data visualization tool is also discussed highlighting how many users are now performing extensive data exploration without necessarily downloading data. Also, we explore our EOSDIS data discovery and access webinars, data recipes and short tutorials, targeted technical and data publications, user profiles and social media as additional tools and methods used for improving our outreach and communications to a diverse user community. These efforts have paid substantial dividends for our user communities by allowing us to target discipline specific community needs. The desired take-away from this presentation will be an improved understanding of how EOSDIS has approached, and in several instances achieved, removing or lowering the barriers to data access and use. As we look ahead to more complex Earth science missions, EOSDIS will continue to focus on our user communities, both broad and specialized, so that our overall data system can continue to serve the needs of science and applications users.

communications↗

Incorporating Parallel Computing into the Goddard Earth Observing System Data Assimilation System (GEOS DAS)

Atmospheric data assimilation is a method of combining actual observations with model forecasts to produce a more accurate description of the earth system than the observations or forecast alone can provide. The output of data assimilation, sometimes called the analysis, are regular, gridded datasets of observed and unobserved variables. Analysis plays a key role in numerical weather prediction and is becoming increasingly important for climate research. These applications, and the need for timely validation of scientific enhancements to the data assimilation system pose computational demands that are best met by distributed parallel software. The mission of the NASA Data Assimilation Office (DAO) is to provide datasets for climate research and to support NASA satellite and aircraft missions. The system used to create these datasets is the Goddard Earth Observing System Data Assimilation System (GEOS DAS). The core components of the the GEOS DAS are: the GEOS General Circulation Model (GCM), the Physical-space Statistical Analysis System (PSAS), the Observer, the on-line Quality Control (QC) system, the Coupler (which feeds analysis increments back to the GCM), and an I/O package for processing the large amounts of data the system produces (which will be described in another presentation in this session). The discussion will center on the following issues: the computational complexity for the whole GEOS DAS, assessment of the performance of the individual elements of GEOS DAS, and parallelization strategy for some of the components of the system.

Larson, Jay W.↗

User requirements for NASA data base management systems. Part 1: Oceanographic discipline

Generic oceanographic user requirements were collected and analyzed for use in developing a general multipurpose data base management system for future missions of the Office of Space and Terrestrial Applications (OSTA) of NASA. The collection of user requirements involved; studying the state-of-the-art technology in data base management systems; analyzing the results of related studies; formulating a viable and diverse list of scientists to be interviewed; developing a presentation format and materials; and interviewing oceanographic data users. More effective data management systems are needed to handle the increasing influx of data.

Fujimoto, B.↗