Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “code verification”

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 451 records · Page 25

Verification and Validation of High Explosive Reactive Burn Models Implemented in LANL's EAP and LAP Code Base

Reactive burn models represent a significant leap in high explosive (HE) modeling capability. The first generation of engineering models of HE detonation are called programmed burn models and they are largely based on the distance between a prescribed detonation point and each zone in a simulation. There have been many advancements to programmed burn models over the years and when the assumptions upon which they are based are met, a properly tuned programmed burn model can be highly accurate but if any of their assumptions is not met, as is the case for corner turning or weakly initiated HE burn, they will give the wrong answer. Reactive burn models represent an entirely new way of modeling HE burn. They use the local conditions of a zone – e.g. temperature, pressure or density – as calculated by a hydrocode to determine if and when the zone is going to detonate and if so, how rapidly. This difference opens up an entirely new set of capabilities for HE modeling. It makes it possible to accurately and predictively model phenomena like the effect of confinement and the formation of dead zones. Reactive burn models have seen sustained development effort at LANL for at least the last decade but several recent developments make it timely to transition reactive burn models from a research topic to a production tool. The main goal of this milestone is to facilitate and accelerate the adoption of reactive burn as a commonly available modeling option, with recommendations on the resolution that will be required and uncertainties associated with their modeling choices. To achieve this, we have performed verification, validation, and uncertainty quantification (UQ) assessments of AWSD and SURF/SURFplus in xRage and FLAG on a variety of different problems.

45 MILITARY TECHNOLOGY, WEAPONRY, AND NATIONAL DEF↗

Critical Software for Human Spaceflight

The NASA Orion vehicle that will fly to the moon in the next years is propelled along its mission by the European Service Module (ESM), developed by ESA and its prime contractor Airbus Defense and Space. This paper describes the development of the Propulsion Drive Electronics (PDE) Software that provides the interface between the propulsion hardware of the European Service Module with the Orion flight computers, and highlights the challenges that have been faced during the development. Particularly, the specific aspects relevant to Human Spaceflight in an international cooperation are presented, as the compliance to both European and US standards and the software criticality classification to the highest category A. An innovative aspect of the PDE SW is its Time- Triggered Ethernet interface with the Orion Flight Computers, which has never been flown so far on any European spacecraft. Finally the verification aspects are presented, applying the most exigent quality requirements defined in the European Cooperation for Space Standardization (ECSS) standards such as the structural coverage analysis of the object code and the recourse to an independent software verification and validation activity carried on in parallel by a different team.

Preden, Antonio↗

Flutter Version of Propulsion Aeroelasticity Code Completed

NASA s Advanced Subsonic Technology (AST) Program seeks to develop new technologies to increase the fuel efficiency of commercial aircraft engines, improve the safety of engine operation, and reduce emissions and engine noise. For new designs of ducted fans, compressors, and turbines to achieve these goals, a basic aeroelastic requirement is that there should be no flutter or high resonant blade stresses in the operating regime. For verifying the aeroelastic soundness of the design, an accurate prediction/analysis code is required. Such a three-dimensional viscous propulsion aeroelastic code, named TURBO-AE, is being developed at the NASA Lewis Research Center. The development and verification of the flutter version of the TURBO-AE code (version 4) has been completed. Validation of the code is partially complete.

Bakhle, Milind A.↗

Development of a New Fixed-source Sensitivity Tally Capability in the MCNP ® Code [Slides]

Current work includes FSEN capability development, continued verification of adjoint-weighted sensitivity method, and improvement of algorithm speed and parallelism capability. Future work is forecasted to include extensions to non-Boltzmann responses, adding more responses and particle types, and connection to new MCNP6.3 tally backend.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Code Coverage Status of the ARC Code PERSENT

