Engineering Papers⌕ Search

SEARCH · Engineering Papers

Results for “input files”

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 163 records · Page 9
All sourcesNASA NTRSDOE OSTI
NASA NTRS2005

Integrated Structural Analysis and Test Program

An integrated structural-analysis and structure-testing computer program is being developed in order to: Automate repetitive processes in testing and analysis; Accelerate pre-test analysis; Accelerate reporting of tests; Facilitate planning of tests; Improve execution of tests; Create a vibration, acoustics, and shock test database; and Integrate analysis and test data. The software package includes modules pertaining to sinusoidal and random vibration, shock and time replication, acoustics, base-driven modal survey, and mass properties and static/dynamic balance. The program is commanded by use of ActiveX controls. There is minimal need to generate command lines. Analysis or test files are selected by opening a Windows Explorer display. After selecting the desired input file, the program goes to a so-called analysis data process or test data process, depending on the type of input data. The status of the process is given by a Windows status bar, and when processing is complete, the data are reported in graphical, tubular, and matrix form.

Kaufman, Daniel↗
NASA NTRS1998

Expert System Architecture for Rocket Engine Numerical Simulators: A Vision

Simulation of any complex physical system like rocket engines involves modeling the behavior of their different components using mostly numerical equations. Typically a simulation package would contain a set of subroutines for these modeling purposes and some other ones for supporting jobs. A user would create an input file configuring a system (part or whole of a rocket engine to be simulated) in appropriate format understandable by the package and run it to create an executable module corresponding to the simulated system. This module would then be run on a given set of input parameters in another file. Simulation jobs are mostly done for performance measurements of a designed system, but could be utilized for failure analysis or a design job such as inverse problems. In order to use any such package the user needs to understand and learn a lot about the software architecture of the package, apart from being knowledgeable in the target domain. We are currently involved in a project in designing an intelligent executive module for the rocket engine simulation packages, which would free any user from this burden of acquiring knowledge on a particular software system. The extended abstract presented here will describe the vision, methodology and the problems encountered in the project. We are employing object-oriented technology in designing the executive module. The problem is connected to the areas like the reverse engineering of any simulation software, and the intelligent systems for simulation.

Mitra, D.↗
NASA NTRS1994

NLEdit: A generic graphical user interface for Fortran programs

NLEdit is a generic graphical user interface for the preprocessing of Fortran namelist input files. The interface consists of a menu system, a message window, a help system, and data entry forms. A form is generated for each namelist. The form has an input field for each namelist variable along with a one-line description of that variable. Detailed help information, default values, and minimum and maximum allowable values can all be displayed via menu picks. Inputs are processed through a scientific calculator program that allows complex equations to be used instead of simple numeric inputs. A custom user interface is generated simply by entering information about the namelist input variables into an ASCII file. There is no need to learn a new graphics system or programming language. NLEdit can be used as a stand-alone program or as part of a larger graphical user interface. Although NLEdit is intended for files using namelist format, it can be easily modified to handle other file formats.

Curlett, Brian P.↗
NASA NTRS2004

MPT Prediction of Aircraft-Engine Fan Noise

A collection of computer programs has been developed that implements a procedure for predicting multiple-pure-tone (MPT) noise generated by fan blades of an aircraft engine (e.g., a turbofan engine). MPT noise arises when the fan is operating with supersonic relative tip Mach No. Under this flow condition, there is a strong upstream running shock. The strength and position of this shock are very sensitive to blade geometry variations. For a fan where all the blades are identical, the primary tone observed upstream of the fan will be the blade passing frequency. If there are small variations in geometry between blades, then tones below the blade passing frequency arise MPTs. Stagger angle differences as small as 0.1 can give rise to significant MPT. It is also noted that MPT noise is more pronounced when the fan is operating in an unstarted mode. Computational results using a three-dimensional flow solver to compute the complete annulus flow with non-uniform fans indicate that MPT noise can be estimated in a relatively simple way. Hence, once the effect of a typical geometry variation of one blade in an otherwise uniform blade row is known, the effect of all the blades being different can be quickly computed via superposition. Two computer programs that were developed as part of this work are used in conjunction with a user s computational fluid dynamics (CFD) code to predict MPT spectra for a fan with a specified set of geometric variations: (1) The first program ROTBLD reads the users CFD solution files for a single blade passage via an API (Application Program Interface). There are options to replicate and perturb the geometry with typical variations stagger, camber, thickness, and pitch. The multi-passage CFD solution files are then written in the user s file format using the API. (2) The second program SUPERPOSE requires two input files: the first is the circumferential upstream pressure distribution extracted from the CFD solution on the multi-passage mesh, the second file defines the geometry variations of each blade in a complete fan. Superposition is used to predict the spectra resulting from the geometric variations.

