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 Small Explorer Data System was developed by NASA Goddard Space Flight Center using a 'standard interfaces' approach. Standard interfaces make it adaptable to a wide variety of missions. The paper describes the Small Explorer Data System with particular emphasis on the standard interfaces incorporated in both the hardware and software.
The National Bureau of Standards (NBS) Data Management Technology Program is discussed. The NBS Data Management Technology Program addresses major problems encountered during the following stages of an application's lifetime: requirements analysis and data base design, system selection and implementation, operations management and conversion. Products developed include standard software specifications, guides to best practice, standard data elements and representations, and reports documenting the experiences of other organizations as they attempt to improve the management of their computing resources. Data base Laboratory facilities are maintained for the investigation and analysis of state of the art data base technology. These facilities support collaborative testing with researchers, vendors, users, and standards developers.
Operating instructions and data on time standard system used in space vehicle telemetry and tracking
International cooperation for space data projects requires common data processing goals and unique data exchange mechanisms. The absence of standards has led to project unique interface definitions and special software on diverse systems. To address this problem, CCSDS Panel 2 is creating a set of standards to support self description of data using standard structures. The proposed standard data interchange mechanism - the Standard Formatted Data Unit (SFDU) - reduces information loss in data transfers, increases automated information exchange, and extends the lifetime of data. Data interchange structures, languages, and services are being developed with necessary control functions to provide these benefits. A set of recommendations for agency review has been issued this year to be the basis for future data exchange and to enhance access to older mission data sets. Space agencies and other space data handling facilities are being encouraged to implement the SFDU concept for ongoing and planned projects.
The state of the art and anticipated requirements for resampling in applications of remote sensing are examined. It is noted that the wide range of potential applications and expanded needs for resampling versatility in new imaging sensors leads to a concern for creating standardized test data sets and ground training sites. Several research areas are defined including the development of (1) a theory for defining an input psf of an instrument such that upon resampling of the processed data into the desired output grid the radiometric and geometric properties are a best estimate of the true upwelling radiances; (2) algorithms for estimating missing data or for ignoring missing data; (3) optimal resampling functions; (4) standard data sets; and (5) merit functions for assessing resampling techniques.
Planetary data include non-imaging remote sensing data, which includes spectrometric, radiometric, and polarimetric remote sensing observations. Also included are in-situ, radio/radar data, and Earth based observation. Also discussed is development of a planetary data system. A catalog to identify observations will be the initial entry point for all levels of users into the data system. There are seven distinct data support services: encyclopedia, data index, data inventory, browse, search, sample, and acquire. Data systems for planetary science users must provide access to data, process, store, and display data. Two standards will be incorporated into the planetary data system: Standard communications protocol and Standard format data unit. The data system configuration must combine a distributed system with those of a centralized system. Fiscal constraints have made prioritization important. Activities include saving previous mission data, planning/cost analysis, and publishing of proceedings.
The TDI project (TDI) investigates trending technical data standards for applicability to NASA vehicles, space stations, payloads, facilities, and equipment. TDI tested COTS software compatible with a certain suite of related industry standards for capabilities of individual benefits and interoperability. These standards not only esnable Information Technology (IT) efficiencies, but also address efficient structures and standard content for business processes. We used source data from generic industry samples as well as NASA and European Space Agency (ESA) data from space systems.
Existing methods of exchanging realtime data between the major control centers in the International Space Station program have resulted in a patchwork of local formats being imposed on each Mission Control Center. This puts the burden on a data customer to comply with the proprietary data formats of each data supplier. This has increased the cost and complexity for each participant, limited access to mission data and hampered the development of efficient and flexible operations concepts. Ideally, a universal format should be promoted in the industry to prevent the unnecessary burden of each center processing a different data format standard for every external interface with another center. With the broad acceptance of XML and other conventions used in other industries, it is now time for the Aerospace industry to fully engage and establish such a standard. This paper will briefly consider the components that would be required by such a standard (XML schema, data dictionaries, etc.) in order to accomplish the goal of a universal low-cost interface, and acquire broad industry acceptance. We will then examine current approaches being developed by standards bodies and other groups. The current state of CCSDS panel work will be reviewed, with a survey of the degree of industry acceptance. Other widely accepted commercial approaches will be considered, sometimes complimentary to the standards work, but sometimes not. The question is whether de facto industry standards are in concert with, or in conflict with the direction of the standards bodies. And given that state of affairs, the author will consider whether a new program establishing its Mission Control Center should implement a data interface based on those standards. The author proposes that broad industry support to unify the various efforts will enable collaboration between control centers and space programs to a wider degree than is currently available. This will reduce the cost for programs to provide realtime access to their data, hence reducing the cost of access to space, and benefiting the industry as a whole.
Detailed tables of pressures and densities are given for altitudes up to 20,000 meters and to 65,000 feet. In addition to the tables the various data pertaining to the standard atmosphere have been compiled in convenient form for ready reference. This report is an extension of NACA-TR-147.
This report examines the critical data exchanges between automated vehicle (AV) service providers and the cities and municipalities they serve. It assists municipal authorities in navigating the often complex and real-time digital data exchanges needed to support AV mobility services, with emphasis in three areas: (1) critical safety data for broad-area situational awareness of hazards typically associated emergency dispatch or roadway work zones; (2) performance metrics of AV services that inform the quantity, quality, spatial extents, and impact on the roadway network; and (3) regulatory and policy information, particularly dynamic information that governs how AV services interact with the roadway network, with emphasis on curb space. The report reviews existing practices and emerging protocols and standards and identifies key gaps to address moving forward.
We envision an artificial intelligence (AI) based system that will provide support and recommendations to the crew medical officer (CMO) and ground flight surgeon during long-duration space missions. Such a system would be pretrained on the knowledgebase of clinical knowledge on Earth, minimizing the amount of Earth data that needs to be transferred into space. Then during deployment, the system would be constantly refined through active learning from diverse streams of data from sensors in the spacecraft, data collected daily from individual astronauts, and human-in-the-loop feedback from the crew. The model could be interrogated for predictions and recommendations on personalized crew health based on the overall status of the spacecraft, medicinal stores, and status of other crew members. Adaptation techniques would be used to incorporate spaceflight data that have very different distributions from the training data due to the extreme environment. Edge computing and the most advanced neuromorphic processing would enable computation in scenarios with low power and bandwidth, while dimensionality reduction would be employed to ensure that the input data streams from spaceflight are as small as possible. In order to realize this long-term vision, several hardware and software aspects need to be developed and assembled. First, models pretrained on Earth biomedical data would need to be evaluated for predictive accuracy, and the best one selected. That model would need to be adapted to learn from diverse, sparse, and inconsistently measured data streams, as well as human-in-the-loop feedback. A data integration, standardization, and dimensionality reduction methodology would need to be developed to handle all data types and feed them into the model. Once the software and data infrastructure is developed, it would need to be integrated with small footprint compute processors and tested in high-radiation, high-vibration, unregulated temperature situations. As a short-term goal, we recommend to focus on the development of the data and model software structure. Several large language models (LLM) already exist that have been trained on Earth biomedical and clinical knowledgebases, including BioMedLLM, Med-PaLM, SPOKE LLM, and Foresight. These models need to be evaluated for accuracy and the best one chosen for a proof-of-concept structure, while maintaining awareness of the accelerating AI field and incorporating any newly improved model architectures as needed. Then, we recommend to develop a database of synthetic data types to mimic the diverse data streams that are expected in a long-duration space mission. This should include environmental and microbial data from the spacecraft, non-invasive data from wearables and point-of-care devices employed by astronauts, and more invasive molecular and physiological monitoring of clinical and biomarker data from astronauts. The data standardization methodology should be developed, and these data streams used to refine the clinical LLM. Several scenarios should be developed that could plausibly come up in a long-duration space mission, and changes or aberrations introduced to the data at specific times to mimic these scenarios. Then, question and answer tasks should be designed to interrogate the model for predictions and recommendations, with acceptable answers already identified.
This dataset contains standardized, processed data from the Leosphere WindCube V2.1 deployed at Nantucket, MA for WFIP-3. The lidar was tall tower validated in May 2023.
These are the standardized buoy data collected during the WFIP3 project period, initially deployed near the Martha's Vineyard region for validation and later deployed at the WFIP3 location. The NetCDF files contain the data for most of the *.csv files for a given day.
The paper gives a functional description and discusses hardware implementation for the Communication and Data Handling (C&DH) subsystem of the Multimission Modular Spacecraft. The C&DH subsystem: (1) provides the command and telemetry link between the spacecraft and the terrestrial system, (2) distributes commands to and collects telemetry from all spacecraft systems via a duplex serial multiplex data bus and remote interface units, and (3) contains onboard computation capability. The C&DH is a single 4 x 4 x 1-1/2 foot module; the stuffed module weighs 270 lbs including 60 lbs of mission unique weight. The hardware is versatile and cost effective, and its modular structure permits repair, refurbishment, and even modification/updating in space
The approach used in the collection, collation, and compilation of normal crop calendar for the foreign commodity production forecasting (FCPF) project of the AgRISTARS program is described.
The two stages of analysis of MAGSAT magnetic data which are designed to evaluate electromagnetic induction effects are described. The first stage consists of comparison of data from contiguous orbit passes over large scale geologic boundaries, such as ocean-land interfaces, at several levels of magnetic disturbance. The purpose of these comparisons is to separate induction effects from effects of lithospheric magnetization. The procdure for reducing the data includes: (1) identifying and subtracting quiet time effects; (2) modelling and subtracting first order ring current effects; and (3) projecting an orbit track onto a map as a nearly straight line so it can serve as an axis on which to plot the corresponding orbit pass data in the context of geography. The second stage consists of comparison of MAGSAT data with standard hourly observatory data. The purpose is to constrain the time evolution of ionospheric and magnetospheric current systems. Qualitative features of the ground based dataset are discussed. Methods for reducing the ground based data are described.
The deposition bridge configuration for a titanium bridge is illustrated. Specifications for the design are presented.