Search NASA⌕ Search

SEARCH · Search NASA

Results for “mcnp”

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 19 records

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↗

MCNP ® Code V.6.3.0 Release Notes

The Monte Carlo N-Particle ® (MCNP ® ) code is a general-purpose, continuous-energy, generalized geometry, time-dependent, radiation transport code developed by the MCNP development team. The MCNP calculations provide predictive capabilities that can replace expensive or impossible-to perform experiments. Specific application problems include simulations of experimental diagnostics, intrinsic radiation, radiation detection and measurement, criticality safety, nuclear threat reduction and response, radiation health protection, nuclear weapons effects, and nuclear forensics. This MCNP code, version 6.3.0, follows the MCNP6.2.0 version. Since the release of MCNP6.2.0, many changes have been made to the MCNP code. These changes include new or improved features, a new build system, code enhancement and modernization, and bug fixes. The MCNP code, version 6.3.0, theory and user input information is documented in MCNP ® Code Version 6.3.0 Theory & User Manual, the build guidance for various platforms is documented in MCNP ® Code Version 6.3.0 Build Guide, and the verification and validation testing for various application benchmark test suites is documented in MCNP ® Code Version 6.3.0 Verification & Validation Testing.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Processing MCNP Elemental Edit Outputs

The Monte Carlo N-Particle (MCNP) transport code version 6 (also known as MCNP6) has the capability for tracking particles on unstructured mesh (UM) geometry models embedded into constructive solid geometry (CSG) cells. A UM geometry is a collection of elements representing a solid geometry. The first step of MCNP UM modeling is using other software packages to create a finite element mesh representation of a solid 3D geometry. Computer-aided design (CAD) or computer-aided manufacturing (CAM) software is typically used to create a solid geometry model, which is later imported into mesh generation software to create a UM model. The MCNP UM feature was originally designed for models generated by the Abaqus/CAE software. The MCNP code version 6.0 and later can process UM models formatted as Abaqus input files. MCNP can process a UM model consisting of several different element types including linear tetrahedral or hexahedral elements and calculate quantities of interest such as flux and energy deposition at elements. An MCNP UM simulation provides high-fidelity elemental edit (i.e., tally) outputs, which can be further used in multiphysics calculations. The MCNP UM feature was used for multiphysics simulations where quantities of interest calculated by MCNP are used as inputs for heat transfer calculations in Abaqus. MCNP6.3 can produce two types of elemental edit output (EEOUT) file formats: ASCII and HDF5. An EEOUT file type must be requested on an EMBED card while output type (flux or energy deposition) must be requested on an EMBEE card. We wrote Python3 scripts to extract energy deposition values in an ASCII or HDF5 EEOUT file and compute a heat flux profile for an Abaqus heat transfer calculation.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

MCNP® Code Version 6.3.1 Release Notes

The Monte Carlo N-Particle® (MCNP® ) code is a general-purpose, continuous-energy, generalized-geometry, time-dependent, radiation transport code developed by the MCNP development team. MCNP calculations provide predictive capabilities that can replace expensive or impossible-to-perform experiments. Specific application problems include simulations of experimental diagnostics, intrinsic radiation, radiation detection and measurement, criticality safety, nuclear threat reduction and response, radiation health protection, nuclear weapons effects, and nuclear forensics. This MCNP code, version 6.3.1, follows the MCNP6.3.0 version. Since the release of MCNP6.3.0, a variety of bug fixes and code enhancements have been completed for MCNP6.3.1. A few new features have also been added to this release to support both ongoing research and the release of the latest ENDF/B-VIII.1 nuclear data library. The MCNP code, version 6.3.1, theory and user input information is documented in MCNP® Code Version 6.3.1 Theory & User Manual, the build guidance for various platforms is documented in MCNP® Code Version 6.3.1 Build Guide, and the verification and validation testing for various application benchmark test suites is documented in MCNP® Code Version 6.3.1 Verification & Validation Testing.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

MontePy: a Python library for reading, editing, and writing MCNP input files.

