Search NASA⌕ Search

SEARCH · Search NASA

Results for “data 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 73 records · Page 4
All sourcesNASA NTRSDOE OSTI
NASA NTRS1985

The orbiter air data system

Air data parameters are required during Orbiter atmospheric entry for use by the autoguidance, navigation, and flight control systems, and for crew displays. Conventional aircraft calibrations of the Orbiter air data system were not practicable for the Space Shuttle, therefore extensive wind tunnel testing was required to give confidence in the preflight calibrations. Many challenges became apparent as the program developed; in the overall system design, in the wind tunnel testing program, in the implementation of the air data system calibration, and in the use of the flight data to modify the wind tunnel results. These challenges are discussed along with the methods used to solve the problems.

Hillje, E. R.↗
NASA NTRS1986

The SIR-C ground data system: Digital processor, data products, information flow

The SIR-C (Shuttle Imaging Radar) instrument will collect both C-Band and L-Band data with each frequency band consisting of direct (HH or VV) and cross-polarized (HV or VH) data. Considering all possible combinations as many as eight different data channels will be available for any given target area. This data will be digitized and formatted on-board for direct downlink via the Tracking and Data Relay Satellite System (TDRSS), or it will be buffered through on-board high density digital recorders for storage or transmission when TDRSS is available. The data is received by the TDRSS ground station at White Sands and is nominally relayed via DOMSAT to the high data rate recording facility at GSFC. The tapes are then shipped to JPL for processing into imagery and eventual distribution to the SIR-C investigators.

Curlander, John C.↗
NASA NTRS1985

Determining Availability Characteristics of DSN Data Systems Using Discrepancy Report Data

A reasonably economical way was developed to determine availability characteristics of Deep Space Network (DSN) data systems, subsystems, and assemblies using the DSN discrepancy report (DR) data base and DSN operating schedule and history data bases. Operating mean time between failures (OMTBF), operating mean time to restore service (OMTTRS), and operating functional availability (OFA) can be computed by year, by system, by subsystem, by assembly, and by station. The effort required to produce the desired reports is described, specific data on the telemetry, command, and tracking systems are presented, and major contributors to system outages are identified. Future improvements in preparing and analyzing DR data are also outlined to enhance their use in correcting conditions that lead to outages.

Ruskin, A. M.↗
NASA NTRS2011

PDS4: Developing the Next Generation Planetary Data System

The Planetary Data System (PDS) is in the midst of a major upgrade to its system. This upgrade is a critical modernization of the PDS as it prepares to support the future needs of both the mission and scientific community. It entails improvements to the software system and the data standards, capitalizing on newer, data system approaches. The upgrade is important not only for the purpose of capturing results from NASA planetary science missions, but also for improving standards and interoperability among international planetary science data archives. As the demands of the missions and science community increase, PDS is positioning itself to evolve and meet those demands.

Crichton, D.↗
NASA NTRS1986

DIOGENES: Expert system for extraction of data system requirements

AA The initial operations concept expresses information about system objectives, and defines the system users, system interfaces, and operational performance constraints. We have developed a prototype expert system which has established the feasibility of automating a scenario-driven methodology for deriving top-level specifications and preliminary designs for user data systems. This scenario-driven methodology uses an initial design, an initial operations concept, and user scenarios as the starting point for system definition. The top-level initial design is a functional description of the system in the form of an annotated data flow diagram. The initial operations concept expresses informationabout system objectives, and defines the system users, system interfaces, and operational performance constraints. The user scenarios are detailed time-lined descriptions of user activities, developed by prospective end users. These scenarios, along with the initial design and operations concept, are analyzed and iterated by the expert system to form a consistent set. The resulting User Scenario-Operation Set plays a key role in the development of requirements and system tests.

Hobbs, Robert W.↗
NASA NTRS1993

Data Systems Dynamic Simulator

The Data System Dynamic Simulator (DSDS) is a discrete event simulation tool. It was developed for NASA for the specific purpose of evaluating candidate architectures for data systems of the Space Station era. DSDS provides three methods for meeting this requirement. First, the user has access to a library of standard pre-programmed elements. These elements represent tailorable components of NASA data systems and can be connected in any logical manner. Secondly, DSDS supports the development of additional elements. This allows the more sophisticated DSDS user the option of extending the standard element set. Thirdly, DSDS supports the use of data streams simulation. Data streams is the name given to a technique that ignores packet boundaries, but is sensitive to rate changes. Because rate changes are rare compared to packet arrivals in a typical NASA data system, data stream simulations require a fraction of the CPU run time. Additionally, the data stream technique is considerably more accurate than another commonly-used optimization technique.

Rouff, Christopher↗
NASA NTRS1979

Portable data system

Compact system for data recording, manipulation, and transmission uses readily available components. Data system originally designed for high-altitude research is used with appropriate sensors to monitor transportation systems, biomedical data, weather stations, mineral exploration equipment, and various other tasks.

Dix, M.↗
NASA NTRS2015

Taming Big Data Variety in the Earth Observing System Data and Information System

Although the volume of the remote sensing data managed by the Earth Observing System Data and Information System is formidable, an oft-overlooked challenge is the variety of data. The diversity in satellite instruments, science disciplines and user communities drives cost as much or more as the data volume. Several strategies are used to tame this variety: data allocation to distinct centers of expertise; a common metadata repository for discovery, data format standards and conventions; and services that further abstract the variations in data.

Information Systems↗
NASA NTRS2009

Using XML Configuration-Driven Development to Create a Customizable Ground Data System

The Mission data Processing and Control Subsystem (MPCS) is being developed as a multi-mission Ground Data System with the Mars Science Laboratory (MSL) as the first fully supported mission. MPCS is a fully featured, Java-based Ground Data System (GDS) for telecommand and telemetry processing based on Configuration-Driven Development (CDD). The eXtensible Markup Language (XML) is the ideal language for CDD because it is easily readable and editable by all levels of users and is also backed by a World Wide Web Consortium (W3C) standard and numerous powerful processing tools that make it uniquely flexible. The CDD approach adopted by MPCS minimizes changes to compiled code by using XML to create a series of configuration files that provide both coarse and fine grained control over all aspects of GDS operation.

Nash, Brent↗
NASA NTRS1992

Functional requirements document for the Earth Observing System Data and Information System (EOSDIS) Scientific Computing Facilities (SCF) of the NASA/MSFC Earth Science and Applications Division, 1992

Five scientists at MSFC/ESAD have EOS SCF investigator status. Each SCF has unique tasks which require the establishment of a computing facility dedicated to accomplishing those tasks. A SCF Working Group was established at ESAD with the charter of defining the computing requirements of the individual SCFs and recommending options for meeting these requirements. The primary goal of the working group was to determine which computing needs can be satisfied using either shared resources or separate but compatible resources, and which needs require unique individual resources. The requirements investigated included CPU-intensive vector and scalar processing, visualization, data storage, connectivity, and I/O peripherals. A review of computer industry directions and a market survey of computing hardware provided information regarding important industry standards and candidate computing platforms. It was determined that the total SCF computing requirements might be most effectively met using a hierarchy consisting of shared and individual resources. This hierarchy is composed of five major system types: (1) a supercomputer class vector processor; (2) a high-end scalar multiprocessor workstation; (3) a file server; (4) a few medium- to high-end visualization workstations; and (5) several low- to medium-range personal graphics workstations. Specific recommendations for meeting the needs of each of these types are presented.

Botts, Michael E.↗