The Argonne Reactor Code (ARC) software system supports users in their fast reactor design goals by providing neutronic, thermal-hydraulic, and structural analysis capabilities. PERSENT fulfills the role of generating reactivity coefficients for a given time point of a REBUS calculation usable in a point kinetics based safety analysis capability. PERSENT also provides a sensitivity coefficient capability on eigenvalue, reactivity worth, and several other key coefficients that are used in the follow-on safety analysis. Given a co-variance matrix, PERSENT can carry out the uncertainty quantification to indicate the amount of error in the reactivity coefficients derived from the errors in the cross section measurements. With continued improvement of computational resources, many of the geometry modeling capabilities in DIF3D that were primarily used in low order schemes are not really needed anymore. Today, the diffusion and transport capabilities of DIF3D-VARIANT are primarily used in the reactor design process with some scattered usage of DIF3D-FD and DIF3D-Nodal. PERSENT is part of the ARC code system and is built around DIF3D-VARIANT and the flux solution it provides. The purpose of the present work is to identify a set of test problems for PERSENT and assess the code coverage of PERSENT for those test problems. PERSENT treats the DIF3D executable as an external executable and thus the code coverage considerations only need to focus on the PERSENT source code and only a fraction of the connected modules in the existing ARC software library. The goal is to document what parts of the existing PERSENT code are touched by the set of test problems and which are not. Because the verification work done on PERSENT was focused on the most common uses of PERSENT for fast reactor analysis, the code coverage assessment of those capabilities is the highest priority. This will ensure that nothing is being missed by the existing verification test problems that users of PERSENT rely upon. The code coverage analysis of PERSENT was performed with the Code Coverage Tool of the Intel Fortran compiler which requires modifications to the compilation of PERSENT. The detailed coverage tables are given for each submodule of PERSENT. Most of the uncovered parts/files could be easily ignored because they are either for error message and debugging output or not needed by PERSENT today. Only a few uncovered parts of PERSENT deserve extending the verification test suite.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Consistency, Verification, and Validation of Turbulence Models for Reynolds-Averaged Navier-Stokes Applications

In current practice, it is often difficult to draw firm conclusions about turbulence model accuracy when performing multi-code CFD studies ostensibly using the same model because of inconsistencies in model formulation or implementation in different codes. This paper describes an effort to improve the consistency, verification, and validation of turbulence models within the aerospace community through a website database of verification and validation cases. Some of the variants of two widely-used turbulence models are described, and two independent computer codes (one structured and one unstructured) are used in conjunction with two specific versions of these models to demonstrate consistency with grid refinement for several representative problems. Naming conventions, implementation consistency, and thorough grid resolution studies are key factors necessary for success.

Rumsey, Christopher L.↗

Recent Updates to the Object Reentry Survival Analysis Tool (ORSAT) Version 7.1

The Object Reentry Survival Analysis Tool (ORSAT) code is maintained and used by the NASA Orbital Debris Program Office (ODPO) and has been under continuous development and improvement since the mid-1990s. ORSAT is an object-oriented reentry simulation tool; it models a satellite as a collection of discrete components that follow independent trajectories upon the breakup of the parent object. Version 7.1 of the tool incorporates five years of new thermal and aerodynamic model development, multi-processor parametric study capability, codebase upgrades, and numerous bug-fixes. The thermal demise model was completely rewritten using a forward-time/central-space numerical stencil and incorporating a new pyrolysis model for fiber-reinforced plastic (FRP) materials. New aerodynamic and aeroheating models for hollow cylinders and hollow square prisms were developed using a combination of flow simulations in the direct simulation Monte Carlo (DSMC) Analysis Code (DAC) and Data Parallel Line Relaxation (DPLR) code and free-flight tests in the University of Texas at San Antonio’s Hypersonic Wind Tunnel. The latest version also incorporates a mechanical, strength-based demise model for FRP materials. Minor improvements include an update to the Fortran 2018 codebase; improved integration and speed with the Python-based, multi-core, parametric study tool, AutoORSAT; and fixes for many minor bugs. This new version of ORSAT will enable more accurate reentry risk assessments for modern satellites. This paper presents an overview of these changes and a summary of the verification and validation performed on the final code.

Benton R. Greene↗

Recent Updates to the Object Reentry Survival Analysis Tool (ORSAT) Version 7.1

The Object Reentry Survival Analysis Tool (ORSAT) code is maintained and used by the NASA Orbital Debris Program Office (ODPO) and has been under continuous development and improvement since the mid-1990s. ORSAT is an object-oriented reentry simulation tool; it models a satellite as a collection of discrete components that follow independent trajectories upon the breakup of the parent object. Version 7.1 of the tool incorporates five years of new thermal and aerodynamic model development, multi-processor parametric study capability, codebase upgrades, and numerous bug-fixes. The thermal demise model was completely rewritten using a forward-time/central-space numerical stencil and incorporating a new pyrolysis model for fiber-reinforced plastic (FRP) materials. New aerodynamic and aeroheating models for hollow cylinders and hollow square prisms were developed using a combination of flow simulations in the direct simulation Monte Carlo (DSMC) Analysis Code (DAC) and Data Parallel Line Relaxation (DPLR) code and free-flight tests in the University of Texas at San Antonio’s Hypersonic Wind Tunnel. The latest version also incorporates a mechanical, strength-based demise model for FRP materials. Minor improvements include an update to the Fortran 2018 codebase; improved integration and speed with the Python-based, multi-core, parametric study tool, AutoORSAT; and fixes for many minor bugs. This new version of ORSAT will enable more accurate reentry risk assessments for modern satellites. This paper presents an overview of these changes and a summary of the verification and validation performed on the final code.