The Monte Carlo N-Particle (MCNP) radiation transport code is a highly capable and accurate code with a long legacy. MCNP uses the Monte Carlo simulation process to simulate the path of particles (e.g., neutrons, photons, charged particles, etc.), and their interaction with materials. It is widely used in nuclear engineering, high-energy physics, and other fields. Its origins in the mid-twentieth century predate many modern software conventions. MCNP users provide an input file to MCNP, which it then uses to create an internal representation of the simulation problem. These input files originally had to be stored as punchcard decks, and the user manual still uses the terminology of cards and decks, despite moving beyond punchcards. MCNP predates nearly all modern human readable markup or data serialization languages, such as the extensible Markup Language (XML), the Standard Generalized Markup Language (SGML), YAML (YAML Ain’t Markup Language), and Javascript Object Notation (JSON). Due to this, MCNP uses an entirely custom defined syntax language for its input, making off-the-shelf libraries for XML, YAML, and JSON impossible to use for scripting various operations on MCNP input files (Kulesza et al., 2022).

97 - MATHEMATICS AND COMPUTING↗

Using CUBIT to Create Unstructured Mesh Models for MCNP Simulations

The Monte Carlo N-Particle (MCNP) transport code version 6 (also known as MCNP6) 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 creating CSG models is a time-consuming and error-prone process as the complexities of geometries increase. An MCNP UM calculation requires UM geometry input files. The UM capability was originally designed to work with UM models created with the Abaqus/CAE software and ASCII input files that it generates. The Abaqus-formatted input files needed for MCNP UM calculations must have the correct Abaqus syntax and meet the additional MCNP requirements. Several software packages can generate a UM model formatted as an Abaqus input file. 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 created by Cubit cannot be used for MCNP simulations. A Python script has been developed to convert an Abaqus file created by Cubit to an Abaqus file that the MCNP code can process. This report describes the process of using Cubit to create UM models for MCNP calculations.

97 MATHEMATICS AND COMPUTING↗

Docker Containers for MCNP ® Development

Containers are a revolutionary technology in software development and deployment that provides a lightweight, portable environment for ensuring consistency across multiple computing environments. In anticipation of the MCNP 6.3.1 release, two Docker container images have been released on DockerHub for general use. The MCNP source code is not included in the images, and users are still required to obtain it through RSICC. The images produced by Docker are compliant with the OCI (Open Container Initiative) standards, ensuring compatibility with other container engines such as Podman or Kubernetes’ CRI-O. Initially, the images are stored under the author’s personal space on DockerHub (docker.io/azukaitis), but they will be relocated to a dedicated MCNP group space once approved. In the future, they will also be available through the registry feature of the https://github.com/lanl/mcnp-containers project. The use of Docker provides a pre-configured environment for building and running MCNP, ensuring reproducibility of results across various host architectures. This significantly improves consistency when running MCNP on different systems. Notably, executables and installers from the Docker images have successfully passed the MCNP development branch testing suite on x86-64 architectures, including Windows, macOS, and Linux operating systems. Furthermore, testing has demonstrated compatibility with macOS Docker in emulation mode on the latest Apple Mac M2 Ultra hardware, ensuring robust support even on the latest platforms. In this document, we will provide a step-by-step guide to using the Docker images across multiple platforms. Additionally, we will present performance numbers for building and running the MCNP test suite.

97 MATHEMATICS AND COMPUTING↗

Evaluation of simulated HPGe detector efficiencies in OpenMC compared to MCNP

In late 2023, the open-source radiation transport code OpenMC introduced a pulse-height tally (PHT) feature, enabling users to track the total energy deposited by individual photons in OpenMC cells. This function represents an important improvement of the OpenMC code because it allows users to simulate the response function of a gamma detector without relying on closed-source alternatives. Despite this, limited work has been published evaluating OpenMC as a radiation transport code for simulating gamma spectroscopy experiments. This study attempts to demonstrate the usefulness of OpenMC in this space by directly comparing its PHT output to MCNP (a trusted industry-standard Monte Carlo code). In the first half of this study, a radiation transport experiment is described in which a detector with a complex internal geometry is exposed to various gamma-emitting isotopes ( 133 Ba, 137 Cs, and 60 Co) over a range of distances. The setup of this experiment was modeled in MCNP with sufficient detail to capture the efficiency characteristics of a high purity germanium (HPGe) detector for the primary gammas of each isotope. After good agreement between the MCNP model and experiment was achieved, an identical model was produced in OpenMC to allow direct comparison between the full energy peak (FEP) values produced in OpenMC and MCNP. The results show strong agreement between OpenMC and MCNP across the full range of tested energies, with each model’s FEP values typically within 2% of each other and most FEP areas within 4% of experimental data. Worse agreement was seen between the Monte Carlo codes and experiment below 300 keV (an expected result). For the 662 keV line of 137 Cs, both codes were found in poor agreement with experiment and each other over the full range of distances tested (possibly indicating an error with the 137 Cs experimental data). Ignoring the anomalous results of the 662 keV line, all other data show good qualitative and quantitative agreement between MCNP and OpenMC. This result demonstrates the accuracy of OpenMC’s PHT feature for spectroscopic applications in which detector efficiency is a primary concern.

