Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Component Architecture”

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 37 records · Page 2

Sequencing System Building Blocks: Using a Component Architecture for Sequencing Software

Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require a new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group. The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a set of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.

multi mission planning↗

Sequence System Building Blocks: Using a Component Architecture for Sequencing Software

Over the last few years software engineering has made significant strides in making more flexible architectures and designs possible. However, at the same time, spacecraft have become more complex and flight software has become more sophisticated. Typically spacecraft are often one-of-a-kind entities that have different hardware designs, different capabilities, different instruments, etc. Ground software has become more complex and operations teams have had to learn a myriad of tools that all have different user interfaces and represent data in different ways. At Jet Propulsion Laboratory (JPL) these themes have collided to require an new approach to producing ground system software. Two different groups have been looking at tackling this particular problem. One group is working for the JPL Mars Technology Program in the Mars Science Laboratory (MSL) Focused Technology area. The other group is the JPL Multi-Mission Planning and Sequencing Group . The major concept driving these two approaches on a similar path is to provide software that can be a more cohesive flexible system that provides a act of planning and sequencing system of services. This paper describes the efforts that have been made to date to create a unified approach from these disparate groups.

flexible architectures↗

Designing a Component-Based Architecture for the Modeling and Simulation of Nuclear Fuels and Reactors

Concerns over the environment and energy security have recently prompted renewed interest in the U.S. in nuclear energy. Recognizing this, the U.S. Dept. of Energy has launched an initiative to revamp and modernize the role that modeling and simulation plays in the development and operation of nuclear facilities. This Nuclear Energy Advanced Modeling and Simulation (NEAMS) program represents a major investment in the development of new software, with one or more large multi-scale multi-physics capabilities in each of four technical areas associated with the nuclear fuel cycle, as well as additional supporting developments. In conjunction with this, we are designing a software architecture, computational environment, and component framework to integrate the NEAMS technical capabilities and make them more accessible to users. In this report of work very much in progress, we lay out the 'problem' we are addressing, describe the model-driven system design approach we are using, and compare them with several large-scale technical software initiatives from the past. We discuss how component technology may be uniquely positioned to address the software integration challenges of the NEAMS program, outline the capabilities planned for the NEAMS computational environment and framework, and describe some initial prototyping activities.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Architecture and Component Selection for the Remote Canister-Monitoring System

This report documents the selected system architecture and components surveyed for the development of a remote, canister-monitoring system (RCMS) for determining and monitoring environmental conditions within dry fuel storage canisters containing aluminum-clad spent nuclear fuel (ASNF) at Idaho National Laboratory (INL). These efforts are in support of the Department of Energy Office of Environmental Management (DOE-EM) investigations into the technical issues associated with extended dry storage (50+ years) of ASNF. It is important to resolve questions regarding storage because the ATR is expected to continue producing approximately 100 elements of spent fuel per year for at least another twenty years. The parameters to be monitored by the RCMS include temperature, relative humidity, hydrogen gas concentration, and radiation environment (dose). Components are selected based on the expected environmental conditions within the canister and fuel storage area and the desired performance of the RCMS. Several of these components have been purchased and are currently undergoing component testing to confirm their suitability for use in delivering the RCMS. Additional components may be identified through the course of design and may be selected in the future. Furthermore, changing performance, interfacing, and compatibility requirements and the results of component testing may necessitate revisiting component selection.

11 NUCLEAR FUEL CYCLE AND FUEL MATERIALS↗

Extending the Concept of Component Interfaces: Experience with the Integrated Plasma Simulator

In the component approach, components are said to interact through well-defined interfaces. Conventionally, these interfaces are based on method signatures which define the syntax, if not the semantics of the interface. However in many cases, this does not encompass all of the interactions a component has with its peers. In the Integrated Plasma Simulator (IPS), a framework for coupled simulation of fusion plasmas developed by the Center for Simulation of RF Wave Interactions with Magnetohydrodynamics (SWIM), we find that components interact through files and through an event service in addition to the usual method calls. In this report, we discuss the motivations for the design of the IPS and our experience with it. We further consider whether the concept of a component interface needs to be extended, and how it might be done. Component-based software engineering (CBSE) has allowed applications to grow in size, scale and power, by coupling components along well-defined interfaces. Many groups have come together to provide rules and standards for component and interface definitions. General purpose component architectures have been designed for business, and scientific computing, while domain specific component frameworks have been created in many domains, including climate modeling, rocket simulation, and engineering. In each architecture, component interfaces, typically implemented as method invocations, are the only ways that are mentioned for components to interact with each other and the outside world. However, components may not always communicate over their interfaces. They can interact with software entities in many other ways including sharing files and publish/subscribe systems. In this paper we consider two ways in which components interact without method invocation in a component framework, how the component interface can be extended to describe these interactions, and the implications on the greater component community. The rest of the paper continues as follows: first we briefly describe the fusion simulation framework that serves as the basis for the discussion (Sec. 2), followed by a description of non-interface interactions (Sec. 3), a discussion of how to extend to the component interface (Sec. 4) and finally some conclusions (Sec. 5).

