Results for “Code Manual” — Page 10

DOE OSTI2021

Industry Level Integrated Fire Modeling Using Fire Risk Investigation in 3D (FRI3D)

The software Fire Risk Investigation in 3D (FRI3D) has been developed over the last 2 years to integrate 3D spatial modeling with existing fire probabilistic risk assessment (PRA) models and fire simulation codes. The goal of this research and development is to automate many of the fire analysis manual tasks to reduce industry efforts in the initial fire modeling and operational costs for the model maintenance and evaluations required during normal plant operations. The tasks for Fiscal Year (FY) 2021 include first testing the FRI3D modeling capabilities by importing an industry fire model into FRI3D and making a 3D model of a complex/high-risk significant area. (For this work, the switchgear room was chosen.) Then, the second task of FY 2021 is to develop a dynamic fire PRA process that can help optimize traditional fire PRA models. The switchgear room model will be used for the dynamic fire PRA work. This report describes the work and insights learned when using FRI3D software to model both a Nuclear Regulatory Report (NUREG) example models and a full industry switchgear room.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

Primer for OTERR Core Reloading Optimization

OTERR (Optimization of Test Reactor Reloading) is a software tool which assists in finding optimal fuel assembly reloading patterns for nuclear reactors. It was created specifically to support the Versatile Test Reactor (VTR) program, but its functionality is general enough to be applied to most fast spectrum reactors which use hexagonal prismatic fuel elements. This document is meant to be a primer for new users of OTERR to walk through example workflows for core reloading optimization cases. Simple cases are followed step-by-step to discuss what needs to be done to complete a reloading optimization sequence. Note that the intent of this document is to provide practical examples for users to follow along with so they can quickly start using OTERR and then make changes to fit their own modeling needs. Detail is limited in terms of addressing additional features not used in these examples and especially lacking in discussion of theory used in the code. To better address these points, users are highly encouraged to refer to the OTERR User Manual and the OTERR Theory Manual.

21 SPECIFIC NUCLEAR REACTORS AND ASSOCIATED PLANTS↗

DOE OSTI2023

Performance Evaluation of Heterogeneous GPU Programming Frameworks for Hemodynamic Simulations

Preparing for the deployment of large scientific and engineering codes on upcoming exascale systems with GPU-dense nodes is made challenging by the unprecedented diversity of device architectures and heterogeneous programming models. In this work, we evaluate the process of porting a massively parallel, fluid dynamics code written in CUDA to SYCL, HIP, and Kokkos with a range of backends, using a combination of automated tools and manual tuning. We use a proxy application along with a custom performance model to inform the results and identify additional optimization strategies. At scale performance of the programming model implementations are evaluated on pre-production GPU node architectures for Frontier and Aurora, as well as on current NVIDIA device-based systems Summit and Polaris. Real-world workloads representing 3D blood flow calculations in complex vasculature are assessed. Our analysis highlights critical trade-offs between code performance, portability, and development time.

Martin, Aristotle↗

DOE OSTI2020

Sierra/SD - Verification Test Manual - 4.56

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2021

Sierra/SD – Verification Test Manual – 5.0

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2020

Sierra/SD–Verification Test Manual - 4.58

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2021

Sierra/SD - Verification Test Manual - 5.2

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

Sierra/SD - Verification Test Manual - 5.4

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

Sierra/SD - Verification Test Manual - 5.6

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

Sierra/SD - Verification Test Manual - 5.8

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2022

Sierra/SD: Verification Test Manual - 5.10

This document presents tests from the Sierra Structural Mechanics verification test suite. Each of these tests is run nightly with the Sierra/SD code suite and the results of the test checked versus the correct analytic result. For each of the tests presented in this document the test setup, derivation of the analytic solution, and comparison of the Sierra/SD code results to the analytic solution is provided. This document can be used to confirm that a given code capability is verified or referenced as a compilation of example problems.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2026

Consist v0.1.0

A Python library for provenance tracking, intelligent caching, and data virtualization in scientific simulation workflows. It automatically records code, configuration, and input data to skip redundant computations and enables querying results across many runs without manual bookkeeping. Designed to support multi-model simulation workflows like the BEAM CORE toolset at LBL, but designed to be extensible to a wide range of research workflows. Combines lineage tracking features as provided by OpenLineage with deterministic hashing like SnakeMake, and adds powerful analysis tools on model outputs.

Needell, Zachary [Lawrence Berkeley National Labor↗

DOE OSTI2024

Optimization Studies of Radiation Shielding for PIP-II Project at Fermilab

The Proton Improvement Plan-II (PIP-II) at Fermilab represents a significant advancement in the quest to answer some of the most profound questions about our universe using the world's most intense high-energy neutrino beam. The project requires the construction of a new addition to the Fermilab accelerator complex – an 800-MeV high-intensity superconducting linear accelerator. Ensuring the safety and regulatory compliance of this ambitious project is paramount, necessitating thorough dose rate assessments under both normal operational and accidental scenarios to align with the Fermilab Radiological Control Manual (FRCM) standards. Our approach included a shielding optimization used for the simulations with the Monte Carlo code MARS [1,2,3] to incorporate new magnet and collimator designs, essential for reflecting the current state of PIP-II infrastructure. The implementation of high-resolution detector planes, despite their computational demands, enabled us to gather detailed radiation field data crucial for optimizing shielding configurations. To overcome the significant computational demands, we developed a branching code that drastically reduced simulation runtimes while maintaining statistical integrity. This was achieved through geometry splitting and the application of Russian Roulette techniques, tailored to prioritize regions of interest based on predefined importances and weight limits.

43 PARTICLE ACCELERATORS↗

DOE OSTI2024

Optimization Studies of Radiation Shielding for PIP-II Project at Fermilab

The Proton Improvement Plan-II (PIP-II) at Fermilab represents a significant advancement in the quest to answer some of the most profound questions about our universe using the world's most intense high-energy neutrino beam. The project requires the construction of a new addition to the Fermilab accelerator complex – an 800-MeV high-intensity superconducting linear accelerator. Ensuring the safety and regulatory compliance of this ambitious project is paramount, necessitating thorough dose rate assessments under both normal operational and accidental scenarios to align with the Fermilab Radiological Control Manual (FRCM) standards. Our approach included a shielding optimization used for the simulations with the Monte Carlo code MARS [1,2,3] to incorporate new magnet and collimator designs, essential for reflecting the current state of PIP-II infrastructure. The implementation of high-resolution detector planes, despite their computational demands, enabled us to gather detailed radiation field data crucial for optimizing shielding configurations. To overcome the significant computational demands, we developed a branching code that drastically reduced simulation runtimes while maintaining statistical integrity. This was achieved through geometry splitting and the application of Russian Roulette techniques, tailored to prioritize regions of interest based on predefined importances and weight limits.

Makovec, Alajos↗

DOE OSTI2025

LLM Benchmarking with LLaMA2: Evaluating Code Development Performance Across Multiple Programming Languages

The rapid evolution of large language models (LLMs) has opened new possibilities for automating various tasks in software development. This paper evaluates the capabilities of the LLaMA 2-70B model in automating these tasks for scientific applications written in commonly used programming languages. Using representative test problems, we assess the model's capacity to generate code, documentation, and unit tests, as well as its ability to translate existing code between commonly used programming languages. Our comprehensive analysis evaluates the compilation, runtime behavior, and correctness of the generated and translated code. Additionally, we assess the quality of automatically generated code, documentation, and unit tests. Here, our results indicate that while LLaMA 2-70B frequently generates syntactically correct and functional code for simpler numerical tasks, it encounters substantial difficulties with more complex, parallelized, or distributed computations, requiring considerable manual corrections. We identify key limitations and suggest areas for future improvements to better leverage AI-driven automation in scientific computing workflows.

97 MATHEMATICS AND COMPUTING↗

DOE OSTI2021

MOFLUX Intensified Soil Moisture Extremes Decrease Soil Organic Carbon Decomposition: Modeling Archive

This Modeling Archive is in support the publication “Intensified Soil Moisture Extremes Decrease Soil Organic Carbon Decomposition: A Mechanistic Modeling Analysis” (Liang et al., 2021). Here we provide model code, inputs, outputs and evaluation datasets for the Microbial ENzyme Decomposition (MEND) model for the Missouri Ozarks AmeriFlux eddy covariance measurement site (MOFLUX) near Ashland, Missouri USA. The MEND model was developed with explicit representation of microbial and enzyme pools to mechanistically simulate the role of microbial organisms and extracellular enzymes in soil organic carbon (SOC) decomposition. Long-term SOC dynamics under intensified moisture extremes are studied using the MEND model that is parameterized with 11 years of measurements from the MOFLUX forest. The model explicitly represents microbial dormancy and resuscitation, different types of SOC-degrading enzymes, and how they vary with changes in soil moisture (Wang et al. 2015, 2019). A combination of two levels of frequency and severity of soil moisture, as well as a control with normal interannual variability, are used to simulate a range of moisture scenarios over 100 years. The code of Microbial-ENzyme Decomposition (MEND) as well as the input and output data are included in the archive. A user’s manual (MEND_Readme.pdf) is included with instructions for compiling and running the model to simulate soil organic carbon decomposition under various moisture scenarios. This dataset contains the modelling archive contained within a compressed (*.zip) file, a file-level metadata file in comma separate (*.csv) format, and two instructional files in PDF (*.pdf) format.

54 ENVIRONMENTAL SCIENCES↗

DOE OSTI2023

Generating MCNP Input Files for Unstructured Mesh Geometries

The Los Alamos National Laboratory’s (LANL) Monte Carlo N-Particle (MCNP)1 transport code version 6.3 (also known as MCNP6.3) has the capability for tracking particles on unstructured mesh (UM) geometry models embedded into constructive solid geometry (CSG) cells. This feature has been developed for performing calculations of complex geometry models because manually creating CSG models is time-consuming and error-prone as the complexities of geometries increase. A UM geometry model is a collection of finite elements representing a solid geometry. The first step of the MCNP UM calculation is using other software packages to create a finite element mesh representation of a solid 3D geometry because the MCNP code cannot be used to generate a UM model. Computer-aided design (CAD) software is typically used to create a solid geometry model, which is later imported into mesh generation software to create a UM model. Some mesh generation software packages may also be used to create solid geometries and thus CAD files are not needed. The MCNP UM feature was originally designed for models generated by the Abaqus/CAE software suite. The MCNP code version 6.0 and later can process UM models formatted as Abaqus input files. Starting with a 6.3 version, the MCNP code can process HDF5 mesh input files. We only focus on the UM models formatted as Abaqus input files in this report since currently no external software can be used to generate HDF5 mesh input files for MCNP UM calculations. The MCNP code version 6.3 can be used to convert the Abaqus mesh input files into the HDF5 mesh input files, but this option is typically used by the MCNP code development team to test the HDF5 mesh input file feature. Several software packages (such as Abaqus, Attila4MC, or Cubit) can be used to create the Abaqus input files for MCNP UM calculations. An MCNP UM calculation using an Abaqus model requires two input file types: MCNP and Abaqus input files. The Abaqus input files needed for MCNP UM calcu lations must have the correct Abaqus syntax and meet the additional requirements by the MCNP code. The MCNP code can process only Abaqus input files that make use of part and assembly definitions, where elements in each part must be grouped into one or more element sets (i.e., elset) using *Elset keyword lines with specified naming formats. The MCNP and Abaqus input files required for MCNP UM simulations must be related; pseudo-cells in an MCNP input file must be constructed from mesh model data from an Abaqus input file. For large complex UM models, it is tedious to manually create MCNP UM input files. The um pre op (unstructured mesh pre operations) program with the -m option can be used to create a skeleton MCNP input file from an Abaqus input file [6]. Since the um pre op program was written in Fortran and was not written for optimized performance, this program is a deprecated feature in the MCNP code version 6.3 and may be removed in the next release of the code. To improve calculation flow of multiphysics calculations, a Python3 code called write mcnp um input has been developed to generate an MCNP input file instead of using the um_pre_op -m option. This Python code was initially released to the public in 2020. We have updated this Python code for MCNP6.3 and it was used to generate the MCNP input files used to verify the MCNP6.3 code. The write_mcnp_um_input code is included with the MCNP6.3 code package which will be released to the public through the Radiation Safety Information Computational Center (RSICC) at Oak Ridge National Laboratory. This report is a revision of LA-UR-20-27139 report.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

DOE OSTI2023

Athena-I CUBIT Journal Files

The Monte Carlo N-Particle (MCNP)1 transport code version 6 (also known as MCNP6) has the capability for tracking particles on unstructured mesh (UM) geometry models embedded into con structive solid geometry (CSG) cells. This feature has been developed for performing calculations of complex geometry models because manually creating CSG models is a time-consuming and error prone process as the complexities of geometries increase. The UM capability was originally designed to work with UM models created with the Abaqus software and ASCII input files that it generates. The MCNP code version 6.0 and later can process UM models formatted as Abaqus input files. Starting with version 6.3, MCNP can also process HDF5 mesh input files. External codes must be used to generate Abaqus input files for MCNP UM calculations. CUBIT, the Sandia National Laboratory automated mesh generation toolkit, can generate a UM model formatted as an Abaqus input file. However, the Abaqus input files exported from CUBIT cannot be used for MCNP simulations because it lacks the proper syntax. A Python script was developed to convert an Abaqus file created by CUBIT to an Abaqus file format that MCNP can process. Creating UM models for complex geometries is not an easy task. The process of creating UM models in CUBIT for MCNP simulations is detailed in. CUBIT provides several user interface options including a graphical user interface (GUI) and a command line interface. A GUI provides an easy way to use CUBIT without learning the CUBIT command syntax. When using CUBIT with either interface option, command lines are written into an ASCII file known as a journal file; this journal file can be edited and archived so that it can be played back in CUBIT to automatically generate a UM model. This report describes the CUBIT journal files of the UM models developed for Athena-I. The Athena platform, an energy-tuning assembly, was developed to spectrally shape the National Ignition Facility (NIF) deuterium-tritium fusion neutron source to a thermonuclear (fusion) plus prompt fission neutron spectrum with capability to act as a short-pulse neutron source. MCNP6 was used for the Athena experiment design analysis.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