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 307 records · Page 17

Space station data system analysis/architecture study. Task 1: Functional requirements definition, DR-5. Appendix: Requirements data base

Appendix A contains data that characterize the system functions in sufficient depth as to determine the requirements for the Space Station Data System (SSDS). This data is in the form of: (1) top down traceability report; (2) bottom up traceability report; (3) requirements data sheets; and (4) cross index of requirements paragraphs of the source documents and the requirements numbers. A data base users guide is included that interested parties can use to access the requirements data base and get up to date information about the functions.

Source record↗

NASA Pilot Land Data System

Project development and planning for a Pilot Land Data System (PLDS) are discussed. The PLDS supplies basic information, data management, and data processing capabilities to the land research community. Topics on design and implementation, user requirements, and project management are examined. The scenarios developed thusfar are also included.

Estes, J. E.↗

Office of Space Tracking and Data Systems

A brief overview of the Office of Space Tracking and Data Systems support functions is given along with a description of the Spaceflight Tracking and Data Network and the Deep Space Network. Preparations for upcoming missions, wideband communications, and Tracking and Data Relay Satellite Systems are discussed.

Source record↗

User Metrics in NASA Earth Science Data Systems

This presentation the collection and use of user metrics in NASA's Earth Science data systems. A variety of collection methods is discussed, with particular emphasis given to the American Customer Satisfaction Index (ASCI). User sentiment on potential use of cloud computing is presented, with generally positive responses. The presentation also discusses various forms of automatically collected metrics, including an example of the relative usage of different functions within the Giovanni analysis system.

user metrics↗

Digital Equivalent Data System for XRF Labeling of Objects

A digital equivalent data system (DEDS) is a system for identifying objects by means of the x-ray fluorescence (XRF) spectra of labeling elements that are encased in or deposited on the objects. As such, a DEDS is a revolutionary new major subsystem of an XRF system. A DEDS embodies the means for converting the spectral data output of an XRF scanner to an ASCII alphanumeric or barcode label that can be used to identify (or verify the assumed or apparent identity of) an XRF-scanned object. A typical XRF spectrum of interest contains peaks at photon energies associated with specific elements on the Periodic Table (see figure). The height of each spectral peak above the local background spectral intensity is proportional to the relative abundance of the corresponding element. Alphanumeric values are assigned to the relative abundances of the elements. Hence, if an object contained labeling elements in suitably chosen proportions, an alphanumeric representation of the object could be extracted from its XRF spectrum. The mixture of labeling elements and for reading the XRF spectrum would be compatible with one of the labeling conventions now used for bar codes and binary matrix patterns (essentially, two-dimensional bar codes that resemble checkerboards). A further benefit of such compatibility is that it would enable the conversion of the XRF spectral output to a bar or matrix-coded label, if needed. In short, a process previously used only for material composition analysis has been reapplied to the world of identification. This new level of verification is now being used for "authentication."

Schramm, Harry F.↗

NASA/Ames Research Center DC-8 data system

In-flight facility data acquisition, distribution, and recording on the NASA Ames Research Center (ARC) DC-8 are performed by the Data Acquisition and Distribution System (DADS). Navigational and environmental data collected by the DADS are converted to engineering units and distributed real-time to investigator stations once per second. Selected engineering units data are printed and displayed on closed circuit television monitors throughout flights. An in-flight graphical display of the DC-8 flight track (with barbs indicating wind direction and magnitude) has recently been added to the DADS capabilities. Logging of data run starts/stops and commentary from the mission director are also provided. All data are recorded to hard disk in-flight and archived to tape medium post-flight. Post-flight, hard copies of the track map and mission director's log are created by the DADS. The DADS is a distributed system consisting of a data subsystem, an Avionic Serial Data-to-VMEbus (ASD2VME) subsystem, and a host subsystem. Each subsystem has a dedicated central processing unit (CPU) and is capable of stand-alone operation. All three subsystems are housed in a single 20-slot VME chassis and communicate with each other over the VMEbus. The data and host subsystems are briefly discussed, and the DC-8 DADS internal configuration and system block diagram are presented.

Cherniss, S. C.↗

NASA End-to-End Data System /NEEDS/ information adaptive system - Performing image processing onboard the spacecraft

The Information Adaptive System (IAS) is an element of the NASA End-to-End Data System (NEEDS) Phase II and is focused toward onbaord image processing. Since the IAS is a data preprocessing system which is closely coupled to the sensor system, it serves as a first step in providing a 'Smart' imaging sensor. Some of the functions planned for the IAS include sensor response nonuniformity correction, geometric correction, data set selection, data formatting, packetization, and adaptive system control. The inclusion of these sensor data preprocessing functions onboard the spacecraft will significantly improve the extraction of information from the sensor data in a timely and cost effective manner and provide the opportunity to design sensor systems which can be reconfigured in near real time for optimum performance. The purpose of this paper is to present the preliminary design of the IAS and the plans for its development.

Kelly, W. L.↗

Moving Away from Ones and Zeros, Designing a Ground Data System Based on Higher Levels of Abstraction

