Search NASA⌕ Search

SEARCH · Search NASA

Results for “Design Codes”

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 469 records · Page 26
All sourcesNASA NTRSDOE OSTI
NASA NTRS1984

Development of a turbomachinery design optimization procedure using a multiple-parameter nonlinear perturbation method

An investigation was carried out to complete the preliminary development of a combined perturbation/optimization procedure and associated computational code for designing optimized blade-to-blade profiles of turbomachinery blades. The overall purpose of the procedures developed is to provide demonstration of a rapid nonlinear perturbation method for minimizing the computational requirements associated with parametric design studies of turbomachinery flows. The method combines the multiple parameter nonlinear perturbation method, successfully developed in previous phases of this study, with the NASA TSONIC blade-to-blade turbomachinery flow solver, and the COPES-CONMIN optimization procedure into a user's code for designing optimized blade-to-blade surface profiles of turbomachinery blades. Results of several design applications and a documented version of the code together with a user's manual are provided.

Stahara, S. S.↗
DOE OSTI2022

Proposed Material Properties, Allowable Stresses, and Design Curves of Diffusion Bonded Alloy 800H for the ASME Code Section III Division 5

Abstract Increased interest in compact heat exchangers (CHXs) to serve as intermediate heat exchangers of very high temperature reactors resulted in significant research and development on their design, analysis, and construction. Printed circuit heat exchangers are a type of CHXs with high thermal efficiency and compactness achieved through diffusion bonding a stack of etched plates with millimeter scaled channels. The diffusion bonding process changes the microstructural and mechanical properties of the wrought metal plates. The current nonnuclear design code ASME section VIII, division 1 captures the material property change through a “joint efficiency factor.” However, the current nuclear design code ASME section III, division 5 does not address or support the diffusion bonded material properties. Hence, there is a need to develop allowable stresses, isochronous curves, and fatigue life curves for various diffusion bonded alloys. In this study, Alloy 800H material was selected to establish the diffusion bonded material properties under tension, creep, fatigue, and creep-fatigue loads at elevated temperatures in the range 550–760 °C. A set of tests on diffusion bonded Alloy 800H (DB 800H) were performed and the acquired data are used in developing allowable stresses Sy, Su, Sr, Sm, St, Smt, So, isochronous curves and fatigue life curves according to the ASME section III, division 5 requirements. This paper also presents detailed procedures used in developing the ASME code section III division 5 design provisions for diffusion bonded Alloy 800H.

Engineering↗
NASA NTRS2008

Certifying Auto-Generated Flight Code

Model-based design and automated code generation are being used increasingly at NASA. Many NASA projects now use MathWorks Simulink and Real-Time Workshop for at least some of their modeling and code development. However, there are substantial obstacles to more widespread adoption of code generators in safety-critical domains. Since code generators are typically not qualified, there is no guarantee that their output is correct, and consequently the generated code still needs to be fully tested and certified. Moreover, the regeneration of code can require complete recertification, which offsets many of the advantages of using a generator. Indeed, manual review of autocode can be more challenging than for hand-written code. Since the direct V&V of code generators is too laborious and complicated due to their complex (and often proprietary) nature, we have developed a generator plug-in to support the certification of the auto-generated code. Specifically, the AutoCert tool supports certification by formally verifying that the generated code is free of different safety violations, by constructing an independently verifiable certificate, and by explaining its analysis in a textual form suitable for code reviews. The generated documentation also contains substantial tracing information, allowing users to trace between model, code, documentation, and V&V artifacts. This enables missions to obtain assurance about the safety and reliability of the code without excessive manual V&V effort and, as a consequence, eases the acceptance of code generators in safety-critical contexts. The generation of explicit certificates and textual reports is particularly well-suited to supporting independent V&V. The primary contribution of this approach is the combination of human-friendly documentation with formal analysis. The key technical idea is to exploit the idiomatic nature of auto-generated code in order to automatically infer logical annotations. The annotation inference algorithm itself is generic, and parametrized with respect to a library of coding patterns that depend on the safety policies and the code generator. The patterns characterize the notions of definitions and uses that are specific to the given safety property. For example, for initialization safety, definitions correspond to variable initializations while uses are statements which read a variable, whereas for array bounds safety, definitions are the array declarations, while uses are statements which access an array variable. The inferred annotations are thus highly dependent on the actual program and the properties being proven. The annotations, themselves, need not be trusted, but are crucial to obtain the automatic formal verification of the safety properties without requiring access to the internals of the code generator. The approach has been applied to both in-house and commercial code generators, but is independent of the particular generator used. It is currently being adapted to flight code generated using MathWorks Real-Time Workshop, an automatic code generator that translates from Simulink/Stateflow models into embedded C code.

Denney, Ewen↗
DOE OSTI2023