07 - ISOTOPES AND RADIATION SOURCES↗

Cubit for MCNP Unstructured Mesh Analysis of Oktavian Benchmarks

The Monte Carlo N-Particle (MCNP) transport code developed by Los Alamos National Laboratory (LANL) can be used to transport various particles across user defined three dimensional (3D) geometries. Traditionally, these geometries are created as constructive solid geometry (CSG), involving the use of Boolean operators on defined surfaces to create 3D regions known as cells. A newer method of geometry definition in the MCNP code is unstructured mesh (UM) embedded within a CSG cell using the universe and fill repeated-structure features. An MCNP UM calculation requires an MCNP input file and mesh geometry file. The MCNP code cannot be used to generate UM geometry models. A computer-aided design (CAD) software is typically used to construct a solid geometry model, and a CAD file is then imported into a mesh generation software to prepare and generate a mesh model. Some mesh generation software packages have the ability to create a solid geometry and thus a separate CAD software for creating a CAD model is not needed. In this work, Cubit, a geometry creation and meshing software developed by Sandia National Laboratories, is used to construct UM models for MCNP simulations.

72 PHYSICS OF ELEMENTARY PARTICLES AND FIELDS↗

Photon detector response function methodology using MCNP and shift hybrid radiation transport code for wide-area contamination assay applications

Here, radiation transport modeling using the Monte Carlo N-Particle (MCNP) radiation transport code and Monte Carlo code, Shift, were employed to model detector responses for a variety of wide-area photon contamination scenarios. In this study, 2" × 2" and 3" × 3" cylindrical NaI(Tl) scintillation detector configurations at source detector-distances of 0.5 cm, 1 cm, 2.54 cm, 10 cm, and 30 cm were modeled. Media of soil, concrete, and steel were evaluated for contamination depths ranging from surface to a depth of an infinite thickness in each medium for photon energies ranging from 20 keV to 3 MeV, which correspond to the energies that current detectors can discern. Monoenergetic photon surface contamination detector responses for each of the media, source–detector distances, and detectors were estimated using MCNP v6.2. Shift was harnessed for improved variance reduction of particle transport in highly attenuating media to obtain average cell fluxes in the two MCNP NaI(Tl) scintillation detector configurations. Average cell flux values in Shift were coupled with detector responses from MCNP to convert average cell flux in a void to energy distribution of pulses in the NaI(Tl) scintillation detector crystal of interest. An optimized detector response function methodology was developed by coupling the MCNP radiation transport method with the Consistent Adjoint Driven Importance Sampling (CADIS) hybrid radiation transport method built into Shift to significantly decrease the runtime of thousands of MCNP pulse height simulations. The methodology may be utilized to quickly and accurately facilitate the assessment of a broad range of wide-area environmental contamination assay and decommissioning cleanup applications.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

Development of MCNP Training Modules for Safeguards Practitioners [Abstract]

The Monte-Carlo N-Particle (MCNP) software developed at LANL is the most widely used neutron transport code in the world. It is an essential tool for a variety of applications including detector development and design, nuclear fuel burnup simulation, criticality safety, and nondestructive assay system optimization. For this reason, it is indispensable within the safeguards and materials control & accountability (MC&A) communities. Multiple MCNP training courses have been created and taught over the last several decades by the MCNP development team at LANL, however there are no existing courses that cover specialized topics considered fundamental to NDA and safeguards models. To fill this gap, the MCNP team and Safeguards Science and Technology group at LANL have co-created a set of training modules customized to meet the specialized needs of the safeguards and MC&A communities. The basic modules cover concepts such as NDA system optimization, He-specific and other capture tallies, and tools for improved theoretical understanding. An advanced module was also created to cover topics including variance reduction for active interrogation simulations, use of the LANL MCNPTools post-processor, PTRAC (particle tracking) and list-mode data simulations, and fuel burnup simulations. The training modules teach to the latest and most state-of-the-art MCNP features and tools released by the development team at LANL and are intended to be taught jointly by the developers and safeguards experts. Ultimately, we hope that creation of these modules will serve to capture and convey the safeguards modeling and MCNP expertise at LANL, and that we will be able to share the modules more broadly with the MC&A and safeguards communities.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