Connell, Stuart D.↗
DOE OSTI2021

VERAIO Software Management Plan

VERAIO is a set of utility codes used to provide a common set of input and outputs to the Virtual Environment for Reactor Applications (VERA). VERA is a collection of several different computer codes that all have a common input and output. This prevents the need to manage input and output from each individual code, allowing for ease of use and reducing errors associated with code operability. The VERAIO utilities include VERAIn, VERAView, and VERARun. Each of these utilities is described below. VERAIn is an input processor that reads an ASCII input file generated by users, parses the file, performs some error checking, and writes an XML file to be read by other VERA codes. The main purpose of VERAIn is to provide a common input to all of the VERA codes so users only need to learn one input. VERAIn is written in Perl and uses YAML configuration files to provide flexibility. VERAView is a graphical user interface (GUI) that reads a VERA HDF output file and allows users to visualize results. VERAView is written in Python. VERARun is a script that drives the VERA execution in a high performance computing (HPC) environment. Work performed at the code level supports the Quality Assurance Program Plan (QAPP) (VERA-QA-001), and VERA Software Quality Assurance Plan (VERA-QA-002).

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2022

VERAIO Software Management Plan

VERAIO is a set of utility codes used to provide a common set of inputs and outputs to the Virtual Environment for Reactor Applications (VERA). VERA is a collection of several different computer codes that all have a common input and output. This prevents the need to manage input and output from each individual code, allowing for ease of use and reducing errors associated with code operability. The VERAIO utilities include VERAIn, VERAView, and VERARun. Each of these utilities is described below. VERAIn is an input processor that reads an ASCII input file generated by users, parses the file, performs some error checking, and writes an XML file to be read by other VERA codes. The main purpose of VERAIn is to provide a common input to all of the VERA codes, so users only need to learn one input. VERAIn is written in Perl and uses YAML configuration files to provide flexibility. VERAView is a graphical user interface (GUI) that reads a VERA hierarchical data format (HDF) output file and allows users to visualize results. VERAView is written in Python. VERARun is a script that drives the VERA execution in a high performance computing (HPC) environment. Work performed at the code level supports the quality assurance program plan (QAPP) (VERA-QA-001) and the VERA Software Quality Assurance Plan (VERA-QA-002).

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Weatherization Assistant NEAT/MHEA

The software provides a measure selection technique indicating cost effective retrofit activities that can be applied to a home using a standard Savings to Investment Ratio (SIR). Users must provide an input file describing the characteristics of the home to be evaluated. The software takes the input data provided and calculates energy savings and cost savings predicted for a standard set of measures given the input parameters. The Weatherization Assistant computes estimates of pre-retrofit whole building space heating and cooling energy consumptions based on the house description data supplied by the user. The consumptions are computed using a monthly heating and cooling variable base degree-day method by algorithms similar to those developed for the CIRA program [LBL, 1982]. The building consumptions are needed in computing the energy savings from measures affecting the efficiencies of the heating and cooling equipment. Weatherization Assistant then computes the energy savings and costs for each individual measure applicable to the building described as if it were the only measure installed in the house. From these energy savings, a discounted dollar savings over the life of each measure is computed. The ratio of this dollar savings to the cost of installing the measure, the "savings-to-investment ratio" (SIR), is used in an initial ranking of the measures' effectiveness. The "interacted" savings and SIR of measures are then determined assuming the measures are added to the house collectively, in order of their ranking, e.g., the second ranked measure is installed in the house initially described by the user after having been modified by the first ranked measure. If this second-ranked measure's updated SIR is greater than a user-defined limit, the measure is left implemented, else it is removed so that the next measure's effectiveness is not dependent on it. The choice between two mutually exclusive measures (such as different levels of insulation) is made on the basis of their "net present value" (NPV), the difference of life-time savings and installation cost, rather than their SIR. This has been shown to be the more correct criterion on which to base the selection between two measures, both of which cannot be installed. The audit computes and reports to the user the energy savings, discounted dollar savings, installation cost, and SIR for each measure considered cost-effective. For those with SIR greater than the user-designated cutoff, a materials list gives the material name, type, and quantity required for installation of the measure. Weatherization Assistant permits entry of pre-retrofit billing data for gas or electrically heated homes or homes with electric air-conditioning. The user may then make the decision to have the savings of the measures adjusted to reflect the difference in billed consumption and that predicted by the program.

