Search NASA⌕ Search

SEARCH · Search NASA

Results for “Radiation Safety Information Computational Center (RSICC)”

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.

Radiation Safety Information Computational Center (RSICC) [Slides]

This presentation touches on the Radiation Safety Information Computational Center (RSICC). This Lecture provides general mission, statistics, and strategies. A general background is provided of the tool. Licensee agreements and export control agreements are discussed. The presentation finishes with a look at the most in demand and requested software packages.

97 MATHEMATICS AND COMPUTING↗

Nuclear Criticality Safety Repository, Radiation Safety Information Computational Center (RSICC), & NDA Program [Slides]

This lecture covers the Nuclear Criticality Safety Repository (NCSR), Radiation Safety Information Computational center (RSICC), and Non-destructive Assay (NDA) program. The lecture provides information on the Fiscal year of 2022 and various phases of the NCSR Program and NDA. Further background information is provided for the RSICC and operations summary.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

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↗

The History of Monte Carlo and MCNP at Los Alamos [Slides]

The Monte Carlo method for radiation particle transport has its origins at LANL dating back to the 1940’s. The creators of these methods were Drs. Stanislaw Ulam, John von Neumann, Robert Richtmyer, and Nicholas Metropolis. Monte Carlo methods for particle transport have been driving computational developments since the beginning of modern computers; this continues today. In the 1950’s and 1960’s, these new methods were organized into a series of special-purpose Monte Carlo codes, including MCS, MCN, MCP, and MCG. These codes were able to transport neutrons and photons for specialized LANL applications. In 1977, these separate codes were combined to create the LANL Monte Carlo N-Particle (MCNP) radiation particle transport code. In 1983, MCNP3 was released for public distribution to the Radiation Safety Information Computational Center (RSICC). MCNP6.3 will be released late in 2021. Each year, LANL has ~100 MCNP new users and RSICC ~1250 new licenses distributed. This talk will review the Los Alamos history of the development of the modern Monte Carlo method and MCNP.

73 NUCLEAR PHYSICS AND RADIATION PHYSICS↗

SOURCES4D

SOURCES is a code for computing neutron source rates and spectra from spontaneous fission (including delayed neutrons) and (alpha,n) reactions in homogeneous materials and (alpha,n) reactions in single-interface and two-interface geometries. SOURCES is a Los Alamos National Laboratory (LANL) code that is written in FORTRAN and distributed through the Radiation Safety Information Computation Center (RSICC). LANL’s last release of SOURCES to RSICC was SOURCES4C in 2002. This disclosure covers the latest version of SOURCES, SOURCES4D. This version adds sensitivity capabilities for (alpha,n) sources in homogeneous materials. Specifically, SOURCES4D writes new output that can be used to calculate, in post-processing, first and second derivatives of the (alpha,n) source rate density and spectrum with respect to nuclide densities in a homogeneous material and first derivatives of the (alpha,n) source rate density and spectrum with respect to nuclide stopping powers and (alpha,n) cross sections (nuclear data). These derivatives are useful for uncertainty quantification, predictive modeling, and other applications in neutron transport problems.

Favorite, Jeffrey A.↗

MCNP6.3: A Year in Review [Slides]

This presentation discusses the past year and the many accomplishments of the MCNP6.3 team. It states that the MCNP6.3 release is imminent and that the approved, final documents have been making their way to the website. The code executables and source are already packaged up for distribution and the new installer is being finalized and tested now, for all platforms. The package will be sent to RSICC before the end of October 2022. Additionally, the presentation discusses some things to think about as MCNP6.3 is requested and/or used. For example, many of the recent efforts have been focused on making development, updates, and distribution of the code and documents more robust and streamlined. They will be revising/updating documents more frequently than ever before and they will be exploring avenues to distribute official patches to MCNP6.3. As they explain, this allows them to be more responsive to bugs and issues that are identified. In conclusion, the application of a patch to MCNP6.3 will require having the source code.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

Results and Responses for the 2022 User Forum Survey [Slides]

This presentation discusses the results of a MCNP user survey. Example of questions asked include: "Which MCNP particle types do you typically use?," "What sort of simulations do you run most often?," "Do you build the code?," "Which variance reduction methods do you use?," "Opinions on HDF5," with frequent discussions regarding each question.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗

MCNP6.3 Code and Nuclear Data Installation Guide [Slides]

This presentation discusses the MCNP6.3 release package and examines how it offers more MCNP6-specific executables and options available than ever before. It also discusses the installer and that it streamlines the MCNP6.3 installation and automatically downloads all production nuclear data and generates xsdir files for the user. Additionally, the nd_manager is also discussed regarding how it allows the LANL Nuclear Data and Monte Carlo teams to work and distribute their products independently. It also allows updates, fixes (errata), and newly released data to be made available in a much faster timescale than ever before.

96 KNOWLEDGE MANAGEMENT AND PRESERVATION↗