Serpent and MCNP Calculations of the Energy Deposition in the Transformational Challenge Reactor

This paper focuses on the calculation of the energy deposition in the Transformational Challenge Reactor by two major Monte Carlo codes: Serpent and MCNP. The first software computation relies on Kinetic Energy Released per unit Mass (KERMA) factors while the second one relies on Q-values. The results from these two independent computation methodologies are in very good agreement; however, Serpent runs much faster than MCNP (for the same computational model) and allows for a detailed energy deposition distribution from a 1-mm-side square mesh with a relative statistical error between 0.5% and 1%. This detailed energy deposition is suitable for multiphysics analyses aimed at design optimizations. In order to calculate the energy deposition, Serpent needs enhanced ACE files (distributed by the software developers). Unlike other Monte Carlo software that uses inputs based on Python or Java languages, the Serpent input syntax is very similar to that of MCNP; a Python script can convert a MCNP input to a Serpent input in seconds. For simulations not requiring the calculation of the energy deposition, Serpent can also read nuclear data from MCNP ACE files, which eventually improves the comparison of the results of the two codes.

22 GENERAL STUDIES OF NUCLEAR REACTORS↗

A Verification of Flux Sensitivity Estimates Using the MCNP Tally Perturbation Tool

Nuclear data is commonly used in applications such as nuclear nonproliferation, safeguards, and criticality safety. More specifically, nuclear data is used in predictive simulation codes like the Monte-Carlo N-Particle (MCNP ® ) transport code, Serpent, and similar radiation transport codes. The improvement of nuclear data enables more precise and accurate simulations, which result in higher fidelity designs and reduced operational/procedural costs. Therefore, the improvement of nuclear data is of paramount importance across the nuclear community. Nuclear data is improved and validated through integral benchmark experiments. The design of benchmark experiments is an extensive process; therefore, these experiments are often optimized on multiple characteristics, including sensitivity to the nuclear data, during the design process. Sensitivity is a measure of how much a quantity changes due to changes in independent variables such as experimental configuration. An experimental design that has a larger sensitivity to the nuclear data of interest will have a larger impact on the accuracy and precision of the validated data. Past integral benchmark experiments have primarily used the effective multiplication factor ($k_{eff}$) as the predominant measured quantity; however, experiments designed with other quantities in mind would be able to optimize on validating different areas of the nuclear data. A primary goal of the EUCLID project is to design, constrain, and reduce compensating errors in experiments focused on quantities other than $k_{eff}$ to better validate nuclear data across the board. Currently, there is a capability in MCNP to easily calculate the sensitivity of $k_{eff}$ to specific nuclear data of numerous reactions types and isotopes (KSEN card); however, the sensitivity of other quantities must be estimated in more strenuous manners. For example, the perturbation feature (PERT card) of MCNP can be used to estimate first-order sensitivities of some response in fixed source simulations. A recent announcement revealed that the first- and second-order perturbation features in previous releases of MCNP contained a bug. It was identified that particles were being scored into the wrong energy bin. The bug is in the most recent public release (MCNP6.2); however, a patch has been added to the most up to date version (MCNP6.2.2) that has not been released publicly. A direct comparison of the PERT card results for an F4 (neutron flux averaged over a cell) tally before and after the patch are shown in figure 1. All simulations used in the sensitivity estimates in this report were performed with MCNP6.2.2. This work verifies the patched MCNP perturbation tool by comparing first order sensitivities made using the PERT card to estimates made using manual perturbation of the compact ENDF (ACE) files.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

MCNP ® Code Version 6.3.0 Theory & User Manual

This document acts as a repository of knowledge for the Monte Carlo N-Particle (MCNP) transport computer code. It is maintained alongside the source code and attempts to introduce new users and re-familiarize experienced users with the theory and practices of using the MCNP code for the wide range of particle transport analyses that it is appropriate for. The latest version of the MCNP code, version 6.3.0, provides the Monte Carlo particle transport community with the latest feature developments and bug fixes in the MCNP code. The MCNP code version 6.0 and later is also known as the MCNP6 code.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