Gettings, Michael↗
DOE OSTI2022

Validation of energetic particle transport models for time-dependent integrated simulations of burning plasmas (Final ST Report)

The major goal of this project is to deliver a suite of validated energetic particle (EP) modeling tools for time-dependent integrated tokamak simulations (with the code TRANSP) that can be used for modeling plasma discharges featuring a substantial EP content, such as burning plasmas. During FY20, issues were resolved with an energetic particle transport model called TGLF-EP, with improvements made to the TGLF-EP workflow, generation of input files, and interpretation of runs on the NERSC supercomputing cluster. The recipient also gave input on simulations with the code TRANSP to reproduce the reference JET discharge, and assessed the accuracy and uncertainties of the simulated B field, current evolution, thermal plasma profiles, stored energy, etc. Input was also given on interpretation of fast-ion instability calculations and recommendations for modifications to JET afterglow discharge for the upcoming DT campaign.

70 PLASMA PHYSICS AND FUSION TECHNOLOGY↗
DOE OSTI2021

RAVEN Theory Manual

RAVEN is a software framework able to perform parametric and stochastic analysis based on the response of complex system codes. The initial development was aimed at providing dynamic risk analysis capabilities to the thermohydraulic code RELAP-7, currently under development at Idaho National Laboratory (INL). Although the initial goal has been fully accomplished, RAVEN is now a multi-purpose stochastic and uncertainty quantification platform, capable of communicating with any system code. In fact, the provided Application Programming Interfaces (APIs) allow RAVEN to interact with any code as long as all the parameters that need to be perturbed are accessible by input files or via python interfaces. RAVEN is capable of investigating system response and explore input space using various sampling schemes such as Monte Carlo, grid, or Latin hypercube. However, RAVEN strength lies in its system feature discovery capabilities such as: constructing limit surfaces, separating regions of the input space leading to system failure, and using dynamic supervised learning techniques. The development of RAVEN started in 2012 when, within the Nuclear Energy Advanced Modeling and Simulation (NEAMS) program, the need to provide a modern risk evaluation framework arose. RAVEN’s principal assignment is to provide the necessary software and algorithms in order to employ the concepts developed by the Risk Informed Safety Margin Characterization (RISMC) program. RISMC is one of the pathways defined within the Light Water Reactor Sustainability (LWRS) program. In the RISMC approach, the goal is not just to identify the frequency of an event potentially leading to a system failure, but the proximity (or lack thereof) to key safety-related events. Hence, the approach is interested in identifying and increasing the safety margins related to those events. A safety margin is a numerical value quantifying the probability that a safety metric (e.g. peak pressure in a pipe) is exceeded under certain conditions. Most of the capabilities, implemented having RELAP-7 as a principal focus, are easily deployable to other system codes. For this reason, several side activates have been employed (e.g. RELAP5-3D, any MOOSE-based App, etc.) or are currently ongoing for coupling RAVEN with several different software. The aim of this document is to provide a set of commented examples that can help the user to become familiar with the RAVEN code usage.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2021

Geant4 based positron beam source (GPos) v1.0

GPos is a software that was created to determine the properties of positron beams resulting from the interaction of the LBNL BELLA center PetaWatt laser-driven plasma-capillary accelerated electron beam and the atoms of a thin solid target. GPos is written in C++, easily compiled with cmake and the spack package manager, which allows for multi-thread and MPI parallel computing. Its functions expand on the Geant4 toolkit library and allow for propagation of the modelled particles through vacuum drift distances with a focusing element (thin lens approximation). Users can change beam-foil-drift-lens parameters - to adapt GPos to other particle sources and infrastructures - in a simple input file. The code particle data output format, openPMD, which is compatible, for example, with the input of the ECP WarpX project code used to explore the physics of particle acceleration in plasmas. Using GPos in conjunction to WarpX allowed us to test various configurations for designing a high-quality and high-energy positron source at BELLA -required for us to address positron acceleration challenges in the development of future linear colliders. GPos can also be advantageous when tackling the physics of muon sources for future muon colliders as well as for the investigation of positron sources in lower energy regimes for applications like annihilation spectroscopy and astrophysical gamma-ray-bursts.

Pinto de Almeida Amorim, Ligia↗
DOE OSTI2020

