Search NASA⌕ Search

SEARCH · Search NASA

Results for “Data Driven Systems”

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 55 records · Page 3

The Unintended Consequences of Focusing on Human Error (And How You Can Help)

The literature on human performance is rich with findings of cognitive failures and methods to identify, label, and measure them. In many real-world contexts, however, outcomes are driven far more by successful than failed cognition. Designers of systems intended for human use, in an effort to be “data driven,” rely upon findings from the cognitive performance literature to inform their system designs. When most available data are about human error, data-driven designs focus on the human primarily as a source of failure. Designs intended to support or replace humans often fail to acknowledge or understand the capabilities that humans routinely contribute to successful performance. Consequently, designs intended to “protect” the system from “error-prone” humans can design-out the capability for the human to effectively intervene or adapt. The development of paradigms to study successful human performance represents a significant and largely untapped opportunity for research in cognition.

Jon Holbrook↗

Monitoring real-time navigation processes using the automated reasoning tool (ART)

An expert system is described for monitoring and controlling navigation processes in real-time. The ART-based system features data-driven computation, accommodation of synchronous and asynchronous data, temporal modeling for individual time intervals and chains of time intervals, and hypothetical reasoning capabilities that consider alternative interpretations of the state of navigation processes. The concept is illustrated in terms of the NAVEX system for monitoring and controlling the high speed ground navigation console for Mission Control at Johnson Space Center. The reasoning processes are outlined, including techniques used to consider alternative data interpretations. Installation of the system has permitted using a single operator, instead of three, to monitor the ascent and entry phases of a Shuttle mission.

Maletz, M. C.↗

Discrete Event Simulation-Based Timeline Validation Using R2U2

The Gateway Vehicle Systems Manager (VSM), the top-level software control system in a distributed, hierarchical Autonomous System Management Architecture is, like most modern spacecraft software control systems, heavily data-driven. For example, schedules (timelines) will be developed on the ground and, due to the high degree of autonomy, contain complex procedures involving conditional branching, variable timing, and resource contention resolution. In order to verify that an uploaded timeline will function correctly, it is necessary to explore the feasible set of possible executions. While it is possible to test a timeline using a mission simulation, the complexity of the system and duration of a timeline limits the number of trials and therefore the test coverage. To address this problem, the VSM team is using a discrete event system model that can rapidly generate from a timeline sets of event sequences using Monte Carlo techniques. To achieve rapid and trustworthy checking of the event sequences, we use an offline version of the runtime model checking tool R2U2. This presentation describes the approach the VSM team is using to implement the discrete event simulation and evaluate event sequences using R2U2. The presentation will discuss: 1. Description of the timelines by VSM in the context of VSM operations 2. Expansion of a timeline into a sequence of atomic events 3. Adjustment, in the Monte Carlo environment, of an event sequence to account for uncertainty, external events, and failures 4. Definition of R2U2 input and mission-time linear temporal logic files 5. Generation and use of R2U2 verdict sequences 6. Lessons learned and future work

Verification↗

File Specification for MERRA-2 Stratospheric Composition Reanalysis of Aura MLS (M2-SCREAM)

This document provides a brief description of the output collections from the MERRA-2 Stratospheric Composition Reanalysis of the Aura Microwave Limb Sounder (M2-SCREAM) produced at NASA’s Global Modeling and Assimilation Office. These data are generated by assimilating retrievals from the Microwave Limb Sounder (MLS) and the Ozone Monitoring Instrument (OMI) into the Global Earth Observing System (GEOS) Constituent Data Assimilation System (CoDAS) driven by meteorological fields from MERRA-2. M2-SCREAM assimilates hydrochloric acid (HCl), nitric acid (HNO3), stratospheric water vapor (H2O), nitrous oxide (N2O) and ozone with a system equipped with a version of the GEOS general circulation model and a stratospheric chemistry model, StratChem. Assimilated fields are provided globally at 0.5° by 0.625° resolution at three-hourly frequencies from 2004/09/01 to 2021. Assimilation uncertainties for each of the assimilated constituents are calculated from the CoDAS statistical output (Wargan et al., 2022) and provided as global full-resolution three-dimensional monthly files.

Krzysztof Wargan↗

Multifunction display system

