SEARCH · Engineering Papers
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.
The Example Problems Manual supplements the User's Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User's Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is.
The Example Problems Manual supplements the User’s Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.
Describes the set of example problems, input decks, and meshes that are distributed with Sierra/SD. The Example Problems Manual supplements the User’s Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is. The organization is similar to the other documents: How to run, Commands, Solution cases, Materials, Elements, Boundary conditions, and then Contact. The table of contents and index are indispensable. The Geometric Rigid Body Modes section is shared with the Users Manual.
The Example Problems Manual supplements the User’s Manual and the Theory Manual. The goal of the Example Problems Manual is to reduce learning time for complex end to end analyses. These documents are intended to be used together. See the User’s Manual for a complete list of the options for a solution case. All the examples are part of the Sierra/SD test suite. Each runs as is.
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.
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.
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.
A theory and user manual of thermal hydraulic code SE2-ANL was prepared in this work, to resolve the missing documentation. SE2-ANL, a special version of SUPERENERGY-2, is a multi-assembly steady-state Liquid Metal Reactor (LMR) core thermal hydraulic analysis code, and it was developed in the 1980s, but no complete documentation was ever made. This report describes the detailed methodology of the temperature calculation, inherited from (original) SUPERENERGY-2, and fuel and cladding temperature calculation capabilities as well as many other features which were incorporated in SE2-ANL. The input and output of SE2-ANL are also demonstrated in detail, using some simple models. The orificing zone capability as well as some other useful features of SE2-ANL are discussed.
The MELCOR Accident Consequence Code System (MACCS) is used by Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This User Guide is intended to assist analysts in understanding the MACCS/WinMACCS model and to provide information regarding the code. This user guide version describes MACCS Version 3.10.0. Features that have been added to MACCS in subsequent versions are described in separate documentation. This User Guide provides a brief description of the model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2. PAPERWORK REDUCTION ACT STATEMENT The NUREG does not contain information collection requirements and, therefore, is not subject to the requirements of the Paperwork Reduction Act of 1995 (44 USC 3501, et seq.). PUBLIC PROTECTION NOTIFICATION The NRC may not conduct or sponsor, and a person is not required to respond to, a request for information or an information collection requirement unless the requesting document displays a currently valid OMB control number. ACKNOWLEDGEMENTS Contributions to this User Guide were received from NRC and Sandia National Laboratories (SNL) project managers, technical experts, and code authors dedicated to the production of a valuable resource for the MACCS user community. Instructions and guidance included herein were developed over many years and include advancements in the code that provide users the ability to develop complex consequence modeling scenarios. WinMACCS and many of the early MACCS developments were due to vision of an earlier Project Manager, Jocelyn Mitchell. Jonathan Barr and AJ Nosek also contributed to the development of this report. The current NRC Project Manager, Salman Haq, provided the leadership to ensure this document was completed. Several other NRC and Sandia staff provided insights supporting development of the MACCS code and of this document.
A number of tasks for the heat pipe simulation tool Sockeye were identified based on customer needs and included both user documentation and code development: (a) Implement saturation-dependence in the capillary pressure model; (b) Provide an analytic utility to analyze the frozen startup limit; (c) Demonstrate custom friction closures; (d) Develop examples for different types of heat transfer sources and boundary conditions; (e) Demonstrate the capillary and sonic limits; and (f) Provide discretization details in the theory manual. These tasks were all completed, and results are given where applicable.
The MELCOR Accident Consequence Code System (MACCS) is used by Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This User Guide is intended to assist analysts in understanding the MACCS/WinMACCS model and to provide information regarding the code. This user guide version describes MACCS Version 4.0. Features that have been added to MACCS in subsequent versions are described in separate documentation. This User Guide provides a brief description of the model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2.
The MELCOR Accident Consequence Code System (MACCS) is used by Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This User Guide is intended to assist analysts in understanding the MACCS/WinMACCS model and to provide information regarding the code. This user guide version describes MACCS Version 4.0. Features that have been added to MACCS in subsequent versions are described in separate documentation. This User Guide provides a brief description of the model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2.
This document is the beginnings of combining the theory of electron production and the code implementations in MCNP and other codes. The hopes of this is to help translate all the theory into the theory manual of MCATK. In addition, this will help the MCATK team to know how other codes treat electron physics.
The fuel characterization models of SAS4A/SASSYS-1 (SAS) have recently been extended to include a new U-Pu-Zr metal fuel model, MFUEL. MFUEL is equipped with mechanistic physics based models to predict the pre-transient characterization and transient response of metal fuel, with emphasis on fuel melting, cladding failure, and the metal fuel’s impact on core reactivity. The MFUEL model will be available in the full version of SAS4A/SASSYS-1 5.7, which is scheduled to be released in June 2023. Fast reactor fuel pins that operated in EBR-II and FFTF with low smear density U-Zr and U-Pu-Zr metal fuels and irradiation resistant ferritic-martensitic cladding showed significant advantages in achieving high burnups and assuring inherent safety characteristics during anticipated transients, design basis events, and beyond design basis events. For safety analysis, a fuel performance model must be able to predict (1) Fuel pin mechanics and compositional and dimensional changes, (2) Clad failure, and (3) Fuel pin thermal resistance. Achieving these high level goals accurately is strongly related to the model performance of individual physical processes taking place within a fuel pin during its lifetime. Metal fuels typically operate above the mid-point temperature of melting during normal, as well as off-normal, conditions. At these elevated temperatures, the availability of thermal activation provides a driving force for various diffusional processes leading to complex phase transformations, micro-structure evolution, significant amounts of fuel swelling, interconnected porosity formation, excessive amounts of fission gas release, and fuel clad chemical interactions. Clad failure in fast reactors primarily occurs as a result of creep rupture augmented by clad wastage formation. The reaction is driven by thermal creep induced dislocation motion, grain boundary cavity nucleation, growth and breakup of grain boundaries. The high level complexity and limited available data requires introducing physics-based modeling approaches to gain extrapolation ability and sensitivity with respect to various conditions. The objective of this report is to perform validation of MFUEL using the experimental data for (1) Normal operation EBR-II fuel behavior, (2) Normal operation PHENIX fuel behavior, (3) HT9 Pressure tube ramp-and-hold creep rupture tests, (4) Whole Pin Furnace (WPF) creep strain, creep rupture and eutectic tests, (5) Fuel Behavior Test Apparatus (FBTA) eutectic tests, and (6) TREAT M5-7 OverPower tests up to clad failure. Section-2 includes a brief description of the MFUEL models. A detailed description of the MFUEL physics-based, semi-empirical models will be presented in the SAS V 5.7 theory manual. Section-3, 4, and 5 describes the validation effort for the pre-transient irradiation, furnace transients, and TREAT M-Series transients, respectively.
MACCS is used by the Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This User Guide is intended to assist analysts in understanding the MACCS/WinMACCS model and to provide information regarding the code. This user guide version describes MACCS Version 4.2. This User Guide provides a brief description of the model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2.
MACCS is used by the Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This user guide is intended to assist analysts in understanding the MACCS/MACCS-UI User Interface (UI) model and to provide information regarding the code. This user guide version describes MACCS Version 5.0, model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2.
MACCS is used by the Nuclear Regulatory Commission (NRC) and various national and international organizations for probabilistic consequence analysis of nuclear power accidents. This user guide is intended to assist analysts in understanding the MACCS/MACCS-UI User Interface (UI) model and to provide information regarding the code. This user guide version describes MACCS Version 5.2, model history, explains how to set up and execute a problem, and informs the user of the definition of various input parameters and any constraints placed on those parameters. This report is part of a series of reports documenting MACCS. Other reports include the MACCS Theory Manual, MACCS Verification Report, Technical Bases for Consequence Analyses Using MACCS, as well as documentation for preprocessor codes including SecPop, MelMACCS, and COMIDA2.
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.