Guide for Using ENDF/B-VIII.0 Nuclear Data with MCNP

This report provides guidance for using the ENDF/B-VIII.0 nuclear data that were released in 2018 and 2020 with MCNP. Appendix A: Obtaining and installing the new ENDF/B-VIII.0 ACE nuclear data. Appendix B. Obtaining & using XSDIR files that include ENDF/B-VIII.0 data. Appendix C: ENDF/B-VIII.0-based ACE files for neutron cross-sections. A listing of the available temperatures and ZA numbers for neutron cross-sections (ACE files with suffix .nnC). Appendix D: ENDF/B-VIII.0-based ACE files for thermal scattering law (TSL) data, $S$(α,β). A listing of the available thermal scattering $S$(α,β) data (ACE files with suffix .nnT) The next section below provides guidance for modifying existing $\textit{mcnp}$ input files to use the ENDF/B-VIII.0 data. Detailed results from running several benchmark suites for nuclear criticality safety with both ENDF/B-VII.1 and ENDF/B-VIII.0 nuclear data are reported in. It is important to note that this report deals only with TSL data released in 2020. With the original release of ENDF/B-VIII.0 in 2018, the ACE files for neutron cross-sections were contained in a directory called Lib80X and the ACE files for TSL data were contained in a directory called ENDF80SaB. A few years later, it was determined that many of the TSL data files had been generated with faulty data or with incorrect processing, and a new set of ACE files for TSL data was created, with the corrected files contained in directory ENDF80SaB2.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗
NASA NTRS1991

Ada Namelist Package

Ada Namelist Package, developed for Ada programming language, enables calling program to read and write FORTRAN-style namelist files. Features are: handling of any combination of types defined by user; ability to read vectors, matrices, and slices of vectors and matrices; handling of mismatches between variables in namelist file and those in programmed list of namelist variables; and ability to avoid searching entire input file for each variable. Principle benefits derived by user: ability to read and write namelist-readable files, ability to detect most file errors in initialization phase, and organization keeping number of instantiated units to few packages rather than to many subprograms.

Klumpp, Allan R.↗
NASA NTRS1991

Structural tailoring of advanced turboprops (STAT): User's manual

This user's manual describes the Structural Tailoring of Advanced Turboprops program. It contains instructions to prepare the input for optimization, blade geometry and analysis, geometry generation, and finite element program control. In addition, a sample input file is provided as well as a section describing special applications (i.e., non-standard input).

Brown, K. W.↗
NASA NTRS1994

Coupled 2-dimensional cascade theory for noise an d unsteady aerodynamics of blade row interaction in turbofans. Volume 2: Documentation for computer code CUP2D

A two dimensional linear aeroacoustic theory for rotor/stator interaction with unsteady coupling was derived and explored in Volume 1 of this report. Computer program CUP2D has been written in FORTRAN embodying the theoretical equations. This volume (Volume 2) describes the structure of the code, installation and running, preparation of the input file, and interpretation of the output. A sample case is provided with printouts of the input and output. The source code is included with comments linking it closely to the theoretical equations in Volume 1.

Hanson, Donald B.↗
DOE OSTI2025

Hyporheic-zone Processes and Stream Oxygen Dynamics: Insights from a Multiscale Reactive Transport Model: Modeling Archive

