Search NASA⌕ Search

SEARCH · Search NASA

Results for “distributed processing”

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 145 records · Page 8

A knowledge based software engineering environment testbed

The Carnegie Group Incorporated and Boeing Computer Services Company are developing a testbed which will provide a framework for integrating conventional software engineering tools with Artifical Intelligence (AI) tools to promote automation and productivity. The emphasis is on the transfer of AI technology to the software development process. Experiments relate to AI issues such as scaling up, inference, and knowledge representation. In its first year, the project has created a model of software development by representing software activities; developed a module representation formalism to specify the behavior and structure of software objects; integrated the model with the formalism to identify shared representation and inheritance mechanisms; demonstrated object programming by writing procedures and applying them to software objects; used data-directed and goal-directed reasoning to, respectively, infer the cause of bugs and evaluate the appropriateness of a configuration; and demonstrated knowledge-based graphics. Future plans include introduction of knowledge-based systems for rapid prototyping or rescheduling; natural language interfaces; blackboard architecture; and distributed processing

Gill, C.↗

EMASS (trademark): An expandable solution for NASA space data storage needs

The data acquisition, distribution, processing, and archiving requirements of NASA and other U.S. Government data centers present significant data management challenges that must be met in the 1990's. The Earth Observing System (EOS) project alone is expected to generate daily data volumes greater than 2 Terabytes (2 x 10(exp 12) Bytes). As the scientific community makes use of this data, their work will result in larger, increasingly complex data sets to be further exploited and managed. The challenge for data storage systems is to satisfy the initial data management requirements with cost effective solutions that provide for planned growth. The expendable architecture of the E-Systems Modular Automated Storage System (EMASS(TM)), a mass storage system which is designed to support NASA's data capture, storage, distribution, and management requirements into the 21st century is described.

Peterson, Anthony L.↗

EMASS (tm): An expandable solution for NASA space data storage needs

The data acquisition, distribution, processing, and archiving requirements of NASA and other U.S. Government data centers present significant data management challenges that must be met in the 1990's. The Earth Observing System (EOS) project alone is expected to generate daily data volumes greater than 2 Terabytes (2(10)(exp 12) Bytes). As the scientific community makes use of this data their work product will result in larger, increasingly complex data sets to be further exploited and managed. The challenge for data storage systems is to satisfy the initial data management requirements with cost effective solutions that provide for planned growth. This paper describes the expandable architecture of the E-Systems Modular Automated Storage System (EMASS (TM)), a mass storage system which is designed to support NASA's data capture, storage, distribution, and management requirements into the 21st century.

Peterson, Anthony L.↗

Monitoring Volcanic Eruptions by OMI/OMPS, ASTER, and MERRA-2

Volcanic lava flows and/or the gas eruptions are the most common characteristics that can be remotely monitored with satellite technology in the global perspective and on different timescales. Atmospheric Sulfur Dioxide (SO2), one of the most abundant gases from volcanic eruptions apart from atmospheric common gases Carbon Dioxide and water vapor, can be directly detected by space-based sensors on satellites. The NASA Goddard Earth Sciences Data and Information Services Center (GES DISC) is one of the 12 Distributed Active Archive Centers (DAACs) within NASA's Earth Observing System Data and Information System (EOSDIS), which archives SO2 data sets from the Nimbus-7 Total Ozone Mapping Spectrometer (TOMS) in 1978, till the ongoing Ozone Monitoring Instrument (OMI) on NASA's EOS-Aura satellite, the Ozone Mapping Profiler Suite (OMPS) Nadir Mapper (NM) on both the Suomi National Polar-Orbiting Partnership (Suomi-NPP or SNPP) and the Joint Polar-orbiting Satellite System-1 (JPSS-1) satellites, into the future JPSS missions. In addition to the standard OMI/Aura and OMPS/S-NPP SO2 products, SO2 products created under the charter of the Making Earth System Data Records for Use in Research Environments (MEaSUREs) project, are also archived at GES DISC, through which NASA enacts to expand understanding the Earth system using consistent data records. The Land Processes Distributed Active Archive Center (LP DAAC) is another EOSDIS's DAAC that provides land data products and operates as a partnership with the U.S. Geological Survey (USGS). The LP DAAC has been archiving the satellite imagery from the Advanced Spaceborne Thermal Emission and Reflection Radiometer (ASTER) aboard NASA's EOS-Terra satellite, a high spatial resolution (15 meters) and 14 band multispectral instrument. The ASTER imagery is one of the land products contributing to the application for monitoring hot spots and land terrain changes caused by volcanic eruption events. The data potential in GES DISC and LP DAAC to monitor volcanic sources of SO2 and the influence of wind fields on the gas plume spread will be demonstrated with the most recent 2018 May-July Kilauea Volcano eruption.