33 ADVANCED PROPULSION SYSTEMS↗

SciDAC-Center for Plasma Edge Simulation Report

The Common Component Architecture (CCA) effort is the embodiment of a long-range program of research and development into the formulation, roles, and use of component technologies in high-performance scientific computing. CCA components can interoperate with other components in a variety of frameworks, including SCIRun2 from the University of Utah. The SCIRun2 framework is also developing the ability to connect components from a variety of different models through a mechanism called meta-components. The meta component model operates by providing a plugin architecture for component models. Abstract components are manipulated and managed by the SCIRun2 framework, while concrete component models perform the actual work and communicate with each other directly. We will leverage the SCIRun2 framework and the Kepler system to orchestrate components in the Fusion Simulation Project (FSP) and to provide a CCA-based interface with Kepler. The groundwork for this functionality is being performed with the Scientific Data Management center. The SDM center is developing CCA-compliant interfaces for expressing and executing workflows and create workflow components based on SCIRun and Ptolemy (Kepler) execution engines, including development of uniform interfaces for selecting, starting, and monitoring scientific workflows. Accomplishments include Introduction to CCA and Simulation Software Systems, Introduction into SCIRun2 and Bridging within SCIRun2, CCALoop: A scalable design for a distributed component framework, and Combining Workflow methodologies with Component Architectures.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗

Executive control systems in the engineering design environment

An executive control system (ECS) is a software structure for unifying various applications codes into a comprehensive system. It provides a library of applications, a uniform access method through a cental user interface, and a data management facility. A survey of twenty-four executive control systems designed to unify various CAD/CAE applications for use in diverse engineering design environments within government and industry was conducted. The goals of this research were to establish system requirements to survey state-of-the-art architectural design approaches, and to provide an overview of the historical evolution of these systems. Foundations for design are presented and include environmental settings, system requirements, major architectural components, and a system classification scheme based on knowledge of the supported engineering domain(s). An overview of the design approaches used in developing the major architectural components of an ECS is presented with examples taken from the surveyed systems. Attention is drawn to four major areas of ECS development: interdisciplinary usage; standardization; knowledge utilization; and computer science technology transfer.

Hurst, P. W.↗

Optics Supply Planning System

The purpose of this study is to specify the design for an initial optics supply planning system for NIF, and to present quality assurance and test plans for the construction of the system as specified. The National Ignition Facility (NIF) is a large laser facility that is just starting operations. Thousands of specialized optics are required to operate the laser, and must be exchanged over time based on the laser shot plan and predictions of damage. Careful planning and tracking of optic exchanges is necessary because of the tight inventory of spare optics, and the long lead times for optics procurements and production changes. Automated inventory forecasting and production planning tools are required to replace existing manual processes. The optics groups members who are expected to use the supply planning system are the stakeholders for this project, and are divided into three groups. Each of these groups participated in a requirements specification that was used to develop this design. (1) Optics Management--These are the top level stakeholdersk, and the final decision makers. This group is the interface to shot operations, is ultimately responsible for optics supply, and decides which exchanges will be made. (2) Work Center Managers--This group manages the on site optics processing work centers. They schedule the daily work center operations, and are responsible for developing long term processing, equipment, and staffing plans. (3) Component Engineers--This group manages the vendor contracts for the manufacture of new optics and the off site rework of existing optics. They are responsible for sourcing vendors, negotiating contracts, and managing vendor processes. The scope of this analysis is to describe the structure and design details of a system that will meet all requirements that were described by stakeholders and documented in the analysis model for this project. The design specifies the architecture, components, interfaces, and data stores of the system at a level of detail that can be used for construction and deployment. Test and quality assurance plans are also included to insure that the system delivers all requirements when it is built. The design is for an automated forecasting prototype that allocates inventory and processing resources in response to potentially daily changes in the forecasted optics exchanges required to operate NIF. It will automatically calculate future inventory levels and processing rates based on current inventory and projected exchanges, procurements, and capacities. It will include screens that allow users to readily assess the feasibility of the forecast, identify failures to meet the demand, revise input data, and re-run the automated forecast calculation. In addition, the system will automatically retrieve the current exchange demand from an external database. Approved forecasts from the system will automatically update work order plans and procurement plans in the existing inventory and production control database. The timing of optics exchanges affects the forecast of damage and future exchanges, so an approved exchange plan will be fed back to the demand database and be used to calculate the next demand projection. The system will read the demand data and update the forecast and output files daily. This specification has been divided into two parts. This document, Part 1 lays out the major design decisions and specifies the architectural, component, and data structure designs. Part 2 will add interface designs, quality assurance and testing plans, and deployment details.