Benton R. Greene↗

Urban weather modeling using WRF: linking physical assumptions, code implementation, and observational needs

The Weather Research and Forecasting (WRF) model includes urban schemes that simulate the influence of urban surfaces on the atmosphere using parameterizations for flux, and radiative exchanges. Three core schemes – the Bulk urban parameterization, Single-Layer Urban Canopy Model (SLUCM), and Multi-Layer Urban Canopy Model (MLUCM) – represent increasing levels of complexity. Although the parameterizations within these urban schemes are described in the literature, their specific implementation remains poorly documented, thus slowing down model development efforts. This manuscript provides a roadmap to the three urban schemes in WRF version 4.5.2, presenting equations using the same symbols as in the model code, along with references to code lines, and including graphics and explanations that connect the code to its physical foundations. Our thorough review of the urban parameterizations implemented in WRF version 4.5.2 highlighted a handful of parameters that may introduce discontinuities in simulations: (i) in the SLUCM, a 1 mm h −1 rain rate threshold is employed to switch between two minimum moisture availability parameterizations, thus impacting latent heat flux calculations; (ii) in the SLUCM a threshold is used to partition shortwave radiation into direct and diffuse components; (iii) in all three urban schemes, the bulk Richardson number is employed to select the similarity function, which influences the vertical distribution of heat and momentum. We also identified a highly simplified treatment of the radiative balance on roof surfaces. The implications of these simplifications can be assessed through targeted observations across relevant conditions, including varying precipitation rates, cloud cover, and transitions between stability regimes. Furthermore, the widespread application of the Monin-Obukhov similarity theory in these urban schemes warrants model evaluation under highly stable and unstable conditions and in heterogeneous urban settings with variable land cover and building heights on scales finer than model resolution. To address these challenges, we offer guidance on observational strategies, emphasizing the need for multi-parametric measurements to capture potential compensating biases and multi-height measurements that align with the levels where quantities are diagnostic and prognosed in the model (i.e., the lowest atmospheric level of the WRF model). Finally, our inspection of the code revealed implementation bugs that have now been corrected in WRF versions 4.6.0 and 4.6.1. Sensitivity tests over the Atlanta urban area show that these corrections affect surface temperatures, underscoring the importance of performing rigorous documentation and verification of the implementation of parameterizations in model code.

54 ENVIRONMENTAL SCIENCES↗

ARC Software Validation Work for the FFTF Reactor

Extensive efforts have been carried out at ANL for the verification and validation of the Argonne Reactor Codes (ARC) software package currently used for the design of Versatile Test Reactor (VTR). The ARC software package consists of steady state neutronics and thermal hydraulics modeling capabilities which are being used by the VTR program to develop most of the VTR reactor design details which will be part of the licensing application. It is anticipated that this software will continue to be used for the design work and for initial operations although additional software may be introduced at a later time. The validation work was focused primarily on obtaining validation data consistent with VTR and usable for the ARC software. Because no critical facilities or operating fast spectrum reactors are available to do experiments for the VTR, the next best option is to identify historical experimental data that can be used as validation data. Early on in VTR, the ZPPR-15 set of experiments was identified as good validation data because of 1) the availability and quality of the data, 2) existing staff that are already familiar with the experimental machine and measurements, 3) most of the ZPPR-15 loadings of interest have already been processed into ARC models, and 4) a full uncertainty quantification has already been done for several loadings of ZPPR-15. The FFTF startup and operations data was identified as the most consistent reactor type that has validation data usable for VTR. Finally, the EBR-II fuel depletion measurements were identified as the best available validation data for VTR. It is important to note that both the FFTF and EBR-II reactors typically come with higher uncertainties than the ZPPR. In the frame of the discussed verification and validation efforts, the present document discusses the analysis of selected FFTF measurements included in the benchmark specifications of the International Reactor Physics Experiment (IRPhE) handbook. The FFTF reactor core configurations from the benchmark specification are presented in Section 2. The analysis is performed with the use of the ARC code suite available at ANL for fast reactor studies and is discussed in Section 3. The reactor parameters from the benchmark include criticality, neutron spectra, effective delayed neutron spectra, control rod worth, isothermal temperature coefficient and low energy gamma-ray spectra. The calculated values and the comparison with the experimental data is discussed in Sections 4 to 9 for each considered reactor parameter. Finally, conclusions are presented in Section 10.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

