Cardinal System Design Description
This template follows INL template TEM-140, "IT System Design Description."
This document serves as an addendum to Framework System Design Description and captures information for SDD specific to the Cardinal application.
- Framework System Design Description
- Fluid Properties System Design Description
- Heat Transfer System Design Description
- Navier Stokes System Design Description
- Reactor System Design Description
- Ray Tracing System Design Description
- Solid Mechanics System Design Description
- Solid Properties System Design Description
- Stochastic Tools System Design Description
- SubChannel System Design Description
- Thermal Hydraulics System Design Description
Introduction
Many of the phenomena related to nuclear energy systems depend on the solutions to multiple physics models, which can be described by partial differential equations that provide spatially- and temporally-varying values of solution variables. When these models for individual physics depend on one another, we call this "multiphysics." Cardinal relies on the OpenMC Monte Carlo radiation transport code and the NekRS spectral element Navier-Stokes code to perform high-fidelity multiphysics and multiscale simulation. Cardinal handles the couplings that may occur between these two codes, in addition to the numerous physics models provided by the MOOSE framework (such as solid mechanics, material science, and radiative heat transfer). This document describes the system design of Cardinal.
System Purpose
The Software Design Description provided here is description of each object in the system. The pluggable architecture of the underlying framework of Cardinal makes MOOSE and MOOSE-based applications straightforward to develop as each piece of end-user (developer) code that goes into the system follows a well-defined interface for the underlying systems that those object plug into. These descriptions are provided through developer-supplied "markdown" files that are required for all new objects that are developed as part of Cardinal. More information about the design documentation for MOOSE-based applications like Cardinal can be found in Documenting MOOSE.
System Scope
Cardinal is an application for performing high-fidelity simulation of nuclear systems incorporating Monte Carlo neutron-photon transport and/or spectral element Computational Fluid Dynamics (CFD). These physics can be combined with one another and with the MOOSE modules to accomplish "multiphysics" simulation. High-fidelity simulations can also be performed independently, for the purpose of data postprocessing, to generate constitutive models suitable for lower-fidelity tools, a process referred to as "multiscale" simulation.
Interfaces to other MOOSE-based codes, including systems-level thermal-hydraulics (SAM), heat pipe flows (Sockeye), and fuel performance (Bison) are also optionally included to support Cardinal simulations. Cardinal enables high-fidelity modeling of heat transfer, fluid flow, passive scalar transport, fluid-structure interaction, nuclear heating, tritium breeding, shielding effectiveness, material activation, material damage, and sensor response. The MultiApp System is leveraged to allow for the multiscale, multiphysics coupling. Further, other MOOSE capabilities in the modules, such as the Stochastic Tools Module enable engineering studies with uncertainty quantification and sensitivity analysis. Cardinal therefore supports design, safety, engineering, and research projects.
Dependencies and Limitations
Cardinal inherits the software dependencies of: - MOOSE framework - OpenMC - NekRS - DAGMC
No additional dependencies are present.
Definitions and Acronyms
This section defines, or provides the definition of, all terms and acronyms required to properly understand this specification.
Definitions
Pull (Merge) Request: A proposed change to the software (e.g. usually a code change, but may also include documentation, requirements, design, and/or testing).
Baseline: A specification or product (e.g., project plan, maintenance and operations (M&O) plan, requirements, or design) that has been formally reviewed and agreed upon, that thereafter serves as the basis for use and further development, and that can be changed only by using an approved change control process (NQA-1, 2009).
Validation: Confirmation, through the provision of objective evidence (e.g., acceptance test), that the requirements for a specific intended use or application have been fulfilled (24765:2010(E), 2010).
Verification: (1) The process of: evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (2) Formal proof of program correctness (e.g., requirements, design, implementation reviews, system tests) (24765:2010(E), 2010).
Acronyms
| Acronym | Description |
|---|---|
| ANL | Argonne National Laboratory |
| API | Application Programming Interface |
| CAD | Computer Aided Design |
| CFD | Computational Fluid Dynamics |
| DOE | Department of Energy |
| FE | finite element |
| HIT | Hierarchical Input Text |
| HPC | High Performance Computing |
| I/O | Input/Output |
| INL | Idaho National Laboratory |
| MOOSE | Multiphysics Object Oriented Simulation Environment |
| MPI | Message Passing Interface |
| SDD | Software Design Description |
Design Stakeholders and Concerns
Design Stakeholders
Stakeholders for Cardinal include several of the funding sources including DOE, INL, and Argonne National Laboratory (ANL). However, since Cardinal is an open-source project, several universities, companies, and foreign governments have an interest in the development and maintenance of the Cardinal project.
Stakeholder Design Concerns
Concerns from many of the stakeholders are similar. These concerns include correctness, stability, and performance. The mitigation plan for each of these can be addressed. For correctness, Cardinal development requires either regression or unit testing for all new code added to the repository. The project contains several comparisons against analytical solutions where possible and also other verification methods such as MMS. For stability, Cardinal maintains multiple branches to incorporate several layers of testing both internally and for dependent applications. Finally, performance tests are also performed as part of the the normal testing suite to monitor code change impacts to performance.
System Design
Cardinal relies on OpenMC to solve for neutron-photon transport (optionally on Computer Aided Design (CAD) geometries by relying on DAGMC). Cardinal also relies on NekRS to solve for fluid flow, heat transfer, and species transport. Cardinal integrates these external libraries within the structure of a MOOSE application, allowing these external libraries to be coupled to existing capabilities and interfaces in the MOOSE framework, such as for physics modeling (e.g., with the MOOSE modules or with other MOOSE applications) or data processing. Because Cardinal is based upon MOOSE, it employs the same concept of modular code objects that define all aspects of the solutions for physics. Cardinal provides specialized
- AuxKernels classes that extract internal solution fields in NekRS and OpenMC - Controls classes that modify NekRS and OpenMC simulations on-the-fly - Mesh classes to build the NekRS and OpenMC geometries in a MOOSE-compatible format, and modify existing meshes useful for postprocessing NekRS and OpenMC simulations - Postprocessors classes that query the NekRS and OpenMC simulations at points, through spatial integrals, etc. - Problem classes to execute NekRS and OpenMC as MOOSE applications and facilitate data transfer - TimeStepper classes to control time stepping based on NekRS's adaptive time stepping routines - UserObjects classes that spatially process the NekRS and OpenMC simulations
Cardinal also provides custom syntax for creating OpenMC tallies needed for multiphysics.
System Structure
Cardinal relies on the MOOSE framework to provide the core functionality of solving multiphysics problems. Cardinal replaces the actual physics solves with external API calls to OpenMC and NekRS, but relies on MOOSE for timestepping, synchronization, data transfers, and overall parallelization. Additional physics needed beyond OpenMC and NekRS are obtained from the MOOSE modules.
A summary listing of the current modules required for complete Cardinal operation are shown below:
Cardinal's Makefile also includes other modules which are by default enabled, due to their common usage with Cardinal (though they are not strictly required).
The structure of Cardinal is based on defining C++ classes that derive from classes in the MOOSE framework or modules that provide functionality that is specifically tailored to nuclear modeling and simulation. By using the interfaces defined in MOOSE base classes for these classes, Cardinal is able to rely on MOOSE to execute these models at the appropriate times during the simulation and use their results in the desired ways.
Data Design and Control
At a high level, the system is designed to process HIT input files to construct several objects that will constitute an FE simulation. Some of the objects in the simulation may in turn load other file-based resources to complete the simulation. Examples include meshes or data files. The system will then assemble systems of equations and solve them using the libraries of the Code Platform. The system can then output the solution in one or more supported output formats commonly used for visualization.
Human-Machine Interface Design
The Cardinal application is a command-line driven program. All interaction with Cardinal is ultimately done through the command line. This is typical for HPC applications that use the MPI interface for running on super computing clusters. Optional GUIs may be used to assist in creating input files and launching executables on the command line.
System Design Interface
All external system interaction is performed either through file I/O or through local API calls. Neither Cardinal, nor the MOOSE framework, nor the MOOSE modules are designed to interact with any external system directly through remote procedure calls. Any code to code coupling performed using the framework are done directly through API calls either in a static binary or after loading shared libraries.
Security Structure
The Cardinal application does not require any elevated privileges to operate and does not run any stateful services, daemons or other network programs. Distributed runs rely on the MPI library.
Requirements Cross-Reference
- cardinal: HeatTransferCoefficientAux
- 1.1.2The system shall compute a convective heat transfer coefficient using userobjects for the wall heat flux, wall temperature, and bulk temperature.
Specification(s): h
Design: HeatTransferCoefficientAux
Issue(s): #1081
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekRSProblem
- 1.3.7A coupled MOOSE-nekRS pincell-fluid flow problem shall predict correct conservation of energy and realistic thermal solutions. Exact conservation of energy (based on the power imposed in the solid) will not be observed because some heat flux GLL points are also on Dirichlet boundaries, which win in boundary condition ties.
Specification(s): sfr_pincell
Design: NekRSProblem
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.3.8Individually conserving heat flux sideset by sideset shall give equivalent results to the all-combined option when there is just one coupling sideset. The gold file for this test is identical to that for the sfr_pincell case.
Specification(s): sfr_pincell_vpp
Design: NekRSProblem
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.3.9The system shall allow imposing heat flux through a dummy main application, instead of coupling NekRS via conjugate heat transfer. This is verified by computing the heat flux on the NekRS mesh, which adequately matches an initial value set in a postprocessor. This gold file is also identical to that obtained by running a dummy main app (solid_dummy) that passes in the desired flux_integral initial condition.
Specification(s): impose_heat_flux
Design: NekRSProblem
Issue(s): #797
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: BoratedWater
- 1.6.1The system shall error if an invalid minimum boron ppm is provided.
Specification(s): negative_min
Design: BoratedWater
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.2The system shall error if an invalid maximum boron ppm is provided.
Specification(s): non_dilute
Design: BoratedWater
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.3The system shall warn the user if nuclides will be erased by the borated water criticality search. This test covers both non-H,B,O elements as well as non-natural isotopes of these elements.
Specification(s): warn_nuclides
Design: BoratedWater
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.4The system shall warn the user if they are omitting a nuclide from their cross section library which is irrelevant for boric acid control.
Specification(s): absent_nuclides
Design: BoratedWater
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.5The system shall perform a criticality search based on boron weight ppm in water. This test changes the water density and then searches for a criticality point; the resulting ppm is compared to a standalone OpenMC model (the comparison is done when running with many more particles for both scenarios). The multiplication factors agree within statistics. Due to floating point non-determinism, the actual test only compares that k matches unity within the desired convergence tolerance.
Specification(s): borated_water
Design: BoratedWater
Issue(s): #1158
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: AddCriticalitySearchAction
- 1.6.6The system shall error if a criticality search is not paired with the correct problem class.
Specification(s): wrong_problem
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.7The system shall error if invalid values are provided for the range of values to consider for the criticality search.
Specification(s): min_max
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.8The system shall warn if the selected tolerance might cause failure to converge due to high statistical noise.
Specification(s): too_tight_tolerance
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.9The system shall error if the criticality search does not converge.
Specification(s): fail_converge
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.10The system shall conduct a criticality search based on material density. This test is created by running a criticality search with a high particle count (1-sigma less than 10 pcm on k) and comparing the critical search result against a standalone OpenMC simulation which is run at the identified critical value of material density. The two approaches match within statistics. Due to floating point non-determinism, the actual test just checks that k converges to the target within the desired tolerance.
Specification(s): search
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.6.11The system shall conduct a criticality search with a non-unity target k. This test is created by running a criticality search with a high particle count (1-sigma less than 10 pcm on k) and comparing the critical search result against a standalone OpenMC simulation which is run at the identified critical value of material density. The two approaches match within statistics. Due to floating point non-determinism, the actual test just checks that k converges to the target within the desired tolerance.
Specification(s): search_with_target
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.6.12The system shall error if an invalid minimum density is provided.
Specification(s): negative_min
Design: AddCriticalitySearchAction
Issue(s): #1158
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: RotationSearch
- 1.6.13The system shall error if the minmum search value passed to a RotationSearch is negative.
Specification(s): bad_lower_bound
Design: RotationSearch
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.14The system shall error if the maximum search value passed to a RotationSearch is greater than 360 degrees.
Specification(s): bad_upper_bound
Design: RotationSearch
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.6.15The system shall conduct a criticality search by modifying a cell rotation. This test is created by running a criticality search with a high particle count (1-sigma less than 10 pcm on k) and comparing the critical search result against a standalone OpenMC simulation which is run at the identified critical value of material density. The two approaches match within statistics. Due to floating point non-determinism, the actual test just checks that k converges to the target within the desired tolerance.
Specification(s): rotation_search
Design: RotationSearch
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.6.16The system shall correctly remap MOOSE mesh elements and OpenMC cells on each step of a rotation criticality search. This ensures tallies are extracted properly and feedback is applied correctly. This test checks to see if the cell IDs are rotated correctly by point sampling a single element. This is more robust than checking kappa_fission from a cell tally as criticality searches are somewhat non-deterministic on CIVET.
Specification(s): with_coupling
Design: RotationSearch
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.6.17The system shall error if the user disables tallies and does not request a critical state calculation.
Specification(s): disable_tallying_and_critical_calc
Design: RotationSearch
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: BooleanComboMarker
- 1.10.1The system shall be able to prioritize refinement while ANDing markers together.
Specification(s): prioritize_refine_and
Design: BooleanComboMarker
Issue(s): #1025
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.10.2The system shall be able to prioritize coarsening while ANDing markers together.
Specification(s): prioritize_coarsen_and
Design: BooleanComboMarker
Issue(s): #1025
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.10.3The system shall be able to prioritize refinement while ORing markers together.
Specification(s): prioritize_refine_or
Design: BooleanComboMarker
Issue(s): #1025
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.10.4The system shall be able to prioritize coarsening while ORing markers together.
Specification(s): prioritize_coarsen_or
Design: BooleanComboMarker
Issue(s): #1025
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: MeshTally
- 1.21.1The system shall allow problems which contain adaptivity on the mesh mirror for cell tallies.
Specification(s): adaptive_cell
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.2The system shall allow problems which contain adaptivity on the mesh mirror for mesh tallies.
Specification(s): adaptive_mesh
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.3The system shall error if adaptivity is active and tallying on a mesh template instead of the mesh block.
Specification(s): adaptive_mesh_template
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.4The system shall error if adaptivity is active and a relaxation scheme is requested.
Specification(s): adaptive_relaxation
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.5The system shall skip running OpenMC when the mesh is unchanged by adaptivity.
Specification(s): skip_openmc_unchanged
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.6The system shall run OpenMC on the first Picard iteration regardless of the mesh being previouslyunchanged by adaptivity. This test relies on noise in the solution; if OpenMC runs more than onceper Picard iteration the PRNG seed changes and so the tally results will be different.
Specification(s): skip_openmc_unchanged_picard
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.21The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to both (i) a CSG-equivalent version of the geometry and (ii) the same input file run with the skinner disabled. The CSG file used for comparison is in the csg_step_1 directory.
Specification(s): null_skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.22The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.23The system shall give identical Monte Carlo solution (direct mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin_direct
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.24The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory. For this case, a bin is split across disjoint elements.
Specification(s): disjoint_bins
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.25The system shall scale a mesh by multiplying by 100.
Specification(s): scale_mesh
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.26The system shall give identical results when scaling the Mesh by an arbitrary multiplier. The gold file was compared against a case with no scaling (scaling = 1) to get identical results.
Specification(s): with_scaling
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.27The system shall allow for the use of relaxation with a MeshTally and a MoabSkinner.
Specification(s): mesh_tally_relaxation_skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.179The system shall be capable of block restricting CellTally variables.
Specification(s): block_restrict_cell
Issue(s): #1195
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.217The system shall allow a mesh tally for coupling OpenMC, without any physics feedback.
Specification(s): no_coupling
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.218The heat source shall be tallied on an unstructured mesh and normalized against a local tally when a single mesh is used.
Specification(s): one_mesh
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.219This test is nearly identical to one_mesh. The difference lies in having no mesh_template in the input file. Without one, the system should be able to directly tally on a moose mesh instead of a file
Specification(s): one_mesh_no_input_file
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.220The system shall error if attempting to directly tally on a MOOSE mesh that is distributed, since all meshes are always replicated in OpenMC.
Specification(s): moose_mesh_tally_distributed
Design: MeshTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.221The system shall allow users to use a mesh tally based on the mesh mirror with scaling. The gold file contains relative errors for an unscaled version of the test. The test itself scales the mesh down in the mesh block, and scales it back up with 'scaling'. If 'scaling' is not applied to the mesh mirror, the relative errors will change due to the difference in element volumes. The min/max values in the gold files are manually converted from W/cm3 (no scaling) to W/m3 (scaled).
Specification(s): scaling
Design: MeshTally
Issue(s): #1246
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.222The heat source shall be tallied on an unstructured mesh and normalized against a global tally when a single mesh is used. This test was run with successively finer meshes (from 256 elements to 94k elements) to show that the power of the mesh tally approaches the value of a cell tally as the difference in volume decreases.
Specification(s): one_mesh_global
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.223Mesh tallies shall allow for block restrictions to be applied.
Specification(s): block_restrict
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.224The heat source shall be tallied on an unstructured mesh and normalized against a local tally when multiple identical meshes are used.
Specification(s): multiple_meshes
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.225The heat source shall be tallied on an unstructured mesh and normalized against a global tally when multiple identical meshes are used. This test was run with successively finer meshes (from 256 elements to 94k elements) to show that the power of the mesh tally approaches the value of a cell tally as the difference in volume decreases.
Specification(s): multiple_meshes_global
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.226The heat source shall be correctly projected onto a Mesh in units of meters when the tally mesh template is in units of centimeters.
Specification(s): different_units
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.227The heat source shall be correctly projected onto a Mesh in units of meters when the tally mesh template and translations are in units of centimeters. The output was compared against the multiple_meshes case, which used an input entirely specified in terms of centimeters.
Specification(s): different_units_and_translations
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.228The fission tally standard deviation shall be output correctly for unstructured mesh tallies.
Specification(s): fission_tally_std_dev
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.229Mesh tallies shall temporarily require disabled renumbering until capability is available
Specification(s): disable_renumbering
Design: MeshTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.230Mesh tallies shall error if the user attempts to apply a block restriction when using a mesh template.
Specification(s): file_mesh_block_restrict
Design: MeshTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.231Mesh tallies shall error if the user attempts to apply a block restriction with no blocks.
Specification(s): block_restrict_no_blocks
Design: MeshTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.301A unity relaxation factor shall be equivalent to an unrelaxed case with globally-normalized mesh tallies.
Specification(s): global_without_alignment_unity_relax
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.302The wrapping shall apply constant relaxation for a case with globally-normalized mesh tallies. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc.i run (without any additional command line parameters).
Specification(s): global_without_alignment_relax
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.303The system shall correctly re-initialize the same mapping when the MooseMesh does not change during a simulation.
Specification(s): none_fixed_mesh
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.304A unity relaxation factor shall be equivalent to an unrelaxed case with locally-normalized mesh tallies.
Specification(s): local_without_alignment_unity_relax
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.305The wrapping shall apply constant relaxation for a case with locally-normalized mesh tallies. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc.i run with normalize_by_global_tally=false.
Specification(s): local_without_alignment_relax
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.306The wrapping shall allow output of the unrelaxed heat source for mesh tallies
Specification(s): output_fission_tally_mesh
Design: MeshTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.327The system shall correctly label elements in blocks which don't contain temperature feedback, density feedback, or a cell tally as unmapped.
Specification(s): cell_tally_unmapped
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.328The system shall correctly normalize local tallies with different estimators using multiple global tallies.
Specification(s): multi_global_estimator
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.329The system shall correctly apply and normalize two different CellTally objects with different scores. The gold file was generated using an input that had a single CellTally with multiple scores.
Specification(s): multiple_tallies_cell
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.330The system shall correctly apply and normalize two different MeshTally objects with different scores. The gold file was generated using an input that had a single MeshTally with multiple scores.
Specification(s): multiple_tallies_mesh
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.331The system shall correctly apply and normalize two different CellTally objects with different scores and triggers. The gold file was generated using an input that had a single CellTally with multiple scores and triggers.
Specification(s): multiple_tallies_cell_triggers
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.332The system shall correctly apply and normalize two different MeshTally objects with different scores and triggers. The gold file was generated using an input that had a single MeshTally with multiple scores and triggers.
Specification(s): multiple_tallies_mesh_triggers
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.333The system shall correctly apply and normalize two different CellTally objects with different scores when using relaxation. The gold file was generated using an input that had a single CellTally with multiple scores when using relaxation.
Specification(s): multiple_tallies_cell_relax
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.334The system shall correctly apply and normalize two different MeshTally objects with different scores when using relaxation. The gold file was generated using an input that had a single MeshTally with multiple scores when using relaxation.
Specification(s): multiple_tallies_mesh_relax
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.335The system shall error if more than one tally is provided and the requested heating score is in none of the tallies.
Specification(s): multi_no_norm
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.336The system shall allow calculations with multiple different tallies.
Specification(s): multiple_different_tallies
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.337The system shall allow calculations with multiple different tally outputs.
Specification(s): multiple_different_outputs
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.338The system shall allow multiple tallies to use the same scores.
Specification(s): same_scores
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.339The system shall error if two tallies score the normalization score and the user does not specify which to use for normalization.
Specification(s): two_kf_unspecified_norm
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.340The system shall error if two tallies scoring the same score add the same variable names.
Specification(s): duplicate_names
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.341The system shall error if attempting to use separate tallies when adding two tallies with the same score.
Specification(s): duplicate_scores_separate_tallies
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: OpenMCCellAverageProblem
- 1.21.1The system shall allow problems which contain adaptivity on the mesh mirror for cell tallies.
Specification(s): adaptive_cell
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.2The system shall allow problems which contain adaptivity on the mesh mirror for mesh tallies.
Specification(s): adaptive_mesh
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.3The system shall error if adaptivity is active and tallying on a mesh template instead of the mesh block.
Specification(s): adaptive_mesh_template
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.4The system shall error if adaptivity is active and a relaxation scheme is requested.
Specification(s): adaptive_relaxation
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.5The system shall skip running OpenMC when the mesh is unchanged by adaptivity.
Specification(s): skip_openmc_unchanged
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.6The system shall run OpenMC on the first Picard iteration regardless of the mesh being previouslyunchanged by adaptivity. This test relies on noise in the solution; if OpenMC runs more than onceper Picard iteration the PRNG seed changes and so the tally results will be different.
Specification(s): skip_openmc_unchanged_picard
Design: MeshTally OpenMCCellAverageProblem
Issue(s): #1054
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.7The system shall error if attempting to use an axisymmetric mesh mirror because MOOSE's element volume functions only return areas for axisymmetric.
Specification(s): error
Design: OpenMCCellAverageProblem
Issue(s): #1222
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.8The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to both (i) a CSG-equivalent version of the geometry and (ii) the same input file run with the skinner disabled. The CSG file used for comparison is in the csg_step_1 directory.
Specification(s): null_skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.9The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.10The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning with a single density bin when compared to a case without any density skinning at all.
Specification(s): skin_null_density
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.11The system shall scale a mesh by multiplying by 100.
Specification(s): scale_mesh
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.12The system shall give identical results when scaling the Mesh by an arbitrary multiplier. The gold file was compared against a case with no scaling (scaling = 1) to get identical results.
Specification(s): with_scaling
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.13The system shall warn the user when there is a mismatch between the mesh mirror and the initial OpenMC DAGMC geometry.
Specification(s): unmapped_cells
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.14
Specification(s): cell_tally_relaxation_skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.15The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning by density as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.16The system shall give identical Monte Carlo solution when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory. For this case, a bin is split across disjoint elements.
Specification(s): disjoint_bins
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.17The system shall error if attempting to apply density skinning without any fluid blocks ready to receive variable density.
Specification(s): cannot_skin_solid
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.18The system shall assign a material to the implicit complement region when skinning as compared to a CSG-equivalent version of the geometry, which is in /csg_equivalent directory. The result for k is within statistics of the CSG equivalent.
Specification(s): add_implicit_complement
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.19The system shall assign a material to the implicit complement region when skinning when there is no graveyard as compared to a CSG-equivalent version of the geometry which is in /csg_equivalent directory. The implicit complement region in this model exists as the space between the mesh geometry and an enclosing CSG cell. Results agree within statistics to the CSG reference.
Specification(s): no_graveyard_implicit_complement
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.20The system shall error if there is an obvious mismatch between the Mesh and DAGMC model for the case where the number of DAGMC materials which map to each Mesh subdomain do not match.
Specification(s): mismatch
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.21The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to both (i) a CSG-equivalent version of the geometry and (ii) the same input file run with the skinner disabled. The CSG file used for comparison is in the csg_step_1 directory.
Specification(s): null_skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.22The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.23The system shall give identical Monte Carlo solution (direct mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin_direct
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.24The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory. For this case, a bin is split across disjoint elements.
Specification(s): disjoint_bins
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.25The system shall scale a mesh by multiplying by 100.
Specification(s): scale_mesh
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.26The system shall give identical results when scaling the Mesh by an arbitrary multiplier. The gold file was compared against a case with no scaling (scaling = 1) to get identical results.
Specification(s): with_scaling
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.27The system shall allow for the use of relaxation with a MeshTally and a MoabSkinner.
Specification(s): mesh_tally_relaxation_skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.28The system shall error if the skinner user object is not the correct type
Specification(s): wrong_uo
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.29The system shall warn if the graveyard is missing for OpenMC skinned models
Specification(s): missing_graveyard
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.30The system shall error if applying a symmetry mapping to an OpenMC model which must already exactly match the mesh.
Specification(s): no_symmetry
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.31The system shall error if loading properties from HDF5 for skinned problems
Specification(s): properties
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.32The system shall error if the cell containing the DAGMC universe is not contained in the root universe. If so, we cannot guarantee that the DAGMC geometry is not replicated and the skinner may produce an incorrect skin.
Specification(s): dag_cell_not_root
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.33The system shall error if the DAGMC universe is used as a lattice element. If so, the DAGMC geometry may be replicated and so the skinner may produce an incorrect skin.
Specification(s): dag_in_lattice
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.34The system shall error if the DAGMC universe is used as a lattice element. If so, the DAGMC geometry may be replicated and so the skinner may produce an incorrect skin.
Specification(s): dag_lattice_outer
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.35The system shall error if the user attempts to map both CSG and DAGMC geometry to the MOOSE mesh.
Specification(s): csg_with_dag_feedback
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.36The system shall error if the DAGMC universe is used by multiple cells. If so, the DAGMC geometry is replicated and so the skinner will produce an incorrect skin.
Specification(s): multi_dag_uni_cells
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.37The system shall error if there are more than one DAGMC universe. If so, the universe to skin cannot be automatically determined.
Specification(s): multi_dag_uni
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.38The system shall allow for the use of CSG and DAGMC geometry when using the MoabSkinner.
Specification(s): allows_csg_with_skinner
Design: MoabSkinnerOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.39The system shall allow a material to be specified both in a cell with density feedback and a cell without density feedback. The gold file for this test was generated with a duplicated material of the feedback cell fill in the respective non-feedback cell.
Specification(s): allow_mat_diff_cell
Design: OpenMCCellAverageProblem
Issue(s): #1197
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.44The system shall allow density feedback in OpenMC models per cell without requiring unique cell materials. This model was compared against a model with unique materials per cell.
Specification(s): pincell
Design: OpenMCCellAverageProblem
Issue(s): #1197
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.209The system shall be able to compute IFP quantities on changing geometries.
Specification(s): ifp_changing
Design: OpenMCCellAverageProblem
Issue(s): #1235
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.210The system shall error if the problem attempts to enable IFP calculations when running in fixed source mode.
Specification(s): non_k_eig
Design: OpenMCCellAverageProblem
Issue(s): #1104
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.211The system shall be able to calculate neutron kinetics parameters.
Specification(s): compute_both
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.212The system shall be able to calculate separate values of beta_eff for each delayed group in the ENDF delayed group structure.
Specification(s): six_group_beta
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.213The system shall error if the problem does not enable IFP calculations and attempts to add an LambdaEffective post processor.
Specification(s): no_ifp_lambda
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.214The system shall error if the problem does not enable IFP calculations and attempts to add a BetaEffective post processor.
Specification(s): no_ifp_beta
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.215The system shall error if the problem does not enable IFP calculations and attempts to add a BetaEffective post processor.
Specification(s): more_ifp_gen_then_inactive
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.232The system shall support nearest temperature interpolation when running in multi-group mode.
Specification(s): nearest
Design: OpenMCCellAverageProblem
Issue(s): #1292
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.233The system shall support linear temperature interpolation when running in multi-group mode.
Specification(s): interpolation
Design: OpenMCCellAverageProblem
Issue(s): #1292
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.234The system shall solve the linear feedback Doppler slab problem with nearest temperature interpolation when running OpenMC's random ray solver.
Specification(s): nearest
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.235The system shall solve the linear feedback Doppler slab problem with linear temperature interpolation when running OpenMC's random ray solver.
Specification(s): interpolation
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.236The system shall solve the inverse square root feedback Doppler slab problem, where cross section feedback is applied as density feedback instead of using MGXS temperature interpolation tables.
Specification(s): doppler_density
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.237The system shall be capable of solving the S2 thermal expansion benchmark problem with OpenMC's random ray solver.
Specification(s): s2_thermal_exp
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.238The system shall support void regions when running in multi-group mode.
Specification(s): nearest
Design: OpenMCCellAverageProblem
Issue(s): #1317
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.239The system shall warn the user if there is an inconsistency between a moving mesh and the underlying OpenMC geometry.
Specification(s): inconsistency
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.240The system shall correctly reinitialize cell tallies when the mesh is moving. This is tested by translating the mesh over a stationary OpenMC model. The two cell tallies in the tallies.out file match the expected power density (accounting for the actual fractions of the cell which map to the moving mesh). This test also checks the cell IDs and instances as the mesh translates.
Specification(s): cell_tally
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.241The system shall correctly use a mesh tally on a moving MOOSE mesh. This is tested by translating the mesh over a stationary OpenMC model. The mesh translation exposes 20 percent of the left subdomain, which from a non-moving case we record 8 percent of the total power deposition in this region. For the moving mesh case, the total power deposited in the mesh tally is 92 percent.
Specification(s): mesh_tally
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.242The system shall generate a file for mesh tallies.
Specification(s): make_mesh
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.243The system shall error if tallying on a file mesh for moving mesh cases, because there will be a disagreement between the mesh elements and the Mesh.
Specification(s): file_mesh
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.244The system shall correctly reinitialize temperature mapping and output of cell temperatures to a moving mesh. This is tested by applying temperatures based on the moving mesh.
Specification(s): temperature
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.245The system shall correctly reinitialize density mapping and output of cell densities and material fills to a moving mesh. This is tested by applying densities based on the moving mesh.
Specification(s): density
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.246The system shall correctly reinitialize volume calculations for a moving mesh. This is tested by comparing the OpenMC stochastic volume calculation against postprocessors for changing volumes.
Specification(s): volumes
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.247The system shall change the OpenMC mesh geometry on-the-fly. This is tested by running this case with a very high number of particles and batches, to compare against the CSG case in the reference folder. The reference case is a CSG model created at the deformed state. We cannot match these cases perfectly because we cannot control the seed of the second Picard iteration. The reference case gives k = 0.88782 plus or minus 5 pcm, and our Cardinal case gives 0.88786 plus of minus 5 pcm; these agree within 1 sigma.
Specification(s): scale
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.248A statepoint file must be written when the batches parameter matches the batches in settings.xml and they are both specified.
Specification(s): check_statepoint_exists
Design: OpenMCCellAverageProblem
Issue(s): #1261
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.21.258The system shall support density feedback to OpenMC's random ray solver for the case when only density feedback blocks are provided. This test was verified with a standalone OpenMC simulation where distributed cell densities were set in the Python API. The k-eff and standard deviations matched exactly.
Specification(s): density_feedback
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.259The system shall support density feedback to OpenMC's random ray solver for the case when only density feedback blocks and variables are provided. This test was verified with a standalone OpenMC simulation where distributed cell densities were set in the Python API. The k-eff and standard deviations matched exactly.
Specification(s): density_feedback_two_var
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.260The system shall warn the user if a single MGXS reference density maps to multiple OpenMC materials.
Specification(s): reference_density_mult_mat
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.261The system shall error if the user requests a combined estimator when running in random ray mode.
Specification(s): err_k_combined
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.262The system shall error if the user provides more reference densities then density blocks/variables.
Specification(s): err_mismatching_reference_densities
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.263The system shall error if the user requests the calculation of kinetics parameters when running in random ray mode.
Specification(s): err_ifp
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.264The system shall error if the user adds a MeshTally when running in random ray mode.
Specification(s): err_mesh_tally
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.265The system shall error if the user requests flux volume normalization in their OpenMC model. This prevents a double-divide by volume, which Cardinal cannot recover due to the random ray volume estimations being cleared after tallies are extracted.
Specification(s): err_volume_norm
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.266The system shall error if the user provides a score to a tally that is not supported by OpenMC's random ray solver.
Specification(s): invalid_scores
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.267The system shall error if the user requests a collision estimator for a tally.
Specification(s): err_tally_collision
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.268The system shall error if the user adds an AngularLegendreFilter when running the random ray solver.
Specification(s): err_angular_legendre
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.269The system shall error if the user adds an AzimuthalAngleFilter when running the random ray solver.
Specification(s): err_azimuthal
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.270The system shall error if the user adds an DelayedGroupFilter when running the random ray solver.
Specification(s): err_delayed
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.271The system shall error if the user adds an EnergyOutFilter when running the random ray solver.
Specification(s): err_e_out
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.272The system shall error if the user adds an SphericalHarmonicsFilter when running the random ray solver.
Specification(s): err_sph
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.273The system shall error if the user adds an PolarAngleFilter when running the random ray solver.
Specification(s): err_polar
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.274The system shall error if the user adds an FromXMLFilter when running the random ray solver.
Specification(s): err_xml
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.275The system shall error if the user adds an ParticleFilter when running the random ray solver.
Specification(s): err_particle
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.276The system shall error if the user adds an OpenMCTallyEditor when running the random ray solver.
Specification(s): err_tally_editor
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.277The system shall error if the user adds an OpenMCNuclideDensities when running the random ray solver.
Specification(s): err_density_editor
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.278The system shall error if the user adds an OpenMCDomainFilterEditor when running the random ray solver.
Specification(s): err_filter_editor
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.279The system shall error if the user adds a BoratedWater criticality search when running the random ray solver.
Specification(s): err_borated_water
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.280The system shall properly normalize scores when running the random ray solver in fixed source mode. Tallies obtained from a standalone OpenMC random ray simulation were normalized manually and confirmed to match the Cardinal tallies on the MOOSE mesh.
Specification(s): random_ray_fs
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.281The system shall properly normalize scores when running the random ray solver in eigenvalue mode. Tallies obtained from a standalone OpenMC random ray simulation were normalized manually and confirmed to match the Cardinal tallies on the MOOSE mesh.
Specification(s): random_ray_eigen
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.282The system shall allow the user to control the random ray inactive length.
Specification(s): inactive_length
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.283The system shall allow the user to control the random ray active length.
Specification(s): active_length
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.284The system shall allow for global tally normalization through the use of a universe filter.
Specification(s): global_norm
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.285The system shall support temperature feedback to OpenMC's random ray solver with linear interpolation. A standalone calculation was performed where distributed cell temperatures were set with the OpenMC Python API. k-eff and its standard deviation were compared between the standalone calculation and the Cardinal result, and found to be in perfect agreement.
Specification(s): temp_interp
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.286The system shall support temperature feedback to OpenMC's random ray solver with nearest interpolation. A standalone calculation was performed where distributed cell temperatures were set with the OpenMC Python API. k-eff and its standard deviation were compared between the standalone calculation and the Cardinal result, and found to be in perfect agreement.
Specification(s): temp_nearest
Design: OpenMCCellAverageProblem
Issue(s): #1273
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: MoabSkinner
- 1.21.8The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to both (i) a CSG-equivalent version of the geometry and (ii) the same input file run with the skinner disabled. The CSG file used for comparison is in the csg_step_1 directory.
Specification(s): null_skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.9The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.10The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning with a single density bin when compared to a case without any density skinning at all.
Specification(s): skin_null_density
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.11The system shall scale a mesh by multiplying by 100.
Specification(s): scale_mesh
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.12The system shall give identical results when scaling the Mesh by an arbitrary multiplier. The gold file was compared against a case with no scaling (scaling = 1) to get identical results.
Specification(s): with_scaling
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.13The system shall warn the user when there is a mismatch between the mesh mirror and the initial OpenMC DAGMC geometry.
Specification(s): unmapped_cells
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.14
Specification(s): cell_tally_relaxation_skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.15The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning by density as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.16The system shall give identical Monte Carlo solution when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory. For this case, a bin is split across disjoint elements.
Specification(s): disjoint_bins
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.17The system shall error if attempting to apply density skinning without any fluid blocks ready to receive variable density.
Specification(s): cannot_skin_solid
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.18The system shall assign a material to the implicit complement region when skinning as compared to a CSG-equivalent version of the geometry, which is in /csg_equivalent directory. The result for k is within statistics of the CSG equivalent.
Specification(s): add_implicit_complement
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.19The system shall assign a material to the implicit complement region when skinning when there is no graveyard as compared to a CSG-equivalent version of the geometry which is in /csg_equivalent directory. The implicit complement region in this model exists as the space between the mesh geometry and an enclosing CSG cell. Results agree within statistics to the CSG reference.
Specification(s): no_graveyard_implicit_complement
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.20The system shall error if there is an obvious mismatch between the Mesh and DAGMC model for the case where the number of DAGMC materials which map to each Mesh subdomain do not match.
Specification(s): mismatch
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.21The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to both (i) a CSG-equivalent version of the geometry and (ii) the same input file run with the skinner disabled. The CSG file used for comparison is in the csg_step_1 directory.
Specification(s): null_skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.22The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.23The system shall give identical Monte Carlo solution (direct mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin_direct
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.24The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory. For this case, a bin is split across disjoint elements.
Specification(s): disjoint_bins
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.25The system shall scale a mesh by multiplying by 100.
Specification(s): scale_mesh
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.26The system shall give identical results when scaling the Mesh by an arbitrary multiplier. The gold file was compared against a case with no scaling (scaling = 1) to get identical results.
Specification(s): with_scaling
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.27The system shall allow for the use of relaxation with a MeshTally and a MoabSkinner.
Specification(s): mesh_tally_relaxation_skin
Design: MoabSkinnerOpenMCCellAverageProblemMeshTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.28The system shall error if the skinner user object is not the correct type
Specification(s): wrong_uo
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.29The system shall warn if the graveyard is missing for OpenMC skinned models
Specification(s): missing_graveyard
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.30The system shall error if applying a symmetry mapping to an OpenMC model which must already exactly match the mesh.
Specification(s): no_symmetry
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.31The system shall error if loading properties from HDF5 for skinned problems
Specification(s): properties
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.32The system shall error if the cell containing the DAGMC universe is not contained in the root universe. If so, we cannot guarantee that the DAGMC geometry is not replicated and the skinner may produce an incorrect skin.
Specification(s): dag_cell_not_root
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.33The system shall error if the DAGMC universe is used as a lattice element. If so, the DAGMC geometry may be replicated and so the skinner may produce an incorrect skin.
Specification(s): dag_in_lattice
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.34The system shall error if the DAGMC universe is used as a lattice element. If so, the DAGMC geometry may be replicated and so the skinner may produce an incorrect skin.
Specification(s): dag_lattice_outer
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.35The system shall error if the user attempts to map both CSG and DAGMC geometry to the MOOSE mesh.
Specification(s): csg_with_dag_feedback
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.36The system shall error if the DAGMC universe is used by multiple cells. If so, the DAGMC geometry is replicated and so the skinner will produce an incorrect skin.
Specification(s): multi_dag_uni_cells
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.37The system shall error if there are more than one DAGMC universe. If so, the universe to skin cannot be automatically determined.
Specification(s): multi_dag_uni
Design: MoabSkinnerOpenMCCellAverageProblem
Issue(s): #1177
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.38The system shall allow for the use of CSG and DAGMC geometry when using the MoabSkinner.
Specification(s): allows_csg_with_skinner
Design: MoabSkinnerOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.239The system shall warn the user if there is an inconsistency between a moving mesh and the underlying OpenMC geometry.
Specification(s): inconsistency
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.240The system shall correctly reinitialize cell tallies when the mesh is moving. This is tested by translating the mesh over a stationary OpenMC model. The two cell tallies in the tallies.out file match the expected power density (accounting for the actual fractions of the cell which map to the moving mesh). This test also checks the cell IDs and instances as the mesh translates.
Specification(s): cell_tally
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.241The system shall correctly use a mesh tally on a moving MOOSE mesh. This is tested by translating the mesh over a stationary OpenMC model. The mesh translation exposes 20 percent of the left subdomain, which from a non-moving case we record 8 percent of the total power deposition in this region. For the moving mesh case, the total power deposited in the mesh tally is 92 percent.
Specification(s): mesh_tally
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.242The system shall generate a file for mesh tallies.
Specification(s): make_mesh
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.243The system shall error if tallying on a file mesh for moving mesh cases, because there will be a disagreement between the mesh elements and the Mesh.
Specification(s): file_mesh
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.244The system shall correctly reinitialize temperature mapping and output of cell temperatures to a moving mesh. This is tested by applying temperatures based on the moving mesh.
Specification(s): temperature
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.245The system shall correctly reinitialize density mapping and output of cell densities and material fills to a moving mesh. This is tested by applying densities based on the moving mesh.
Specification(s): density
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.246The system shall correctly reinitialize volume calculations for a moving mesh. This is tested by comparing the OpenMC stochastic volume calculation against postprocessors for changing volumes.
Specification(s): volumes
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.247The system shall change the OpenMC mesh geometry on-the-fly. This is tested by running this case with a very high number of particles and batches, to compare against the CSG case in the reference folder. The reference case is a CSG model created at the deformed state. We cannot match these cases perfectly because we cannot control the seed of the second Picard iteration. The reference case gives k = 0.88782 plus or minus 5 pcm, and our Cardinal case gives 0.88786 plus of minus 5 pcm; these agree within 1 sigma.
Specification(s): scale
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.28.31The system shall error if the maximum temperature is lower than the minimum temperature for the skinner bins
Specification(s): invalid_max_temp
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.32The system shall error if the maximum density is lower than the minimum density for the skinner bins
Specification(s): invalid_max_density
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.33The system shall error if the temperature is below the minimum bin bound
Specification(s): too_low_temp
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.34The system shall error if the temperature is above the maximum bin bound
Specification(s): too_high_temp
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.35The system shall error if the density is below the minimum bin bound
Specification(s): too_low_density
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.36The system shall error if the density is above the maximum bin bound
Specification(s): too_high_density
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.37The system shall error if the outer graveyard surface is not larger than the inner graveyard surface
Specification(s): invalid_graveyard_scales
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.38The system shall error if the specified temperature auxiliary variable cannot be found
Specification(s): no_aux_temp
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.39The system shall error if the specified density auxiliary variable cannot be found
Specification(s): no_aux_density
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.40The system shall error if the specified density and temperature auxiliary variables are the same
Specification(s): overlap_t_rho
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.41The system shall error if trying to run in distributed mesh mode
Specification(s): distributed
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.42The system shall error if the material_names provided to the skinner do not match the required length
Specification(s): incorrect_material_names
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.43The system shall bin elements according to temperature and density on an expanding mesh and be able to visualize the bins on the mesh volume.
Specification(s): bins
Design: MoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.44The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step0
Design: MoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.45The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step1
Design: MoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.46The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions
Specification(s): check_skins_step0
Design: MoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.47The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions after expansion with the correct displacements.
Specification(s): check_skins_step1
Design: MoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.48
Specification(s): graveyard
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.28.49The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.50The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions, with a graveyard region outside the original mesh.
Specification(s): check_skins
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.51The system shall bin hex mesh elements according to temperature and density, on multiple subdomains, and be able to visualize the bins on the mesh volume.
Specification(s): bins
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.52The system shall bin hex mesh elements according to temperature, on multiple subdomains, and be able to visualize the bins.
Specification(s): bins_without_density
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.53The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step0
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.54The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step1
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.55The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions from a hex mesh
Specification(s): check_skins_step0
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.56The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions. The bins shall be re-generated on each time step from a hex mesh.
Specification(s): check_skins_step1
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.57The system shall bin mixed HEX8 and PRISM6 mesh elements from the loaded mesh according to temperature and density, on multiple subdomains, and be able to visualize the bins on the mesh volume.
Specification(s): mixed_elements
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.58The system shall bin mixed HEX27 and PRISM18 mesh elements from the loaded mesh according to temperature and density, on multiple subdomains, and be able to visualize the bins on the mesh volume.
Specification(s): second_order
Design: MoabSkinner
Issue(s): #1352
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.59The system shall output the MOAB mesh copied from libMesh into the .h5m format
Specification(s): output_mesh
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.60The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.61The system shall properly convert from libMesh to MOAB meshes in-memory. We check this in a somewhat circuitous manner by writing the volume mesh, then converting it to gmsh, and finally re-reading it into MOOSE so that we can use the Exodiff utility.
Specification(s): check_volume0
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.62The system shall bin elements according to temperature and density, on multiple subdomains, and be able to visualize the bins on the mesh volume for second-order tets.
Specification(s): bins
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.63The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step0
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.64The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step1
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.65The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions for second-order tets
Specification(s): check_skins_step0
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.66The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions for second-order tets. The bins shall be re-generated on each time step.
Specification(s): check_skins_step1
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.67The system shall bin elements according to temperature and density, on multiple subdomains, and be able to visualize the bins on the mesh volume.
Specification(s): bins
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.68The system shall bin elements according to temperature, on multiple subdomains, and be able to visualize the bins.
Specification(s): bins_without_density
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.69The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step0
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.70The system shall be able to convert a .h5m file to gmsh
Specification(s): convert_to_gmsh_step1
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunCommand
- 1.28.71The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions
Specification(s): check_skins_step0
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.72The system shall properly skin a MOAB mesh and create new MOAB surface meshes bounding bin regions. The bins shall be re-generated on each time step.
Specification(s): check_skins_step1
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.73The system shall error if the requirements for a binning variable type are violated.
Specification(s): wrong_type
Design: MoabSkinner
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: CellTally
- 1.21.8The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to both (i) a CSG-equivalent version of the geometry and (ii) the same input file run with the skinner disabled. The CSG file used for comparison is in the csg_step_1 directory.
Specification(s): null_skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.9The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning as compared to a CSG-equivalent version of the geometry, which is in the csg_step_2 directory.
Specification(s): skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.10The system shall give identical Monte Carlo solution (file mesh tallies and k) when skinning with a single density bin when compared to a case without any density skinning at all.
Specification(s): skin_null_density
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.11The system shall scale a mesh by multiplying by 100.
Specification(s): scale_mesh
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.12The system shall give identical results when scaling the Mesh by an arbitrary multiplier. The gold file was compared against a case with no scaling (scaling = 1) to get identical results.
Specification(s): with_scaling
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.13The system shall warn the user when there is a mismatch between the mesh mirror and the initial OpenMC DAGMC geometry.
Specification(s): unmapped_cells
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.14
Specification(s): cell_tally_relaxation_skin
Design: MoabSkinnerOpenMCCellAverageProblemCellTally
Issue(s): #567
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.179The system shall be capable of block restricting CellTally variables.
Specification(s): block_restrict_cell
Issue(s): #1195
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.287A unity relaxation factor shall be equivalent to an unrelaxed case with globally-normalzed cell tallies on a model with perfect alignment between OpenMC model and the mesh mirror
Specification(s): global_with_alignment_unity_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.288The wrapping shall apply constant relaxation for a case with globally-normalized cell tallies with perfect alignment between the OpenMC model and the mesh mirror. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc.i run (without any command line parameter settings).
Specification(s): global_with_alignment_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.289The wrapping shall apply Robbins-Monro relaxation for a case with globally-normalized cell tallies with perfect alignment between the OpenMC model and the mesh mirror. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc.i run (without any command line parameter settings).
Specification(s): global_with_alignment_rm_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.290The wrapping shall apply Dufek-Gudowski relaxation for a case with globally-normalized cell tallies with perfect alignment between the OpenMC model and the mesh mirror. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the same input file, but with the relaxation part commented out in the source code (so that we can compare directly against runs that only differ by changing the number of particles.
Specification(s): global_with_alignment_dg_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.291A unity relaxation factor shall be equivalent to an unrelaxed case with locally-normalzed cell tallies on a model with perfect alignment between OpenMC model and the mesh mirror
Specification(s): local_with_alignment_unity_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.292The wrapping shall apply constant relaxation for a case with locally-normalized cell tallies with perfect alignment between the OpenMC model and the mesh mirror. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc.i case with normalize_by_global_tally=false.
Specification(s): local_with_alignment_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.293A unity relaxation factor shall be equivalent to an unrelaxed case with globally-normalzed cell tallies on a model with imperfect alignment between OpenMC model and the mesh mirror.
Specification(s): global_without_alignment_unity_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.294The wrapping shall apply constant relaxation for a case with globally-normalized cell tallies with imperfect alignment between the OpenMC model and the mesh mirror. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc_nonaligned.i case (without additional command line parameters)
Specification(s): global_without_alignment_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.295A unity relaxation factor shall be equivalent to an unrelaxed case with locally-normalzed cell tallies on a model with imperfect alignment between OpenMC model and the mesh mirror
Specification(s): local_without_alignment_unity_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.296The wrapping shall apply constant relaxation for a case with locally-normalized cell tallies with imperfect alignment between the OpenMC model and the mesh mirror. This test is verified by comparing the heat source computed via relaxation with the un-relaxed iterations from the openmc_nonaligned.i case with normalize_by_global_tally=false
Specification(s): local_without_alignment_relax
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.297The system shall correctly re-initialize the same mapping when the MooseMesh does not change during a simulation.
Specification(s): none_fixed_mesh
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.298The wrapping shall allow output of the unrelaxed heat source for cell tallies
Specification(s): output_fission_tally_cell
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.299The wrapping shall allow output of multiple tally scores, with relaxation applied independently to each score
Specification(s): multi_tally
Design: CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.300The system shall correctly error if trying to use relaxation with a time-varying mesh.
Specification(s): no_relax_with_fixed_mesh
Design: CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.327The system shall correctly label elements in blocks which don't contain temperature feedback, density feedback, or a cell tally as unmapped.
Specification(s): cell_tally_unmapped
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.328The system shall correctly normalize local tallies with different estimators using multiple global tallies.
Specification(s): multi_global_estimator
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.329The system shall correctly apply and normalize two different CellTally objects with different scores. The gold file was generated using an input that had a single CellTally with multiple scores.
Specification(s): multiple_tallies_cell
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.330The system shall correctly apply and normalize two different MeshTally objects with different scores. The gold file was generated using an input that had a single MeshTally with multiple scores.
Specification(s): multiple_tallies_mesh
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.331The system shall correctly apply and normalize two different CellTally objects with different scores and triggers. The gold file was generated using an input that had a single CellTally with multiple scores and triggers.
Specification(s): multiple_tallies_cell_triggers
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.332The system shall correctly apply and normalize two different MeshTally objects with different scores and triggers. The gold file was generated using an input that had a single MeshTally with multiple scores and triggers.
Specification(s): multiple_tallies_mesh_triggers
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.333The system shall correctly apply and normalize two different CellTally objects with different scores when using relaxation. The gold file was generated using an input that had a single CellTally with multiple scores when using relaxation.
Specification(s): multiple_tallies_cell_relax
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.334The system shall correctly apply and normalize two different MeshTally objects with different scores when using relaxation. The gold file was generated using an input that had a single MeshTally with multiple scores when using relaxation.
Specification(s): multiple_tallies_mesh_relax
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.335The system shall error if more than one tally is provided and the requested heating score is in none of the tallies.
Specification(s): multi_no_norm
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.336The system shall allow calculations with multiple different tallies.
Specification(s): multiple_different_tallies
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.337The system shall allow calculations with multiple different tally outputs.
Specification(s): multiple_different_outputs
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.338The system shall allow multiple tallies to use the same scores.
Specification(s): same_scores
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.339The system shall error if two tallies score the normalization score and the user does not specify which to use for normalization.
Specification(s): two_kf_unspecified_norm
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.340The system shall error if two tallies scoring the same score add the same variable names.
Specification(s): duplicate_names
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.341The system shall error if attempting to use separate tallies when adding two tallies with the same score.
Specification(s): duplicate_scores_separate_tallies
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: AzimuthalAngleFilter
- 1.21.94The system shall be capable of adding an AzimuthalAngleFilter to a CellTally with bins that are provided. This test also ensures the binned fluxes sum to the total flux through the use of global normalization.
Specification(s): azimuthal_cell_provided_bins
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.95The system shall be capable of adding an AzimuthalAngleFilter to a CellTally with equally spaced bins. This test also ensures the binned fluxes sum to the total flux through the use of global normalization.
Specification(s): azimuthal_cell_equally_spaced_bins
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.96The system shall be capable of adding an AzimuthalAngleFilter to a MeshTally.
Specification(s): azimuthal_mesh
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.97The system shall correctly compute azimuthal binned fluxes with mesh tallies such that the sum of the flux over each bin equals the total flux. The gold file was generated with an input file that scored the flux without a AzimuthalAngleFilter.
Specification(s): bin_sum
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.98The system shall error if 'azimuthal_angle_boundaries' doesn't contain enough boundaries to form bins.
Specification(s): not_enough_provided_bnds
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.99The system shall automatically sort bins to ensure they're monotonically increasing.
Specification(s): bnds_wrong_order
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.100The system shall error if neither 'num_equal_divisions' or 'azimuthal_angle_boundaries' are provided.
Specification(s): no_bins
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.101The system shall error if both 'num_equal_divisions' and 'azimuthal_angle_boundaries' are provided.
Specification(s): both_bins
Design: AzimuthalAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: DelayedGroupFilter
- 1.21.102The system shall be capable of adding a DelayedGroupFilter to delayed neutron scores.
Specification(s): delayed
Design: DelayedGroupFilter
Issue(s): #1207
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.103The system shall error if the use attempts to add a DelayedGroupFilter to a tally with non-delayed scores.
Specification(s): delayed_scores
Design: DelayedGroupFilter
Issue(s): #1207
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: EnergyFilter
- 1.21.104The system shall be capable of adding an EnergyFilter (with energy boundaries provided) to a CellTally. This test also ensures multi-group fluxes sum to the total flux for cell tallies.
Specification(s): energy_cell_bnds
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.105The system shall be capable of adding an EnergyFilter (with a group structure) to a CellTally. This test also ensures multi-group fluxes sum to the total flux for cell tallies.
Specification(s): energy_cell_structure
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.106The system shall be capable of adding an EnergyFilter to a MeshTally.
Specification(s): energy_mesh
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.107The system shall correctly compute multi-group fluxes with mesh tallies such that the sum of the flux over each group equals the total flux. The gold file was generated with an input file that scored the flux without an EnergyFilter.
Specification(s): group_sum
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.108The system shall error if there aren't enough energy boundaries to form an EnergyTally.
Specification(s): not_enough_bnds
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.109The system shall automatically sort bins to ensure they're monotonically increasing.
Specification(s): bnds_wrong_order
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.110The system shall error if no energy bins are provided.
Specification(s): missing_bins
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.111The system shall error if no energy bins are provided.
Specification(s): both_bins
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.112The system shall error if duplicate energy boundaries are provided.
Specification(s): duplicate_bnds
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.113The system shall error if negative energy boundaries are provided.
Specification(s): negative_bnds
Design: EnergyFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: EnergyOutFilter
- 1.21.114The system shall be capable of adding an EnergyOutFilter (with energy boundaries provided).
Specification(s): energy_cell_bnds
Design: EnergyOutFilter
Issue(s): #1094
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.115The system shall be capable of adding an EnergyOutFilter (with a group structure).
Specification(s): energy_cell_structure
Design: EnergyOutFilter
Issue(s): #1094
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.116The system shall error if the user attempts to use a non-analog estimator with an EnergyOutFilter.
Specification(s): force_analog
Design: EnergyOutFilter
Issue(s): #1094
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: AngularLegendreFilter
- 1.21.117The system shall support Legendre filters in the scattering angle.
Specification(s): legendre_l1
Design: AngularLegendreFilter
Issue(s): #1094
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.118The L0 Legendre moment in a L>0 Legendre expansion shall match the scattering reaction rate computed without a Legendre filter. This ensures that the L>0 Legendre moments are skipped during normalization.The gold file for this test was generated without a Legendre filter.
Specification(s): l0_in_l1_vs_no_legendre
Design: AngularLegendreFilter
Issue(s): #1094
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.119The system shall error if the user attempts to use a non-analog estimator with an AngularLegendreFilter.
Specification(s): force_analog
Design: AngularLegendreFilter
Issue(s): #1094
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: ParticleFilter
- 1.21.120The system shall be capable of adding a ParticleFilter for all particle types supported in OpenMC.
Specification(s): filter_particles
Design: ParticleFilter
Issue(s): #1094
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: PolarAngleFilter
- 1.21.121The system shall be capable of adding an PolarAngleFilter to a CellTally with bins that are provided. This test also ensures the binned fluxes sum to the total flux through the use of global normalization.
Specification(s): polar_cell_provided_bins
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.122The system shall be capable of adding an PolarAngleFilter to a CellTally with equally spaced bins. This test also ensures the binned fluxes sum to the total flux through the use of global normalization.
Specification(s): polar_cell_equally_spaced_bins
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.123The system shall be capable of adding an PolarAngleFilter to a MeshTally.
Specification(s): polar_mesh
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.124The system shall correctly compute polar binned fluxes with mesh tallies such that the sum of the flux over each bin equals the total flux. The gold file was generated with an input file that scored the flux without a PolarAngleFilter.
Specification(s): bin_sum
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.125The system shall error if 'polar_angle_boundaries' doesn't contain enough boundaries to form bins.
Specification(s): not_enough_provided_bnds
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.126The system shall automatically sort bins to ensure they're monotonically increasing.
Specification(s): bnds_wrong_order
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.127The system shall error if neither 'num_equal_divisions' or 'polar_angle_boundaries' are provided.
Specification(s): no_bins
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.128The system shall error if both 'num_equal_divisions' and 'polar_angle_boundaries' are provided.
Specification(s): both_bins
Design: PolarAngleFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: SphericalHarmonicsFilter
- 1.21.129The system shall support spherical harmonics filters.
Specification(s): sh_l1
Design: SphericalHarmonicsFilter
Issue(s): #1091
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.130The system shall support spherical harmonics filters composed with other filters.
Specification(s): sh_l1_mult
Design: SphericalHarmonicsFilter
Issue(s): #1091
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.131The L0 spherical harmonics moment in a L>0 SH expansion shall match the scalar fluxes computed without a spherical harmonics filter. This ensures that the L>0 SH moments are skipped during normalization.The gold file for this test was generated without a SH filter.
Specification(s): sh_l0_in_l1_vs_no_sh
Design: SphericalHarmonicsFilter
Issue(s): #1091
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: AddFilterAction
- 1.21.132The system shall support multiple filters within a tally.
Specification(s): multi_filter
Design: AddFilterAction
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.133The system shall support the automatic addition of the requested source rate normalization score to a single tally when using filters.
Specification(s): no_norm_score
Design: AddFilterAction
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.134The system shall error if a non-existent filter is requested by a tally.
Specification(s): missing_filter
Design: AddFilterAction
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.135The system shall error if a filter is added when an OpenMCCellAverageProblem is not present.
Specification(s): wrong_problem
Design: AddFilterAction
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: FromXMLFilter
- 1.21.136The system shall allow cell tallies to access filters added in the OpenMC tallies XML file.
Specification(s): arbitrary_cell
Design: FromXMLFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.137The system shall allow mesh tallies to access filters added in the OpenMC tallies XML file.
Specification(s): arbitrary_mesh
Design: FromXMLFilter
Issue(s): #1249
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.138The system shall error if a filter with the id requested has not been added by the tallie xml file.
Specification(s): missing_filter
Design: FromXMLFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.139The system shall error if the user selects a spatial filter.
Specification(s): spatial_filter_error
Design: FromXMLFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.140The system shall warn the user if they have selected a functional expansion filter and set allow_expansion_filters = true.
Specification(s): func_exp_warning
Design: FromXMLFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.141The system shall error if the user selected a functional expansion filter without setting allow_expansion_filters = true.
Specification(s): func_exp_error
Design: FromXMLFilter
Issue(s): #1249
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: FoMAux
- 1.21.153The system shall ensure the provided tally values are constant monomials.
Specification(s): const_mono_tally_val
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.154The system shall ensure the provided initial tally values are constant monomials.
Specification(s): const_mono_tally_val_init
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.155The system shall ensure a tally variable is provided when using the AMR FoM.
Specification(s): no_tally_val
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.156The system shall ensure an initial tally variable is provided when using the AMR FoM.
Specification(s): no_tally_val_init
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.157The system shall ensure the provided stochastic relative errors are constant monomials.
Specification(s): const_mono_rel_err
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.158The system shall allow for the calculation of the variance reduction figure of merit.
Specification(s): vr_fom
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.159The system shall allow for the calculation of the AMR figure of merit.
Specification(s): amr_fom
Design: FoMAux
Issue(s): #1333
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: ComputeDiffusionCoeffMGAux
- 1.21.160The system shall support the calculation of multi-group particle diffusion coefficients.
- The system shall calculate multi-group particle diffusion coefficients.
- The system shall prevent divide by zeros when calculating multi-group diffusion coefficients. This also checks for cases where the transport cross section is zero.
Specification(s): diffusion_coefficient/calc, diffusion_coefficient/catch_zero_flux
Design: ComputeDiffusionCoeffMGAux
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: ComputeTCScatterMGXSAux
- 1.21.161The system shall support the calculation of multi-group transport corrected P0 scattering cross sections.
- The system shall calculate multi-group transport corrected P0 scattering cross sections.
- The system shall prevent divide by zeros when calculating transport corrected P0 scattering cross sections.
Specification(s): transport_scattering/calc, transport_scattering/catch_zero_flux
Design: ComputeTCScatterMGXSAux
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: ComputeMGXSAux
- 1.21.162The system shall support the calculation of multi-group cross sections using an arbitrary reaction rate and normalization factor.
- The system shall calculate multi-group cross sections using an arbitrary reaction rate and normalization factor.
- The system shall prevent divide by zeros when calculating cross sections.
Specification(s): generic_mgxs/calc, generic_mgxs/catch_zero_flux
Design: ComputeMGXSAux
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: SetupMGXSAction
- 1.21.163The system shall be capable of setting up MGXS generation for all relevant cross section types for photon.
Specification(s): photon
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.164The system shall be capable of setting up MGXS generation for all relevant cross section types using mapped distributed cell tallies.
Specification(s): all_cell
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.165The system shall be capable of generating L = 0 scattering cross sections without a transport correction.
Specification(s): l0_scatter_no_tc
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.166The system shall be capable of generating L > 0 scattering MGXS generation.
Specification(s): l1_scatter
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.167The system shall be capable of generating certain multi-group cross sections with a collision estimator.
Specification(s): collision
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.168The system shall be capable of generating certain multi-group cross sections with a tracklength estimator.
Specification(s): tracklength
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.169The system shall be capable of setting up MGXS generation for all relevant cross section types using unstructured mesh tallies.
Specification(s): all_mesh
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.170The system shall be hide tally variables added for MGXS generation unless requested by the user.
Specification(s): hide_tally_vars
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.171The system shall error if the user requests electron cross sections.
Specification(s): electron
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.172The system shall error if the user requests positron cross sections.
Specification(s): positron
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.173The system shall error if the user requests photon cross sections and includes fission.
Specification(s): photon_fission_xs
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.174The system shall error if the user requests photon cross sections and includes fission.
Specification(s): photon_fission_heating
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.175The system shall warn the user if they request transport corrected scattering cross sections with L > 0.
Specification(s): l1_scatter_with_transport_corr
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.176The system shall warn the user if they select a mesh tally and request a tracklength estimator.
Specification(s): error_mesh_with_tracklength
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.177The system shall warn the user if they wish to generate scattering / fission / diffusion group properties without an analog estimator.
Specification(s): error_non_analog
Design: SetupMGXSAction
Issue(s): #1020
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: ElementOpticalDepthIndicator
- 1.21.198The system shall allow for the calculation of the optical depth using the min/max vertex separation or the cube root of the element volume.
Specification(s): all_h
Design: ElementOpticalDepthIndicator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.199The system shall allow for the calculation of the inverse optical depth using the min/max vertex separation or the cube root of the element volume.
Specification(s): invert_all_h
Design: ElementOpticalDepthIndicator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.200The system shall error if a non-reaction rate score is provided to ElementOpticalDepthIndicator.
Specification(s): not_rxn_rate
Design: ElementOpticalDepthIndicator
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.201The system shall error if a a reaction rate score is requested, but not available in a tally.
Specification(s): missing_score
Design: ElementOpticalDepthIndicator
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.202The system shall error if the flux is not available in a tally.
Specification(s): missing_flux
Design: ElementOpticalDepthIndicator
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.203The system shall allow for the computation of optical depth indicators when multiple tallies are added which accumulate the same scores.
Specification(s): duplicate_scores
Design: ElementOpticalDepthIndicator
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: StatRelErrorIndicator
- 1.21.204The system shall allow for the use of the statistical relative error of a tally score as an indicator.
Specification(s): rel_err
Design: StatRelErrorIndicator
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.205The system shall error if the provided score does not exist in StatRelErrorIndicator.
Specification(s): no_score
Design: StatRelErrorIndicator
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.206The system shall error if no tallies are storing the relative error of the provided score.
Specification(s): no_rel_err
Design: StatRelErrorIndicator
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.207The system shall error if the provided tally external filter bin is greater than the total number of external filter bins.
Specification(s): invalid_bin
Design: StatRelErrorIndicator
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.208The system shall allow for the computation of relative error indicators when multiple tallies are added which accumulate the same scores.
Specification(s): duplicate_scores
Design: StatRelErrorIndicator
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: LambdaEffective
- 1.21.211The system shall be able to calculate neutron kinetics parameters.
Specification(s): compute_both
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.212The system shall be able to calculate separate values of beta_eff for each delayed group in the ENDF delayed group structure.
Specification(s): six_group_beta
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.213The system shall error if the problem does not enable IFP calculations and attempts to add an LambdaEffective post processor.
Specification(s): no_ifp_lambda
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.214The system shall error if the problem does not enable IFP calculations and attempts to add a BetaEffective post processor.
Specification(s): no_ifp_beta
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.215The system shall error if the problem does not enable IFP calculations and attempts to add a BetaEffective post processor.
Specification(s): more_ifp_gen_then_inactive
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: BetaEffective
- 1.21.211The system shall be able to calculate neutron kinetics parameters.
Specification(s): compute_both
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.212The system shall be able to calculate separate values of beta_eff for each delayed group in the ENDF delayed group structure.
Specification(s): six_group_beta
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.213The system shall error if the problem does not enable IFP calculations and attempts to add an LambdaEffective post processor.
Specification(s): no_ifp_lambda
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.214The system shall error if the problem does not enable IFP calculations and attempts to add a BetaEffective post processor.
Specification(s): no_ifp_beta
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.215The system shall error if the problem does not enable IFP calculations and attempts to add a BetaEffective post processor.
Specification(s): more_ifp_gen_then_inactive
Design: LambdaEffectiveBetaEffectiveOpenMCCellAverageProblem
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: ErrorFractionLookAheadMarker
- 1.21.216The system shall allow the use of a look ahead marker to mitigate cyclic refinement.
Specification(s): mark
Design: ErrorFractionLookAheadMarker
Issue(s): #1146
Collection(s): FUNCTIONAL
Type(s): Exodiff
- cardinal: OpenMCVolumeCalculation
- 1.21.239The system shall warn the user if there is an inconsistency between a moving mesh and the underlying OpenMC geometry.
Specification(s): inconsistency
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.240The system shall correctly reinitialize cell tallies when the mesh is moving. This is tested by translating the mesh over a stationary OpenMC model. The two cell tallies in the tallies.out file match the expected power density (accounting for the actual fractions of the cell which map to the moving mesh). This test also checks the cell IDs and instances as the mesh translates.
Specification(s): cell_tally
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.241The system shall correctly use a mesh tally on a moving MOOSE mesh. This is tested by translating the mesh over a stationary OpenMC model. The mesh translation exposes 20 percent of the left subdomain, which from a non-moving case we record 8 percent of the total power deposition in this region. For the moving mesh case, the total power deposited in the mesh tally is 92 percent.
Specification(s): mesh_tally
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.242The system shall generate a file for mesh tallies.
Specification(s): make_mesh
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): RunApp
- 1.21.243The system shall error if tallying on a file mesh for moving mesh cases, because there will be a disagreement between the mesh elements and the Mesh.
Specification(s): file_mesh
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.244The system shall correctly reinitialize temperature mapping and output of cell temperatures to a moving mesh. This is tested by applying temperatures based on the moving mesh.
Specification(s): temperature
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.245The system shall correctly reinitialize density mapping and output of cell densities and material fills to a moving mesh. This is tested by applying densities based on the moving mesh.
Specification(s): density
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.246The system shall correctly reinitialize volume calculations for a moving mesh. This is tested by comparing the OpenMC stochastic volume calculation against postprocessors for changing volumes.
Specification(s): volumes
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.247The system shall change the OpenMC mesh geometry on-the-fly. This is tested by running this case with a very high number of particles and batches, to compare against the CSG case in the reference folder. The reference case is a CSG model created at the deformed state. We cannot match these cases perfectly because we cannot control the seed of the second Picard iteration. The reference case gives k = 0.88782 plus or minus 5 pcm, and our Cardinal case gives 0.88786 plus of minus 5 pcm; these agree within 1 sigma.
Specification(s): scale
Design: OpenMCVolumeCalculationOpenMCCellAverageProblemMoabSkinner
Issue(s): #899
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: AddTallyAction
- 1.21.256The system shall error if using incompatible tally estimator with a photon transport heating score.
Specification(s): photon_heating
Design: AddTallyAction
Issue(s): #1114
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.257The system shall error if using a single tally with a photon transport heating score and nu-scatter score.
Specification(s): photon_nu_scatter_heating
Design: AddTallyAction
Issue(s): #1089
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.318The system shall allow tallying of absorption/fission/scattering/total reaction rates in fixed source mode.
Specification(s): reaction_rates
Design: AddTallyAction
Issue(s): #912
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.319The system shall allow tallying of nu-scatter, nu-fission, and inverse-velocity in fixed source mode.
- The system shall compute nu-scatter, nu-fission, and inverse-velocity scores in fixed source mode.
- The system shall error if the user attempts to specify a nu-scatter score without an analog estimator.
Specification(s): mgxs/reaction_rates, mgxs/nu_scatter_analog
Design: AddTallyAction
Issue(s): #1089
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunExceptionCSVDiff
- 1.21.320The system shall allow tallying of prompt-nu-fission, delayed-nu-fission, and decay-rate in fixed source mode.
- The system shall compute prompt-nu-fission, delayed-nu-fission, and decay-rate scores in fixed source mode.
Specification(s): delayed_mgxs/reaction_rates
Design: AddTallyAction
Issue(s): #1207
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.327The system shall correctly label elements in blocks which don't contain temperature feedback, density feedback, or a cell tally as unmapped.
Specification(s): cell_tally_unmapped
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.328The system shall correctly normalize local tallies with different estimators using multiple global tallies.
Specification(s): multi_global_estimator
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.329The system shall correctly apply and normalize two different CellTally objects with different scores. The gold file was generated using an input that had a single CellTally with multiple scores.
Specification(s): multiple_tallies_cell
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.330The system shall correctly apply and normalize two different MeshTally objects with different scores. The gold file was generated using an input that had a single MeshTally with multiple scores.
Specification(s): multiple_tallies_mesh
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.331The system shall correctly apply and normalize two different CellTally objects with different scores and triggers. The gold file was generated using an input that had a single CellTally with multiple scores and triggers.
Specification(s): multiple_tallies_cell_triggers
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.332The system shall correctly apply and normalize two different MeshTally objects with different scores and triggers. The gold file was generated using an input that had a single MeshTally with multiple scores and triggers.
Specification(s): multiple_tallies_mesh_triggers
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.333The system shall correctly apply and normalize two different CellTally objects with different scores when using relaxation. The gold file was generated using an input that had a single CellTally with multiple scores when using relaxation.
Specification(s): multiple_tallies_cell_relax
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.334The system shall correctly apply and normalize two different MeshTally objects with different scores when using relaxation. The gold file was generated using an input that had a single MeshTally with multiple scores when using relaxation.
Specification(s): multiple_tallies_mesh_relax
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.335The system shall error if more than one tally is provided and the requested heating score is in none of the tallies.
Specification(s): multi_no_norm
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.336The system shall allow calculations with multiple different tallies.
Specification(s): multiple_different_tallies
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.337The system shall allow calculations with multiple different tally outputs.
Specification(s): multiple_different_outputs
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.338The system shall allow multiple tallies to use the same scores.
Specification(s): same_scores
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.21.339The system shall error if two tallies score the normalization score and the user does not specify which to use for normalization.
Specification(s): two_kf_unspecified_norm
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.340The system shall error if two tallies scoring the same score add the same variable names.
Specification(s): duplicate_names
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.341The system shall error if attempting to use separate tallies when adding two tallies with the same score.
Specification(s): duplicate_scores_separate_tallies
Design: AddTallyActionMeshTally CellTally
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: FDTallyGradAux
- 1.21.322The system shall allow for the approximation of tally gradients using finite differences.
Specification(s): gradients
Design: FDTallyGradAux
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.21.323The system shall error if the variable provided to FDTallyGradAux is not of type CONSTANT MONOMIAL_VEC.
Specification(s): not_const_mon
Design: FDTallyGradAux
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.324The system shall error if a score is requested, but not available in a tally.
Specification(s): missing_score
Design: FDTallyGradAux
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.325The system shall error if the external filter bin provided by the user is out of bounds for the filters applied to the given score.
Specification(s): invalid_bin_index
Design: FDTallyGradAux
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.21.326The system shall allow for the computation of tally gradients with finite differences when multiple tallies are added which accumulate the same scores.
Specification(s): duplicate_scores
Design: FDTallyGradAux
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: TallyRelativeError
- 1.23.8The maximum and minimum tally relative errors shall be correctly retrieved from the OpenMC solution.
Specification(s): fission_tally_relative_error
Design: TallyRelativeError
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.9The maximum and minimum tally relative errors shall be correctly retrieved from the OpenMC solution when using multiple scores.
Specification(s): multi_score
Design: TallyRelativeError
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.10The system shall error if trying to extract score information that does not exist
Specification(s): nonexistent_score
Design: TallyRelativeError
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.23.11The system shall prove equivalence between a by-hand calculation of relative error (std_dev output divided by tally value) as compared to the tally relative error postprocessor.
Specification(s): manual_rel_err_calc
Design: TallyRelativeError
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.12The system shall allow for the computation of tally relative errors when multiple tallies accumulating the same scores are added to the problem.
Specification(s): duplicate_scores
Design: TallyRelativeError
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.13The system shall error if two tallies accumulate the same scores and the user doesn't select one to use for computing a relative error metric.
Specification(s): duplicate_scores_tally_not_provided
Design: TallyRelativeError
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.23.14The system shall error if the user provides a non-existent tally.
Specification(s): duplicate_scores_missing_tally
Design: TallyRelativeError
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.23.15The system shall error if the user provides a tally that does not accumulate the score.
Specification(s): duplicate_scores_tally_has_no_score
Design: TallyRelativeError
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: NekPointValue
- 1.23.17The system shall warn the user if dimensionalization is requested and cannot be performed, for
- usrwrk slot 0
- usrwrk slot 1
- usrwrk slot 2
Specification(s): warn/u00, warn/u01, warn/u02
Design: NekPointValue
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: NekSideAverage
- 1.23.21NekSideAverage shall correctly compute area-averaged temperatures on the nekRS mesh. The gold file was created by running the moose.i input, which computes the same averages using existing MOOSE postprocessors on the same mesh on auxvariables that match the functional form of the solution fields initialized in the pyramid.udf. Perfect agreement is not to be expected, since the underlying basis functions and quadrature rules are different between nekRS and MOOSE's linear Lagrange variables - we just require that they are reasonably close.
Specification(s): nek_side_average
Design: NekSideAverage
Issue(s): #1015
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekViscousSurfaceForce
- 1.23.26The system shall allow total viscous drag to be computed in dimensional form. This test compares drag as computed via Nek with by-hand calculations using combinations of native MOOSE postprocessors using the analytic expression for velocity.
Specification(s): drag
Design: NekViscousSurfaceForce
Issue(s): #1290
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.27The system shall error if trying to compute viscous drag on non-fluid NekRS boundaries
Specification(s): invalid_mesh
Design: NekViscousSurfaceForce
Issue(s): #1290
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: NekVolumeAverage
- 1.23.28dimensional form
Specification(s): nek
Design: NekVolumeAverage
Issue(s): #1065
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.29nondimensional form
Specification(s): nondimensional
Design: NekVolumeAverage
Issue(s): #1065
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekVolumeIntegral
- 1.23.32dimensional form
Specification(s): nek
Design: NekVolumeIntegral
Issue(s): #1065
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.33nondimensional form
Specification(s): nondimensional
Design: NekVolumeIntegral
Issue(s): #1065
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekYPlus
- 1.23.37The system shall allow y plus to be computed. The resulting expression is checked against an analytic expression for the friction velocity and by inspection of the wall distance for the first GLL points near the wall.
Specification(s): drag
Design: NekYPlus
Issue(s): #1290
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.23.38The system shall error if trying to compute y plus on non-fluid NekRS boundaries
Specification(s): invalid_mesh
Design: NekYPlus
Issue(s): #1290
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: OpenMCWallTime
- 1.23.40The system shall allow for the output of different timing statistics from OpenMC. Golding execution times is non-deterministic due to the difference in testing hardware and hardware utilization. This test is designed to avoid non-determinism when possible, and so raw timing statistics are not reported in the gold file.
Specification(s): walltime
Design: OpenMCWallTime
Issue(s): #1338
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: Reactivity
- 1.23.41The k-eigenvalue and its standard deviation shall be correctly retrieved from the OpenMC solution.
Specification(s): k_eigenvalue
Design: Reactivity
Issue(s): #1051
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekBoundaryFlux
- 1.27.2The system shall be able to read the flux from NekRS and write onto a boundary mesh mirror. This is tested by setting a known temperature distribution in NekRS such that the analytic heat flux can be computed and compared.
Specification(s): flux
Design: NekBoundaryFlux
Issue(s): #1166
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.27.3The system shall error if trying to write heat flux on a boundary when the mesh mirror is a volume mesh.
Specification(s): volume
Design: NekBoundaryFlux
Issue(s): #1166
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.27.6The system shall be able to write multiple incoming volumetric source terms to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_source_transfers
Design: NekUsrWrkBoundaryIntegralNekVolumetricSourceNekBoundaryFlux
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.27.7The system shall be able to write multiple incoming boundary flux terms to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_flux_transfers
Design: NekUsrWrkBoundaryIntegralNekVolumetricSourceNekBoundaryFlux
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekUsrWrkBoundaryIntegral
- 1.27.6The system shall be able to write multiple incoming volumetric source terms to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_source_transfers
Design: NekUsrWrkBoundaryIntegralNekVolumetricSourceNekBoundaryFlux
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.27.7The system shall be able to write multiple incoming boundary flux terms to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_flux_transfers
Design: NekUsrWrkBoundaryIntegralNekVolumetricSourceNekBoundaryFlux
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekVolumetricSource
- 1.27.6The system shall be able to write multiple incoming volumetric source terms to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_source_transfers
Design: NekUsrWrkBoundaryIntegralNekVolumetricSourceNekBoundaryFlux
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.27.7The system shall be able to write multiple incoming boundary flux terms to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_flux_transfers
Design: NekUsrWrkBoundaryIntegralNekVolumetricSourceNekBoundaryFlux
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: NekFieldVariable
- 1.27.8The system shall be able to write into the scratch space a temperature which NekRS can use in its case files. This is tested by passing in a temperature field on a boundary and then applying that field as a Dirichlet condition.
Specification(s): temperature_input
Design: NekFieldVariable
Issue(s): #1166
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.27.9The system shall error if too many usrwrk slots are specified for a single field transfer
Specification(s): too_many_slots
Design: NekFieldVariable
Issue(s): #1166
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.27.10The system shall be able to write multiple incoming field transfers to NekRS. This is tested by writing two constant fields into the usrwrk array, and then integrating them over boundaries to ensure different fields are stored in each.
Specification(s): multiple_field_transfers
Design: NekFieldVariable
Issue(s): #1230
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- 1.27.11The system shall be able to write into the scratch space a temperature which NekRS can use in its case files. This is tested by passing in a temperature field in the volume and applying this field to the temperature instead of solving it.
Specification(s): temperature_input
Design: NekFieldVariable
Issue(s): #1166
Collection(s): FUNCTIONAL
Type(s): CSVDiff
- cardinal: BooleanComboClusteringUserObject
- 1.28.1The system shall throw a warning if the extra element integer is not found in mesh.
Specification(s): no_extra_integer_provided_boolean_combo
Design: BooleanComboClusteringUserObject
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.2The system shall error if a non-replicated mesh is used while clustering.
Specification(s): mesh_is_not_replicated
Design: BooleanComboClusteringUserObject
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.3The system shall error if the 'metric_variable' is not constant monomial.
Specification(s): element_needs_to_be_constant_monomial
Design: BooleanComboClusteringUserObject
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.4The system shall error if 'lower_faction + upper_fraction' is more than 1.
Specification(s): lower_fraction_is_more_than_upper_fraction
Design: BooleanComboClusteringUserObject
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: ThresholdHeuristicUserObject
- 1.28.5The system shall reproduce the clustering pattern by evaluating a boolean expression which combines multiple threshold-based heuristics and operates on element pairs.
Specification(s): grid
Design: ThresholdHeuristicUserObject
Collection(s): FUNCTIONAL
Type(s): Exodiff
- cardinal: ValueDifferenceHeuristicUserObject
- 1.28.6The system shall be able to cluster mesh elements by identifying elements with equal metric values within a specified tolerance using a value-difference heuristic.
Specification(s): grid
Design: ValueDifferenceHeuristicUserObject
Collection(s): FUNCTIONAL
Type(s): Exodiff
- cardinal: ValueFractionHeuristicUserObject
- 1.28.7The system shall be able to cluster elements by identifying element pairs whose variable values both fall within either a specified upper or lower fraction of the extremes.
Specification(s): grid
Design: ValueFractionHeuristicUserObject
Collection(s): FUNCTIONAL
Type(s): Exodiff
- cardinal: ValueRangeHeuristicUserObject
- 1.28.8The system shall be able to cluster elements by identifying element pairs whose metric values both fall within a range defined by a user-specified percentage above and below given reference values, with multiple ranges combined through a boolean expression.
Specification(s): grid
Design: ValueRangeHeuristicUserObject
Collection(s): FUNCTIONAL
Type(s): Exodiff
- cardinal: OpenMCCellTransform
- 1.28.74The system shall correctly reinitialize OpenMC coupling when multiple geometry cells are translated.This is tested by translating the mesh while also translating OpenMC universe which contains the coupled cells.
Specification(s): translate_multiple_cells
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.75The system shall error if the same cell id is provided more than once.
Specification(s): duplicate_cell_id
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.76The system shall correctly reinitialize OpenMC coupling when the geometry is translated.This is tested by translating the mesh while also translating OpenMC universe which contains the coupled cells.
Specification(s): translate_cells
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.77The system shall correctly reinitialize OpenMC coupling when a scaled geometry is translated.This is tested by translating the scaled mesh while also translating OpenMC universe which contains the coupled cells.
Specification(s): scaled_translation
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.78The system shall correctly reinitialize OpenMC coupling when the geometry is rotated.This is tested by rotating the mesh while also rotating OpenMC universe which contains the coupled cells.
Specification(s): rotate_cells
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.79The system shall correctly reinitialize OpenMC coupling when the geometry is translated.This is tested by translating an OpenMC geometry on a stationary mesh and ensure elements are reset correctly.
Specification(s): cells_shadow
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONAL
Type(s): Exodiff
- 1.28.80
Specification(s): invalid_phi
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.81
Specification(s): invalid_theta
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.82
Specification(s): invalid_psi
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.83
Specification(s): empty_cell_ids
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.84
Specification(s): wrong_vector_size
Design: OpenMCCellTransform
Issue(s): #1255
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- cardinal: OpenMCTallyEditor
- 1.28.92The system shall error if
- trying to edit a non-existant tally
- trying to add a nuclide not accessible in the cross section library
- trying to add an invalid score to a tally
- the filter referenced by an OpenMCFilterEditor via ID does not exist and is not flagged for creation
- an OpenMCDomainFilter editor exists with the same filter ID but a different filter type
- more than one OpenMCDomainFilterEditor eixsts with the same filter ID
- more than one OpenMCTallyEditor eixsts with the same tally ID
- an OpenMCTallyEditor eixsts for a mapped tally created by Cardinal
Specification(s): errors/nonexistent_tally, errors/nonexistent_nuclide, errors/invalid_score, errors/nonexistent_filter, errors/clashing_filter_types, errors/clashing_filter_ids, errors/clashing_tally_ids, errors/clashing_mapped_tally
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.93Ensure that nuclides specified by a tally editor UO are present in the tally output
Specification(s): nuclides
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.94Ensure that the scattering score specified by a tally editor UO are present in the tally output
Specification(s): scatter_tally
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.95Ensure that the absorption score for a specific nuclide specified by a tally editor UO are present in the tally output
Specification(s): absorption_u238
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.96Ensure that a cell filter specified by a tally editor UO are present in the tally output
Specification(s): add_cell_filter
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.97Ensure that a material filter specified by a tally editor UO are present in the tally output
Specification(s): add_material_filter
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.98Ensure that a universe filters specified by a tally editor UO are present in the tally output
Specification(s): add_universe_filter
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- cardinal: OpenMCDomainFilterEditor
- 1.28.92The system shall error if
- trying to edit a non-existant tally
- trying to add a nuclide not accessible in the cross section library
- trying to add an invalid score to a tally
- the filter referenced by an OpenMCFilterEditor via ID does not exist and is not flagged for creation
- an OpenMCDomainFilter editor exists with the same filter ID but a different filter type
- more than one OpenMCDomainFilterEditor eixsts with the same filter ID
- more than one OpenMCTallyEditor eixsts with the same tally ID
- an OpenMCTallyEditor eixsts for a mapped tally created by Cardinal
Specification(s): errors/nonexistent_tally, errors/nonexistent_nuclide, errors/invalid_score, errors/nonexistent_filter, errors/clashing_filter_types, errors/clashing_filter_ids, errors/clashing_tally_ids, errors/clashing_mapped_tally
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 1.28.93Ensure that nuclides specified by a tally editor UO are present in the tally output
Specification(s): nuclides
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.94Ensure that the scattering score specified by a tally editor UO are present in the tally output
Specification(s): scatter_tally
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.95Ensure that the absorption score for a specific nuclide specified by a tally editor UO are present in the tally output
Specification(s): absorption_u238
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.96Ensure that a cell filter specified by a tally editor UO are present in the tally output
Specification(s): add_cell_filter
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.97Ensure that a material filter specified by a tally editor UO are present in the tally output
Specification(s): add_material_filter
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles
- 1.28.98Ensure that a universe filters specified by a tally editor UO are present in the tally output
Specification(s): add_universe_filter
Design: OpenMCTallyEditorOpenMCDomainFilterEditor
Issue(s): #837
Collection(s): FUNCTIONAL
Type(s): CheckFiles