42 ENGINEERING↗

Design and Implementation of a High-Performance CCA Event Service

Event services based on publish-subscribe architectures are well established components of distributed computing applications. Recently, an event service has been proposed as part of the Common Component Architecture (CCA) for high-performance computing applications. In this paper we describe our implementation, experimental evaluation, and initial experience with a high performance CCA event service that exploits efficient communications mechanisms commonly used on high-performance computing (HPC) platforms. We describe the CCA event service model, and discuss briefly the possible implementation strategies of that model. We then present the design and implementation of the event service using the Aggregate Remote Memory Copy Interface (ARMCI) as an underlying communication layer for this mechanism. Two alternative implementations are presented and evaluated on a Cray XD-1 platform. The performance results demonstrate that event delivery latencies are low and that the event service is able to achieve high throughput levels. Finally, we describe the use of the event service in an application for high-speed processing of data from a mass spectrometer, and conclude by discussing some possible extensions to the event service for other HPC applications.

97 MATHEMATICS AND COMPUTING↗

Evaluating Performance of Components

Parallel Component Performance Benchmarks is a computer program developed to aid the evaluation of the Common Component Architecture (CCA) - a software architecture, based on a component model, that was conceived to foster high-performance computing, including parallel computing. More specifically, this program compares the performances (principally by measuring computing times) of componentized versus conventional versions of the Parallel Pyramid 2D Adaptive Mesh Refinement library - a software library that is used to generate computational meshes for solving physical problems and that is typical of software libraries in use at NASA s Jet Propulsion Laboratory.

Katz, Daniel↗

Multiple Component Multiple Data Programming in Subsurface Simulations: The CCA Approach

The dynamic nature and the encapsulation provided by the component approach maps quite naturally to the concepts of multiple-program multiple-data (MPMD) programming. In this paper, we will introduce a new programming model called multiple component multiple data (MCMD). The MCMD model provides a high-level infrastructure in the common component architecture (CCA) environment to exploit hardware parallelism in emerging petascale and exascale systems. We demonstrate the effectiveness of CCA MCMD programming in context of subsurface simulations to express and manage many-task parallelism. Our target application is STOMP, a large scale (~800K lines of code) subsurface simulation code. The performance results for a 3D saturated flow problem with the STOMP CCA framework show that the MCMD programming model is very effective to achieve scalability on thousands of processors with high efficiency. For example, to simulate the saturated flow problem containing ~1.2 million nodes on 2048 processors, the CCA MCMD version of STOMP is an order of magnitude faster than the original parallel version of STOMP.

99 GENERAL AND MISCELLANEOUS↗

Aquarius' Object-Oriented, Plug and Play Component-Based Flight Software

The Aquarius mission involves a combined radiometer and radar instrument in low-Earth orbit, providing monthly global maps of Sea Surface Salinity. Operating successfully in orbit since June, 2011, the spacecraft bus was furnished by the Argentine space agency, Comision Nacional de Actividades Espaciales (CONAE). The instrument, built jointly by NASA's Caltech/JPL and Goddard Space Flight Center, has been successfully producing expectation-exceeding data since it was powered on in August of 2011. In addition to the radiometer and scatterometer, the instrument contains an command & data-handling subsystem with a computer and flight software (FSW) that is responsible for managing the instrument, its operation, and its data. Aquarius' FSW is conceived and architected as a Component-based system, in which the running software consists of a set of Components, each playing a distinctive role in the subsystem, instantiated and connected together at runtime. Component architectures feature a well-defined set of interfaces between the Components, visible and analyzable at the architectural level (see [1]). As we will describe, this kind of an architecture offers significant advantages over more traditional FSW architectures, which often feature a monolithic runtime structure. Component-based software is enabled by Object-Oriented (OO) techniques and languages, the use of which again is not typical in space mission FSW. We will argue in this paper that the use of OO design methods and tools (especially the Unified Modeling Language), as well as the judicious usage of C++, are very well suited to FSW applications, and we will present Aquarius FSW, describing our methods, processes, and design, as a successful case in point.

Component Architecture↗

QUASAR - QUAsi-Stationary Absolute Radiance Mission