Development and Testing of Automatically Generated ACS Flight Software for the MAP Spacecraft

By integrating the attitude determination and control system (ACS) analysis and design, flight software development, and flight software testing processes, it is possible to improve the overall spacecraft development cycle, as well as allow for more thorough software testing. One of the ways to achieve this integration is to use code-generation tools to automatically generate components of the ACS flight software directly from a high-fidelity (HiFi) simulation. In the development of the Microwave Anisotropy Probe (MAP) spacecraft, currently underway at the NASA Goddard Space Flight Center, approximately 1/3 of the ACS flight software was automatically generated. In this paper, we will examine each phase of the ACS subsystem and flight software design life cycle: analysis, design, and testing. In the analysis phase, we scoped how much software we would automatically generate and created the initial interface. The design phase included parallel development of the HiFi simulation and the hand-coded flight software components. Everything came together in the test phase, in which the flight software was tested, using results from the HiFi simulation as one of the bases of comparison for testing. Because parts of the spacecraft HiFi simulation were converted into flight software, more care needed to be put into its development and configuration control to support both the HiFi simulation and flight software. The components of the HiFi simulation from which code was generated needed to be designed based on the fact that they would become flight software. This process involved such considerations as protecting against mathematical exceptions, using acceptable module and parameter naming conventions, and using an input/output interface compatible with the rest of the flight software. Maintaining good configuration control was an issue for the HiFi simulation and the flight software, and a way to track the two systems was devised. Finally, an integrated test approach was devised to support flight software testing at both the unit- and build-test levels using the HiFi simulation to generate data for performance verification. Another benefit of the simulation and code-generation application used on the MAP project is that it supported bringing flight software and test data into the HiFi simulation environment. It was possible to integrate parts of the hand-coded flight software into the HiFi simulation, and also possible to import flight software test data for comparison and performance verification. This capability was used to incorporate the flight software Kalman filter into the HiFi simulation. This enabled us to greatly increase the amount of testing that could be done on the filter, because we could exert a greater degree of control over the software-only simulation than over the flight software test environment. Also, since the simulation could be used to run the Kalman filter faster than real time, our testing efficiency was greatly increased. We will conclude our discussion with a summary of the lessons learned thus far using automatically- generated code for the MAP project, and the spacecraft status as we work towards our scheduled launch in the year 2000.

ODonnell, James R., Jr.↗

Software verification and testing

General procedures for software verification and validation are provided as a guide for managers, programmers, and analysts involved in software development. The verification and validation procedures described are based primarily on testing techniques. Testing refers to the execution of all or part of a software system for the purpose of detecting errors. Planning, execution, and analysis of tests are outlined in this document. Code reading and static analysis techniques for software verification are also described.

Source record↗

Replication Package for "Union-Find and Usability: A Case Study and Analysis of Rust Formal Verifier

This replication package is a case study on automated deductive verification for Rust for practical programs. It is a companion artifact to a corresponding usability study on verification titled "Union-Find and Usability: A Case Study and Analysis of Rust Formal Verifiers". It seeks to answer the question "Can Rust developers today use Rust verifiers to verify their code?". To answer this question, the study contrasts the verification experience of two mature Rust verifiers, Creusot and Prusti, by using the tools to develop a verified implementation of union-find in Rust. The union-find implementation is based on real-world code as used in the popular egg E-graph library. The artifact consists of two different verified libraries, one using Creusot and one using Prusti. The libraries have similar Rust interfaces and high-level proofs but differ in their details: Creusot and Prusti have different annotation languages and support different proof styles. Each implementation can be verified with its respective tool and compiles as a traditional Rust development.

Sarracino, John↗

Study of recirculating liquid fuel in a 1D critical stationary system

Several studies have been conducted to investigate the physics of liquid fuel reactors, showing also applications with molten salts. A liquid nuclear fuel implies changes in the neutron balance equation to take into account the precursors' displacement and the emission of delayed neutrons in a different position than at the original fission. This requires to upgrade the computer codes normally used to calculate nuclear reactors using only solid fuel. In this work, we revisit a simple problem with liquid fuel, which is proposed for the verification of the numerical solutions obtained by advanced computer codes. This problem studies criticality with constant coefficients, thus neglecting thermal feedback. We elaborate on the analytical solution of the problem, deriving also a generalized eigenvalue problem by finite-volume integration over the cells of a discretized mesh to study the evolution of the dominance ratio with fuel velocity. Finally, we investigate the influence of the fuel velocity on the reactivity of the system. (authors)

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