SPND Sensitivity Calculations Using MCNP and Experimental Data from ACRR

The use of the Monte Carlo N-Particle Transport Code (MCNP) to calculate detector sensitivity for Self-Powered Neutron Detectors (SPNDs) in the Annular Core Research Reactor (ACRR) could be a vital tool in the effort to optimize the design of next-generation SPNDs. Next-generation SPND designs, which consider specific materials and geometry, may provide experimenters with capabilities for advanced mixed field dosimetry. These detectors will need to be optimized for configuration, materials, and geometries and the ability to model and iterate must be available in order to decide on the ideal. SPND design. SPNDs were modeled in MCNP which closely resembled the dimensions and location of actual detectors used in the ACRR. Tallies were used to calculate detector sensitivity. Using metrics from a previous report, oscilloscope data from pulses were manipulated in a Matrix Laboratory computing environment (MATLAB) script to calculate experimental detector sensitivity. This report outlines the process in which experimental data from ACRR pulses verified results from tallies in an MCNP ACRR model. The sensitivity values from experiments and MCNP calculations agreed within one standard deviation. Parametric studies were also performed with MCNP to investigate the effects of materials and dimensions of different SPNDs.

46 INSTRUMENTATION RELATED TO NUCLEAR SCIENCE AND ↗

MCNP ® Code Version 6.3.1 Theory & User Manual

This document acts as a repository of knowledge for the Monte Carlo N-Particle (MCNP) transport computer code. It is maintained alongside the source code and attempts to introduce new users and re-familiarize experienced users with the theory and practices of using the MCNP code for the wide range of particle transport analyses that it is appropriate for. The latest version of the MCNP code, version 6.3.1, provides the Monte Carlo particle transport community with the latest feature developments and bug fixes in the MCNP code. The MCNP code version 6.0 and later is also known as the MCNP6 code.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

MCNP® Code Version 6.3.2 Theory & User Manual (Rev. 1)

This document acts as a repository of knowledge for the Monte Carlo N-Particle (MCNP) transport computer code. It is maintained alongside the source code and attempts to introduce new users and re-familiarize experienced users with the theory and practices of using the MCNP code for the wide range of particle transport analyses that it is appropriate for. The latest version of the MCNP code, version 6.3.2, provides the Monte Carlo particle transport community with the latest feature developments and bug fixes in the MCNP code. The MCNP code version 6.0 and later is also known as the MCNP6 code.

42 ENGINEERING↗

Verification of Upcoming MCNP Features For Estimating Nuclear Data Sensitivities in Fixed Source Simulations [Abstract]

Predictive simulation codes, like the Monte Carlo N-Particle (MCNP) transport code, are used throughout the nuclear community. These simulations are based on nuclear data. Maximizing the accuracy and precision of nuclear data maximizes the accuracy and precision of the overall simulation. This is imperative to applications that rely on simulations. For example, improving nuclear data for special nuclear material improves simulation accuracy in stockpile stewardship applications, which results in larger safety margins and decreased operational costs. The improvement and validation of nuclear data is completed through integral benchmark experiments. Past benchmarks have primarily been limited to focus on the effective multiplication factor ($\kappa$ eff ); broadening the purview of benchmarks beyond $\kappa$ eff -dependent nuclear data addresses nuclear data deficiencies. Different response types depend on different areas of nuclear data. This dependence is quantified as nuclear data sensitivity: the change in response due to perturbation of a contributing parameter. The larger the nuclear data sensitivity of a response, the more the experiment is influenced by the uncertainties of the nuclear data. The optimization of nuclear data sensitivities in future benchmarks would result in more detailed validation of lesser studied areas of nuclear data. Currently, direct sensitivity capabilities are not easily found for all experiment types and parameters. An MCNP tool to directly estimate the cross section sensitivities of tallied values is under development. Additionally, updates have been made to the perturbation feature of MCNP, which can be used in a less direct approach to estimating sensitivities. This work verifies these features to estimate nuclear data sensitivities in fixed source simulations of a 4.5-kg sphere of alpha- phase weapons-grade plutonium surrounded by differing amounts of copper and polyethylene. Integrated estimates made using MCNP’s tools were found to statistically agree with integrated estimates made from manual perturbation of nuclear data proving the validity of the MCNP tools.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