Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “Software Design”

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 181 records · Page 10

The conical scanner evaluation system design

The software design for the conical scanner evaluation system is presented. The purpose of this system is to support the performance analysis of the LANDSAT-D conical scanners, which are infrared horizon detection attitude sensors designed for improved accuracy. The system consists of six functionally independent subsystems and five interface data bases. The system structure and interfaces of each of the subsystems is described and the content, format, and file structure of each of the data bases is specified. For each subsystem, the functional logic, the control parameters, the baseline structure, and each of the subroutines are described. The subroutine descriptions include a procedure definition and the input and output parameters.

Cumella, K. E.↗

A design methodology for portable software on parallel computers

This final report for research that was supported by grant number NAG-1-995 documents our progress in addressing two difficulties in parallel programming. The first difficulty is developing software that will execute quickly on a parallel computer. The second difficulty is transporting software between dissimilar parallel computers. In general, we expect that more hardware-specific information will be included in software designs for parallel computers than in designs for sequential computers. This inclusion is an instance of portability being sacrificed for high performance. New parallel computers are being introduced frequently. Trying to keep one's software on the current high performance hardware, a software developer almost continually faces yet another expensive software transportation. The problem of the proposed research is to create a design methodology that helps designers to more precisely control both portability and hardware-specific programming details. The proposed research emphasizes programming for scientific applications. We completed our study of the parallelizability of a subsystem of the NASA Earth Radiation Budget Experiment (ERBE) data processing system. This work is summarized in section two. A more detailed description is provided in Appendix A ('Programming Practices to Support Eventual Parallelism'). Mr. Chrisman, a graduate student, wrote and successfully defended a Ph.D. dissertation proposal which describes our research associated with the issues of software portability and high performance. The list of research tasks are specified in the proposal. The proposal 'A Design Methodology for Portable Software on Parallel Computers' is summarized in section three and is provided in its entirety in Appendix B. We are currently studying a proposed subsystem of the NASA Clouds and the Earth's Radiant Energy System (CERES) data processing system. This software is the proof-of-concept for the Ph.D. dissertation. We have implemented and measured the performance of a portion of this subsystem on the Intel iPSC/2 parallel computer. These results are provided in section four. Our future work is summarized in section five, our acknowledgements are stated in section six, and references for published papers associated with NAG-1-995 are provided in section seven.

Nicol, David M.↗

COG Software Architecture Design Description Document

This COG Software Architecture Design Description Document describes the organization and functionality of the COG Multiparticle Monte Carlo Transport Code for radiation shielding and criticality calculations, at a level of detail suitable for guiding a new code developer in the maintenance and enhancement of COG. The intended audience also includes managers and scientists and engineers who wish to have a general knowledge of how the code works. This Document is not intended for end-users. This document covers the software implemented in the standard COG Version 10, as released through RSICC and IAEA. Software resources provided by other institutions will not be covered. This document presents the routines grouped by modules and in the order of the three processing phases. Some routines are used in multiple phases. The routine description is presented once - the first time the routine is referenced. Since this is presented at the level of detail for guiding a new code developer, only the routines invoked by another routine that are significant for the processing phase that is being detailed are presented. An index to all routines detailed is included. Tables for the primary data structures are also presented.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

COG Software Architecture Design Description Document

This COG Software Architecture Design Description Document describes the organization and functionality of the COG Multiparticle Monte Carlo Transport Code for radiation shielding and criticality calculations, at a level of detail suitable for guiding a new code developer in the maintenance and enhancement of COG. The intended audience also includes managers and scientists and engineers who wish to have a general knowledge of how the code works. This Document is not intended for end-users.

61 RADIATION PROTECTION AND DOSIMETRY↗

Formalization and visualization of domain-specific software architectures

This paper describes a domain-specific software design system based on the concepts of software architectures engineering and domain-specific models and languages. In this system, software architectures are used as high level abstractions to formulate a domain-specific software design. The software architecture serves as a framework for composing architectural fragments (e.g., domain objects, system components, and hardware interfaces) that make up the knowledge (or model) base for solving a problem in a particular application area. A corresponding software design is generated by analyzing and describing a system in the context of the software architecture. While the software architecture serves as the framework for the design, this concept is insufficient by itself for supplying the additional details required for a specific design. Additional domain knowledge is still needed to instantiate components of the architecture and develop optimized algorithms for the problem domain. One possible way to obtain the additional details is through the use of domain-specific languages. Thus, the general concept of a software architecture and the specific design details provided by domain-specific languages are combined to create what can be termed a domain-specific software architecture (DSSA).

Bailor, Paul D.↗

