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 325 records · Page 18
All sourcesNASA NTRSDOE OSTI
NASA NTRS2003

Deploying Object Oriented Data Technology to the Planetary Data System

How do you provide more than 350 scientists and researchers access to data from every instrument in Odyssey when the data is curated across half a dozen institutions and in different formats and is too big to mail on a CD-ROM anymore? The Planetary Data System (PDS) faced this exact question. The solution was to use a metadata-based middleware framework developed by the Object Oriented Data Technology task at NASA s Jet Propulsion Laboratory. Using OODT, PDS provided - for the first time ever - data from all mission instruments through a single system immediately upon data delivery.

Kelly, S.↗
NASA NTRS1991

The planetary data system

Nasa has sponsored the development of the Planetary Data System (PDS) in order to preserve the scientific returns from past and future planeary missions and to make those data readily accessible in a well-documented form. The PDS encompasses all planetary data, but also provides a distributed, discipline-oriented architecture to best serve the needs of the diverse planetary sciences user-community. It is the intention of the PDS to ease and promote the analysis of planetary data through the development and application of data and documentation standards, basic analysis tools, and technology.

Lee, Steven W.↗
NASA NTRS1986

Crash response data system for the controlled impact demonstration (CID) of a full-scale transport aircraft

A study involving the Controlled Impact Demonstration (CID) of a transport category aircraft was conducted with the objective to improve occupant safety during survivable crash scenarios. in connection with this study, the first remotely-piloted Full-Scale Transport aircraft was purposely crashed into the California desert. The program was initated to demonstrate the effectiveness of an imisting kerosene (AMK), a fuel additive emplyed to reduce postcrash fires. The unmanned CID flight carried 73 life-like flight research dummies, multiple experiments, high-speed interior cabin cameras, and the high-environment Crash Response Data System. Attention is given to the design approach, a block diagram of the Crash Response Data System, measurements, the digital data subsystem, signal conditioning, telemetry, on-board recording, the power subsystem, preflight checkout and calibration, and aspects of system qualification.

Calloway, R. S.↗
NASA NTRS1985

Space Station data system analysis/architecture study. Task 1: Functional requirements definition, DR-5

The initial task in the Space Station Data System (SSDS) Analysis/Architecture Study is the definition of the functional and key performance requirements for the SSDS. The SSDS is the set of hardware and software, both on the ground and in space, that provides the basic data management services for Space Station customers and systems. The primary purpose of the requirements development activity was to provide a coordinated, documented requirements set as a basis for the system definition of the SSDS and for other subsequent study activities. These requirements should also prove useful to other Space Station activities in that they provide an indication of the scope of the information services and systems that will be needed in the Space Station program. The major results of the requirements development task are as follows: (1) identification of a conceptual topology and architecture for the end-to-end Space Station Information Systems (SSIS); (2) development of a complete set of functional requirements and design drivers for the SSIS; (3) development of functional requirements and key performance requirements for the Space Station Data System (SSDS); and (4) definition of an operating concept for the SSIS. The operating concept was developed both from a Space Station payload customer and operator perspective in order to allow a requirements practicality assessment.

Source record↗
NASA NTRS2013

Smarter Earth Science Data System

The explosive growth in Earth observational data in the recent decade demands a better method of interoperability across heterogeneous systems. The Earth science data system community has mastered the art in storing large volume of observational data, but it is still unclear how this traditional method scale over time as we are entering the age of Big Data. Indexed search solutions such as Apache Solr (Smiley and Pugh, 2011) provides fast, scalable search via keyword or phases without any reasoning or inference. The modern search solutions such as Googles Knowledge Graph (Singhal, 2012) and Microsoft Bing, all utilize semantic reasoning to improve its accuracy in searches. The Earth science user community is demanding for an intelligent solution to help them finding the right data for their researches. The Ontological System for Context Artifacts and Resources (OSCAR) (Huang et al., 2012), was created in response to the DARPA Adaptive Vehicle Make (AVM) programs need for an intelligent context models management system to empower its terrain simulation subsystem. The core component of OSCAR is the Environmental Context Ontology (ECO) is built using the Semantic Web for Earth and Environmental Terminology (SWEET) (Raskin and Pan, 2005). This paper presents the current data archival methodology within a NASA Earth science data centers and discuss using semantic web to improve the way we capture and serve data to our users.