The design and characteristics of a multifunction display system are discussed. The system is a general purpose, time-shared, electro-optical display driven by onboard data management systems. It is capable of presenting information in forms such as alphanumerics, symbolics, and graphics, separately or in combination. The components of the system are: (1) data terminal simulator/input loader, (2) keyboard controller, (3) CRT display indicator, and (4) programmable symbol generator.

Kendall, K.↗

A Comparison of the Lower Stratospheric Age-Spectra Derived from a General Circulation Model and Two Data Assimilation Systems

We use kinematic and diabatic back trajectory calculations, driven by winds from a general circulation model (GCM) and two different data assimilation systems (DAS), to compute the age spectrum at three latitudes in the lower stratosphere. The age-spectra are compared to chemical transport model (CTM) calculations, and the mean ages from all of these studies are compared to observations. The age spectra computed using the GCM winds show a reasonably isolated tropics in good agreement with observations; however, the age spectra determined from the DAS differ from the GCM spectra. For the DAS diabatic trajectory calculations there is too much exchange between the tropics and mid-latitudes. The age spectrum is thus too broad and the tropical mean age is too old as a result of mixing older mid latitude air with tropical air. Likewise the mid latitude mean age is too young due to the in mixing of tropical air. The DAS kinematic trajectory calculations show excessive vertical dispersion of parcels in addition to excessive exchange between the tropics and mid latitudes. Because air is moved rapidly to the troposphere from the vertical dispersion, the age spectrum is shifted toward the young side. The excessive vertical and meridional dispersion compensate in the kinematic case giving a reasonable tropical mean age. The CTM calculation of the age spectrum using the DAS winds shows the same vertical and meridional dispersive characteristics of the kinematic trajectory calculation. These results suggest that the current DAS products will not give realistic trace gas distributions for long integrations; they also help explain why the extra tropical mean ages determined in a number of previous DAS driven CTM s are too young compared with observations. Finally, we note trajectory-generated age spectra . show significant age anomalies correlated with the seasonal cycles. These anomalies can be linked to year-to-year variations in the tropical heating rate. The anomalies are suppressed in the CTM spectra suggesting that the CTM transport scheme is too diffusive.

Schoeberl, Mark R.↗

Resource Allocation Planning Helper (RALPH): Lessons learned

The current task of Resource Allocation Process includes the planning and apportionment of JPL's Ground Data System composed of the Deep Space Network and Mission Control and Computing Center facilities. The addition of the data driven, rule based planning system, RALPH, has expanded the planning horizon from 8 weeks to 10 years and has resulted in large labor savings. Use of the system has also resulted in important improvements in science return through enhanced resource utilization. In addition, RALPH has been instrumental in supporting rapid turn around for an increased volume of special what if studies. The status of RALPH is briefly reviewed and important lessons learned from the creation of an highly functional design team are focused on through an evolutionary design and implementation period in which an AI shell was selected, prototyped, and ultimately abandoned, and through the fundamental changes to the very process that spawned the tool kit. Principal topics include proper integration of software tools within the planning environment, transition from prototype to delivered to delivered software, changes in the planning methodology as a result of evolving software capabilities and creation of the ability to develop and process generic requirements to allow planning flexibility.

Durham, Ralph↗

System control module diagnostic Expert Assistant

The Orbiter EXperiments (OEX) Program was established by NASA's Office of Aeronautics and Space Technology (OAST) to accomplish the precise data collection necessary to support a complete and accurate assessment of Space Transportation System (STS) Orbiter performance during all phases of a mission. During a mission, data generated by the various experiments are conveyed to the OEX System Control Module (SCM) which arranges for and monitors storage of the data on the OEX tape recorder. The SCM Diagnostic Expert Assistant (DEA) is an expert system which provides on demand advice to technicians performing repairs of a malfunctioning SCM. The DEA is a self-contained, data-driven knowledge-based system written in the 'C' Language Production System (CLIPS) for a portable micro-computer of the IBM PC/XT class. The DEA reasons about SCM hardware faults at multiple levels; the most detailed layer of encoded knowledge of the SCM is a representation of individual components and layouts of the custom-designed component boards.

Flores, Luis M.↗

HPT Clearance Control: Intelligent Engine Systems-Phase 1

