Cardinal Failure Analysis Report

Introduction

The Failure Analysis Report (FAR) for Cardinal describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.

Dependencies

The Cardinal application is developed using MOOSE and is based on various modules, as such the FAR for Cardinal is dependent upon the following documents.

Failure Analysis Requirements

The following is a complete list for all the requirements related to failure analysis for Cardinal.

  • cardinal: Auxkernels
  • 1.1.3System shall error if auxkernel is not paired with a compatible bin user object.

    Specification(s): invalid_uo

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.1.4System shall error if auxkernel is not paired with a velocity vector bin user object.

    Specification(s): invalid_field

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Conduction
  • 1.4.3The system shall error if the user specifies a duplicate variable with a name overlapping with special names reserved for Cardinal data transfers.

    Specification(s): duplicate_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.4.19The system shall print a helpful error message if the sideset flux reporter does not have the correct length.

    Specification(s): mismatch_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.4.20The system shall error if conserving flux on each unique sideset, but with nodes shared across multiple sidesets.

    Specification(s): nodes_on_shared

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Controls
  • 1.5.1The system shall error if the controls is not used with the proper user object

    Specification(s): wrong_uo

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Ics
  • 1.9.1The volume postprocessor must have execute_on initial

    Specification(s): missing_initial

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.9.2The system shall error if invalid parameters are provided

    Specification(s): invalid_mdot_cp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.9.4The system shall error if the pairing heat source action is missing

    Specification(s): missing_paired_action

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Meshgenerators
  • 1.12.1The system shall error if the boundary specified for corner fitting does not exist

    Specification(s): invalid_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.2The system shall error if an invalid polygon boundary is provided

    Specification(s): duplicate_boundary

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.3The system shall error if the radius of curvature is too big to fit inside the polygon

    Specification(s): too_big_radius

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.6The system shall error if applying a rotation angle to a polygon not centered on (0, 0)

    Specification(s): corners_translate_rotate

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.8The system shall error if the length of smoothing adjustments does not equal the number of polygon layers

    Specification(s): invalid_number_of_smoothing

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.9The system shall error if the length of smoothing adjustments are not set to valid values

    Specification(s): zero_smoothing

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.11The system shall error if an invalid element type is used with a quad9 to quad8 converter

    Specification(s): invalid_elem

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.12The system shall error if attempting to move elements to a circular surface when those elements have more than one face on the circular sideset.

    Specification(s): multiple_sides

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.13The system shall error if attempting to move elements to a circular surface when those elements have more than one face on the circular sidesets.

    Specification(s): repeated_sides

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.14The system shall error if the boundary specified for circular sideset fitting does not exist

    Specification(s): invalid_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.18The system shall error if the boundary specified for rebuilding sidesets does not exist

    Specification(s): convert_some_sidsets_invalid

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.24The system shall error if a point is already located on the origin, because then it lacks a nonzero unit vector to move it to a circular surface.

    Specification(s): point_already_on_origin

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.26The system shall error if there is an obvious mismatch between the number of boundary layers and the mesh.

    Specification(s): layers_too_many

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.28The system shall error if an invalid element type is used with a hex27 to hex20 converter

    Specification(s): invalid_elem

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.29The system shall error if attempting to move elements to a circular surface when those elements have more than one face on the circular sideset.

    Specification(s): multiple_sides

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.30The system shall error if attempting to move elements to a circular surface when those elements have more than one face on the circular sidesets.

    Specification(s): repeated_sides

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.31The system shall error if the boundary specified for circular sideset fitting does not exist

    Specification(s): invalid_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.35The system shall error if the boundary specified for rebuilding sidesets does not exist

    Specification(s): convert_some_sidsets_invalid

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.41The system shall error if the invalid values are used for the radii.

    Specification(s): invalid_radius

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.42The system shall error if the radius and boundary are not the same length.

    Specification(s): mismatch_radius_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.43The system shall error if the origin and boundary are not the same length.

    Specification(s): mismatch_origin_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.44The system shall error if the origin and boundary are not the same length.

    Specification(s): mismatch_origin_file_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.45The system shall error if the origin entries are not the correct length.

    Specification(s): mismatch_origin_space

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.46The system shall error if the origin entries are not the correct length.

    Specification(s): mismatch_origin_empty

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.48The system shall error if the number of layers does not match the number of boundaries to move

    Specification(s): layers_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.50The system shall error if there is an obvious mismatch between the number of boundary layers and the mesh.

    Specification(s): layers_too_many

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.52The system shall error if trying to set the origins in more than one manner

    Specification(s): too_many_origins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.12.53The system shall error if invalid points are provided for the origins

    Specification(s): invalid_origin_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Multiple Nek Apps
  • 1.13.2The system shall error if an invalid directory path is provided for the case

    Specification(s): invalid_directory

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.13.3The system shall error if trying to write output files for a Nek input without sibling apps

    Specification(s): invalid_write_fld

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Nek Errors
  • 1.14.1The system shall error if Cardinal has displacements associated with NekRSMesh, but there is no mesh solver.

    Specification(s): missing_mesh_solver

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.2The system shall error if Cardinal is using NekRSStandaloneProblem with NekRS's moving mesh problems.

    Specification(s): standalone

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.3The system shall error if the Nek .par file has a mesh solverbut the nekRS .par file has no moving mesh (codedFixedValue) boundary in the Mesh block.

    Specification(s): missing_mv_boundary

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.4The system shall error if Cardinal is using the NekRS mesh blending solver without indicating the moving boundary of interest

    Specification(s): missing_boundary

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.5The system shall error if NekRSMesh is not paired with displacements for moving mesh problems.

    Specification(s): displacements

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.6The system shall error if Cardinal has solver=user in the par file's MESH block, but there is no volume mesh mirror.

    Specification(s): volume_for_user_solver

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.7The system shall error if the nekRS .par file has a moving mesh solverbut the problem type in Cardinal is NekRSSeprateDomainProblem.

    Specification(s): separate_domain

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.9The system shall error if the user tries to allocate scratch from Cardinal for standalone NekRS cases, but the Nek case files are also separately trying to allocate scratch.

    Specification(s): error_standalone

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.10The system shall error if the user enters too small a scratch space allocation; NekRSProblem always requires at least 1 slot

    Specification(s): too_small_a

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.11The system shall error if the user enters too small a scratch space allocation

    Specification(s): too_small_b

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.12The system shall error if the user enters too small a scratch space allocation

    Specification(s): too_small_c

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.13The system shall error if the user enters too small a scratch space allocation

    Specification(s): too_small_d

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.14The system shall error if the user enters too small a scratch space allocation

    Specification(s): too_small_e

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.15The system shall error if the user enters too small a scratch space allocation

    Specification(s): too_small_f

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.16The system shall error if the user enters too small a scratch space allocation

    Specification(s): too_small_g

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.17The system shall error if the user enters too small a scratch space allocation; an initial shift cannot exceed the number of allocated slots

    Specification(s): too_small_h

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.18The system shall error if the user enters too small a scratch space allocation, when using a front shift for the slots

    Specification(s): too_small_i

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.19MOOSE shall throw an error if an invalid boundary is specified for the construction of nekRS's mesh as a MooseMesh.

    Specification(s): invalid_boundary_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.20The system shall throw an error if trying to use temperature as a field for cases that do not have a temperature variable

    Specification(s): temperature

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.21The system shall throw an error if trying to use scalar01 as a field for problems that don't have a scalar01 variable.

    Specification(s): scalar01

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.22The system shall throw an error if trying to use scalar02 as a field for problems that don't have a scalar02 variable.

    Specification(s): scalar02

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.23The system shall throw an error if trying to use scalar03 as a field for problems that don't have a scalar03 variable.

    Specification(s): scalar03

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.24The system shall throw an error if trying to use usrwrk00 as a field for problems that don't have sufficient usrwrk slots.

    Specification(s): usrwrk00

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.25The system shall throw an error if trying to use usrwrk01 as a field for problems that don't have sufficient usrwrk slots.

    Specification(s): usrwrk01

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.26The system shall throw an error if trying to use usrwrk02 as a field for problems that don't have sufficient usrwrk slots.

    Specification(s): usrwrk02

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.28The system shall error if the user manually specifies a duplicate name for an output field.

    Specification(s): duplicate_auxvar

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.29The system shall error if the user manually specifies a duplicate name for an output field.

    Specification(s): duplicate_var

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.30The system shall error if NekRSProblem is not paired with the correct executioner.

    Specification(s): executioner

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.31The system shall error if the Dimensionalize action is not paired with the correct problem.

    Specification(s): dimensionalize

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.32The system shall error if NekRSProblem is not paired with the correct mesh type.

    Specification(s): mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.33The system shall error if a Nek object is not paired with the correct problem.

    Specification(s): problem_base

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.34The system shall error if a NekRSMesh is used without a corresponding Nek-wrappedproblem.

    Specification(s): problem_mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.35The system shall error if NekRSProblem is not paired with the correct time stepper.

    Specification(s): timestepper

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.36MOOSE shall throw an error if there is no receiving heat flux boundary condition on the nekRS boundaries that are coupled to MOOSE.

    Specification(s): missing_flux_bc

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.37MOOSE shall throw an error if an invalid boundary is specified for the construction of nekRS's mesh as a MooseMesh.

    Specification(s): boundary_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.38MOOSE shall throw an error if 'boundary' is empty for separate domain coupling, because the correct internal arrays would not be initialized

    Specification(s): separate_boundary

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.39The system shall error if there is a mismatch between the scaling of the mesh and NekRS problem.

    Specification(s): scaling_mismatch

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.40When using the minimized transfers setting, the default value for the postprocessor in the master application must not be zero.

    Specification(s): invalid_transfer_pp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.41The system shall error if the same MPI communicator is used to set up more than one Nek case.

    Specification(s): too_few_mpi_ranks

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.42The system shall throw an error if there is no heat source kernel when using volume coupling

    Specification(s): no_occa_source_kernel

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.43MOOSE shall throw an error if there is no temperature passive scalar variable initialized in nekRS.

    Specification(s): no_temperature_variable

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.14.44MOOSE shall throw an error if the user attempts to allocate the scratch space arrays in NekRS, since they are automatically allocated by Cardinal.

    Specification(s): occupied_scratch_space

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Nek Mesh
  • 1.16.3The system shall error if trying to build an exact mesh mirror that is second order.

    Specification(s): second_exact

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Nek Output
  • 1.17.2The system shall error if trying to write a usrwrk slot greater than the total number of allocated slots

    Specification(s): too_high_slot

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.17.3The system shall error if there is a mismatch between parameter lengths for writing usrwrk field files

    Specification(s): mismatch_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Nek Separatedomain
  • 1.18.1The system shall throw an error if trying to assign inlet_boundary to multiple boundary IDs.

    Specification(s): invalid_inlet_boundary_multiple

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.18.2The system shall throw an error if trying to assign inlet_boundary to an ID not contained in NekRSMesh's boundary input.

    Specification(s): invalid_inlet_boundary_mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.18.3The system shall throw an error if trying to assign inlet_boundary to an ID not contained in NekRS boundary IDs.

    Specification(s): invalid_inlet_boundary_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.18.4The system shall throw an error if trying to assign outlet_boundary to multiple boundary IDs.

    Specification(s): invalid_outlet_boundary_multiple

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.18.5The system shall throw an error if trying to assign outlet_boundary to an ID not contained in NekRS boundary IDs.

    Specification(s): invalid_outlet_boundary_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Nek Standalone
  • 1.19.5The system shall throw an error if trying to act on only the NekRS solid mesh for side postprocessors.

    Specification(s): invalid_mesh_solid

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Nek Stochastic
  • 1.20.3The system shall error if trying to write stochastic input into a scratch space slot that has not been allocated

    Specification(s): exceed_available

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.20.4The system shall error if trying to write stochastic input into a scratch space slot that is needed for other physics coupling purposes.

    Specification(s): overlap_coupling

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.20.5The system shall error if the scratch space is not allocated via Cardinal for stochastic cases for standalone Nek runs. We only need to test this for the standalone case because the other two coupling classes (NekRSProblem, NekRSSeparateDomainProblem) automatically require scratch allocated from Cardinal.

    Specification(s): standalone_scratch

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.20.6The system shall error if there is a gap between the slots used for coupling (0 to n) and the slots needed for NekScalarValue, because this would mess up the host to device data transfer.

    Specification(s): lower_gap

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.20.7The system shall error if there is a gap between the slots used for NekScalarValues, because this would mess up the host to device data transfer.

    Specification(s): interior_gap

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.20.6

  • cardinal: Nek Warnings
  • 1.22.1MOOSE shall throw a warning if there is no temperature passive scalar solve in nekRS.

    Specification(s): no_temp_solve

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.22.2The system shall print a warning if both volume and boundary mesh mirror information is set on NekRSStandaloneProblem, since the combined specification of these quantities for NekRSMesh is exclusively used for CHT coupling + volume coupling.

    Specification(s): boundary_warning

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Neutronics
  • 1.23.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.23.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.23.12The system shall warn the user when there is a mismatch between the mesh mirror and the initial OpenMC DAGMC geometry.

    Specification(s): unmapped_cells

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.15The system shall error if attempting to apply density skinning without any fluid blocks ready to receive variable density.

    Specification(s): cannot_skin_solid

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.16The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.23The system shall error if the skinner user object is not the correct type

    Specification(s): wrong_uo

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.24The system shall warn if the graveyard is missing for OpenMC skinned models

    Specification(s): missing_graveyard

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.25The system shall error if applying a symmetry mapping to an OpenMC model which must already exactly match the mesh.

    Specification(s): no_symmetry

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.26The system shall error if loading properties from HDF5 for skinned problems

    Specification(s): properties

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.27The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.28The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.29The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.30The system shall error if the user attempts to map both CSG and DAGMC geometry to the MOOSE mesh.

    Specification(s): csg_with_dag_feedback

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.31The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.32The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.34The system shall give a warning when T+rho feedback is specified, but not all specified elements mapped into OpenMC

    Specification(s): warn_T_rho

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.35The system shall give a warning when T feedback is specified, but not all specified elements mapped into OpenMC

    Specification(s): warn_T

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.36The system shall give a warning when rho feedback is specified, but not all specified elements mapped into OpenMC

    Specification(s): warn_rho

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.53The system shall error if the user adds a duplicate variable with a name Cardinal reserves for OpenMC coupling.

    Specification(s): duplicate_variable

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.54The system shall error if trying to set density in a cell filled by a universe or lattice.

    Specification(s): nonmaterial_fluid

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.59The system shall error if the blocks and variables are not the same length

    Specification(s): wrong_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.60The system shall error if a sub-vector is empty

    Specification(s): empty

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.61The system shall error if an entry in density_variables is not of unity length

    Specification(s): multi_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.62The system shall error if trying to collate multiple density variables onto the same block due to undefined behavior

    Specification(s): block_already_used

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.63The system shall error if the blocks and variables are not the same length

    Specification(s): wrong_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.64The system shall error if a sub-vector is empty

    Specification(s): empty

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.65The system shall error if an entry in temperature_variables is not of unity length

    Specification(s): multi_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.66The system shall error if trying to collate multiple temperature variables onto the same block due to undefined behavior

    Specification(s): block_already_used

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.79The system shall warn the user if the identical cell fill is unused because all mapped cells are simple, material-fills.

    Specification(s): warn_unused

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.80The system shall error if trying to utilize identical cell fills but the filling cell IDs are not identical among the cells

    Specification(s): different_fill_universes

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.81The system shall error if trying to utilize identical cell fills for a non-solid block

    Specification(s): non_solid

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.82The system shall error if inconsistent settings are applied for the identical cell mapping

    Specification(s): inconsistent_map

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.83The system shall error if the single-increment applied to the tally cell contained material instances fails, such as when a TRISO universe is not being tallied.

    Specification(s): noncontinguous_triso_univs

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.85The system shall error if Cardinal tries to change the temperature of a given OpenMC cell more than once, since this indicates a problem with model setup.

    Specification(s): triso_lattice

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.91The system shall error if 'azimuthal_angle_boundaries' doesn't contain enough boundaries to form bins.

    Specification(s): not_enough_provided_bnds

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.93The system shall error if neither 'num_equal_divisions' or 'azimuthal_angle_boundaries' are provided.

    Specification(s): no_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.94The system shall error if both 'num_equal_divisions' and 'azimuthal_angle_boundaries' are provided.

    Specification(s): both_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.99The system shall error if there aren't enough energy boundaries to form an EnergyTally.

    Specification(s): not_enough_bnds

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.101The system shall error if no energy bins are provided.

    Specification(s): missing_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.102The system shall error if no energy bins are provided.

    Specification(s): both_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.107The system shall error if 'polar_angle_boundaries' doesn't contain enough boundaries to form bins.

    Specification(s): not_enough_provided_bnds

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.109The system shall error if neither 'num_equal_divisions' or 'polar_angle_boundaries' are provided.

    Specification(s): no_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.110The system shall error if both 'num_equal_divisions' and 'polar_angle_boundaries' are provided.

    Specification(s): both_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.113The system shall error if a non-existent filter is requested by a tally.

    Specification(s): missing_filter

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.114The system shall error if a filter is added when an OpenMCCellAverageProblem is not present.

    Specification(s): wrong_problem

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.117The system shall error if a filter with the id requested has not been added by the tallie xml file.

    Specification(s): missing_filter

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.118The system shall error if the user selects a spatial filter.

    Specification(s): spatial_filter_error

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.119The system shall warn the user if they have selected a functional expansion filter and set allow_expansion_filters = true.

    Specification(s): func_exp_warning

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.120The system shall error if the user selected a functional expansion filter without setting allow_expansion_filters = true.

    Specification(s): func_exp_error

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.122The system shall notify the user that the settings related to normalizing by global or local tallies are inconsequential for fixed source mode.

    Specification(s): normalize_unused

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.123The system shall error if the total tally sum does not match the system-wide value for fixed source simulations.

    Specification(s): missing_power

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.130The system shall error if the user tries to name only a partial set of the total tally scores.

    Specification(s): missing_name

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.131The system shall error if the user omits the required normalization tally for non-heating scores in eigenvalue mode

    Specification(s): missing_norm

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.139A warning shall be printed if any portion of the MOOSE solid blocks did not get mapped to OpenMC cells.

    Specification(s): partial_overlap_moose_union_msg

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.150The system shall error if a non-reaction rate score is provided to ElementOpticalDepthIndicator.

    Specification(s): not_rxn_rate

    Design: ElementOpticalDepthIndicator

    Issue(s): #1028

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.151The system shall error if a a reaction rate score is requested, but not available in a tally.

    Specification(s): missing_score

    Design: ElementOpticalDepthIndicator

    Issue(s): #1028

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.152The system shall error if the flux is not available in a tally.

    Specification(s): missing_flux

    Design: ElementOpticalDepthIndicator

    Issue(s): #1028

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.156The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.157The system shall error if attempting to directly tally on a MOOSE mesh that has a scaling not equal to 1.0.

    Specification(s): scaling

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.165Mesh tallies shall temporarily require disabled renumbering until capability is available

    Specification(s): disable_renumbering

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.166Mesh tallies shall error if the user attempts to apply a block restriction when using a mesh template.

    Specification(s): file_mesh_block_restrict

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.167Mesh tallies shall error if the user attempts to apply a block restriction with no blocks.

    Specification(s): block_restrict_no_blocks

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.174The system shall error if using incompatible tally estimator with a photon transport heating score.

    Specification(s): photon_heating

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.188The system shall correctly error if trying to use relaxation with a time-varying mesh.

    Specification(s): no_relax_with_fixed_mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.196The system shall error if the heating tallies are missing power from other parts of the problem.

    Specification(s): missing_pebble

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.203The system shall error if the symmetry mapper is not of the correct type

    Specification(s): wrong_uo

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.209The system shall error if the variable provided to FDTallyGradAux is not of type CONSTANT MONOMIAL_VEC.

    Specification(s): not_const_mon

    Design: FDTallyGradAux

    Issue(s): #1031

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.210The system shall error if a score is requested, but not available in a tally.

    Specification(s): missing_score

    Design: FDTallyGradAux

    Issue(s): #1031

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.211The 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

    Issue(s): #1031

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.220The system shall error if the user provides multiple tallies with overlapping scores.

    Specification(s): duplicate_scores

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.221The 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

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.225The system shall enforce correct trigger ignore zero length

    Specification(s): length_igore_zero

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.226The system shall ensure that the users provide values of trigger_ignore_zeros when the parameter is set.

    Specification(s): set_trigger_ignore_zero

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.235The system shall enforce correct trigger length

    Specification(s): length_trigger

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.23.236The system shall enforce correct trigger threshold length

    Specification(s): length_threshold

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Openmc Errors
  • 1.24.1The system shall error if the user specifies a block for coupling that does not exist.

    Specification(s): nonexistent_block

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.2The system shall error if an empty vector is provided for the blocks

    Specification(s): empty_block

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.3The system shall error if the MOOSE blocks and OpenMC cells don't overlap

    Specification(s): no_overlap

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.4The system shall print a warning if some MOOSE elements are unmapped

    Specification(s): skipping_moose_feedback

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.5The system shall error if one OpenMC cell maps to more than one type of feedback

    Specification(s): multiple_phases

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.6The system shall error if one OpenMC cell maps to multiple subdomains that don't all have the same tally setting

    Specification(s): multiple_tally_settings

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.7The system shall error if the user sets feedback blocks, but none of the elements map to OpenMC

    Specification(s): absent_solid_block

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.8The system shall error if the user enforces equal mapped tally volumes but the mapped volumes are not identical across tally bins

    Specification(s): unequal_volumes

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.9The system shall error if we attempt to set a density in a material that is repeated throughout our list of fluid cells.

    Specification(s): insufficient_materials

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.11The system shall error if attempting to pass temperature feedback to a lattice outer universe due to lack of instance support in OpenMC

    Specification(s): temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.12The system shall error if we attempt to set a density less than or equal to zero in OpenMC

    Specification(s): zero_density

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.13The system shall error if we attempt to set a density in a void OpenMC cell

    Specification(s): void_density

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.14The system shall error if attempting to extract the eigenvalue from an OpenMC run that is not run with eigenvalue mode.

    Specification(s): k

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.15The system shall error if attempting to extract the eigenvalue standard deviation from an OpenMC run that is not run with eigenvalue mode.

    Specification(s): k_std_dev

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.16The system shall error if attempting to set a k trigger for an OpenMC mode that doesn't have a notion of eigenvalues

    Specification(s): k_trigger

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.17The system shall error if an OpenMC object is used without the correct OpenMC wrapped problem.

    Specification(s): incorrect_problem

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.18The system shall error if a auxkernel that queries OpenMC data structures is not used with the correct variable type.

    Specification(s): incorrect_var_type

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.19The system shall error if attempting to set a negative number of active batches

    Specification(s): invalid_batches

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.20The system shall error if attempting to set a negative number of active batches

    Specification(s): invalid_max_batches

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.21The system shall error if a properties file is loaded but does not exist

    Specification(s): missing_properties

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.22The system shall error if using a skinner without a DagMC geometry

    Specification(s): no_dag

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.23The system shall error if both or none of the cell level options have been prescribed.

    Specification(s): duplicate_levels

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.24The system shall error if the specified coordinate level for a phase is within the maximum coordinate levels across the OpenMC domain, but invalid for the particular region of the geometry.

    Specification(s): fluid_too_high

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.25The system shall error if the specified coordinate level for finding a cell is greater than the maximum number of coordinate levels throughout the geometry.

    Specification(s): level_too_high

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.26The system shall error if a fluid material exists in non-fluid parts of the domain, because density would inadvertently be changed in other parts of the OpenMC model.

    Specification(s): material_duplication

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.27The system shall error if the mesh template is not provided in the same units as the Mesh.

    Specification(s): incorrect_scaling

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.28The system shall error if the mesh template does not exactly match the Mesh, such as when the order of mesh translations does not match the order of inputs in a CombinerGenerator.

    Specification(s): incorrect_order

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.29The system shall error if the mesh template does not exactly match the Mesh, such as when a totally different mesh is used (pincell versus pebbles).

    Specification(s): incorrect_file

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.30The system shall error if a tracklength estimator is attempted with unstructured mesh tallies, since this capability is not supported in libMesh.

    Specification(s): invalid_estimator

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.31The system shall error if a particular set of coordinates in the mesh translations does not have all requisite x, y, and z components.

    Specification(s): invalid_row

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.32The system shall error if attempting to run OpenMC in particle restart mode through Cardinal.

    Specification(s): volume

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.33The system shall error if attempting to run OpenMC in plotting mode through Cardinal.

    Specification(s): plot

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.34The system shall error if attempting to run OpenMC in volume mode through Cardinal.

    Specification(s): volume

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.35The system shall warn the user if they did not set the temperature range, protecting against seg faults within the tracking loop when trying to access nuclear data at temperatures that Cardinal wants to apply, but that weren't actually loaded at initialization.

    Specification(s): no_range

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.36The system shall error if attempting to use separate tallies when a global tally exists

    Specification(s): separate_tallies

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.37The system shall error if name and score are not the same length.

    Specification(s): invalid_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.38The system shall error if trigger and trigger_threshold are not simultaneously specified

    Specification(s): missing_threshold

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.39The system shall error if name has duplicate entries.

    Specification(s): duplicate_name

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.40The system shall error if score has duplicate entries.

    Specification(s): duplicate_score

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.41The system shall error if we attempt to set a temperature in OpenMC below the lower bound of available data when using the interpolation method.

    Specification(s): interpolation_min

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.24.42The system shall error if we attempt to set a temperature in OpenMC above the upper bound of available data when using the interpolation method.

    Specification(s): interpolation_max

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Postprocessors
  • 1.25.9The system shall error if trying to extract score information that does not exist

    Specification(s): nonexistent_score

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.13The system shall warn the user if dimensionalization is requested and cannot be performed, for
    1. usrwrk slot 0
    2. usrwrk slot 1
    3. usrwrk slot 2

    Specification(s): warn/u00, warn/u01, warn/u02

    Design: NekPointValue

    Issue(s): #1015#1016#1079

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.16The system shall error if trying to compute pressure drag on non-fluid NekRS boundaries

    Specification(s): invalid_mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.19System shall error if using an unsupported field with a side extrema postprocessor.

    Specification(s): invalid_field

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.21The system shall error if the requested usrwrk slot to integrate exceeds the number allocated

    Specification(s): invalid_slot

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.23The system shall error if trying to compute viscous drag on non-fluid NekRS boundaries

    Specification(s): invalid_mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.27System shall error if using an unsupported field with a volume extrema postprocessor.

    Specification(s): invalid_field

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.25.32System shall error if using an unsupported field with a mass flux weighted postprocessor.

    Specification(s): invalid_field

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • cardinal: Userobjects
  • 1.30.5The system shall error if the userobjects aren't derived from the correct base class.

    Specification(s): type_error

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.8The system shall error if there are zero contributions to a gap bin.

    Specification(s): bins_too_fine

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.19System shall error if user attemps to combine multiple bins that specify the same coordinate direction.

    Specification(s): conflicting_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.22System shall error if no points map to a spatial bin

    Specification(s): bins_too_fine

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.23The system shall error if the maximum temperature is lower than the minimum temperature for the skinner bins

    Specification(s): invalid_max_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.24The system shall error if the maximum density is lower than the minimum density for the skinner bins

    Specification(s): invalid_max_density

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.25The system shall error if the temperature is below the minimum bin bound

    Specification(s): too_low_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.26The system shall error if the temperature is above the maximum bin bound

    Specification(s): too_high_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.27The system shall error if the density is below the minimum bin bound

    Specification(s): too_low_density

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.28The system shall error if the density is above the maximum bin bound

    Specification(s): too_high_density

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.29The system shall error if the skinned mesh does not contain tetrahedral elements

    Specification(s): invalid_mesh

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.30The system shall error if the outer graveyard surface is not larger than the inner graveyard surface

    Specification(s): invalid_graveyard_scales

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.31The system shall error if the specified temperature auxiliary variable cannot be found

    Specification(s): no_aux_temp

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.32The system shall error if the specified density auxiliary variable cannot be found

    Specification(s): no_aux_density

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.33The system shall error if the specified density and temperature auxiliary variables are the same

    Specification(s): overlap_t_rho

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.34The system shall error if trying to run in distributed mesh mode

    Specification(s): distributed

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.35The system shall error if the material_names provided to the skinner do not match the required length

    Specification(s): incorrect_material_names

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.58The system shall error if the requirements for a binning variable type are violated.

    Specification(s): wrong_type

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.61The system shall error if trying to change nuclide densities for a non-existing material ID.

    Specification(s): nonexistent_id

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.62The system shall error if trying to add a nuclide not accessible in the cross section library.

    Specification(s): nonexistent_nuclide

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.67The system shall error if inconsistent lengths for names and densities are provided.

    Specification(s): different_length

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.68The system shall error if
    1. trying to edit a non-existant tally
    2. trying to add a nuclide not accessible in the cross section library
    3. trying to add an invalid score to a tally
    4. the filter referenced by an OpenMCFilterEditor via ID does not exist and is not flagged for creation
    5. an OpenMCDomainFilter editor exists with the same filter ID but a different filter type
    6. more than one OpenMCDomainFilterEditor eixsts with the same filter ID
    7. more than one OpenMCTallyEditor eixsts with the same tally ID
    8. 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.30.79The system shall error if an invalid boundary ID is specified

    Specification(s): invalid_boundary

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.83The system shall error if the userobjects aren't derived from the correct base class.

    Specification(s): type_error

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.84The system shall error if the userobjects aren't listed in the correct order in the input file.

    Specification(s): ordering_error

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.86System shall error if user attemps to combine multiple bins that specify the same coordinate direction.

    Specification(s): conflicting_bins

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.88System shall error if a side user object is provided to a volume binning user object.

    Specification(s): wrong_type

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.89System shall error if attempting to use a normal velocity component with a user object that does not have normals defined

    Specification(s): invalid_component

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.92The system shall error if the rotation axis is not perpendicular to the symmetry normal

    Specification(s): non_perpendicular_axis

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.93The system shall error if the rotation angle does not describe a valid symmetry wedge

    Specification(s): non_integer_angle

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.95The system shall warn the user if encountering volume calculations needing instance-level granularity, since this is not available yet in OpenMC itself.

    Specification(s): warn_instances

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.98The system shall error if an invalid bounding box is specified for volume calculations

    Specification(s): invalid_box

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.30.101The system shall error if trying to view stochastic volumes without the stochastic volume calculation having been created.

    Specification(s): missing_vol

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException