Engineering Papers⌕ Search

SEARCH · Engineering Papers

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 163 records · Page 9

MODIS-HIRIS ground data systems commonality report

The High Resolution Imaging Spectrometer (HIRIS) and Moderate Resolution Imaging Spectrometer (MODIS) Data Systems Working Group was formed in September 1988 with representatives of the MODIS Data System Study Group and the HIRIS Project Data System Design Group to collaborate in the development of requirements on the EosDIS necessary to meet the science objectives of the two facility instruments. A major objective was to identify and promote commonality between the HIRIS and MODIS data systems, especially from the science users' point of view. A goal was to provide a base set of joint requirements and specifications which could easily be expanded to a Phase-B representation of the needs of the science users of all EOS instruments. This document describes the points of commonality and difference between the Level-II Requirements, Operations Concepts, and Systems Specifications for the ground data systems for the MODIS and HIRIS instruments at their present state of development.

Han, D.↗

Evolving the Technical Infrastructure of the Planetary Data System for the 21st Century

The Planetary Data System (PDS) was established in 1989 as a distributed system to assure scientific oversight. Initially the PDS followed guidelines recommended by the National Academies Committee on Data Management and Computation (CODMAC, 1982) and placed emphasis on archiving validated datasets. But overtime user demands, supported by increased computing capabilities and communication methods, have placed increasing demands on the PDS. The PDS must add additional services to better enable scientific analysis within distributed environments and to ensure that those services integrate with existing systems and data. To face these challenges the Planetary Data System (PDS) must modernize its architecture and technical implementation. The PDS 2010 project addresses these challenges. As part of this project, the PDS has three fundamental project goals that include: (1) Providing more efficient client delivery of data by data providers to the PDS (2) Enabling a stable, long-term usable planetary science data archive (3) Enabling services for the data consumer to find, access and use the data they require in contemporary data formats. In order to achieve these goals, the PDS 2010 project is upgrading both the technical infrastructure and the data standards to support increased efficiency in data delivery as well as usability of the PDS. Efforts are underway to interface with missions as early as possible and to streamline the preparation and delivery of data to the PDS. Likewise, the PDS is working to define and plan for data services that will help researchers to perform analysis in cost-constrained environments. This presentation will cover the PDS 2010 project including the goals, data standards and technical implementation plans that are underway within the Planetary Data System. It will discuss the plans for moving from the current system, version PDS 3, to version PDS 4.

Beebe, Reta F.↗

The Pilot Land Data System (PLDS) at the Ames Research Center manages aircraft data in collaboration with an ecosystem research project

The Pilot Land Data System (PLDS) is a data and information system serving NASA-supported investigators in the land science community. The three nodes of the PLDS, one each at the Ames Research Center (ARC), the Goddard Space Flight Center (GSFC) and the Jet Propulsion Laboratory (JPL), cooperate in providing consistent information describing the various data holding in the hardware and software (accessible via network and modem) that provide information about and access to PLDS-held data, which is available for distribution. A major new activity of the PLDS node at the Ames Research Center involves the interaction of the PLDS with an active NASA ecosystem science project, the Oregon Transect Ecosystems Research involves the management of, access to, and distribution of the large volume of widely-varying aircraft data collected by OTTER. The OTTER project, is managed by researchers at the Ames Research Center and Oregon State University. Its principal objective is to estimate major fluxes of carbon, nitrogen, and water of forest ecosystems using an ecosystem process model driven by remote sensing data. Ten researchers at NASA centers and universities are analyzing data for six sites along a temperature-moisture gradient across the western half of central Oregon (called the Oregon Transect). Sensors mounted on six different aircraft have acquired data over the Oregon Transect in support of the OTTER project.

Angelici, Gary↗

Pilot land data system

The Pilot Land Data System (PLDS) is a multi-institutional effort directed towards solving the data access and management needs of scientists studying the land surface. Some of the hardware and software, which are now available, are reviewed.

Star, J. L.↗

On-the-shaft data systems for rotating engine components

Two rotating data systems for engine component testing, which demonstrate the techniques of on-the-shaft microelectronic signal conditioning and rotary transformer power- and data-transfer, are described. These systems are a digital data system which provides 69 channels of 1100 C maximum thermocouple data with less than 0.5% error from a turbine test rig rotating at speeds up to 9000 rpm and an analog data system which amplifies and transfers 72 channels of dynamic strain data with less than 5% error from a compressor rig at speeds above 14,000 rpm.

Lesco, D. J.↗

Moirai Land Data System (Moirai) v3.0.0