data center↗
NASA NTRS1982

Thematic mapper flight model preshipment review data package. Volume 3, part C: System data

Failure reports for flight model-1 of the thematic mapper are summarized showing the symptom and cause of failure as well as the corrective action taken. Each report is keyed to the major subsystem against which the failure occurred. Requests for deviation/waiver are listed by number, description, and current status. Copies of engineering proposals are included.

Source record↗
NASA NTRS1983

A ground test measurement system for the shuttle entry air data system

The Ground Test Measurement System (GTMS) for determining vacuum decay leak rate within the orifice tubing assembly of SEADS is described. The system can also monitor the absolute pressure in the tubing assembly under certain conditions. The GTMS determines leak rate by measuring vacuum-pressure decay which can be converted into leakage flow rate. Results of performance testing and operation of the GTMS are given.

Schutte, P. C.↗
NASA NTRS1983

The NASA data systems standardization program - Rationale and scope

A simple, top level logical reference model of the NASA Space Transportation System's end-to-end data system is being developed which can identify the functions and services of the system. Each function or service may be mapped into specific physical subsystems, so that interface relationships are evident and 'standard' protocols may be identified for development. By means of this interface standardization, subsystems can be designed not only independently and in parallel, but with confidence that when the subsystems are aggregated, the end-to-end system will operate efficiently and at low cost. This standardization effort has thus far been principally directed toward space-to-ground communications links.

Smylie, R. E.↗
NASA NTRS1982

Channel coding in the space station data system network

A detailed discussion of the use of channel coding for error correction, privacy/secrecy, channel separation, and synchronization is presented. Channel coding, in one form or another, is an established and common element in data systems. No analysis and design of a major new system would fail to consider ways in which channel coding could make the system more effective. The presence of channel coding on TDRS, Shuttle, the Advanced Communication Technology Satellite Program system, the JSC-proposed Space Operations Center, and the proposed 30/20 GHz Satellite Communication System strongly support the requirement for the utilization of coding for the communications channel. The designers of the space station data system have to consider the use of channel coding.

Healy, T.↗
NASA NTRS1979

A real-time ISEE data system

A real time International Sun Earth Explorer (ISEE) data system directed toward the prediction of geomagnetic substorms and storms is discussed in detail. Such a system may allow up to 60 minutes or more, advance warning of magnetospheric substorms and up to 30 minute warnings of geomagnetic storms induced by high speed streams and solar flares. The proposed system utilizes existing capabilities of several agencies thereby minimizing costs.

Tsurutani, B. T.↗
NASA NTRS1985

Space station data system analysis/architecture study. Task 4: System definition report

Functional/performance requirements for the Space Station Data System (SSDS) are analyzed and architectural design concepts are derived and evaluated in terms of their performance and growth potential, technical feasibility and risk, and cost effectiveness. The design concepts discussed are grouped under five major areas: SSDS top-level architecture overview, end-to-end SSDS design and operations perspective, communications assumptions and traffic analysis, onboard SSDS definition, and ground SSDS definition.

Source record↗
NASA NTRS1974

Real time computer data system for the 40 x 80 ft wind tunnel facility at Ames Research Center

The wind tunnel realtime computer system is a distributed data gathering system that features a master computer subsystem, a high speed data gathering subsystem, a quick look dynamic analysis and vibration control subsystem, an analog recording back-up subsystem, a pulse code modulation (PCM) on-board subsystem, a communications subsystem, and a transducer excitation and calibration subsystem. The subsystems are married to the master computer through an executive software system and standard hardware and FORTRAN software interfaces. The executive software system has four basic software routines. These are the playback, setup, record, and monitor routines. The standard hardware interfaces along with the software interfaces provide the system with the capability of adapting to new environments.

Cambra, J. M.↗
NASA NTRS1977

The screwworm eradication data system archives

The archives accumulated during 1 year of operation of the Satellite Temperature-Monitoring System during development of the Screwworm Eradication Data System are reported. Brief descriptions of all the kinds of tapes, as well as their potential uses, are presented. Reference is made to other documents that explain the generation of these data.

Barnes, C. M.↗