Previous JPL ground systems have been designed with the Ground Data System (GDS) engineer in mind. The focus on these systems has been on packaging and delivery of low level information (frames, packets, telemetry values) to the end user. It was not that long ago when project teams would be huddled over a workstation, examining crude displays of telemetry bits organized in various ways, trying to determine the status of a spacecraft. Understanding the data often required additional levels of GDS expertise, or worse, transformation of the raw data into alternative formats followed by ingestion into other tools so that the data became meaningful. The primary focus was often to answer these types of questions: "Why did this particular frame fail Reed-Solomon decode? Why did this packet get marked as invalid? Why am I missing a block of telemetry from my query?" -- which are completely valid questions to ask from a GDS Engineer's point of view, and large families of tools have been designed to help answer these questions. But these are not the questions that most users care about - which are more like: "Why is the battery state of charge trending down? Show me a summary image report for the last traverse to the target. Show me a data accountability summary for the last DSN pass." Answers to these questions, which are what users are looking for, requires a higher level of abstraction and supporting tools than mining through ones and zeros. JPL has created a next generation capability called the Mission Data Processing and Control System (MPCS) which is designed to support this higher level of abstraction by providing customizable views of the ground system combining collections of lower level information into more meaningful ways. Instead of examining frames, packets, and individual telemetry data points -- MPCS is capable of providing comprehensive summary reports, product status, overall flight/ground event status, as well as payload health summaries. Based on these higher level views, end users can make tactical or strategic decisions, or drop into detailed analysis as needed. System designers need to continue building systems that support low level GDS troubleshooting - but the basic design of a GDS should be geared towards what end users actually need to see. This paper will describe the capabilities of MPCS that directly support these higher levels of abstraction, and which are being used today in missions such as the Mars Science Laboratory and other NASA missions.

MPCS↗

Listing of data systems elements authorities

The NASA personnel have a need to be aware of and to interact with key technical experts in all areas of data systems. This report presents a partial listing (names, addresses and telephone numbers) of individuals known to be authorities in selected areas of data systems of interest to NASA. The listings are based primarily on recent publications by the named individuals.

Source record↗

The data systems tests - The final phase

The U.S.A. has conducted a series of data systems tests (DSTs) as a precursor to its participation in FGGE, the Global Weather Experiment. The paper briefly describes the impact those tests have had on the FGGE observing system and on the data management plans. In particular, the final phase of the DST programs is described, wherein a number of investigators have been selected to work with the DST data sets in research studies directed toward the GARP objectives. Thus, an important first step has been taken in providing feedback to the potential FGGE research community.

Greaves, J. R.↗

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

Results of vibration, acoustical noise, and thermal vacuum are described as well as tests studies of EMI/EMC and mass properties conducted for thematic mapper systems integration. Liens are summarized and the engineering change proposal status is presented. Requests for deviation/waiver are included along with failure and nonforming material reports.

Source record↗

A Science Data System Approach for the SMAP Mission

Though Science Data System (SDS) development has not traditionally been part of the mission concept phase, lessons learned and study of past Earth science missions indicate that SDS functionality can greatly benefit algorithm developers in all mission phases. We have proposed a SDS approach for the SMAP Mission that incorporates early support for an algorithm testbed, allowing scientists to develop codes and seamlessly integrate them into the operational SDS. This approach will greatly reduce both the costs and risks involved in algorithm transitioning and SDS development.

PCS↗

Numerical methods for the analysis of sampled-data systems and for the computation of system zeros

MARSYAS is a computer-aided control system design package for the simulation and analysis of dynamic systems. In the summer of 1991 MARSYAS was updated to allow for the analysis of sampled-data systems in terms of frequency response, stability, etc. This update was continued during the summer of 1992 in order to extend further MARSYAS commands to the study of sampled-data systems. Further work was done to examine the computation of OPENAT transfer functions, root-locii and w-plane frequency response plots.

Hodel, A. Scottedward↗

Mars Entry Atmospheric Data System Modelling and Algorithm Development

The Mars Entry Atmospheric Data System (MEADS) is being developed as part of the Mars Science Laboratory (MSL), Entry, Descent, and Landing Instrumentation (MEDLI) project. The MEADS project involves installing an array of seven pressure transducers linked to ports on the MSL forebody to record the surface pressure distribution during atmospheric entry. These measured surface pressures are used to generate estimates of atmospheric quantities based on modeled surface pressure distributions. In particular, the quantities to be estimated from the MEADS pressure measurements include the total pressure, dynamic pressure, Mach number, angle of attack, and angle of sideslip. Secondary objectives are to estimate atmospheric winds by coupling the pressure measurements with the on-board Inertial Measurement Unit (IMU) data. This paper provides details of the algorithm development, MEADS system performance based on calibration, and uncertainty analysis for the aerodynamic and atmospheric quantities of interest. The work presented here is part of the MEDLI performance pre-flight validation and will culminate with processing flight data after Mars entry in 2012.

Karlgaard, Christopher D.↗

Open-Source Science-led Development of the AOS Mission Science Data System (SDS)

The Earth System Observatory (ESO) Atmosphere Observing System (AOS) mission will provide space-based and suborbital observations of collocated cloud, dynamic, precipitation and aerosol processing leading to improved weather, air quality, and climate predictions. The AOS Science Data System (SDS) will be a system of systems developed within the Cloud to manage the research and operational processing of AOS mission orbital and suborbital sensors and curate these data for reprocessing (e.g., in near real-time or by collection) and transfer them to a NASA Distributed Active Archive Center (DAAC) for long-term storage. Further, AOS SDS will follow guidelines provided by NASA Earth Science Data Systems (ESDS) program including standard conventions for data file formats, naming, and metadata to improve data interoperability, interpretability, usability, discovery, provenance, and spatiotemporal representativeness. The AOS mission follows NASA’s lead in making a commitment to Open-Source Science (OSS) including the sharing of data, software, and knowledge in an open and timely manner. Each of the AOS SDS system components will be developed with open-source concepts including components of SDS itself as well as AOS mission algorithms. Further, the AOS SDS assumes the role to lead and facilitate OSS activities for the AOS mission. This presentation describes the framework of the AOS SDS and its integral part in facilitating OSS within the AOS mission.

David M. Giles↗