IDEF4 technical report, version 1.0

A language for the representation of object oriented software designs is described. IDEF4, a methodology for object-oriented design, is being developed as a design tool for software designers who use such object-oriented languages. Such languages include the Common LISP Object System, Flavors, C++, Smalltalk, Objective C, and others. Since effective usage of the object-oriented paradigm requires a different thought process than that used with conventional procedural or database languages, standard methodologies such as structure charts, data flow diagrams, and traditional data design models (hierarchical, relational, and network) are not sufficient. IDEF4 seeks to provide the necessary facilities to support the object-oriented design decision making process. Specifically, the two primary design goals of IDEF4 are: (1) to provide support for creating object oriented designs whose implementations will exhibit desirable life cycle qualities and reduce total implementation development time; and (2) to make it easy to evaluate object oriented code to determine whether or not the delivered product both conforms to the design and exhibits the desired life cycle qualities. The application of IDEF4 in the life cycle of a software development project is intended to be focused on those activities after a decision has been made to employ object oriented programming technology, but prior to detailed code specification.

Mayer, Richard J.↗

Software System Design for Large Scale, Spatially-explicit Agroecosystem Modeling

Recently, site-based agroecosystem model has been applied at regional and state level to enable comprehensive analyses of environmental sustainability of food and biofuel production. Those large-scale, spatially-explicit simulations present computational challenges in software systems design. Herein, we describe our software system design for large-scale, spatially-explicit agroecosystem modeling and data analysis. First, we describe the software design principles in three major phases: data preparation, high performance simulation, and data management and analysis. Then, we use a case study at a regional intensive modeling area (RIMA) to demonstrate our system implementation and capability.

Wang, Dali↗

Advanced software development workstation project: Engineering scripting language. Graphical editor

Software development is widely considered to be a bottleneck in the development of complex systems, both in terms of development and in terms of maintenance of deployed systems. Cost of software development and maintenance can also be very high. One approach to reducing costs and relieving this bottleneck is increasing the reuse of software designs and software components. A method for achieving such reuse is a software parts composition system. Such a system consists of a language for modeling software parts and their interfaces, a catalog of existing parts, an editor for combining parts, and a code generator that takes a specification and generates code for that application in the target language. The Advanced Software Development Workstation is intended to be an expert system shell designed to provide the capabilities of a software part composition system.

Source record↗

CARD: CFD for Advanced Reactor Design

Software Tools and Expertise To Address Multiphase Flow Challenges in<p>Research, Design, and Optimization</p><p>This is the annual CARD project update to be presented at the 2024 FECM/NETL Spring R&amp;D Project Review Meeting.</p>

Dietiker, Jeff↗

SEPAC flight software detailed design specifications, volume 1

The detailed design specifications (as built) for the SEPAC Flight Software are defined. The design includes a description of the total software system and of each individual module within the system. The design specifications describe the decomposition of the software system into its major components. The system structure is expressed in the following forms: the control-flow hierarchy of the system, the data-flow structure of the system, the task hierarchy, the memory structure, and the software to hardware configuration mapping. The component design description includes details on the following elements: register conventions, module (subroutines) invocaton, module functions, interrupt servicing, data definitions, and database structure.

Source record↗

Lessons learned from an Ada conversion project

Recognizing the importance of building software with the robustness to accommodate rapid advances in technology, developers have focused on methods which preserve both past and future investment in software and in providing an advanced software engineering environment that frees the engineer, to the greatest extent possible, from the more routine aspects of software design and development. The software engineer is permitted to concentrate on the creative aspects of problem resolution. Standard languages such as Ada maximize portability across hardware and operating systems. Standard interfaces which enhance portability and permit the incorporation of new technology as it becomes available have been developed. Software design and development techniques which maximize portability receive increasing emphasis. Experience gained in porting an Ada application between two widely varying environments is evaluated in light of current practices to maximize software portability.

Porter, Tim↗

Using SFOC to fly the Magellan Venus mapping mission

Traditionally, spacecraft flight operations at the Jet Propulsion Laboratory (JPL) have been performed by teams of spacecraft experts utilizing ground software designed specifically for the current mission. The Jet Propulsion Laboratory set out to reduce the cost of spacecraft mission operations by designing ground data processing software that could be used by multiple spacecraft missions, either sequentially or concurrently. The Space Flight Operations Center (SFOC) System was developed to provide the ground data system capabilities needed to monitor several spacecraft simultaneously and provide enough flexibility to meet the specific needs of individual projects. The Magellan Spacecraft Team utilizes the SFOC hardware and software designed for engineering telemetry analysis, both real-time and non-real-time. The flexibility of the SFOC System has allowed the spacecraft team to integrate their own tools with SFOC tools to perform the tasks required to operate a spacecraft mission. This paper describes how the Magellan Spacecraft Team is utilizing the SFOC System in conjunction with their own software tools to perform the required tasks of spacecraft event monitoring as well as engineering data analysis and trending.