Zeng, Jian↗

EDOS operations concept and development approach

The Earth Observing System (EOS) Data and Operations System (EDOS) is being developed by the National Aeronautics and Space Administration (NASA) Goddard Space Flight Center (GSFC) for the capture, level zero processing, distribution, and backup archiving of high speed telemetry data received from EOS spacecraft. All data received will conform to the Consultative Committee for Space Data Standards (CCSDS) recommendations. The major EDOS goals are to: (1) minimize EOS program costs to implement and operate EDOS; (2) respond effectively to EOS growth requirements; and (3) maintain compatibility with existing and enhanced versions of NASA institutional systems required to support EOS spacecraft. In order to meet these goals, the following objectives have been defined for EDOS: (1) standardize EDOS interfaces to maximize utility for future requirements; (2) emphasize life-cycle cost (LCC) considerations (rather than procurement costs) in making design decisions and meeting reliability, maintainability, availability (RMA) and upgradability requirements; (3) implement data-driven operations to the maximum extent possible to minimize staffing requirements and to maximize system responsiveness; (4) provide a system capable of simultaneously supporting multiple spacecraft, each in different phases of their life-cycles; (5) provide for technology insertion features to accommodate growth and future LCC reductions during the operations phase; and (6) provide a system that is sufficiently robust to accommodate incremental performance upgrades while supporting operations. Operations concept working group meetings were facilitated to help develop the EDOS operations concept. This provided a cohesive concept that met with approval of responsible personnel from the start. This approach not only speeded up the development process by reducing review cycles, it also provided a medium for generating good ideas that were immediately molded into feasible concepts. The operations concept was then used as a basis for the EDOS specification. When it was felt that concept elements did not support detailed requirements, the facilitator process was used to resolve discrepancies or to add new concept elements to support the specification. This method provided an ongoing revisal of the operations concept and prevented large revisions at the end of the requirement analysis phase of system development.

Knoble, G.↗

Mineralogical, Elemental, and Tomographic Reconnaissance Investigation for CLPS (METRIC)