The following work has been completed to satisfy the Phase I Deliverables for the "HPT Clearance Control" project under NASA GRC's "Intelligent Engine Systems" program: (1) Need for the development of an advanced HPT ACC system has been very clearly laid out, (2) Several existing and potential clearance control systems have been reviewed, (3) A scorecard has been developed to document the system, performance (fuel burn, range, payload, etc.), thermal, and mechanical characteristics of the existing clearance control systems, (4) Engine size and flight cycle selection for the advanced HPT ACC system has been reviewed with "large engine"/"long range mission" combination showing the most benefit, (5) A scoring criteria has been developed to tie together performance parameters for an objective, data driven comparison of competing systems, and (6) The existing HPT ACC systems have been scored based on this scoring system.

Source record↗

Large Field Visualization with Demand-Driven Calculation

We present a system designed for the interactive definition and visualization of fields derived from large data sets: the Demand-Driven Visualizer (DDV). The system allows the user to write arbitrary expressions to define new fields, and then apply a variety of visualization techniques to the result. Expressions can include differential operators and numerous other built-in functions, ail of which are evaluated at specific field locations completely on demand. The payoff of following a demand-driven design philosophy throughout becomes particularly evident when working with large time-series data, where the costs of eager evaluation alternatives can be prohibitive.

Moran, Patrick J.↗

Application of a PC based, real-time, data-aquisition system in rotorcraft wind-tunnel testing

Data has been acquired for a rotocraft test in the NASA Langley Transonic Dynamics Tunnel using a desktop data acquisition system. The system, which consists of an IBM Personal Computer AT (PC-AT) and an Omega Engineering OM-900 Stand-Alone Interface System, is well suited for acquiring high speed data on a limited number of channels. The data acquisition system and the interrupt driven software which provides the capability for near real-time cyclic data acquisition as well as data storage and display are described.

Wilbur, Matthew L.↗

GEOS-Carb III: Delivering Mature Carbon Flux and Concentration Datasets in Support of NASA's Carbon Monitoring System

The GEOS-Carb project seeks to make high quality, data-driven products that support NASA's Carbon Monitoring System Program. These include bottom-up land and ocean flux estimates along with fossil fuel emissions, all informed by satellite data and the MERRA-2 reanalysis. These flux data support atmospheric carbon products that include both simulations and data assimilation products. We show examples of this work and discuss applications to future mission planning.

Ott, L.↗

A Multi-mission Event-Driven Component-Based System for Support of Flight Software Development, ATLO, and Operations first used by the Mars Science Laboratory (MSL) Project

This viewgraph presentation reviews the architectural description of the Mission Data Processing and Control System (MPCS). MPCS is an event-driven, multi-mission ground data processing components providing uplink, downlink, and data management capabilities which will support the Mars Science Laboratory (MSL) project as its first target mission. MPCS is designed with these factors (1) Enabling plug and play architecture (2) MPCS has strong inheritance from GDS components that have been developed for other Flight Projects (MER, MRO, DAWN, MSAP), and are currently being used in operations and ATLO, and (3) MPCS components are Java-based, platform independent, and are designed to consume and produce XML-formatted data

Mission Data Processing and Control System (MPCS)↗

Adaptation of Control Center Software to Commerical Real-Time Display Applications

NASA-Marshall Space Flight Center (MSFC) is currently developing an enhanced Huntsville Operation Support Center (HOSC) system designed to support multiple spacecraft missions. The Enhanced HOSC is based upon a distributed computing architecture using graphic workstation hardware and industry standard software including POSIX, X Windows, Motif, TCP/IP, and ANSI C. Southwest Research Institute (SwRI) is currently developing a prototype of the Display Services application for this system. Display Services provides the capability to generate and operate real-time data-driven graphic displays. This prototype is a highly functional application designed to allow system end users to easily generate complex data-driven displays. The prototype is easy to use, flexible, highly functional, and portable. Although this prototype is being developed for NASA-MSFC, the general-purpose real-time display capability can be reused in similar mission and process control environments. This includes any environment depending heavily upon real-time data acquisition and display. Reuse of the prototype will be a straight-forward transition because the prototype is portable, is designed to add new display types easily, has a user interface which is separated from the application code, and is very independent of the specifics of NASA-MSFC's system. Reuse of this prototype in other environments is a excellent alternative to creation of a new custom application, or for environments with a large number of users, to purchasing a COTS package.