Bucher, Allen W.↗

Radiometric Testing of Germicidal UV Products, Round 1: UV-C Towers and Whole-Room Luminaires (CALiPER Summary Report)

This summary report analyzes the independently tested performance of 13 germicidal ultraviolet (GUV) products purchased between February and July 2022. A companion full report (DOE 2023) provides additional information and discussion of the tested products, test methods, and results. The products were of three different types: • Seven portable, consumer-oriented GUV towers designed to be placed on the floor or a desk of an unoccupied room to disinfect air and surfaces. Five of these products used LED sources and two products had low-pressure mercury (LPM) sources. • One GUV whole-room luminaire designed to be installed on a ceiling to disinfect air when a room is occupied. This product had LED sources. • Five GUV troffer or high-bay style whole-room luminaires designed to be installed in or suspended from a ceiling to disinfect air and surfaces when a room is unoccupied. All five had LPM sources. Product testing covered radiometric and electrical performance for all 13 products as well as photobiological safety evaluation if product documentation included testable claims. Measurement results enable comparison between products and against manufacturer or vendor claims. Testing identified numerous issues related to the accuracy of claimed GUV product performance. Claims were often untestable, contradictory, ambiguous, or used incorrect units and/or terminology. When claims were testable, they often did not match test results. For example, three LED products that claimed to emit UV-C emitted only UV-A. Product claim issues were more common among consumer-oriented tower products, but all product types exhibited problems with accurate performance claims. The UV-C radiant efficiency (calculated as UV-C output power divided by electrical input power) of the products varied widely, even among similar products using the same source technologies. For example, the UV-C radiant efficiency of LPM products varied by greater than a factor of three for the same product type, indicating a large potential energy savings opportunity for products that are better designed for efficiency. LED products had orders-of-magnitude lower UV-C radiant efficiency than LPM products. This study also identified several testing challenges and limitations. Most significant among these is the capability to accurately test and report the performance of larger GUV products. Whereas integrating spheres are used to quickly measure total radiant flux (i.e., output power) and spectral distribution, goniometers are used to measure radiant intensity distribution (from which radiant flux can be calculated). Integrating spheres require a specialized and costly coating to test UV, and the testing laboratory for this round of products had only a 20-inch diameter hemisphere with this capability. The integrating sphere accommodated just 2 of the 10 UV-C emitting products. Goniometer testing had a different size limitation in that mirrors typically used to increase goniometer test distance to the far field reflect little to no UV. As a result, the study evaluated only 6 of 13 products in the far field. Electronic files of UV-C intensity data for the other 7 products, which would typically be imported into design software for designing GUV applications, may not be reliable for predicting irradiance at arbitrary far-field distances (IES 2022a; CIE 2020). Specifiers and buyers of GUV products need accurate performance claims and data to deploy GUV technology safely and effectively. This CALiPER GUV Round 1 report demonstrates the significant education and training manufacturers and vendors still require to accurately test and report the performance of their GUV products. Further industry standards and guidelines may address testing limitations and improve test methods, product performance, and the accuracy of performance claims.

42 ENGINEERING↗

Radiometric Testing of Germicidal UV Products, Round 1: UV-C Towers and Whole-Room Luminaires (CALiPER Full Report)