This paper describes the scientific and developmental aspects behind the QUAsi-Stationary Absolute Radiance (QUASAR) mission study. The scientific motivation on which the mission is built is established, including the absolute flux calibration of standard and exoplanet host stars, supernova cosmology, and interferometry. Furthermore, we present a science traceability matrix that determines the requirements for the mission through the scientific objectives. Additionally, we provide the mission configuration. This includes the spacecraft structure, its payload, and the component architecture. Finally, we describe how components within the payload provide efficiency and redundancy within the mission.

Eliad Peretz↗

LISA Framework for Enhancing Gravitational Wave Signal Extraction Techniques

This paper describes the development of a Framework for benchmarking and comparing signal-extraction and noise-interference-removal methods that are applicable to interferometric Gravitational Wave detector systems. The primary use is towards comparing signal and noise extraction techniques at LISA frequencies from multiple (possibly confused) ,gravitational wave sources. The Framework includes extensive hybrid learning/classification algorithms, as well as post-processing regularization methods, and is based on a unique plug-and-play (component) architecture. Published methods for signal extraction and interference removal at LISA Frequencies are being encoded, as well as multiple source noise models, so that the stiffness of GW Sensitivity Space can be explored under each combination of methods. Furthermore, synthetic datasets and source models can be created and imported into the Framework, and specific degraded numerical experiments can be run to test the flexibility of the analysis methods. The Framework also supports use of full current LISA Testbeds, Synthetic data systems, and Simulators already in existence through plug-ins and wrappers, thus preserving those legacy codes and systems in tact. Because of the component-based architecture, all selected procedures can be registered or de-registered at run-time, and are completely reusable, reconfigurable, and modular.

Thompson, David E.↗

Decision Point 3 of Statement of Project Objectives (SOPO) “Recovery Act: Development of ITM Oxygen Technology for Integration with Advanced Industrial Systems”

Air Products is carrying out a scope of work under Phase 5 of the ITM Oxygen Cooperative Agreement to design, build, and operate a ceramic membrane fabrication facility (the -CerFabII) to enable production of membrane modules to supply a conceptual 2000 ton per day (TPD) ITM Oxygen facility (the -ITM Oxygen Development FacilityII), and to perform supporting development tasks in materials development and engineering development toward industrial, carbon capture and sequestration applications. Air Products is executing this project under the American Recovery and Reinvestment Act (ARRA) with the objective to accelerate the adoption of ITM Oxygen technology to help meet the country’s goals for deploying clean power plants. The objective of this Topical Report is to address the requirements of Decision Point 3 (DP3), which pertains to the status of all Tasks within Phase 5 and most notably the project status of the CerFab (Task 30) prior to authorization of funds for equipment purchase and construction of the facility. The intent of the DP3 is to provide the opportunity for DOE-NETL to review the status of these tasks and to make recommendations on forward project direction, including a recommendation to pass into Budget Period 8. In the area of Materials Development, Air Products has specified a high pressure dilatometer system which will enable measurements of material expansion of ITM ceramic compounds at very high oxygen partial pressures consistent with CCS applications. Under Task 28.2, subcontractor Ceramatec has made significant progress since DP2 in materials selection and process development and improvement for advanced architecture module fabrication. Ceramatec has determined a materials specification, and has selected a process for making the material. Ceramatec has further developed and selected the process for applying the membrane to unsintered advanced architecture wafers with a Two Step process. Ceramatec has built submodules meeting leak rate specifications and intact 1-TPD modules compromised of advanced architecture components. Equipment and processes required for implementation of the advanced architecture design in the CerFab have been identified and are included in the Task 30 scope of equipment supply. Under Task 29.0, Air Products has developed conceptual ideas for implementation of ITM Oxygen in a 2000 TPD test unit. These concepts are proposed for scale up of the ITM technology to large scale with reduced commercial risk. Under Task 30, Air Products and Ceramatec have collaborated to re-design the CerFab process with the advanced architecture wafer production process as primary, and laid out the new process in the Tooele building; the required process equipment have been specified. The project team updated the project cost and schedule estimates, including all environmental permit schedules. The team also re-assessed project risk and costs for the commissioning and operating phases of the program. Newly projected costs for the CerFab, for which details are provided here as attachments, indicate a savings of approximately $100,000 relative to the original estimate at the time of Phase 5 contract definitization. However, an assessment of risks associated with the equipment, process, and operations of the CerFab indicate that approximately $2.9 million of costs should be expected to address various issues in the project. In addition, $1.6 million of additional spending is expected relative to the original estimate to operate the facility during Task 30.2. Air Products proposes a plan to re-direct funds from Tasks 28, 29, and 31 to Task 30 as necessary to allow the CerFab to meet the Phase 5 program objectives.

Armstrong, Phillip↗