Centrifugal Pump Model for System Codes for Advanced NPP Designs

In this document, a homologous model and one-dimensional line model for centrifugal pump are described to provide the theoretical background of a pump model to be developed in system-level codes. Input and output parameters are proposed, along with a summary of the governing equations for each model. Furthermore, hydraulic performance degradation of centrifugal pump is also modeled in the homologous pump model. This document suggests that system codes provide a homologous and one-dimensional line model for centrifugal pumps, allowing the users to choose the model that best fits their purposes.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗
DOE OSTI2025

An archaeal genetic code with all TAG codons as pyrrolysine

Multiple genetic codes developed during the evolution of eukaryotes and bacteria, yet no alternative genetic code is known for archaea. We used proteomics to confirm our prediction that certain archaea consistently incorporate pyrrolysine (Pyl) at TAG codons, supporting an alternative archaeal genetic code that we designate the Pyl code. This genetic code has 62 sense codons encoding 21 amino acids. In contrast to monophyletic genetic code distributions in bacteria, the archaeal Pyl code occurs sporadically, indicating that it arose independently in multiple lineages. We discovered that more than 1800 archaeal proteins contain Pyl, increasing the number of such proteins by two orders of magnitude. Additionally, five Pyl transfer RNA (tRNA) pyrrolysyl–tRNA synthetase pairs from Pyl-code archaea were used to introduce Pyl analogs into proteins in Escherichia coli.