RASPA3

RASPA3, a molecular simulation code for computing adsorption and diffusion in nanoporous materials and thermodynamic and transport properties of fluids. It implements force field based classical Monte Carlo/molecular dynamics in various ensembles. RASPA3 is rewritten from the ground up in C++23 with speed and code readability in mind. Transition-matrix Monte Carlo is added to compute the density of states and free energies. The Monte Carlo code for rigid molecules is based on quaternions, and the atomic positions needed in the energy evaluation are recreated from the center of mass position and quaternion orientation. The expanded ensemble methodology for fractional molecules, with a scaling parameter λ between 0 and 1, now also keeps track of analytic expressions of dU/dλ, allowing independent verification of the chemical potential using thermodynamic integration. The source code is freely available under the MIT license on GitHub.

Dubbeldam, David↗

Verification and Performance Impact of the New Parallel MCNP6.3 Particle Track Output Capability for Subcritical Multiplication Simulations

The MCNP6® code, version 6.3, has several new features that are intended to ultimately replace legacy features that are now marked for deprecation. One of these features is the new particle track output (PTRAC) format and capability, where the legacy PTRAC capability still exists alongside the modern PTRAC capability in MCNP6.3. While the MCNP6.3 code has been extensively verified and validated for many applications, the PTRAC feature is not exercised in any of the typical verification and validation (V&V) applications studied during the course of a typical MCNP code release. The primary goal of this paper is to verify that the legacy and modern PTRAC feature produces equivalent results for subcritical multiplication benchmarks previously studied. In the process of verifying that the simulated benchmark results are equivalent, the computational performance is compared between the legacy and modern PTRAC uses. In addition to verification of the update, which is important to the community as a whole, this effort also supports advances in the simulation of recent subcritical neutron noise measurements that require higher computational effort per second of real-time measurement than that of systems typically measured.

97 MATHEMATICS AND COMPUTING↗

Using Hydrodynamic Similarity as a Verification Method for Impact Cratering Simulations in the FLAG Hydrocode

Hydrodynamic codes (hydrocodes) are common tools for modeling hypervelocity impacts to provide insight into the physical phenomenon. Hydrocodes can simulate impacts from micrometer to kilometer spatial scales and reach impact velocities difficult to achieve in experimental settings. However, numerical models are approximations, and demonstrating that a numerical method is capable of providing physical results for these models is essential. In this work, we employ a hydrocode verification technique that leverages hydrodynamic similarity, a mathematical property of the conservation equations of fluid mechanics that form the basis for hydrocode models. Using the FLAG hydrocode, we simulate aluminum (Al) and basalt projectiles and targets at spatial scales spanning 7 orders of magnitude (hundreds of micrometers to kilometers). These materials were chosen because Al-6061 is a common material in spacecraft and satellites and basalt is a useful approximation of rocky astronomical bodies. Our results show that hydrodynamic similarity holds for each material model used and across spatial scales. We show that under certain conditions hydrodynamic similarity can apply in the presence of gravity and that similarity does not hold in the presence of strength models. We conclude that the FLAG hydrocode preserves important mathematical properties of fluid dynamics in hypervelocity impacts of Al-6061 and basalt.

79 ASTRONOMY AND ASTROPHYSICS↗

NASA. Lewis Research Center Advanced Modulation and Coding Project: Introduction and overview

The Advanced Modulation and Coding Project at LeRC is sponsored by the Office of Space Science and Applications, Communications Division, Code EC, at NASA Headquarters and conducted by the Digital Systems Technology Branch of the Space Electronics Division. Advanced Modulation and Coding is one of three focused technology development projects within the branch's overall Processing and Switching Program. The program consists of industry contracts for developing proof-of-concept (POC) and demonstration model hardware, university grants for analyzing advanced techniques, and in-house integration and testing of performance verification and systems evaluation. The Advanced Modulation and Coding Project is broken into five elements: (1) bandwidth- and power-efficient modems; (2) high-speed codecs; (3) digital modems; (4) multichannel demodulators; and (5) very high-data-rate modems. At least one contract and one grant were awarded for each element.

Budinger, James M.↗