Collier, Mark D.↗

NASA Wrangler: Automated Cloud-Based Data Assembly in the RECOVER Wildfire Decision Support System

NASA Wrangler is a loosely-coupled, event driven, highly parallel data aggregation service designed to take advantageof the elastic resource capabilities of cloud computing. Wrangler automatically collects Earth observational data, climate model outputs, derived remote sensing data products, and historic biophysical data for pre-, active-, and post-wildfire decision making. It is a core service of the RECOVER decision support system, which is providing rapid-response GIS analytic capabilities to state and local government agencies. Wrangler reduces to minutes the time needed to assemble and deliver crucial wildfire-related data.

decision support↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challange

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), responsible for project management and flight operations; Orbital Sciences Corporation (OSC), spacecraft builder and responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), responsible for science planning and operations. As a cost-capped mission, one of Dawn s implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL s ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL s GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project s commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to an overall systems engineering process and fundamental systems engineering practices: decomposition of the project request into manageable requirements; definition of a structured yet flexible development process; integration of multiple ground disciplines and experts into a focused team effort; in-process risk management; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

systems engineering↗

Zero to Integration in Eight Months, the Dawn Ground Data System Engineering Challenge

The Dawn Project has presented the Ground Data System (GDS) with technical challenges driven by cost and schedule constraints commonly associated with National Aeronautics and Space Administration (NASA) Discovery Projects. The Dawn mission consists of a new and exciting Deep Space partnership among: the Jet Propulsion Laboratory (JPL), manages the project and is responsible for flight operation; Orbital Sciences Corporation (OSC), is the spacecraft builder and is responsible for flight system test and integration; and the University of California, at Los Angeles (UCLA), is responsible for science planning and operations. As a cost-capped mission, one of Dawn's implementation strategies is to leverage from both flight and ground heritage. OSC's ground data system is used for flight system test and integration as part of the flight heritage strategy. Mission operations, however, are to be conducted with JPL's ground system. The system engineering challenge of dealing with two heterogeneous ground systems emerged immediately. During the first technical interchange meeting between the JPL's GDS Team and OSC's Flight Software Team, August 2003, the need to integrate the ground system with the flight software was brought to the table. This need was driven by the project's commitment to enable instrument engineering model integration in a spacecraft simulator environment, for both demonstration and risk mitigation purposes, by April 2004. This paper will describe the system engineering approach that was undertaken by JPL's GDS Team in order to meet the technical challenge within a non-negotiable eight-month schedule. Key to the success was adherence to fundamental systems engineering practices: decomposition of the project request into manageable requirements; integration of multiple ground disciplines and experts into a focused team effort; definition of a structured yet flexible development process; definition of an in-process risk reduction plan; and aggregation of the intermediate products to an integrated final product. In addition, this paper will highlight the role of lessons learned from the integration experience. The lessons learned from an early GDS deployment have served as the foundation for the design and implementation of the Dawn Ground Data System.

Ground Data System (GDS)↗

Satellite Data Processing System (SDPS) users manual V1.0

SDPS is a menu driven interactive program designed to facilitate the display and output of image and line-based data sets common to telemetry, modeling and remote sensing. This program can be used to display up to four separate raster images and overlay line-based data such as coastlines, ship tracks and velocity vectors. The program uses multiple windows to communicate information with the user. At any given time, the program may have up to four image display windows as well as auxiliary windows containing information about each image displayed. SDPS is not a commercial program. It does not contain complete type checking or error diagnostics which may allow the program to crash. Known anomalies will be mentioned in the appropriate section as notes or cautions. SDPS was designed to be used on Sun Microsystems Workstations running SunView1 (Sun Visual/Integrated Environment for Workstations). It was primarily designed to be used on workstations equipped with color monitors, but most of the line-based functions and several of the raster-based functions can be used with monochrome monitors. The program currently runs on Sun 3 series workstations running Sun OS 4.0 and should port easily to Sun 4 and Sun 386 series workstations with SunView1. Users should also be familiar with UNIX, Sun workstations and the SunView window system.

Caruso, Michael↗