METRIC is a robotic science laboratory that can determine the mineralogy, elemental chemistry, micromorphology, and thermophysical properties of planetary regolith. The METRIC suite comprises METRIC XRD/F, an X-ray diffraction/X-ray fluorescence instrument that can determine the mineralogy and elemental chemistry of regolith samples; METRIC XCT, a micro X-ray computed tomography instrument that can be used to evaluate grain/crystallite sizes and textures; METRIC IRS, an imaging spectrometer mounted on a rover that can determine mineralogy and thermophysical properties at the landing site; and a pneumatic sample collection, processing, distribution system developed by Honeybee Robotics. The payload elements could be deployed on a static lander or a rover. Data returned from the METRIC payload would inform origin, formation, and evolution of rocky planetary bodies. METRIC XRD/F draws on heritage from the CheMin instrument on the Mars Science Laboratory (MSL) Curiosity rover [1], with a few important improvements. Like CheMin, METRIC XRD/F operates in transmission geometry and uses piezoelectric actuators on sample cells in a tuning fork geometry to induce convective grain motion of the regolith to create a randomly oriented powder. MSL CheMin uses an energy-sensitive CCD to collect XRD patterns and XRF spectra simultaneously from the same sample cell, resulting in qualitative XRF data. METRIC XRD/F uses two different sample cells, one optimized for XRD and one optimized for XRF, and a silicon drift detector to detect fluoresced X-rays. This improvement to the XRF capabilities provides quantitative geochemical data of major elements down to Z = 11 and allows for the detection of minor and trace elements that are critical for evaluating geologic evolution of the Moon (e.g., P and Th). Modest improvements to the XRD geometry and hardware allow for better angular resolution and the ability to distinguish between members of the pyroxene group. METRIC XCT uses the same geometry and much of the same hardware as METRIC XRD/F, where a CCD would capture images of a regolith sample in a 3 mm diameter sample tube that is rotated 360° in steps <1°. Image brightness can be used to infer compositional data, where brighter materials indicate a higher Z, much like scanning electron microscopy. Data from METRIC XCT complement those from METRIC XRD/F. Particle size, shape, and texture can provide petrologic and provenance information, whereas vesicle size and morphology in volcanic or impact melt lithologies can inform cooling rates. METRIC IRS is a hyperspectral thermal imager that can be mounted to a lander or rover to provide mineralogical data from the broader landing site and help determine whether the samples analyzed by METRIC XRD/F and XCT are representative. The METRIC IRS spectral range (8–14 μm) and resolution (10.8 cm-1) allow for quantitative mineralogy from modelling Reststrahlen bands of major rock-forming minerals (e.g., silicates, phosphates). Radiance cubes can be processed and modelled with an onboard high-performance computer to determine mineral abundances of plagioclase, high-Ca pyroxene, pigeonite, orthopyroxene, olivine, and glass. Regolith samples can be acquired, processed, and delivered to the X-ray instruments via multiple sample handling systems, but the pneumatic sampling systems developed by Honeybee Robotics [e.g., 2] are best suited for relatively low-cost missions that are being competed for the Moon (e.g., NASA’s Payloads and Research Investigations for the Surface of the Moon program). There are pneumatic sampling systems that collect surface material and other systems that pneumatically drill up to ~1 m below the surface, providing material that has not been space weathered and has not been affected by the lander’s exhaust. [1] Blake, D. F., Vaniman, D., Achilles, C., Anderson, R., Bish, D., et al. (2012). Space Sci. Rev. 170, 341-478. https://doi.org/10.1007/s11214-012-9905-1. [2] Zacny, K., Betts, B., Hedlund, M., Long, P., Gramlich, M., Tura, K., Chu, P., Jacob, A., Garcia, A. (2014). IEEE Aerospace Conference, 3-7 March 2014, Big Sky, MT, U.S.A.

X-ray diffraction↗

The NASA Integrated Information Technology Architecture

This document defines an Information Technology Architecture for the National Aeronautics and Space Administration (NASA), where Information Technology (IT) refers to the hardware, software, standards, protocols and processes that enable the creation, manipulation, storage, organization and sharing of information. An architecture provides an itemization and definition of these IT structures, a view of the relationship of the structures to each other and, most importantly, an accessible view of the whole. It is a fundamental assumption of this document that a useful, interoperable and affordable IT environment is key to the execution of the core NASA scientific and project competencies and business practices. This Architecture represents the highest level system design and guideline for NASA IT related activities and has been created on the authority of the NASA Chief Information Officer (CIO) and will be maintained under the auspices of that office. It addresses all aspects of general purpose, research, administrative and scientific computing and networking throughout the NASA Agency and is applicable to all NASA administrative offices, projects, field centers and remote sites. Through the establishment of five Objectives and six Principles this Architecture provides a blueprint for all NASA IT service providers: civil service, contractor and outsourcer. The most significant of the Objectives and Principles are the commitment to customer-driven IT implementations and the commitment to a simpler, cost-efficient, standards-based, modular IT infrastructure. In order to ensure that the Architecture is presented and defined in the context of the mission, project and business goals of NASA, this Architecture consists of four layers in which each subsequent layer builds on the previous layer. They are: 1) the Business Architecture: the operational functions of the business, or Enterprise, 2) the Systems Architecture: the specific Enterprise activities within the context of IT systems, 3) the Technical Architecture: a common, vendor-independent framework for design, integration and implementation of IT systems and 4) the Product Architecture: vendor=specific IT solutions. The Systems Architecture is effectively a description of the end-user "requirements". Generalized end-user requirements are discussed and subsequently organized into specific mission and project functions. The Technical Architecture depicts the framework, and relationship, of the specific IT components that enable the end-user functionality as described in the Systems Architecture. The primary components as described in the Technical Architecture are: 1) Applications: Basic Client Component, Object Creation Applications, Collaborative Applications, Object Analysis Applications, 2) Services: Messaging, Information Broker, Collaboration, Distributed Processing, and 3) Infrastructure: Network, Security, Directory, Certificate Management, Enterprise Management and File System. This Architecture also provides specific Implementation Recommendations, the most significant of which is the recognition of IT as core to NASA activities and defines a plan, which is aligned with the NASA strategic planning processes, for keeping the Architecture alive and useful.