The Moirai Land Data System (Moirai LDS) is designed to produce recent historical land data inputs for the AgLU module of GCAM data system , but the Moirai LDS outputs could also be used by other models/applications. The Moirai are the Greek Fates, and this software is named Moirai to represent the fundamental influence of land data inputs on model outcomes. The primary function of the Moirai LDS is to combine spatially explicit input data (e.g., raster images) with tabular input data (e.g., crop price table) to generate tabular output data for a suite of variables. Some of these outputs replace the data provide by the Global Trade Analysis Project (GTAP), and other data replace and augment the original GCAM GIS processing. The Moirai LDS output data are aggregated by Geographic Land Unit (GLU) within each country. The GLU coverage is an input to the Moirai LDS (as a thematic raster image and an associated CSV file that maps the thematic integers to names), and the GLU boundaries can be determined arbitrarily. Previous versions of GCAM (and Moirai LDS) used only bioclimatic Agro-Ecological Zones (AEZs) and corresponding data that were provided by GTAP, as the GLUs. As a result, some AEZ terminology still exists in the code, but this terminology now refers more generally to GLUs. The Moirai LDS now enables any set of boundaries to be used as GLUs (including AEZs), allowing for more flexible generation of land use region boundaries (defined as the intersection of GLUs with geopolitical regions). The current default set of GLUs is the same set of 235 global watersheds as used by the GCAM water module. The GCAM 5.1 geopolitical regions (32 or 14) are included and used as inputs to Moirai to generate a mapping file between the Moirai outputs, which are at the level of the intersection between the GLUs and the country boundaries, and the geopolitical regions. The diagnostics scripts use this geopolitical region mapping in some cases. Moirai can also recalibrate three of the outputs (crop production, harvested area, and land rent) to a specified year that is the center of a five-year averaging window. No recalibration retains the circa 2000, 7-year average of the source data. The cucrrency-year for land rent can also be specified, and the default is 2001 to match the GTAP data.

Di Vittorio, Alan↗

Reference architecture for space data systems

This paper introduces the Reference Architecture for Space Data Systems (RASDS)that is being developed by CCSDS. RASDS uses five views to describe architectures of space data systems. These views are derived from the viewpoints of the Reference Model of Open Distributed Processing (RM-ODP), but they are slightly modified from the RM-ODP viewpoints so that they can better represent the concerns of space data systems.

CCSDS space communication reference architecture s↗

Development of a Low-Cost UAV Doppler Radar Data System

A viewgraph presentation on the design of a low cost unmanned aerial vehicle (UAV) doppler radar data system is presented. The topics include: 1) Science and Mission Background; 2) Radar Requirements and Specs; 3) Radar Realization: RF System; 4) Processing of RF Signal; 5) Data System Design Process; 6) Can We Remove the DSP? 7) Determining Approximate Speed Requirements; 8) Radar Realization: Data System; 9) Data System Operation; and 10) Results.

Knuble, Joseph↗

Transforming NASA Earth Science Data Systems: A Journey from Big Earth Data Initiative (BEDI) to Open-Source Science Initiative (OSSI)

NASA's Earth Science Data and Information Systems (ESDIS) have undergone a significant evolution, particularly with the introduction of the Big Earth Data Initiative (BEDI) and the Open-Source Science Initiative (OSSI). In this talk, I will provide an overview of NASA's Earth Science Data and Information systems, highlighting key components such as EOSDIS, ESDIS, and ESDS. Moving forward, I will delve into the BEDI initiative, discussing its objectives, key players, and lessons learned. The second part of the talk will cover the OSSI initiative, exploring its objectives, strategy, and innovative solutions. Throughout the presentation, I will provide insights into the requests, strategies, and solutions behind both BEDI and OSSI. By the end, you will gain a comprehensive understanding of how NASA's Earth Science Data Systems have evolved over the years and witness the organization's commitment to advancing an open-source and collaborative approach to data science. Join me for an enlightening exploration into the future of Earth science data and the pivotal role played by NASA in shaping this transformative landscape.

Jennifer Wei↗

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↗

Lossless Coding Standards for Space Data Systems

The International Consultative Committee for Space Data Systems (CCSDS) is preparing to issue its first recommendation for a digital data compression standard. Because the space data systems of primary interest are employed to support scientific investigations requiring accurate representation, this initial standard will be restricted to lossless compression.

digital data compression digital data compression ↗

A multiprocessor airborne lidar data system

A new multiprocessor data acquisition system was developed for the existing Airborne Oceanographic Lidar (AOL). This implementation simultaneously utilizes five single board 68010 microcomputers, the UNIX system V operating system, and the real time executive VRTX. The original data acquisition system was implemented on a Hewlett Packard HP 21-MX 16 bit minicomputer using a multi-tasking real time operating system and a mixture of assembly and FORTRAN languages. The present collection of data sources produce data at widely varied rates and require varied amounts of burdensome real time processing and formatting. It was decided to replace the aging HP 21-MX minicomputer with a multiprocessor system. A new and flexible recording format was devised and implemented to accommodate the constantly changing sensor configuration. A central feature of this data system is the minimization of non-remote sensing bus traffic. Therefore, it is highly desirable that each micro be capable of functioning as much as possible on-card or via private peripherals. The bus is used primarily for the transfer of remote sensing data to or from the buffer queue.

Wright, C. W.↗

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)↗

Adapting the NSCAT data system to changing requirements

The data system of the spaceborne eight-beam NASA scatterometer for measuring ocean backscatter is a nonreal-time ground-based science data processing system which inputs backscatter telemetry, processes the data into wind vectors, and archives and distributes the wind vector data and other products. Special attention is given to changes to the baseline design intended to meet new requirements for the data granularity, the data needs of the science team receiving the data, and the telemetry data source.

Benada, J. R.↗

The ARM Data System and Archive

Every observationally based research program needs a way to collect data from instruments, convert the data from its raw format into a more usable format, apply quality control, process it into higher-order data products, store the data, and make the data available to its scientific community. This data flow is illustrated pictorially in Fig. 11-1. These are the basic requirements of any scientific data system, and ARM’s data system would have to address these requirements and more. This research provides one view of the development of the ARM data system, which includes the ARM Data Archive, and some of the notable decisions that were made along the way.

97 MATHEMATICS AND COMPUTING↗