This report analyzes the independently tested performance of 13 germicidal ultraviolet (GUV) products purchased between February and July 2022. The products were of three different types: • Seven portable, consumer-oriented GUV towers designed to be placed on the floor or a desk of an unoccupied room to disinfect air and surfaces. Five of these products used LED sources and two products had low-pressure mercury (LPM) sources. • One GUV whole-room luminaire designed to be installed on a ceiling to disinfect air when a room is occupied. This product had LED sources. • Five GUV troffer or high-bay style whole-room luminaires designed to be installed in or suspended from a ceiling to disinfect air and surfaces when a room is unoccupied. All five had LPM sources. Product testing covered radiometric and electrical performance for all 13 products as well as photobiological safety evaluation if product documentation included testable claims. Measurement results enable comparison between products and against manufacturer or vendor claims. Testing identified numerous issues related to the accuracy of claimed GUV product performance. Claims were often untestable, contradictory, ambiguous, or used incorrect units and/or terminology. When claims were testable, they often did not match test results. For example, three LED products that claimed to emit UV-C emitted only UV-A. Product claim issues were more common among consumer-oriented tower products, but all product types exhibited problems with accurate performance claims. The UV-C radiant efficiency (calculated as UV-C output power divided by electrical input power) of the products varied widely, even among similar products using the same source technologies. For example, the UV-C radiant efficiency of LPM products varied by greater than a factor of three for the same product type, indicating a large potential energy savings opportunity for products that are better designed for efficiency. LED products had orders-of-magnitude lower UV-C radiant efficiency than LPM products. This study also identified several testing challenges and limitations. Most significant among these is the capability to accurately test and report the performance of larger GUV products. Whereas integrating spheres are used to quickly measure total radiant flux (i.e., output power) and spectral distribution, goniometers are used to measure radiant intensity distribution (from which radiant flux can be calculated). Integrating spheres require a specialized and costly coating to test UV, and the testing laboratory for this round of products had only a 20-inch diameter hemisphere with this capability. The integrating sphere accommodated just 2 of the 10 UV-C emitting products. Goniometer testing had a different size limitation in that mirrors typically used to increase goniometer test distance to the far field reflect little to no UV. As a result, the study evaluated only 6 of 13 products in the far field. Electronic files of UV-C intensity data for the other 7 products, which would typically be imported into design software for designing GUV applications, may not be reliable for predicting irradiance at arbitrary far-field distances (IES 2022a; CIE 2020). Specifiers and buyers of GUV products need accurate performance claims and data to deploy GUV technology safely and effectively. This CALiPER GUV Round 1 report demonstrates the significant education and training manufacturers and vendors still require to accurately test and report the performance of their GUV products. Further industry standards and guidelines may address testing limitations and improve test methods, product performance, and the accuracy of performance claims.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Radiometric Testing of Germicidal UV Products, Round 1: UV-C Towers and Whole-Room Luminaires (CALiPER Full Report)

This report analyzes the independently tested performance of 13 germicidal ultraviolet (GUV) products purchased between February and July 2022. The products were of three different types: • Seven portable, consumer-oriented GUV towers designed to be placed on the floor or a desk of an unoccupied room to disinfect air and surfaces. Five of these products used LED sources and two products used low-pressure mercury (LPM) sources. • One non-portable GUV whole-room luminaire designed to be installed on a ceiling to disinfect air when a room is occupied. This product used an LED source. • Five non-portable GUV troffer or high-bay style whole-room luminaires designed to be installed in or suspended from a ceiling to disinfect air and surfaces when a room is unoccupied. All five used LPM sources. Radiometric and electrical performance was evaluated for all 13 products. Photobiological safety was also assessed for two of the products because their documentation included testable claims. The test results were compared across products and to manufacturer or vendor claims. The testing identified many issues related to the accuracy of reported GUV product performance. Claims were often untestable, contradictory, ambiguous, or used incorrect units and/or terminology. And when claims were testable, they often did not match test results. For example, three products that claimed to emit UV-C emitted only UV-A. These product claim issues were more numerous with consumer-oriented tower products, but problems with accurate performance claims were found across all products. The UV-C radiant efficiency of the products varied widely, even among similar products using the same source technologies. For example, the UV-C radiant efficiency of LPM products varied by greater than a factor of three for the same product type, indicating a large potential energy savings opportunity for products that are better designed for efficiency. LED products had orders-of-magnitude lower UV-C radiant efficiency than LPM products. Several testing challenges and limitations were identified. Most significant among these is the capability to accurately test and report the performance of larger GUV products. Integrating spheres require a specialized and costly coating to test UV, and the testing laboratory for this round of products had only a 20-inch diameter hemisphere with this capability. Only 2 of the 10 UV-C emitting products could be tested in this sphere. Goniometer testing had a different size limitation in that mirrors typically used to increase goniometer test distance to the far field are not reflective of UV and therefore could not be used to increase test distance. As a result, 7 of 13 products could not be tested far field. The implication is that electronic files of UV-C intensity data typically imported into design software for designing GUV applications may not be reliable for predicting irradiance at arbitrary far-field distances. It is currently unclear if these are industry-wide testing laboratory limitations, and what solutions may exist to address them. Specifiers and buyers of GUV products will need accurate performance claims and data to safely and effectively deploy GUV technology to reduce the transmission of diseases in buildings. This CALiPER GUV Round 1 report demonstrates the significant education and training that is needed for manufacturers and vendors to accurately test and report the performance of their GUV products. Further standards and guidelines are needed to improve test methods, address testing limitations, and improve reporting of product performance. Additionally, the wide range in UV-C radiant efficiency of GUV products means there is a large energy-savings opportunity for more energy efficient GUV products.