Baldridge, Tim↗

The LCLStream Ecosystem for Multi-Institutional Dataset Exploration

We describe a new end-to-end experimental data streaming framework designed from the ground up to support new types of applications – AI training, extremely high-rate X-ray time-of-flight analysis, crystal structure determination with distributed processing, and custom data science applications and visualizers yet to be created. Throughout, we use design choices merging cloud microservices with traditional HPC batch execution models for security and flexibility. This project makes a unique contribution to the DOE Integrated Research Infrastructure (IRI) landscape. By creating a flexible, API-driven data request service, we address a significant need for high-speed data streaming sources for the X-ray science data analysis community. With the combination of data request API, mutual authentication web security framework, job queue system, high-rate data buffer, and complementary nature to facility infrastructure, the LCLStreamer framework has prototyped and implemented several new paradigms critical for future generation experiments.

Rogers, David [ORNL] (ORCID:0000000251871768)↗

Considerations for a Medium-Voltage DC Electrolysis Testbed

Here we present the results of a study focused on the feasibility of using Medium Voltage DC (MVDC) power distribution from wind power generation to electrolyzers for hydrogen production. This approach, using hybrid energy generation in a MVDC microgrid, offers many advantages. These include possible improvements in efficiency, reliability and installation cost compared to a more typical state-of-the-art AC distribution configuration. It also eliminates the need for transformers, which have recently been subject to price volatility and availability concerns. This study highlights the practical feasibility of MVDC distribution networks for integrating various energy sources, offering improved efficiency and reduced system complexity compared to conventional AC-based solutions. Future work will focus on enhancing fault protection strategies, scaling the system to larger renewable installations, and conducting hardware implementation at the National Renewable Energy Laboratory's (NREL) Flatirons Campus (FC). In the sections that follow we show that a DC Collection and Distribution System (DC CDS) reduces the losses associated with the electrical conversion / distribution process relative to a state-of-the-art AC approach, improving overall efficiency by 5%. On the qualitative side, reducing the number of conversion stages is likely to improve reliability, reduce capital investment cost, and enable simpler control algorithms to be used, and reduced risk of instabilities and malfunctions.

08 HYDROGEN↗

NASA Office of Aeronautics and Space Technology Summer Workshop. Volume 4: Power technology panel

Technology requirements in the areas of energy sources and conversion, power processing, distribution, conversion, and transmission, and energy storage are identified for space shuttle payloads. It is concluded that the power system technology currently available is adequate to accomplish all missions in the 1973 Mission Model, but that further development is needed to support space opportunities of the future as identified by users. Space experiments are proposed in the following areas: power generation in space, advanced photovoltaic energy converters, solar and nuclear thermoelectric technology, nickel-cadmium batteries, flywheels (mechanical storage), satellite-to-ground transmission and reconversion systems, and regenerative fuel cells.

Source record↗

OAST Space Theme Workshop. Volume 3: Working group summary. 6: Power (P-2). A. Statement. B. Technology needs (form 1). C. Priority assessment (form 2)

Power requirements for the multipurpose space power platform, for space industrialization, SETI, the solar system exploration facility, and for global services are assessed for various launch dates. Priorities and initiatives for the development of elements of space power systems are described for systems using light power input (solar energy source) or thermal power input, (solar, chemical, nuclear, radioisotopes, reactors). Systems for power conversion, power processing, distribution and control are likewise examined.

Source record↗

A distributed microprocessor system for spacecraft control and data handling