Kivenson, Veronika [University of California, Berk↗
NASA NTRS1973

A digital communications system for manned spaceflight applications.

A highly efficient, all-digital communications signal design employing convolutional coding and PN spectrum spreading is described for two-way transmission of voice and data between a manned spacecraft and ground. Variable-slope delta modulation is selected for analog/digital conversion of the voice signal, and a convolutional decoder utilizing the Viterbi decoding algorithm is selected for use at each receiving terminal. A PN spread spectrum technique is implemented to protect against multipath effects and to reduce the energy density (per unit bandwidth) impinging on the earth's surface to a value within the guidelines adopted by international agreement. Performance predictions are presented for transmission via a TDRS (tracking and data relay satellite) system and for direct transmission between the spacecraft and earth. Hardware estimates are provided for a flight-qualified communications system employing the coded digital signal design.

Batson, B. H.↗
NASA NTRS1988

The Environment for Application Software Integration and Execution (EASIE), version 1.0. Volume 3: Program execution guide

The Environment for Application Software Integration and Execution, EASIE, provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating the results of many stand-alone engineering analysis programs. EASIE provides access to these programs via a quick, uniform, user-friendly interface. In addition, EASIE provides utilities which aid in the execution of the following tasks: selection of application programs, modification and review of program data, automatic definition and coordination of data files during program execution and a logging of steps executed throughout a design study. Volume 3, the Program Execution Guide, describes the executive capabilities provided by EASIE and defines the command language and menus available under Version 1.0. EASIE provides users with two basic modes of operation. One is the Application-Derived Executive (ADE) which provides users with sufficient guidance to quickly review data, select menu action items, and execute application programs. The second is the Complete Control Executive (CCE), which provides a full executive interface allowing users in-depth control of the design process.

Schwing, James L.↗
NASA NTRS1988

The Environment for Application Software Integration and Execution (EASIE), version 1.0. Volume 2: Program integration guide

The Environment for Application Software Integration and Execution, EASIE, provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational data base management system. In volume 2, the use of a SYSTEM LIBRARY PROCESSOR is used to construct a DATA DICTIONARY describing all relations defined in the data base, and a TEMPLATE LIBRARY. A TEMPLATE is a description of all subsets of relations (including conditional selection criteria and sorting specifications) to be accessed as input or output for a given application. Together, these form the SYSTEM LIBRARY which is used to automatically produce the data base schema, FORTRAN subroutines to retrieve/store data from/to the data base, and instructions to a generic REVIEWER program providing review/modification of data for a given template. Automation of these functions eliminates much of the tedious, error prone work required by the usual approach to data base integration.

Jones, Kennie H.↗
NASA NTRS1989

The Environment for Application Software Integration and Execution (EASIE) version 1.0. Volume 1: Executive overview

The Environment for Application Software Integration and Execution (EASIE) provides a methodology and a set of software utility programs to ease the task of coordinating engineering design and analysis codes. EASIE was designed to meet the needs of conceptual design engineers that face the task of integrating many stand-alone engineering analysis programs. Using EASIE, programs are integrated through a relational database management system. Volume 1, Executive Overview, gives an overview of the functions provided by EASIE and describes their use. Three operational design systems based upon the EASIE software are briefly described.

Rowell, Lawrence F.↗
NASA NTRS1991

Discrete shape sensitivity equations for aerodynamic problems

Intensive research and development in Computational Fluid Dynamics (CFD) has recently produced many powerful CFD codes to simulate complex aerodynamic phenomena. However, in order to enhance the usefulness of these CFD codes for design practice, development of design sensitivity equations compatible to these codes becomes very important. This paper represents a part of such an effort to develop a sensitivity analysis methodology that enables the sensitivity equations to be implemented into existing CFD codes with minimal code modification. The methodology is based upon a preelimination procedure which accounts for consistently linearized boundary conditions. Formulations of both the direct differentiation and the adjoint variable methods will be presented in the paper.

Hou, Gene J.-W.↗
DOE OSTI2021

Comprehensive Margin Assessment of the ASME Section III, Division 5, Class A Primary Load Design Rules

This report provides a comprehensive margin assessment of the ASME Section III, Division 5, Subsection HB, Subpart B rules for the design of high temperature reactor components against load controlled stress limits. These rules, often called the Code primary load design rules, provide protection against creep rupture and plastic collapse under steady conditions. The method adopted here is to compare the deterministic ASME design life, according to the primary load design rules, against the expected, statistical service life of the component, considering creep rupture as the relevant failure mode. The report provides the design margin of the ASME rules in terms of the probability of premature failure -- the probability that the component fails in service before reaching the ASME design life. To complete this assessment, the report describes the development of a statistical creep life assessment procedure accounting for variations in the component loading, material creep rate, and the material rupture time. This includes a novel method for correlating creep rupture data using a Gaussian process accounting for heat-to-heat variation in the Larson-Miller time-temperature parameter. The report applies the complete margin assessment process to quantify the design margin inherent in the ASME primary load design rules as a function of temperature for relevant component geometries and materials. The overall conclusion is that the ASME rules are conservative, providing designs with very small probability of premature failure, but some optimization of the Code design rules is possible to provide a more uniform design margin.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗
NASA NTRS1981

Transonic wing design using potential-flow codes - Successes and failures

The state-of-the-art of transonic wing design by use of computer codes based on the potential flow-theory is presented. The capabilities and limitations of these codes are exemplified by several experiment-theory correlations, including an assessment of pressure distribution from isolated wing and wing-body codes. Computer codes using both conservative and nonconservative differencing schemes were used, and the effects of boundary-layer corrections were considered. Results showed that calculations from a full potential, isolated code correlate well with data from an isolated wing test, but may give poor predictions of the aerodynamic characteristics of some wing-body configurations. Boundary-layer correlations were found to have only moderate effects on experiment-theory correlation. Aeroelastic effects were considered important for high aspect ratio wings of low to moderate thickness, and viscous effects were minimal for typical cruise conditions, even for Reynold's numbers as low as two million. The effect of wind-tunnel walls on experiment-theory correlations remained inconclusive. A wing-body code was used to calculate the flow field about a wing-body configuration with body-mounted engines, typical of the transonic Biz-Jet aircraft.

Hicks, R. M.↗
NASA NTRS1988

A performance index approach to aerodynamic design with the use of analysis codes only

A method is described for designing an aerodynamic configuration for a specified performance vector, based on results from several similar, but not identical, trial configurations, each defined by a geometry parameter vector. The theory shows the method effective provided that: (1) the results for the trial configuration provide sufficient variation so that a linear combination of them approximates the specified performance; and (2) the difference between the performance vectors (including the specifed performance) are sufficiently small that the linearity assumption of sensitivity analysis applies to the differences. A computed example describes the design of a high supersonic Mach number missile wing body configuration based on results from a set of four trial configurations.

Barger, Raymond L.↗
NASA NTRS1999

Software Development Processes Applied to Computational Icing Simulation

The development of computational icing simulation methods is making the transition form the research to common place use in design and certification efforts. As such, standards of code management, design validation, and documentation must be adjusted to accommodate the increased expectations of the user community with respect to accuracy, reliability, capability, and usability. This paper discusses these concepts with regard to current and future icing simulation code development efforts as implemented by the Icing Branch of the NASA Lewis Research Center in collaboration with the NASA Lewis Engineering Design and Analysis Division. With the application of the techniques outlined in this paper, the LEWICE ice accretion code has become a more stable and reliable software product.

Levinson, Laurie H.↗
DOE OSTI2020

Model uncertainty in accelerator application simulations

Monte-Carlo nuclear reaction and transport codes are widely used to devise accelerator-based nuclear physics experiments; at the same time, many experiments are performed to validate the Monte-Carlo codes, which can be used for the design of full-scale nuclear power applications or the design of new benchmark experiments. Dedicated model benchmark studies investigate a broad range of nuclear reactions and quantities. Examples of these include isotope formation or secondary particle fluxes that result from the interactions of GeV-range hadrons with monoisotopic targets, which can be used to assess the respective systematic uncertainty of models. Such benchmark studies, as well as many nuclear application experiments and simulations carried out by various groups over the last few decades, enable us to draw methodological lessons. In this work, model uncertainty determined based on available experimental data allow us to identify the effects of practitioner expertise as well as the design of codes (user access to micro-scale parameters) on the range of uncertainties. We found that in cases when simulations are performed by code developers or users that are very experienced in performing simulations, the model to experiment quantity ratios generally agree with the limits determined by dedicated benchmark studies. In other cases, the ratios generally tend to be either smaller (underestimation of model error) or larger (overestimation of model error). A plausible explanation of the aforementioned effects is suggested.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗
NASA NTRS1998

Multiphysics Code Demonstrated for Propulsion Applications

The utility of multidisciplinary analysis tools for aeropropulsion applications is being investigated at the NASA Lewis Research Center. The goal of this project is to apply Spectrum, a multiphysics code developed by Centric Engineering Systems, Inc., to simulate multidisciplinary effects in turbomachinery components. Many engineering problems today involve detailed computer analyses to predict the thermal, aerodynamic, and structural response of a mechanical system as it undergoes service loading. Analysis of aerospace structures generally requires attention in all three disciplinary areas to adequately predict component service behavior, and in many cases, the results from one discipline substantially affect the outcome of the other two. There are numerous computer codes currently available in the engineering community to perform such analyses in each of these disciplines. Many of these codes are developed and used in-house by a given organization, and many are commercially available. However, few, if any, of these codes are designed specifically for multidisciplinary analyses. The Spectrum code has been developed for performing fully coupled fluid, thermal, and structural analyses on a mechanical system with a single simulation that accounts for all simultaneous interactions, thus eliminating the requirement for running a large number of sequential, separate, disciplinary analyses. The Spectrum code has a true multiphysics analysis capability, which improves analysis efficiency as well as accuracy. Centric Engineering, Inc., working with a team of Lewis and AlliedSignal Engines engineers, has been evaluating Spectrum for a variety of propulsion applications including disk quenching, drum cavity flow, aeromechanical simulations, and a centrifugal compressor flow simulation.

Lawrence, Charles↗
NASA NTRS2016

NDARC NASA Design and Analysis of Rotorcraft - Input, Appendix 4

The NDARC code performs design and analysis tasks. The design task involves sizing the rotorcraft to satisfy specified design conditions and missions. The analysis tasks can include off-design mission performance analysis, flight performance calculation for point operating conditions, and generation of subsystem or component performance maps. The principal tasks (sizing, mission analysis, flight performance analysis) are shown in the figure as boxes with heavy borders. Heavy arrows show control of subordinate tasks. The aircraft description consists of all the information, input and derived, that denes the aircraft. The aircraft consists of a set of components, including fuselage, rotors, wings, tails, and propulsion. This information can be the result of the sizing task; can come entirely from input, for a fixed model; or can come from the sizing task in a previous case or previous job. The aircraft description information is available to all tasks and all solutions. The sizing task determines the dimensions, power, and weight of a rotorcraft that can perform a specified set of design conditions and missions. The aircraft size is characterized by parameters such as design gross weight, weight empty, rotor radius, and engine power available. The relations between dimensions, power, and weight generally require an iterative solution. From the design flight conditions and missions, the task can determine the total engine power or the rotor radius (or both power and radius can be fixed), as well as the design gross weight, maximum takeoff weight, drive system torque limit, and fuel tank capacity. For each propulsion group, the engine power or the rotor radius can be sized. Missions are defined for the sizing task, and for the mission performance analysis. A mission consists of a number of mission segments, for which time, distance, and fuel burn are evaluated. For the sizing task, certain missions are designated to be used for design gross weight calculations; for transmission sizing; and for fuel tank sizing. The mission parameters include mission takeoff gross weight and useful load. For specified takeoff fuel weight with adjustable segments, the mission time or distance is adjusted so the fuel required for the mission equals the takeoff fuel weight. The mission iteration is on fuel weight or energy. Flight conditions are specified for the sizing task, and for the flight performance analysis. For the sizing task, certain flight conditions are designated to be used for design gross weight calculations; for transmission sizing; for maximum takeoff weight calculations; and for anti-torque or auxiliary thrust rotor sizing. The flight condition parameters include gross weight and useful load. For flight conditions and mission takeoff, the gross weight can be maximized, such that the power required equals the power available. A flight state is defined for each mission segment and each flight condition. The aircraft performance can be analyzed for the specified state, or a maximum effort performance can be identified. The maximum effort is specified in terms of a quantity such as best endurance or best range, and a variable such as speed, rate of climb, or altitude.

Rotorcraft Input↗