32 ENERGY CONSERVATION, CONSUMPTION, AND UTILIZATI↗

Radiometric Testing of Germicidal UV Products, Round 1: UV-C Towers and Whole-Room Luminaires (CALiPER Summary Report)

This summary report analyzes the independently tested performance of 13 germicidal ultraviolet (GUV) products purchased between February and July 2022. A companion full report provides additional information and discussion of the tested products, test methods, and results. The products were of three different types: • Seven portable, consumer-oriented GUV towers designed to be placed on the floor or a desk of an unoccupied room to disinfect air and surfaces. Five of these products used LED sources and two products used low-pressure mercury (LPM) sources. • One non-portable GUV whole-room luminaire designed to be installed on a ceiling to disinfect air when a room is occupied. This product used an LED source. • Five non-portable GUV troffer or high-bay style whole-room luminaires designed to be installed in or suspended from a ceiling to disinfect air and surfaces when a room is unoccupied. All five used LPM sources. Radiometric and electrical performance was evaluated for all 13 products. Photobiological safety was also assessed for two of the products because their documentation included testable claims. The test results were compared across products and to manufacturer or vendor claims. The testing identified many issues related to the accuracy of reported GUV product performance. Claims were often untestable, contradictory, ambiguous, or used incorrect units and/or terminology. And when claims were testable, they often did not match test results. For example, three products that claimed to emit UV-C emitted only UV-A. These product claim issues were more numerous with consumer-oriented tower products, but problems with accurate performance claims were found across all products. The UV-C radiant efficiency of the products varied widely, even among similar products using the same source technologies. For example, the UV-C radiant efficiency of LPM products varied by greater than a factor of three for the same product type, indicating a large potential energy savings opportunity for products that are better designed for efficiency. LED products had orders-of-magnitude lower UV-C radiant efficiency than LPM products. Several testing challenges and limitations were identified. Most significant among these is the capability to accurately test and report the performance of larger GUV products. Integrating spheres require a specialized and costly coating to test UV, and the testing laboratory for this round of products had only a 20-inch diameter hemisphere with this capability. Only 2 of the 10 UV-C emitting products could be tested in this sphere. Goniometer testing had a different size limitation in that mirrors typically used to increase goniometer test distance to the far field are not reflective of UV and therefore could not be used to increase test distance. As a result, 7 of 13 products could not be tested far field. The implication is that electronic files of UV-C intensity data typically imported into design software for designing GUV applications may not be reliable for predicting irradiance at arbitrary far-field distances. It is currently unclear if these are industry-wide testing laboratory limitations, and what solutions may exist to address them. Specifiers and buyers of GUV products will need accurate performance claims and data to safely and effectively deploy GUV technology to reduce the transmission of diseases in buildings. This CALiPER GUV Round 1 report demonstrates the significant education and training that is needed for manufacturers and vendors to accurately test and report the performance of their GUV products. Further standards and guidelines are needed to improve test methods, address testing limitations, and improve reporting of product performance. Additionally, the wide range in UV-C radiant efficiency of GUV products means there is a large energy-savings opportunity for more energy efficient GUV products.

37 INORGANIC, ORGANIC, PHYSICAL, AND ANALYTICAL CH↗

Basic avionics module design for general aviation aircraft

The design of an advanced digital avionics system (basic avionics module) for general aviation aircraft operated with a single pilot under IFR conditions is described. The microprocessor based system provided all avionic functions, including flight management, navigation, and lateral flight control. The mode selection was interactive with the pilot. The system used a navigation map data base to provide operation in the current and planned air traffic control environment. The system design included software design listings for some of the required modules. The distributed microcomputer uses the IEEE 488 bus for interconnecting the microcomputer and sensors.

Smyth, R. K.↗

Modular hardware synthesis using an HDL

Although hardware description languages (HDL) are becoming more and more necessary to automated design systems, their application is complicated due to the difficulty in translating the HDL description into an implementable format, nonfamiliarity of hardware designers with high-level language programming, nonuniform design methodologies and the time and costs involved in transfering HDL design software. Digital design language (DDL) suffers from all of the above problems and in addition can only by synthesized on a complete system and not on its subparts, making it unsuitable for synthesis using standard modules or prefabricated chips such as those required in LSI or VLSI circuits. The present paper presents a method by which the DDL translator can be made to generate modular equations that will allow the system to be synthesized as an interconnection of lower-level modules. The method involves the introduction of a new language construct called a Module which provides for the separate translation of all equations bounded by it.

Covington, J. A.↗