This archive contains the data and Python scripts required to reproduce the analyses and figures in the study: Gomez-Velez, J. D., Rathore, S. S., Cohen, M. J., & Painter, S. L. (2025). Hyporheic-zone Processes and Stream Oxygen Dynamics: Insights from a Multiscale Reactive Transport Model. Submitted to Water Resources Research. The analysis utilizes the subgrid model Advection Dispersion Equation with Lagrangian Subgrids (ADELS) implemented in the Advanced Terrestrial Simulator (ATS; https://amanzi.github.io/ats/stable/). In this case, the ATS and Amanzi versions are (1) ATS version 1.5.1_f5ba18f8 and (2) Amanzi version 1.6-dev_53444cca4. The repository includes a Jupyter Notebook and the necessary data (Pandas DataFrames stored as pickle files) to generate the figures for the manuscript. Additionally, it contains Python scripts to create ATS input files, run the ATS simulations, and post-process the results. Finally, it provides routines for parameter estimation using the Single-Station Metabolism (SSM) model with the Differential Evolution Adaptive Metropolis (DREAM) Markov Chain Monte Carlo (MCMC) algorithm with ZS enhancements (DREAM-ZS).

54 ENVIRONMENTAL SCIENCES↗
DOE OSTI2021

RAVEN User Manual

RAVEN is a generic software framework to perform parametric and probabilistic analysis based on the response of complex system codes. The initial development was aimed to provide dynamic risk analysis capabilities to the Thermo-Hydraulic code RELAP-7, currently under development at the Idaho National Laboratory (INL). Although the initial goal has been fully accomplished, RAVEN is now a multi-purpose probabilistic and uncertainty quantification platform, capable to agnostically communicate with any system code. This agnosticism includes providing Application Programming Interfaces (APIs). These APIs are used to allow RAVEN to interact with any code as long as all the parameters that need to be perturbed are accessible by inputs files or via python interfaces. RAVEN is capable of investigating the system response, and investigating the input space using Monte Carlo, Grid, or Latin Hyper Cube sampling schemes, but its strength is focused to- ward system feature discovery, such as limit surfaces, separating regions of the input space leading to system failure, using dynamic supervised learning techniques. The development of RAVEN has started in 2012, when, within the Nuclear Energy Advanced Modeling and Simulation (NEAMS) program, the need to provide a modern risk evaluation framework became stronger. RAVEN principal assignment is to provide the necessary software and algorithms in order to employ the concept developed by the Risk Informed Safety Margin Characterization (RISMC) program. RISMC is one of the pathways defined within the Light Water Reactor Sustainability (LWRS) program. In the RISMC approach, the goal is not just the individuation of the frequency of an event potentially leading to a system failure, but the closeness (or not) to key safety-related events. Hence, the approach is interested in identifying and increasing the safety margins related to those events. A safety margin is a numerical value quantifying the probability that a safety metric (e.g. for an important process such as peak pressure in a pipe) is exceeded under certain conditions. The initial development of RAVEN has been focused on providing dynamic risk assessment capability to RELAP-7, currently under development at the INL and, likely, future replacement of the RELAP5-3D code. Most the capabilities that have been implemented having RELAP-7 as principal focus are easily deployable for other system codes. For this reason, several side activates are currently ongoing for coupling RAVEN with soft- ware such as RELAP5-3D, etc. The aim of this document is the explanation of the input requirements, focalizing on the input structure.

97 MATHEMATICS AND COMPUTING↗
DOE OSTI2020

Vadose Zone Model for SALDS for Composite Analysis

The objectives of the vadose modeling for the updated Hanford Site composite analysis (CA) are to simulate the flow and transport of water and radionuclide releases from the surface to the water table and to provide radionuclide transfer rates for the plateau to river (P2R) model, version 8.3 (CP-57037, Model Package Report: Plateau to River Groundwater Model, Version 8.3). Water additions include natural recharge and water discharged to the ground as a result of industrial processes associated with Hanford Site operations. Contaminant sources include radionuclides in water discharged to the ground during operations and radionuclides disposed “dry” in solid waste burial grounds or other means. The following 16 radionuclides were selected for this modeling effort: carbon-14 (C-14), chlorine-36 (Cl-36), tritium (H-3), iodine-129 (I-129), neptunium-237 (Np-237), rhenium-187 (Re-187), strontium-90 (Sr-90), technetium-99 (Tc-99), uranium-232 (U-232), uranium-233 (U-233), uranium-234 (U-234), uranium-235 (U-235), uranium-236 (U-236), uranium-238 (U-238), radium-226 (Ra-226), and thorium-230 (Th-230). The simulation time starts in 1943 and ends at 12070, which is 10,000 years after assumed Hanford Site closure in 2070. The parallel version of the Subsurface Transport Over Multiple Phases (STOMP1) simulator, officially named the exascale Subsurface Transport Over Multiple Phases (eSTOMP) is used to simulate flow and transport for the vadose models. The documentation for the STOMP code is comprehensive. The theoretical and numerical approaches applied in the STOMP code are documented in a published theory guide (PNNL-12030, STOMP Subsurface Transport Over Multiple Phases Version 2.0 Theory Guide). The code has undergone a rigorous verification procedure against analytical solutions, laboratory-scale experiments, and field-scale demonstrations. The application guide (PNNL-11216, STOMP Subsurface Transport Over Multiple Phases Application Guide) provides instructive examples in the application of the code to classical groundwater problems. The user’s guide (PNNL-15782, STOMP: Subsurface Transport Over Multiple Phases Version 4.0: User’s Guide) describes the general use, input file formatting, compilation, and execution of the code. The primary output of the vadose zone modeling is radionuclide transfer rates to the groundwater for input into the P2R model. The rates will be summed over the 100 by 100 m P2R grid cells that fall within the vadose zone model source domain. The Hanford Site Central Plateau was subdivided into 26 individual vadose zone models, with 13 in the 200 East Area and 13 in the 200 West Area. Waste sites that have a completed performance assessment (PA) or past-leak analysis were not included as sources of radionuclides. Instead the vadose zone to groundwater transfer rates of the Environmental Restoration Disposal Facility, Integrated Disposal Facility, US Ecology, and Waste Management Area C (WMA C) PAs and the past-leak analysis for WMA C were used as direct input to the P2R model. Each of the vadose zone models is documented in separate environmental calculation files (ECFs). This ECF describes the State-Approved Land Disposal Site (SALDS) model. The scope of this ECF is to document the development and results of the SALDS vadose zone model. CP-63515, Model Package Report: Central Plateau Vadose Zone Models, describes the approach, assumptions, process of determining the number of models required and domain of each model, input data, and processing common to all the models.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗
DOE OSTI2020

Vadose Zone Model for B-3A/B Pond for Composite Analysis

The objectives of the vadose modeling for the updated Hanford Site composite analysis (CA) are to simulate the flow and transport of water and radionuclide releases from the surface to the water table and to provide radionuclide transfer rates for the plateau to river (P2R) model, version 8.3 (CP-57037, Model Package Report: Plateau to River Groundwater Model, Version 8.3). Water additions include natural recharge and water discharged to the ground as a result of industrial processes associated with Hanford Site operations. Contaminant sources include radionuclides in water discharged to the ground during operations and radionuclides disposed “dry” in solid waste burial grounds or other means. The following 16 radionuclides were selected for this modeling effort; carbon-14 (C-14), chlorine-36 (Cl-36), tritium (H-3), iodine-129 (I-129), neptunium-237 (Np-237), rhenium-187 (Re-187), strontium-90 (Sr-90), technetium-99 (Tc-99), uranium-232 (U-232), uranium-233 (U-233), uranium-234 (U-234), uranium-235 (U-235), uranium-236 (U-236), uranium-238 (U-238), radium-226 (Ra-226), and thorium-230 (Th-230). The simulation time starts in 1943 and ends at 12070, which is 10,000 years after assumed Hanford Site closure in 2070. The parallel version of the Subsurface Transport Over Multiple Phases (STOMP) simulator officially named the exascale Subsurface Transport Over Multiple Phases (eSTOMP), is used to simulate flow and transport for the vadose models. The documentation for the STOMP code is comprehensive. The theoretical and numerical approaches applied in the STOMP code are documented in a published theory guide (PNNL-12030, STOMP Subsurface Transport Over Multiple Phases Version 2.0 Theory Guide). The code has undergone a rigorous verification procedure against analytical solutions, laboratory-scale experiments, and field-scale demonstrations. The application guide (PNNL-11216, STOMP Subsurface Transport Over Multiple Phases Application Guide) provides instructive examples in the application of the code to classical groundwater problems. The user’s guide (PNNL-15782, STOMP: Subsurface Transport Over Multiple Phases Version 4.0: User’s Guide) describes the general use, input file formatting, compilation, and execution of the code. The primary output of the vadose zone modeling is radionuclide transfer rates to the groundwater for input into the P2R model. The rates will be summed over the 100 by 100 m P2R grid cells that fall within the vadose zone model source domain. The Hanford Site Central Plateau was subdivided into 26 individual vadose zone models, with 13 in the 200 East Area and 13 in the 200 West Area. Waste sites that have a completed performance assessment (PA) or past-leak analysis were not included as sources of radionuclides. Instead the vadose zone to groundwater transfer rates of the Environmental Restoration Disposal Facility, Integrated Disposal Facility, US Ecology, and Waste Management Area C (WMA C) PAs and the past-leak analysis for WMA C were used as direct input to the P2R model. Each of the vadose zone models is documented in separate environmental calculation files (ECFs). This ECF describes the B-3A/B Ponds model. The scope of this ECF is to document the development and results of the B-3 A/B Ponds vadose zone model. CP-63515, Model Package Report: Central Plateau Vadose Zone Models, describes the approach, assumptions, process of determining the number of models required and domain of each model, input data, and processing common to all the models.

12 MANAGEMENT OF RADIOACTIVE AND NON-RADIOACTIVE W↗