SEARCH · Search NASA
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.
The purpose of this document is to assist NASA Project personnel in the preparation of their Project Data Management Plans (PDMP) in accordance with NASA Management Instruction (NMI) 8030.3A. In addition, this report summarizes the scope of a PDMP and establishes important aspects that must be addressed for the long term management and archiving of the data from a NASA space flight investigation.
Airborne/spaceborn computer design and techniques for space shuttle data management systems
Computer trades and analyses of selected Power Module Data Management Subsystem issues to support concurrent inhouse MSFC Power Study are provided. The charts which summarize and describe the results are presented. Software requirements and definitions are included.
The data management procedures for tiepoint registration, pre and post processing, and "ICD116' are described. With each procedure description, the pertinent execs are listed and purposes defined. An example run of each of the 32 execs is included with user inputs identified.
This document establishes the Configuration and Data Management Plan for the Thermophysics Facilities Branch (TSF) and describes the implementation of the plan within the organization. Its intent is to control and document changes to facility hardware, software, and facility operating procedures; to control changes to Quality System documents; to ensure that all documents and drawings are current; and to provide for quick retrieval of facility information and documentation while safeguarding original records and documents.
The high volume of Earth Observing System data has proven to be challenging to manage for data centers and users alike. At the Goddard Earth Sciences Distributed Active Archive Center (GES DAAC), about 1 TB of new data are archived each day. Distribution to users is also about 1 TB/day. A substantial portion of this distribution is MODIS calibrated radiance data, which has a wide variety of uses. However, much of the data is not useful for a particular user's needs: for example, ocean color users typically need oceanic pixels that are free of cloud and sun-glint. The GES DAAC is using a simple Bayesian classification scheme to rapidly classify each pixel in the scene in order to support several experimental content-based data services for near-real-time MODIS calibrated radiance products (from Direct Readout stations). Content-based subsetting would allow distribution of, say, only clear pixels to the user if desired. Content-based subscriptions would distribute data to users only when they fit the user's usability criteria in their area of interest within the scene. Content-based cache management would retain more useful data on disk for easy online access. The classification may even be exploited in an automated quality assessment of the geolocation product. Though initially to be demonstrated at the GES DAAC, these techniques have applicability in other resource-limited environments, such as spaceborne data systems.
A simulation program for the flow of data through the Data Management System of Spacelab and Space Shuttle was presented. The science, engineering, command and guidance, navigation and control data were included. The programming language used was General Purpose Simulation System V (OS). The science and engineering data flow was modeled from its origin at the experiments and subsystems to transmission from Space Shuttle. Command data flow was modeled from the point of reception onboard and from the CDMS Control Panel to the experiments and subsystems. The GN&C data flow model handled data between the General Purpose Computer and the experiments and subsystems. Mission 18 was the particular flight chosen for simulation. The general structure of the program is presented, followed by a user's manual. Input data required to make runs are discussed followed by identification of the output statistics. The appendices contain a detailed model configuration, program listing and results.
Described in detail are: (1) results obtained in modifying the onboard data management system software to a multiprocessor fault tolerant system; (2) a functional description of the prototype buffer I/O units; (3) description of modification to the ACADC and stimuli generating unit of the DTS; and (4) summaries and conclusions on techniques implemented in the rack and prototype buffers. Also documented is the work done in investigating techniques of high speed (5 Mbps) digital data transmission in the data bus environment. The application considered is a multiport data bus operating with the following constraints: no preferred stations; random bus access by all stations; all stations equally likely to source or sink data; no limit to the number of stations along the bus; no branching of the bus; and no restriction on station placement along the bus.
The functions and data base structures that the data base manager will be responsible for maintaining are documented. All normal and error sequences are included.
Contractor data package for administration of procurement and contracting of Voyager spacecraft systems
Computer program requirements for onboard checkout and data management system of Saturn/Apollo application program
Supervisory computer program for onboard checkout and data management system of Saturn/Apollo application program
Development and characteristics of executive software for application to space shuttle data management system
The MIRADS is a generalized data management system. The feasibility of using MIRADS by the State of Alabama Air Pollution Control Commission is explored. The State's enforcement management system and the emission inventory system were implemented into MIRADS.
The simulation program of the science and engineering data management system for the space shuttle is presented. The programming language used was General Purpose Simulation System V (OS). The data flow was modeled from its origin at the experiments or subsystems to transmission from the space shuttle. Mission 18 was the particular flight chosen for simulation. First, the general structure of the program is presented and the trade studies which were performed are identified. Inputs required to make runs are discussed followed by identification of the output statistics. Some areas for model modifications are pointed out. A detailed model configuration, program listing and results are included.
Technical description and systems engineering contractor data package for Voyager spacecraft
Manufacturing contractor data project for Voyager spacecraft systems
Test and mission operations contractor data package for Voyager spacecraft