The specific requirements for spacecraft computing systems are considered. These requirements are partly related to the constraints of limited resources of power, weight, and volume. Another important factor is the requirement of extremely high reliability. These reliability requirements have led to introduction of automated redundancy techniques on board the spacecraft. The various redundant computers check each other and provide recovery procedures when a computer is found to have failed. Past and future capabilities are considered along with distributed processing requirements. System considerations are discussed, taking into account suboptimum computer throughput, sensitivity to software modifications, hierarchic timing, I/O granularity, restricted communications, synchronous functions, hierarchic control, and concurrent error detection. A description is presented of the Unified Data System (UDS), which consists of a set of standard microcomputers connected by several buses. Attention is also given to synchronization and timing, the executive control structure, the programming language, and the executive program.

Rennels, D. A.↗

An experimental distributed microprocessor implementation with a shared memory communications and control medium

The distributed processing concept is defined in terms of control primitives, variables, and structures and their use in performing a decomposed discrete Fourier transform (DET) application function. The design assumes interprocessor communications to be anonymous. In this scheme, all processors can access an entire common database by employing control primitives. Access to selected areas within the common database is random, enforced by a hardware lock, and determined by task and subtask pointers. This enables the number of processors to be varied in the configuration without any modifications to the control structure. Decompositional elements of the DFT application function in terms of tasks and subtasks are also described. The experimental hardware configuration consists of IMSAI 8080 chassis which are independent, 8 bit microcomputer units. These chassis are linked together to form a multiple processing system by means of a shared memory facility. This facility consists of hardware which provides a bus structure to enable up to six microcomputers to be interconnected. It provides polling and arbitration logic so that only one processor has access to shared memory at any one time.

Mejzak, R. S.↗

Should we attempt global (inlet engine airframe) control design?

The feasibility of multivariable design of the entire airplane control system is briefly addressed. An intermediate step in that direction is to design a control for an inlet engine augmentor system by using multivariable techniques. The supersonic cruise large scale inlet research program is described which will provide an opportunity to develop, integrate, and wind tunnel test a control for a mixed compression inlet and variable cycle engine. The integrated propulsion airframe control program is also discussed which will introduce the problem of implementing MVC within a distributed processing avionics architecture, requiring real time decomposition of the global design into independent modules in response to hardware communication failures.

Carlin, C. M.↗

Computer Science Research at Langley

A workshop was held at Langley Research Center, November 2-5, 1981, to highlight ongoing computer science research at Langley and to identify additional areas of research based upon the computer user requirements. A panel discussion was held in each of nine application areas, and these are summarized in the proceedings. Slides presented by the invited speakers are also included. A survey of scientific, business, data reduction, and microprocessor computer users helped identify areas of focus for the workshop. Several areas of computer science which are of most concern to the Langley computer users were identified during the workshop discussions. These include graphics, distributed processing, programmer support systems and tools, database management, and numerical methods.

Voigt, S. J.↗

An Engineering Data Management System for Ipad

An overview of the capabilities and software architecture of the IPAD information processor (IPIP) is presented. IPIP is a state-of-the-art data base management system that satisfies engineering requirements not addressed by present day commercial systems. It also significantly advances a number of capabilities that are offered commercially. IPIP capabilities range from support for multiple schemas and data models to support for distributed processing, configuration control, and data inventory management. IPIP exploits semantic commonality in features offered in various forms at different user interfaces in today's commercial systems. An integrated software architecture supports all user interfaces: programming languages, interactive data manipulation, and schema languages. This approach promotes simplicity and compactness in software and permits features to be offered symmetrically across all appropriate user interfaces.

H R Johnson↗

Integrated airframe/propulsion control system architectures (IAPSA) study

Three integrated airframe/propulsion control system (ACS) architectures have been developed and are discussed. The baseline is a state of the art design which integrates autonomous propusion control and airframe flight control systems. Two alternate ACSs for the 1990s using emerging technologies were developed and are compared with each other and the baseline. One of these, designated D/D, uses parallel distributed processing, while the other, designated C/D, centralizes the processing into two centrally located redundant electronics complex. The C/D system locates all redundant computing elements and interfacing electronics in two boxes with optical sensor and actuation devices optically connected to the two boxes. Evaluation reveals the C/D architecture to be better than the other two in five of ten categories; D/D is superior in only two of the ten.

Stern,, A. d.↗