Reconstructed Discontinuous Galerkin Failure Analysis Report

Introduction

The FAR for the Reconstructed Discontinuous Galerkin module describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.

Dependencies

The Reconstructed Discontinuous Galerkin module is developed using MOOSE and can itself be based on various MOOSE modules, as such the FAR for the Reconstructed Discontinuous Galerkin module is dependent upon the following documents.

• Framework Failure Analysis Report

Failure Analysis Requirements

The following is a complete list for all the requirements related to failure analysis for the Reconstructed Discontinuous Galerkin module.

• rdg: Actions
• 15.2.2The system shall report an error if the supplied order of scalar auxiliary variable is of an unknown order.

  Specification(s): invalid_order_high

  Design: AuxVariables System

  Issue(s): #960#2294#4668

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Adaptivity
• 15.3.2The system shall emit a warning if the block restriction of the marker is larger than that of its indicator.

  Specification(s): mismatch

  Design: Adaptivity System

  Issue(s): #14531

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Auxkernels
• 15.4.2The system shall throw an error when finite volume variables are used to compute a volumetric advection flux, as it is currently not supported.

  Specification(s): finite_volume

  Design: AdvectiveFluxAux

  Issue(s): #24289

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.5The system shall issue an error when evaluating a parsed expression with array variable values if the number of components of the variable and coupled variables do not match.

  Specification(s): array_parsed_aux_error

  Design: ArrayParsedAux

  Issue(s): #20818

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.11The system shall report a reasonable error when copying standard variables into the components of an array variable when
  1. the variables have inconsistent sizes or
  2. when the variables have inconsistent types.

  Specification(s): error/size, error/type

  Design: BuildArrayVariableAux

  Issue(s): #16402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.4.22The system shall report an error if a boundary restricted elemental auxiliary kernel is evaluated on an element with multiple boundary sides

  Specification(s): boundary_restricted_error_test

  Design: AuxKernels System

  Issue(s): #5061

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.50The system shall error if a boundary auxiliary kernel attempts to populate a lower-dimensional auxiliary variable when
  1. the mesh lower-dimensional block restriction is not a superset of the boundary, or when
  2. the variable lower-dimensional block restriction is not a superset of the boundary.

  Specification(s): non_superset/mesh_blocks, non_superset/variable_blocks

  Design: AuxKernels System

  Issue(s): #26592

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.4.60Writing to auxiliary variables shall be limited to use from AuxKernels, ElementUserObjects, or NodalUserObjects.

  Specification(s): multi_update_error

  Design: AuxKernels SystemCoupleable

  Issue(s): #22563

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.62Writing to auxiliary variables shall be limited to use from AuxKernels, ElementUserObjects, or NodalUserObjects using variable values.

  Specification(s): multi_update_deprecated_error

  Design: AuxKernels SystemCoupleable

  Issue(s): #22563

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.63The writing to auxiliary variables shall enforce nodal/elemental consistency between the kernel variable and the writable variables.

  Specification(s): multi_update_deprecated_error2

  Design: AuxKernels SystemCoupleable

  Issue(s): #22563

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.64The writableCoupledValue API can only act on AuxVariables.

  Specification(s): multi_update_deprecated_error3

  Design: AuxKernels SystemCoupleable

  Issue(s): #22563

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.65The writing to auxiliary variables shall error out if a constant value is passed in as variable name.

  Specification(s): multi_update_deprecated_error4

  Design: AuxKernels SystemCoupleable

  Issue(s): #22563

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.69The MOOSE auxiliary system shall check compatibility between primary and writable coupled variables.

  Specification(s): multi_update_elem_family_error

  Design: AuxKernels SystemCoupleable

  Issue(s): #22563

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.79The system shall report an error if
  1. functor symbols parameter does not have the same length as functor names parameter
  2. functor symbols parameter contains 'x', 'y', 'z', or 't' when coordinates and time parameters are already in use
  3. functor symbols cannot overlap with coupled variable names
  4. functor names parameter contains 'x', 'y', 'z', or 't' when coordinates and time parameters are already in use
  5. functor names cannot overlap with coupled variable names
  6. an invalid function is provided.

  Specification(s): errors/functor_symbol_length, errors/invalid_functor_symbol, errors/functor_symbol_variable_name_overlap, errors/invalid_functor_name, errors/functor_name_variable_name_overlap, errors/expression

  Design: ParsedAux

  Issue(s): #21244

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234
• 15.4.82The system shall be able to detect wrong implicit dependencies of a function value postprocessor that depends on a function which depends on a second postprocessor.

  Specification(s): pp_depend_indirect_wrong

  Design: AuxKernels SystemPostprocessor System

  Issue(s): #2848#16354

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.86The system shall be capable of initializing an auxiliary variable from an existing solution
  1. from data generated by a simulation
  2. and loaded using location,
  3. using a direct degree-of-freedom copy for identical meshes,
  4. with scaling the supplied data,
  5. and that errors if data for the supplied variable is not found.

  Specification(s): aux/build, aux/test, aux/direct, aux/solution_aux_scale, aux/output_error

  Design: SolutionAuxSolutionUserObject

  Issue(s): #1891

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  406234406406406
• 15.4.97The SolutionAux object shall produce an error if the 'from_variable' parameter is not set and the supplied UserObject has multiple variables.

  Specification(s): multiple_input_error

  Design: SolutionAuxSolutionUserObject

  Issue(s): #1891

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.104Error an AuxKernel object attemps to couple to the time derivative of an auxiliary variable.

  Specification(s): coupled_aux_time_derivative_to_aux

  Design: AuxKernels SystemKernels SystemAuxVariable

  Issue(s): #442

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.4.108The system shall report an error if
  1. a time derivative is requested from a functor material property for which the functor time derivative not implemented
  2. a time derivative is requested but the variable is a nodal variable which is currently unsupported
  3. a time derivative for a finite element variable is to be saved in a finite volume variable
  4. a time derivative for a finite volume variable is to be saved in a finite element variable

  Specification(s): errors/not_implemented_functor_matprop, errors/not_a_nodal_kernel, errors/implicit_fe_fv_conversion, errors/implicit_fv_fe_conversion

  Design: AuxKernels SystemKernels SystemAuxVariableFunctions SystemMaterials System

  Issue(s): #442#762

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.4.110The system shall report an error if
  1. a second time derivative is requested but the variable is a nodal variable which is currently unsupported, and
  2. a second time derivative for a finite element variable is requested to be stored in a finite volume variable.

  Specification(s): errors/not_a_nodal_kernel, errors/implicit_fe_fv_conversion

  Design: AuxKernels SystemKernels SystemAuxVariableFunctions SystemMaterials System

  Issue(s): #442#762

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.4.120The system shall report a reasonable error when trying to sample element volumes into a non constant monomial variable

  Specification(s): incorrect_type

  Design: VolumeAux

  Issue(s): #19307

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Bcs
• 15.7.31The system shall be able to determine if a non-scalable algorithm is being used for ghosting boundaries.

  Specification(s): check

  Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

  Issue(s): #15501

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.7.58The system shall produce an error within the PeriodicDistanceAux object when a point is provided that is outside the mesh domain.

  Specification(s): auto_wrap_2d_test_error_check

  Design: Periodic System

  Issue(s): #935#1530

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.7.56

  234

• rdg: Bounds
• 15.8.5The system shall
  1. emit a warning if a variational inequalities (VI) solver is not found when the bounds system is used.
  2. error if an unsupported variable type is provided to the constant bounds kernel
  3. error if the type of the dummy auxiliary variable does not match the bounded variable.

  Specification(s): exceptions/solver, exceptions/bounded_variable_type, exceptions/mismatch_dummy

  Design: ConstantBounds

  Issue(s): #14946

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234234234

• rdg: Controls
• 15.10.8The Control system shall error if an attempt to alter a non-controllable parameter is performed.

  Specification(s): non_controllable_error

  Design: Controls System

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.10The Control system shall error if an unknown parameter is supplied for control.

  Specification(s): no_param_found

  Design: Controls System

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.11The Control system shall error if a thread id greater than the number of threads available is supplied when retrieving a Control object.

  Specification(s): tid_warehouse_error

  Design: Controls System

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  10
• 15.10.12The Control system shall error if an attempt is made to disable the Executioner.

  Specification(s): disable_executioner

  Design: Controls System

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.13The Control system shall error if an invalid control name is supplied to the Control dependency resolution procedure.

  Specification(s): non_existing_dependency

  Design: Controls System

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.17The system shall forbid specifying parameters when reading a neural network from a torchscript file.

  Specification(s): invalid-torchscript-error

  Design: LibtorchNeuralNetControl

  Issue(s): #19571

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  18
• 15.10.27The MOOSE control system shall be capable of restricting parameters to be controlled for specific execution flags.

  Specification(s): error

  Design: Controls System

  Issue(s): #12576

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.46The TimePeriod object shall error when used with a steady state problem.

  Specification(s): steady_error

  Design: TimePeriod

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.47The TimePeriod object shall error when the start and end time parameters are not the same length.

  Specification(s): start_end_size_mismatch

  Design: TimePeriod

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.48The TimePeriod object shall error when start and end time parameters differ in length than the supplied object list.

  Specification(s): time_disable_size_mismatch

  Design: TimePeriod

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.49The TimePeriod object shall error when a list of objects to control is omitted.

  Specification(s): enable_disable_not_set

  Design: TimePeriod

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.50The TimePeriod object shall error when start time is greater than the end time.

  Specification(s): start_greater_than_end_error

  Design: TimePeriod

  Issue(s): #5676

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.10.64The system shall report a reasonable error when interacting with the REST API when
  1. setting a controllable parameter that does not exist
  2. getting a postprocessor that does not exist
  3. setting a controllable parameter whose type is not supported
  4. setting a controllable parameter with an incompatible JSON type
  5. setting a controllable parameter with a type that does not match

  Specification(s): errors/set_controllable_no_exist, errors/postprocessor_no_exist, errors/set_controllable_unregistered_type, errors/set_controllable_bad_convert_json, errors/set_controllable_vector_non_array

  Design: Controls SystemWebServerControl

  Issue(s): #23359#27909

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  232232232232232
• 15.10.65The system that supports controlling parameters via a REST API should report a reasonable error when
  1. a parameter was not provided that specifies where the server should listen
  2. both a port and a file were specified to listen on

  Specification(s): param_errors/no_port_and_socket, param_errors/port_and_socket

  Design: Controls SystemWebServerControl

  Issue(s): #23359#27909

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234

• rdg: Dampers
• 15.12.1The system shall include the ability to reduce the change in nonlinear residual based on a maximum value on elements.

  Specification(s): bounding_value_max

  Design: BoundingValueElementDamper

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.2The system shall include the ability to reduce the change in nonlinear residual based on a minimum value on elements.

  Specification(s): bounding_value_min

  Design: BoundingValueElementDamper

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.3The system shall include the ability to reduce the change in nonlinear residual based on a maximum value on nodes.

  Specification(s): bounding_value_max

  Design: BoundingValueNodalDamper

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.4The system shall include the ability to reduce the change in nonlinear residual based on a minimum value on nodes.

  Specification(s): bounding_value_min

  Design: BoundingValueNodalDamper

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.6The Damper system shall use the minimum of NodalDamper and ElementDamper, when the later computes the minimum.

  Specification(s): interacting_node_elem1

  Design: BoundingValueElementDamper

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.7The Damper system shall use the minimum of NodalDamper and ElementDamper, when the former computes the minimum.

  Specification(s): interacting_node_elem2

  Design: BoundingValueElementDamper

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.10The system shall give an informative error if user code requests a variable from the warehouse with a bad key.

  Specification(s): bad_key

  Design: MaxIncrement

  Issue(s): 5509fd360a4ca128a642b1c6603fa3f5205c05d8

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.12.13The Damper system shall error if the damping value is below a minimum.

  Specification(s): min_general_damping

  Design: Dampers System

  Issue(s): #7856

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: DGKernel Objects
• 15.13.18The system shall report an error if the triad of dg kernels, adaptivity, and stateful properties are used together.

  Specification(s): error_stateful_dg_adaptivity

  Design: DGKernels System

  Issue(s): #10977

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Dirackernels
• 15.14.3The system shall behave accordingly if the added point is not found, when point_not_found_behavior is set to
  1. ERROR or
  2. WARNING.

  Specification(s): point_not_found/error, point_not_found/warning

  Design: DiracKernels System

  Issue(s): #17561

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234234
• 15.14.8DiracKernel objects shall report an error if a material property from a previous time step is requested:
  1. one step back, and
  2. two steps back.

  Specification(s): check_errors/old, check_errors/older

  Design: DiracKernels System

  Issue(s): #7720#2379

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.14.12The DiracKernel system shall report an error if a location does not correspond with the supplied element id.

  Specification(s): point_caching_error

  Design: DiracKernels System

  Issue(s): #2364

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.14.13The system shall support point sources with locations and values given by a Reporter
  1. in a steady state 2D problem, reading data from a reporter and reproducing the constantPointSource.
  2. in a steady state 2D problem, reading data from a vectorPostProcessor and reproducing the constantPointSource.
  3. in a steady state 2D problem, reading data from a reporter with duplicate points and reproducing the constantPointSource.
  4. in steady state 3D problem, reproducing the constantPointSource.
  5. in a transient problem with the vpp source value changing as the vpp changes.
  6. shall report an error if the input arrays are not the same size.
  7. shall report an error if the input arrays have duplicated values.

  Specification(s): reporterPointSource/2dConstantReporter, reporterPointSource/2dConstantVPP, reporterPointSource/2dConstReporterDuplicates, reporterPointSource/3dConstant, reporterPointSource/2dTransient, reporterPointSource/wrong_size_error, reporterPointSource/duplicate_error

  Design: ReporterPointSource

  Issue(s): #15831#18528

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunExceptionCSVDiff

  406406406234406234406

• rdg: Executioners
• 15.15.24The system shall provide informative warnings when
  1. fixed_point_rel_tol is set by the user and disable_fixed_point_residual_norm_check is set to true.
  2. fixed_point_abs_tol is set by the user and disable_fixed_point_residual_norm_check is set to true.
  3. fixed_point_force_norms is set by the user and disable_fixed_point_residual_norm_check is set to true.

  Specification(s): warnings/rel_tol, warnings/abs_tol, warnings/force_norms

  Design: TaggingInterface

  Issue(s): #26285

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234

• rdg: Executors
• 15.16.2The system shall report an error if the Executor system contains an infinite cycle

  Specification(s): cycle

  Design: Executor

  Issue(s): #5229#18180

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.16.3The system shall only have one root node in the Executor tree

  Specification(s): multi_root

  Design: Executor

  Issue(s): #5229#18180

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Functions
• 15.18.11The Material system shall error out if the number of functions supplied does not match the size of the vector function material properties.

  Specification(s): vector_error

  Design: GenericFunctionVectorMaterial

  Issue(s): #18372

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.13The system shall include the ability to create functions from image files that errors if
  1. an unsupported file type is provided;
  2. if an invalid component value is supplied;
  3. if an invalid filename is provided; and
  4. the system is not configured with the correct dependencies.

  Specification(s): errors/file_suffix, errors/component, errors/invalid_file, errors/no_vtk

  Design: ImageFunctionImageMesh

  Issue(s): #5927

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  17817817856
• 15.18.32The LinearCombinationFunction shall report an error if the parameters listing the functions differs in size than the list of coefficients.

  Specification(s): except1

  Design: LinearCombinationFunction

  Issue(s): #4828

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.43The ParsedFunction object shall fail with a human readable error if a vals entry is supplied that is neither a valid postprocessor, scalar variable, function, or real number.

  Specification(s): vals_error

  Design: ParsedFunction

  Issue(s): #14169

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.44The system should error if a field variable is passed into a parsed function object, as this capability is currently not supported.

  Specification(s): nl_vars

  Design: ParsedFunction

  Issue(s): #15523

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.49The system shall report an error if
  1. parameters meant for loading data from file are passed for a function loading data differently,
  2. or if parameters meant for loading data from JSON are passed for a function loading data differently.

  Specification(s): errors/param_meant_for_file, errors/param_meant_for_json

  Design: PiecewiseConstant

  Issue(s): #2272#25058

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.18.51The system shall report an error if
  1. if the CSV reader object and the function expect the CSV data to be ordered differently
  2. if the desired column number in the CSV file is higher than the number of columns in the file
  3. if the data saught exceeds the row number in the CSV file
  4. if the number of blocks specified to a CSV reader reading block-data is 0
  5. if the number of nearest-neighbor regions specified to a CSV reader reading nearest-neighbor-region-data is 0

  Specification(s): errors/read_type, errors/num_columns, errors/num_rows, errors/zero_blocks, errors/zero_voronoi

  Design: PiecewiseConstantFromCSV

  Issue(s): #19109

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234
• 15.18.52The system shall issue a warning if
  1. if the desired column number in the CSV file is known to be a column holding point coordinates
  2. if the data file contains more points/rows than the reader needs

  Specification(s): warnings/num_columns, warnings/too_much_data_in_file

  Design: PiecewiseConstantFromCSV

  Issue(s): #19109

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.18.57The PiecewiseMultilinear object will error if the supplied file fails to open.

  Specification(s): except1

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.58The PiecewiseMultiInterpolation object shall error if the supplied data is not monotonically increasing.

  Specification(s): except2

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.59The PiecewiseMultiInterpolation object shall error if the number of requested functions differ than the number available from the file.

  Specification(s): except3

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.60The PiecewiseMultiInterpolation errors if the axes supplied are not independent.

  Specification(s): except4

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.61The PiecewiseMultilinear shall error if the axis lines are not located in the supplied data.

  Specification(s): except5

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.18.79The SolutionFunction object shall error if a variable that does not exist is requested.

  Specification(s): nonexistent_var_err

  Design: SolutionFunction

  Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Fvbcs
• 15.21.5The system shall report an error if a finite volume flux boundary condition, in this case a finite volume Neumann boundary condition, is used inside the domain.

  Specification(s): fvbcs_internal

  Design: FVNeumannBC

  Issue(s): #16882

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.21.6The system shall report an error if a finite volume flux boundary condition is used on a mesh element face that is not connected to an element with the corresponding finite volume variable.

  Specification(s): fvbcs_disconnected_from_variable

  Design: FVNeumannBC

  Issue(s): #16882

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Fviks
• 15.23.5The system shall report an error if a user specified variable on the 1st side of an interface does not actually exist on the 1st side.

  Specification(s): run_except1

  Design: FVInterfaceKernels System

  Issue(s): #17087

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.23.6The system shall report an error if a user specified variable on the 2nd side of an interface does not actually exist on the 2nd side.

  Specification(s): run_except2

  Design: FVInterfaceKernels System

  Issue(s): #17087

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.23.7The system shall report an error if a user does not specify a variable on the 2nd side of an interface, leading the system to assume that the variable on the 1st side of the interface should be used on the 2nd side, and the variable on the 1st side does not exist on the 2nd side.

  Specification(s): run_except3

  Design: FVInterfaceKernels System

  Issue(s): #17087

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Fvkernels
• 15.24.11The system shall report an error if conflictingly told to avoid and execute a flux kernel on the same boundary.

  Specification(s): overlapping_lists

  Design: Finite Volume Design Decisions in MOOSE

  Issue(s): #20695

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.24.20The system shall suggest that the user add a finite volume variable if a finite volume object cannot retrieve one

  Specification(s): var_except

  Design: Finite Volume Design Decisions in MOOSE

  Issue(s): #14549

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Geomsearch
• 15.25.56The system shall report an error in the penetration locator system if penetration is not detected.

  Specification(s): never_warning

  Design: GapValueAuxMesh System

  Issue(s): #3901

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.25.52

  234

• rdg: Globalparams
• 15.26.2The system shall report an error if a private / suppressed parameter is set in the input file.

  Specification(s): test_suppress_ignore

  Design: Parser

  Issue(s): #437#8761

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148

• rdg: Hdgkernels
• 15.27.5The system shall error if hybridized discontinuous Galerkin kernels and boundary conditions operate on a different variable set.

  Specification(s): different_vars

  Design: DiffusionHDGKernelDiffusionHDGDirichletBCDiffusionHDGPrescribedGradientBC

  Issue(s): #26406

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.27.6The system shall error if a user attempts to use a non-unity scaling factor for a variable in a hybridized Discontinuous Galerkin discretization.

  Specification(s): bad_scaling_factor

  Design: DiffusionHDGKernelDiffusionHDGDirichletBCDiffusionHDGPrescribedGradientBC

  Issue(s): #26406

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Ics
• 15.28.2The system shall report an error if the wrong number of components are provided in a constant initial condition for array variables.

  Specification(s): size_error

  Design: ArrayConstantIC

  Issue(s): #6881

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.4The system shall report an error if the wrong number of components are provided in a functionalized initial condition for array variables.

  Specification(s): size_error

  Design: ArrayFunctionIC

  Issue(s): #6881

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.8The system shall report an error when multiple initial conditions are applied to the same boundary.

  Specification(s): ics_on_same_boundary

  Design: ICs System

  Issue(s): #6580

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.9The system shall report an error when multiple initial conditions are applied to the same subdomain.

  Specification(s): ics_on_same_block

  Design: ICs System

  Issue(s): #6580

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.10The system shall report an error when a global initial conditions overlap on the same variable.

  Specification(s): ics_on_same_block_both_global

  Design: ICs System

  Issue(s): #6580

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.11The system shall report an error when a global and subdomain restricted initial conditions overlap on the same variable.

  Specification(s): ics_on_same_block_first_global

  Design: ICs System

  Issue(s): #6580

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.32The system shall report an error if
  1. the postprocessor does not have execute_on initial
  2. the postprocessor for normalization is zero

  Specification(s): errors/missing_initial, errors/zero_integral

  Design: IntegralPreservingFunctionIC

  Issue(s): #19476

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.28.40The system shall report an error if
  1. a solution is to be loaded at a block that does not exist in the source file.

  Specification(s): errors/missing_block

  Design: SolutionICSolutionUserObject

  Issue(s): #24581

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.45The system shall report an error if the 'function' and 'function_x' parameters are both set within the VectorFunctionIC object.

  Specification(s): comp_x_error

  Design: VectorConstantIC

  Issue(s): #13309

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.46The system shall report an error if the 'function' and 'function_y' parameters are both set within the VectorFunctionIC object.

  Specification(s): comp_y_error

  Design: VectorConstantIC

  Issue(s): #13309

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.28.47The system shall report an error if the 'function' and 'function_z' parameters are both set within the VectorFunctionIC object.

  Specification(s): comp_z_error

  Design: VectorConstantIC

  Issue(s): #13309

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: InterfaceKernel Objects
• 15.30.35The system shall report an error if the triad of interface kernels, adaptivity, and stateful properties are used together.

  Specification(s): error_stateful_ik_adaptivity

  Design: InterfaceKernels System

  Issue(s): #10977

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Interfaces
• 15.31.6The system shall report a reasonable error when retrieving a property of the mesh when the underlying types differ

  Specification(s): get_wrong_type

  Design: MeshMetaDataInterface

  Issue(s): #23447

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.31.7The system shall report a reasonable error when requesting a Postprocessor from a parameter when
  1. the parameter is not found,
  2. the parameter does not represent a Postprocessor,
  3. the parameter is a single Postprocessor value and a greater index than zero is requested,
  4. and the parameter is a single Postprocessor value and a greater index than zero is requested.

  Specification(s): param_errors/missing_parameter, param_errors/bad_parameter_type, param_errors/out_of_range_single, param_errors/out_of_range_vector

  Design: PostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.31.8The system shall report a reasonable error when requesting a Postprocessor name from a parameter in which the postprocessor is a default value and not a name.

  Specification(s): name_for_default_error

  Design: PostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.31.9The system shall report a reasonable error when it is too early to request if a postprocesor exists
  1. by parameter name and
  2. by Postprocessor name.

  Specification(s): has_errors/param, has_errors/name

  Design: PostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.31.10The system shall report a reasonable error when requesting a Postprocessor value
  1. by parameter and the Postprocessor does not exist and
  2. by Postprocessor name and the Postprocessor does not exist.

  Specification(s): missing_errors/by_param, missing_errors/by_name

  Design: PostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.31.21The system shall report a reasonable error when requesting a Reporter value from a parameter when
  1. the parameter is not found and
  2. the parameter does not represent a Reporter

  Specification(s): param_errors/missing_parameter, param_errors/bad_parameter_type

  Design: ReporterInterface

  Issue(s): #17512#17605

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.31.22The system shall report a reasonable error when requesting a Reporter value when a Reporter with the same name exists with a different type.

  Specification(s): other_type_requested_error

  Design: ReporterInterface

  Issue(s): #17512#17605

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.31.23The system shall report a reasonable error when requesting a Reporter value
  1. by parameter and the Reporter value does not exist and
  2. by Reporter name and the Reporter value does not exist.

  Specification(s): missing_errors/param, missing_errors/name

  Design: ReporterInterface

  Issue(s): #17512#17605

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.31.24The system shall report a reasonable error when it is too early to request if a Reporter value exists
  1. by parameter name and
  2. by Reporter name.

  Specification(s): has_errors/param, has_errors/name

  Design: ReporterInterface

  Issue(s): #17512#17605

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.31.25The system shall report a reasonable error when requesting a UserObject when
  1. getting the name from a parameter and the parameter is not found,
  2. getting the name from a parameter and the parameter does not represent a name,
  3. getting the name from a parameter and the user object is not found,
  4. getting the UserObject by name and the user object is not found,
  5. getting the name from a paremeter and the provided object is not of the correct type, and
  6. getting the UserObject by name and the provided object is not of the correct type.

  Specification(s): errors/missing_parameter, errors/bad_parameter_type, errors/not_found_by_param, errors/not_found_by_name, errors/bad_cast, errors/bad_cast_by_name

  Design: UserObjectInterface

  Issue(s): #17446#17512#17949

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234
• 15.31.27The system shall report a reasonable error when requesting a VectorPostprocessor value from a parameter when
  1. the parameter is not found and
  2. the parameter does not represent a VectorPostprocessor.

  Specification(s): param_errors/missing_parameter, param_errors/bad_parameter_type

  Design: VectorPostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.31.28The system shall report a reasonable error when it is too early to request if a VectorPostprocessor exists
  1. by vector name and parameter name,
  2. by vector name and VectorPostprocessor name,
  3. by parameter name, and
  4. and by VectorPostprocessor name.

  Specification(s): has_errors/value_param, has_errors/value_name, has_errors/param, has_errors/name

  Design: VectorPostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.31.29The system shall report a reasonable error when requesting a VectorPostprocessor value
  1. by parameter and the VectorPostprocessor does not exist,
  2. by parameter and the VectorPostprocessor exists but the requested vector does not,
  3. by VectorPostprocessor name and the VectorPostprocessor does not exist, and
  4. by VectorPostprocessor name and the VectorPostprocessor exists but the requested vector does not.

  Specification(s): missing_errors/by_param, missing_errors/by_param_vector, missing_errors/by_name, missing_errors/by_name_vector

  Design: VectorPostprocessorInterface

  Issue(s): #17512

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234

• rdg: Kernels
• 15.32.19The system shall allow the user to override the automated generation of a full coupling matrix when doing global AD indexing, which for this test results in a new nonzero allocation because there is off-diagonal coupling.

  Specification(s): trust_user_and_then_error

  Design: Coupleable

  Issue(s): #16396

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.36The system shall report an error if a user assigns a scalar and requests evaluation of scalar residuals, but does not override the quadrature point residual evaluation routine in their derived class.

  Specification(s): override

  Design: ADScalarLMKernel

  Issue(s): #22174

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.66The system shall report an error when a parsed function expression contains quote characters.

  Specification(s): parsed_func_error_check

  Design: BodyForce

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.32.63

  234
• 15.32.92The system shall issue an error for unsupported mesh adaptation with hybrid finite element method (HFEM) calculations.

  Specification(s): robin_adpatation

  Design: DGKernels System

  Issue(s): #17447

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.122The system shall report an error if a derived object uses scalars and computes scalar residuals but does not override the quadrature point residual calculation routine.

  Specification(s): override

  Design: ScalarLMKernel

  Issue(s): #22174

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.127We shall not be able to solve a problem where the physics Jacobians are very large compared to the jacobian from a Dirichlet BC (unity)

  Specification(s): cant-solve-poorly-scaled

  Design: FEProblemSolve

  Issue(s): #12601

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.130We shall not be able to solve a problem where the physics has large changes over time if we only scale once

  Specification(s): cant-solve-large-transient-changes

  Design: FEProblemSolve

  Issue(s): #12601

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.134The system shall report an error if the volumetric residual calculation is not assigned an associated vector within the numerical solving routine.

  Specification(s): test

  Design: Kernels System

  Issue(s): #9669

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.135Time kernel requires a transient executioner

  Specification(s): bad_transient

  Design: TaggingInterface

  Issue(s): #9669

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.136The kernel can be only assigned to the existing vector tags in the system

  Specification(s): bad_vector_tag

  Design: TaggingInterface

  Issue(s): #9669

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.137The kernel can be only assigned to the existing matrix tags in the system

  Specification(s): bad_matrix_tag

  Design: TaggingInterface

  Issue(s): #9669

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.156The system shall report an error if the 'function' and 'function_x' parameters are both set when defining a vector function Dirichlet boundary condition.

  Specification(s): comp_error

  Design: VectorBodyForce

  Issue(s): #13309

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.32.157The system shall report an error if the 'function' and 'function_x' parameters are both set within the ADVectorFunctionDirichletBC object.

  Specification(s): ad_comp_error

  Design: ADVectorFunctionDirichletBC

  Issue(s): #13309

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Make Install
• 15.34.2The system shall support the ability to "install" inputs:
  1. from a pre-determined user-readable location;
  2. copied using a MOOSE-based binary;
  3. verifying a successful copy operation;
  4. able to report an error if overwriting may occur using a MOOSE-based binary;
  5. able to link a binary to an installed location;
  6. able to successfully launch the TestHarness using a MOOSE-based binary;
  7. and cleaned up from a user-readable location.

  Specification(s): test_copy_install/setup_fake_test_structure, test_copy_install/copy_tests, test_copy_install/check_files, test_copy_install/copy_warn_overwrite, test_copy_install/link_exec_installed, test_copy_install/run, test_copy_install/tear_down

  Design: MooseApp

  Issue(s): #19022

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunCommandRunExceptionCheckFilesRunApp

  232232232232414232232

• rdg: Markers
• 15.35.14It shall not be possible to specify Markers to run on the displaced mesh.

  Specification(s): displaced_error

  Design: Markers System

  Issue(s): #11430

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.35.18The marker shall create an error if the coordinate vectors are not all the same size

  Specification(s): wrong_size_error

  Design: Markers SystemReporterPointMarker

  Issue(s): #18886

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Materials
• 15.36.14ADPiecewiseLinearInterpolationMaterial shall throw an error if x, y, and xy_data are all specified

  Specification(s): test_err1

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.36.12

  234
• 15.36.15ADPiecewiseLinearInterpolationMaterial shall throw an error if x and xy_data are both specified

  Specification(s): test_err2

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.36.14

  234
• 15.36.16ADPiecewiseLinearInterpolationMaterial shall throw an error if x and y vectors are different lengths

  Specification(s): test_err3

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.36.15

  234
• 15.36.17ADPiecewiseLinearInterpolationMaterial shall throw an error if xy_data vector is not a multiple of two

  Specification(s): test_err4

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.36.16

  234
• 15.36.26Duplicate positions in the coupled variable mapping to function parameters shall raise an error.

  Specification(s): order_duplicate_error

  Design: CoupledValueFunctionMaterial

  Issue(s): #20193

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.27A number of positions in mapping to function parameters that does not match the number of coupled variable shall raise an error.

  Specification(s): order_count_error

  Design: CoupledValueFunctionMaterial

  Issue(s): #20193

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.29The system shall issue an error when multiple materials properties with the same name are declared on the same block.

  Specification(s): error

  Design: Materials System

  Issue(s): #6533

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.34The system shall issue an error when required derivative materials that are retrieved are never declared.

  Specification(s): warn

  Design: DerivativeMaterialInterface

  Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.35The system shall handle a bad evaluation by
  1. passing a silent nan.
  2. throwing a warning and passing a silent nan.
  3. throwing an error.
  4. throwing an exception.

  Specification(s): bad_evaluation/nan, bad_evaluation/warning, bad_evaluation/error, bad_evaluation/exception

  Design: DerivativeMaterialInterface

  Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234234234234
• 15.36.36The system shall handle a bad evaluation when using JIT by
  1. passing a silent nan.
  2. throwing a warning and passing a silent nan.
  3. throwing an error.
  4. throwing an exception.

  Specification(s): bad_evaluation_jit/nan, bad_evaluation_jit/warning, bad_evaluation_jit/error, bad_evaluation_jit/exception

  Design: DerivativeMaterialInterface

  Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234234234234
• 15.36.43The system shall issue an error when required dual number derivative materials that are retrieved are never declared.

  Specification(s): ad_warn

  Design: DerivativeMaterialInterface

  Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.44The system shall handle a bad evaluation using dual numbers by
  1. passing a silent nan.
  2. throwing a warning and passing a silent nan.
  3. throwing an error.
  4. throwing an exception.

  Specification(s): ad_bad_evaluation/nan, ad_bad_evaluation/warning, ad_bad_evaluation/error, ad_bad_evaluation/exception

  Design: DerivativeMaterialInterface

  Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234234234234
• 15.36.45The system shall allow users to request derivatives with respect to function symbols other than MOOSE variables
  1. such as derivatives w.r.t. material properties
  2. and error out if derivatives w.r.t unknown symbols are requested
  3. and error out if derivatives MOOSE variables are requested in additional_derivative_symbols (as they are requested by default)
  4. and error out if any symbols are supplied more than once

  Specification(s): additional_derivatives/mat_props, additional_derivatives/error_unknown, additional_derivatives/error_variable, additional_derivatives/error_duplicate

  Design: DerivativeMaterialInterface

  Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  234234234406
• 15.36.46The system shall require explicitly coupled properties to exist
  1. for regular properties in ParsedMaterials
  2. and error out for non-existing for explicitly requested derivatives in ParsedMaterials
  3. for explicitly requested derivatives in ParsedMaterials
  4. for explicitly requested derivatives but optimized out derivatives in ParsedMaterials
  5. but provide for a user override to default non-existing properties to zero
  6. in DerivativeParsedMaterials

  Specification(s): required_property/parsed_material, required_property/parsed_material_requested_non_existing_derivative, required_property/parsed_material_requested_existing_derivative, required_property/parsed_material_requested_optimized_out_derivative, required_property/allow_override, required_property/derivative_parsed_material

  Design: DerivativeMaterialInterface

  Issue(s): #18917

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234406234234234406
• 15.36.52The system shall issue a warning when a "discrete" material object is retrieved for use in a controlling material but it is set to auto-execute.

  Specification(s): newton_warning

  Design: Materials System

  Issue(s): #5166#6533

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.53The system shall verify that a material being retrieved is defined everywhere that the retrieving material is defined:
  1. on compatible blocks, and
  2. on compatible boundaries.

  Specification(s): coverage_check/block_incompatible, coverage_check/boundary_incompatible

  Design: Materials System

  Issue(s): #5166#6533

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.36.54The system shall issue a warning when a "discrete" material's "reset" method is not defined.

  Specification(s): reset_warning

  Design: Materials System

  Issue(s): #5166#6533

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.59The system shall report an error
  1. if the user requests conversions to both AD and regular material properties, as this is not supported,
  2. if the user inputs a different number of functors and material properties, as the conversion match one to one.

  Specification(s): exception_checks/ad_and_regular, exception_checks/wrong_size

  Design: MaterialFunctorConverter

  Issue(s): #19420

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.36.61The system shall report an error with a clear parameter error if
  1. the names for the regular functors to be converted are going to overlap with the new automatic differentiation functors
  2. the names for the regular functors to be converted are going to overlap with the other new regular functors
  3. the names for the automatic differentiation functors to be converted are going to overlap with the new regular functors
  4. the names for the automatic differentiation functors to be converted are going to overlap with the other new automatic differentiation functors
  5. the number of automatic differentiation functors to convert does not match the number of names for the converted functors
  6. the number of regular functors to convert does not match the number of names for the converted functors

  Specification(s): errors/reg_in_ad_out, errors/reg_in_reg_out, errors/ad_in_reg_out, errors/ad_in_ad_out, errors/size_ad_in, errors/size_reg_in

  Design: FunctorADConverter

  Issue(s): #19420

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234
• 15.36.65The system shall report an error if multiple definitions are given for a functor material property on a given subdomain.

  Specification(s): multiple_definitions

  Design: GenericFunctorMaterial

  Issue(s): #16809

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.36.6015.36.6315.36.64

  234
• 15.36.69The system shall report an error if an automatic differentiation (AD) object requests a non-AD functor when the functor is AD. This prevents potential dropping of derivative information.

  Specification(s): bad-functor-type-mixing

  Design: Materials System

  Issue(s): #16809

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.70The system shall report an error if a functor material property is declared with the same name as another functor.

  Specification(s): prop_name_issue

  Design: Materials System

  Issue(s): #16809

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.71The system shall report an error if a functor vector material property is declared with the same name as another functor.

  Specification(s): vector_prop_name_issue

  Design: Materials System

  Issue(s): #16809

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.75The system shall report an error if a user provides to the vector magnitude functor material both a vector functor parameter and
  1. x-component functor parameter
  2. y-component functor parameter

  Specification(s): multiple_provided/x_functor, multiple_provided/y_functor

  Design: VectorMagnitudeFunctorMaterial

  Issue(s): #20360

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.36.79The system shall report the retrieval of material properties by names:
  1. on boundaries,
  2. on blocks,
  3. on the all mesh boundaries, and
  4. on the all mesh blocks.

  Specification(s): get_prop_names/boundary, get_prop_names/block, get_prop_names/any_boundary, get_prop_names/any_block

  Design: Materials System

  Issue(s): #4420

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.36.81The system shall report an error if a material property is needed on the entire domain but is only supplied on a subset of the subdomains.

  Specification(s): property_on_one_block

  Design: Materials System

  Issue(s): #1228#5055

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.82The system shall report that a material property is available when it is defined on a subdomain.

  Specification(s): hasMaterialProperty

  Design: Materials System

  Issue(s): #1228#5055

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.84The system shall report and error when a boundary restricted material is not defined on the same boundary as a boundary restricted object using that property in a calculation.

  Specification(s): property_not_on_boundary

  Design: Materials System

  Issue(s): #1228#5055

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.92The system shall report an error if material property calculations result in a cyclic dependency.

  Specification(s): mat_cyclic_dep_error_test

  Design: Materials System

  Issue(s): 6683d503d6441165249f8d49c65b76722430019a

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.94The system shall report an error if material properties are not computed on all subdomains.

  Specification(s): check_test

  Design: Materials System

  Issue(s): 6683d503d6441165249f8d49c65b76722430019a

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.98The system shall report an error if a requested material property does not exist for
  1. regular material properties
  2. AD material properties

  Specification(s): nonexistent_material_property/regular, nonexistent_material_property/ad

  Design: Materials System

  Issue(s): #21867

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.36.99The material data system shall report a reasonable error when requesting
  1. a non-AD property and the property has already been requested with a different non-AD type
  2. an AD property and the property has already been requested with a different AD type
  3. a non-AD property and the property has already been requested as an AD property
  4. an AD property and the property has already been requested as a non-AD property

  Specification(s): errors/get_different_types, errors/get_different_types_ad, errors/get_different_ad_types, errors/get_different_ad_types_ad

  Design: Materials System

  Issue(s): #8444

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.36.104The optional material property system use from a material object shall return
  1. an accessible material for existing AD properties
  2. an accessible material for existing non-AD properties
  3. an inaccessible material for non-existing AD properties
  4. an inaccessible material for non-existing non-AD properties

  Specification(s): material_error/ad_expected, material_error/non-ad_expected, material_error/ad_not_expected, material_error/non-ad_not_expected

  Design: Materials System

  Issue(s): #18999

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.36.107The system shall report an error if an existing variable shares the same name as an auxiliary variable used for material output

  Specification(s): duplicate_variable_name

  Design: Materials SystemOutput System

  Issue(s): #1189#3538

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.108The system shall report an error if the supplied output options for material data output are not consistent with the list of available outputs.

  Specification(s): invalid_outputs

  Design: Materials SystemOutput System

  Issue(s): #1189#3538

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.36.116The system shall support the calculation of a material property with a linear interpolation and error if
  1. x, y, and xy_data are all specified;
  2. x and xy_data are both specified;
  3. the x and y vectors are different lengths; and
  4. the xy_data vector length is not a multiple of two.

  Specification(s): errors/err1, errors/err2, errors/err3, errors/err4

  Design: PiecewiseLinearInterpolationMaterial

  Issue(s): #13224

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.36.134The system shall report and error when invalid indices are requested when attempting to output material properties through auxiliary field variables.

  Specification(s): except1

  Design: Materials System

  Issue(s): #4489

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.36.1115.36.2315.36.7315.36.9315.36.10015.36.10115.36.12015.36.12215.36.133

  2322

• rdg: Mesh
• 15.37.51The system shall include the ability to generate an annular mesh that errors when
  1. the min radius is larger than the max radius;
  2. the min angle is greater than or equal to the max angle;
  3. the angle separation is larger than 360 degrees;
  4. the number of elements in the angular direction is too small due to the number of elements; and
  5. the number of elements in the angular direction is too small due to the maximum angle.
  6. shall throw an error if the quadrilateral and triangular subdomain ids are the same.
  7. shall throw an error if both radial positions and the number of radial elements are prescribed.
  8. shall throw an error if both radial positions and the radius growth parameter are prescribed.
  9. shall throw an error if any of the radial positions fall out of the bounds between rmin and rmax.

  Specification(s): annular_errors/annular_except1, annular_errors/annular_except2, annular_errors/annular_except3, annular_errors/annular_except4, annular_errors/annular_except5, annular_errors/annular_except6, annular_errors/annular_except7, annular_errors/annular_except8, annular_errors/annular_except9

  Design: AnnularMeshGenerator

  Issue(s): #8432#18486

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234234234234
• 15.37.68The system shall throw a warning if user-provided extra element id names do not exist on mesh.

  Specification(s): mesh_only_with_unrecognized_elem_ids

  Design: Mesh System

  Issue(s): #23386

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  224
• 15.37.79The system shall issue an error if no Mesh block is provided.

  Specification(s): no_mesh_block_err

  Design: Mesh System

  Issue(s): #2408

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.37.80The system shall issue a diagnostic when a referenced node set does not exist in the mesh

  Specification(s): test

  Design: MooseMesh

  Issue(s): #13509#6985#6987

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.37.88The system shall report a useful error when saving additional meshes when
  1. the requested names are not unique,
  2. the requested name uses a reserved name,
  3. trying to use the mesh-saving capability with the final mesh,
  4. the requested saved mesh does not exist, and when
  5. the requested saved mesh has already been retrieved.

  Specification(s): save_in_name_error/repeat_save_in_name, save_in_name_error/save_in_name_as_main, save_in_name_error/save_in_name_for_final_mesh_generator, save_in_name_error/save_in_meshes_not_find, save_in_name_error/save_in_meshes_retrieved_twice

  Design: MeshGenerator

  Issue(s): #23618

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234
• 15.37.89The system shall issue a diagnostic when a referenced side set does not exist in the mesh.

  Specification(s): missing_side_set

  Design: MooseMesh

  Issue(s): #13509

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.37.95The mesh splitter will throw an error when an attempt is made to split a "DistributedMesh".

  Specification(s): split_with_distributed_error

  Design: Mesh Splitting

  Issue(s): #11434

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  86
• 15.37.102The system shall report an error if at least one mesh file is not supplied when creating a mesh from multiple meshes stitched together.

  Specification(s): files_error

  Design: StitchedMesh

  Issue(s): #8308

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.37.104The parallel partitioning capability by subdomain shall report a reasonable error when a given subdomain does not exist

  Specification(s): missing_block

  Design: Partitioner System

  Issue(s): #8672#8747#8950#8956

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Meshdivisions
• 15.38.2The system shall report an error if
  1. Cartesian divisions from a group of co-planar center positions are overlapping,
  2. cylindrical divisions from a group of co-planar center positions are overlapping,
  3. and spherical divisions from a group of co-planar center positions are overlapping.

  Specification(s): errors/cartesian_too_close, errors/cylindrical_too_close, errors/spherical_too_close

  Design: MeshDivisions

  Issue(s): #25901#26223

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234

• rdg: Meshgenerators
• 15.39.4The system shall throw an error if real_scalar_metadata_names and real_scalar_metadata_values are different in size.

  Specification(s): err_diff_real_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.5The system shall throw an error if uint_scalar_metadata_names and uint_scalar_metadata_values are different in size.

  Specification(s): err_diff_uint_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.6The system shall throw an error if int_scalar_metadata_names and int_scalar_metadata_values are different in size.

  Specification(s): err_diff_int_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.7The system shall throw an error if dof_id_type_scalar_metadata_names and dof_id_type_scalar_metadata_values are different in size.

  Specification(s): err_diff_dof_id_type_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.8The system shall throw an error if subdomain_id_type_scalar_metadata_names and subdomain_id_type_scalar_metadata_values are different in size.

  Specification(s): err_diff_subdomain_id_type_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.9The system shall throw an error if boolean_scalar_metadata_names and boolean_scalar_metadata_values are different in size.

  Specification(s): err_diff_boolean_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.10The system shall throw an error if point_scalar_metadata_names and point_scalar_metadata_values are different in size.

  Specification(s): err_diff_point_scalar_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.11The system shall throw an error if real_vector_metadata_names and real_vector_metadata_values are different in size.

  Specification(s): err_diff_real_vector_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.12The system shall throw an error if uint_vector_metadata_names and uint_vector_metadata_values are different in size.

  Specification(s): err_diff_uint_vector_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.13The system shall throw an error if int_vector_metadata_names and int_vector_metadata_values are different in size.

  Specification(s): err_diff_int_vector_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.14The system shall throw an error if dof_id_type_vector_metadata_names and dof_id_type_vector_metadata_values are different in size.

  Specification(s): err_diff_dof_id_type_vector_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.15The system shall throw an error if subdomain_id_type_vector_metadata_names and subdomain_id_type_vector_metadata_values are different in size.

  Specification(s): err_diff_subdomain_id_type_vector_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.16The system shall throw an error if point_vector_metadata_names and point_vector_metadata_values are different in size.

  Specification(s): err_diff_point_vector_size

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.17The system shall throw an error if real_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_real_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.18The system shall throw an error if uint_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_uint_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.19The system shall throw an error if int_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_int_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.20The system shall throw an error if dof_id_type_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_dof_id_type_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.21The system shall throw an error if subdomain_id_type_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_subdomain_id_type_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.22The system shall throw an error if boolean_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_boolean_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.23The system shall throw an error if point_scalar_metadata_names contains non-unique elements.

  Specification(s): err_dup_point_scalar_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.24The system shall throw an error if real_vector_metadata_names contains non-unique elements.

  Specification(s): err_dup_real_vector_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.25The system shall throw an error if uint_vector_metadata_names contains non-unique elements.

  Specification(s): err_dup_uint_vector_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.26The system shall throw an error if int_vector_metadata_names contains non-unique elements.

  Specification(s): err_dup_int_vector_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.27The system shall throw an error if dof_id_type_vector_metadata_names contains non-unique elements.

  Specification(s): err_dup_dof_id_type_vector_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.28The system shall throw an error if subdomain_id_type_vector_metadata_names contains non-unique elements.

  Specification(s): err_dup_subdomain_id_type_vector_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.29The system shall throw an error if point_vector_metadata_names contains non-unique elements.

  Specification(s): err_dup_point_vector_name

  Design: AddMetaDataGenerator

  Issue(s): #23135

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.39The system shall report an error if missing a consistent positive or negative extrusion direction.

  Specification(s): mixed_extrude

  Design: AdvancedExtruderGenerator

  Issue(s): #21273

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.42The system shall error
  1. if the source subdomain for a subdomain swap in a layer does not exist in the mesh,
  2. if the source boundary for a boundary swap in a layer does not exist in the mesh,
  3. if the source subdomain for an upward boundary assignment in a layer does not exist in the mesh,
  4. if the source subdomain for an downward boundary assignment in a layer does not exist in the mesh,

  Specification(s): errors/bad_subdomain_swap, errors/bad_boundary_swap, errors/bad_upward_source_subdomain, errors/bad_downward_source_subdomain

  Design: AdvancedExtruderGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.39.48The system shall report an error when generating an annular mesh with equal-area elements when a growth ratio is also provided

  Specification(s): conflicting_settings

  Design: AnnularMeshGenerator

  Issue(s): #20422

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.49The system shall report an error when generating an annual mesh with equal-area elements when radial positions are also provided

  Specification(s): conflicting_settings_nr

  Design: AnnularMeshGenerator

  Issue(s): #20422

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.52The system shall only support the ability to add additional mesh generators from a user accessible programmatic interface when
  1. there exists a generator to append to
  2. such mesh generators take an input
  3. other mesh generators have been added to be appended to

  Specification(s): errors/nothing_to_append_to, errors/no_input, errors/wrong_time

  Design: MeshGenerator

  Issue(s): #15121#23447

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148148148
• 15.39.53The system shall be capable of deleting
  1. all of the elements in a mesh based on subdomain ID,
  2. all of the elements in a mesh based on subdomain names and
  3. multiple blocks simultaneously in a mesh based on subdomain ID.
  4. blocks and assigning the new boundary even if the input mesh is not prepared.
  5. blocks and properly removing lower dimensional elements with a deleted element as their interior parent.
  6. blocks and retaining lower dimensional elements with a deleted interior parent if requested,
  7. blocks and erroring if a block does not exist.

  Specification(s): block_deletion/all_by_block_ids, block_deletion/all_by_block_names, block_deletion/multiple_blocks, block_deletion/input_not_prepared, block_deletion/delete_interior_parents, block_deletion/preserve_exteriors, block_deletion/missing_block

  Design: BlockDeletionGenerator

  Issue(s): #11640#17052#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  234234234234234234234
• 15.39.56The system shall return an error if the following unsupported features are present:
  1. the mesh is distributed in parallel
  2. the block to extract is uniformly refined

  Specification(s): errors/distributed, errors/refined

  Design: BlockToMeshConverterGenerator

  Issue(s): #20880

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  86148
• 15.39.58The system shall report an error if attempting to delete a non-existent boundary

  Specification(s): invalid_boundary

  Design: BoundaryDeletionGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.60The system shall produce an error when attempting to add a new mesh node set based on a bounding box
  1. where the bounding box fails to span any mesh nodes, and
  2. where multiple boundary IDs are supplied for a single bounding box.

  Specification(s): errors/bad_coord, errors/test_bad_boundaryid

  Design: BoundingBoxNodeSetGenerator

  Issue(s): #11640

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.39.61The system shall be capable of splitting existing mesh boundary sets where their underlying subdomain changes
  1. on external boundaries, and
  2. on internal boundaries, and
  3. error when the boundary does not exist in the mesh.

  Specification(s): boundary_type/external, boundary_type/internal, boundary_type/invalid_boundary

  Design: BreakBoundaryOnSubdomainGenerator

  Issue(s): #7887#11640#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  148148234
• 15.39.68The system shall report an error if the mesh does not contain the specified block pair

  Specification(s): invalid_block_pair

  Design: BreakMeshByBlockGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.69The system shall report an error if the mesh does not contain the specified surrounding block

  Specification(s): invalid_surrounding_block

  Design: BreakMeshByBlockGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.71The system shall throw an error if the subdomains with different ID have duplicate names.

  Specification(s): check_duplicate_subdomain_names

  Design: MooseMesh

  Issue(s): #23735

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.75The system shall throw an error if the length of the provided customized transition layer rarios does not match the number of the boundaries to be corrected.

  Specification(s): err_transition_layer_ratios_length

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.76The system shall throw an error if the length of the provided customized circular verification tolerance does not match the number of the boundaries to be corrected.

  Specification(s): err_custom_circular_tolerance_length

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.77The system shall throw an error if the provided boundaries are not in XY plane.

  Specification(s): err_non_xy_plane

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.78The system shall throw an error if the provided boundary contains fewer than three nodes.

  Specification(s): err_few_points

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.79The system shall throw an error if any nodes are moved twice for radius correction.

  Specification(s): err_overlapped_transition_area

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.80The system shall throw an error if the provided boundary to correct is not circular.

  Specification(s): err_non_circular

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.81The system shall throw an error if the provided boundaries are all full circles and the parameter to move the end nodes in the span direction is set to true.

  Specification(s): err_full_cirles_and_span_direction

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.82The system shall throw an error if an input boundary does not exist in the input mesh.

  Specification(s): err_boundary_not_found

  Design: CircularBoundaryCorrectionGenerator

  Issue(s): #23972

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.87The system shall report an error if
  1. attempting to coarsen a block that does not exist in the mesh, and
  2. if specifying a vector of coarsening levels that does not match the vector of subdomains to coarsen,
  3. the coarsening starting element is not in the block to coarsen the most.

  Specification(s): errors/invalid_block, errors/wrong_size_inputs, errors/wrong_starting_point

  Design: CoarsenBlockGenerator

  Issue(s): #25280

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234148234
• 15.39.89The system shall report an error when trying to combine multiple meshes,
  1. but only one input is supplied with no positions, or
  2. but only one input is supplied with no positions file, or
  3. the number of meshes and the number of positions is mismatched, or
  4. the number of meshes and the number of positions in the file is mismatched.

  Specification(s): errors/missing_pos, errors/missing_pos_file, errors/mismatch_pos, errors/mismatch_pos_from_file

  Design: CombinerGenerator

  Issue(s): #13412

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.39.95The system shall throw an error
  1. if the input mesh to be cut is not a replicated mesh.
  2. if the input mesh to be cut contains non-3D elements.
  3. if the input mesh to be cut contains high-order elements.
  4. if the specified cut face id and names are inconsistent with the input mesh.

  Specification(s): error/err_distributed, error/err_non_3d, error/err_high_order, error/err_boundary_conflict

  Design: CutMeshByPlaneGenerator

  Issue(s): #26579#26902

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148148148148
• 15.39.96The system shall be able to give a clear error message about a cyclic graph in mesh generation.

  Specification(s): error

  Design: Mesh System

  Issue(s): #21743

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.99The system shall report a reasonable error when generating a mesh with data-driven capabilities when
  1. the specified data-driven generator does not exist
  2. the parent generators do not support data-driven mode
  3. a generator that is supposed to be data-only is also set to be output
  4. a mesh generator is requested to generate data that does not have a data generation implementation
  5. the application does not allow data-driven generation

  Specification(s): errors/missing, errors/parent_unsupported, errors/parent_save_with_name, errors/unimplimented, errors/disabled

  Design: MeshGenerator

  Issue(s): #26295#27075

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234
• 15.39.105The system shall be able to check if or not users ask for too many layers of ghosting elements.

  Specification(s): check_nlayers

  Design: DistributedRectilinearMeshGenerator

  Issue(s): #11485

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.111The system shall report an error if the number of cores for partition is larger than the total number of cores.

  Specification(s): 3d_scomm_10_out

  Design: DistributedRectilinearMeshGenerator

  Issue(s): #15464

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.130The system shall throw an error
  1. if the input mesh to be converted is not a replicated mesh.
  2. if the input mesh to be converted contains non-3D elements.
  3. if the input mesh to be converted contains high-order elements.

  Specification(s): error/err_distributed, error/err_non_3d, error/err_high_order

  Design: ElementsToTetrahedronsConverter

  Issue(s): #26579

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148148148
• 15.39.133The system shall report an error if the subdomain to explode was not found in the mesh

  Specification(s): invalid_subdomain

  Design: BreakMeshByElementGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.137The system shall report an error on assigning boundary identifiers if the supplied location is outside of the domain.

  Specification(s): test_bad_coord

  Design: ExtraNodesetGenerator

  Issue(s): #13814

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.160The system shall throw an error if either input vector of points include points that are not in XY plane.

  Specification(s): non_xy_plane

  Design: FillBetweenPointVectorsGenerator

  Issue(s): #20641

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.161The system shall throw an error if either input vector of points include less than 2 points.

  Specification(s): not_enough_points

  Design: FillBetweenPointVectorsGenerator

  Issue(s): #20641

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.162The system shall throw an error if the two input vectors have different length and QUAD4 elements option is selected.

  Specification(s): quad_with_different_vector_sizes

  Design: FillBetweenPointVectorsGenerator

  Issue(s): #20641

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.167The system shall throw an error if the two input meshes are the same.

  Specification(s): err_same_inputs

  Design: FillBetweenSidesetsGenerator

  Issue(s): #20641

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.168The system shall throw an error if one of the input boundary to generate a mesh in-between has multiple segments.

  Specification(s): err_multiseg_boundary

  Design: FillBetweenSidesetsGenerator

  Issue(s): #20641

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.169The system shall throw an error if one of the input boundary to generate a mesh in-between is a closed loop.

  Specification(s): err_closed_loop_boundary

  Design: FillBetweenSidesetsGenerator

  Issue(s): #20641

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.172The system shall generate an error when the objects used to generate a mesh results in an ambiguous end point
  1. due to a single graph with multiple end points, or
  2. due to multiple independent trees.

  Specification(s): ambigious/single_graph, ambigious/independent_graphs

  Design: Mesh System

  Issue(s): #14058

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.39.175The system shall produce a reasonable error when switching the normal orientation of a sideset if the sideset does not exist

  Specification(s): no_sideset_exception

  Design: FlipSidesetGenerator

  Issue(s): #25528

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.176The system shall produce a reasonable error when switching the normal orientation of a sideset if the sideset cannot be flipped

  Specification(s): no_neighbor_exception

  Design: FlipSidesetGenerator

  Issue(s): #25528

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.181The system shall generate a warning if Mesh Generators are used with a mesh type that does not accept them

  Specification(s): type_test

  Design: GeneratedMeshGenerator

  Issue(s): #13959

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.39.3015.39.5115.39.9715.39.10015.39.13915.39.17715.39.25215.39.271

  234
• 15.39.190The system shall report an error
  1. if refinement generators are executed before lower dimensional elements are added,
  2. if a non-existing sideset is specified as the sideset to create a lower-dimensional block from.

  Specification(s): error/dont_refine_before, error/invalid_sideset

  Design: LowerDBlockFromSidesetGenerator

  Issue(s): #24638#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.39.193The system shall be able to diagnostize potential issues in a mesh, such as
  1. element overlapping,
  2. inconsistently oriented sidesets between subdomains,
  3. inconsistently oriented sidesets between two neighbor sides within the sideset,
  4. 2D meshed square missing a sideset on one side
  5. 3D meshed cube missing a sideset on one side
  6. non-conformality in two dimensions,
  7. non-conformality in three dimensions,
  8. different element types in a single subdomain,
  9. elements above a certain volume,
  10. elements below a certain volume,
  11. non-planar sides on elements,
  12. elements with negative Jacobians

  Specification(s): generate/nonconformality, generate/inconsistent_sidesets, generate/inconsistent_internal_sidesets, generate/2D_watertight_sidesets, generate/3D_Watertight_sidesets, generate/overlap, generate/nonconformality_3d, generate/elem_types, generate/max_size, generate/min_size, generate/non_planar, generate/negative_jacobian

  Design: MeshDiagnosticsGenerator

  Issue(s): #25278

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  148148148148148148148148148148148148
• 15.39.194The system shall be able to recognize non-conformalities created by uniform mesh refinements for
  1. quadrilateral elements,
  2. quadrilateral elements of second order,
  3. quadrilateral elements refined twice near an unrefined quadrilateral element,
  4. hexahedral elements,
  5. hexahedral elements of second order,
  6. hexahedral elements refined twice near an unrefined quadrilateral element,
  7. triangle elements,
  8. triangle elements of second order,
  9. triangle elements of third order,
  10. triangle elements refined twice near an unrefined triangle element,
  11. tetrahedral elements,
  12. tetrahedral elements of second order,
  13. tetrahedral elements of third order,

  Specification(s): amr_detection/quad, amr_detection/quad_second_order, amr_detection/quad_two_levels_across, amr_detection/hex, amr_detection/hex_second_order, amr_detection/hex_two_levels_across, amr_detection/tri, amr_detection/tri_second_order, amr_detection/tri_third_order, amr_detection/tri_two_levels_across, amr_detection/tet, amr_detection/tet_second_order, amr_detection/tet_third_order

  Design: MeshDiagnosticsGenerator

  Issue(s): #25278

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  148148148148148148148148148148148148148
• 15.39.196The system shall report an error if
  1. a diagnostics object is created but no diagnostics are requested.

  Specification(s): errors/no_diag

  Design: MeshDiagnosticsGenerator

  Issue(s): #25278

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.198The system shall report an error if the existing subdomain does not exist in the mesh

  Specification(s): invalid_existing_subdomain

  Design: MeshExtruderGenerator

  Issue(s): #11640#14037#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.204The system shall issue an error when mesh meta-data properties are requested but never declared.

  Specification(s): meta_data_error_check

  Design: MeshMetaDataInterface

  Issue(s): #13841

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.205The system shall report an error if a invalid identifier is supplied when attempting to retrieve a restart meta data object.

  Specification(s): get_meta_data_error_check

  Design: MeshMetaDataInterface

  Issue(s): #13841

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.209The system shall report an error if the node to be moved cannot be found in the mesh.

  Specification(s): failure_missing

  Design: MoveNodeGenerator

  Issue(s): #18577#21468

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.210The system shall report an error if the node position and node id arrays do not match in size

  Specification(s): failure_mismatch

  Design: MoveNodeGenerator

  Issue(s): #18577#21468

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.211The system shall report an error if both shifts and positions are specified

  Specification(s): failure_overspecified

  Design: MoveNodeGenerator

  Issue(s): #18577#21468

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.224The system shall throw an error if the starting and ending points of a section are overlapped while the section is supposed to be open.

  Specification(s): err_crossed_curve

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.225The system shall throw an error if the oversampling algorithm exceeds its designated maximum sampling number.

  Specification(s): err_max_oversample

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.226The system shall throw an error if there are repeated elements in the user-specified curve abscissas.

  Specification(s): err_repeated_t_series

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.227The system shall throw an error if the user specifies to force closing a parsed curve, but it is already closed as the starting and ending points of the curve are overlapped.

  Specification(s): err_unneeded_forced_closed_num_segments_1

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.228The system shall throw an error if the user specifies to force closing a parsed curve but the curve to be generated is also specified to be open.

  Specification(s): err_unneeded_forced_closed_num_segments_2

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.229The system shall throw an error if the abscissa used to generate the curve is specified non-monotonically.

  Specification(s): err_unsorted_t_series

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.230The system shall throw an error if the number of curve segments is not consistent with the number of abscissa ranges.

  Specification(s): err_bad_nums_segments

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.231The system shall throw an error if the parsed expression for the x coordinate cannot be parsed as a function.

  Specification(s): err_failed_parsing_x

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.232The system shall throw an error if the parsed expression for the y coordinate cannot be parsed as a function.

  Specification(s): err_failed_parsing_y

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.233The system shall throw an error if the parsed expression for the z coordinate cannot be parsed as a function.

  Specification(s): err_failed_parsing_z

  Design: ParsedCurveGenerator

  Issue(s): #22848

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.242The system shall report an error
  1. if one of the included subdomains does not exist in the mesh,
  2. if one of the included neighbors does not exist in the mesh,
  3. if one of the included sidesets does not exist in the mesh,
  4. if one of the excluded sidesets does not exist in the mesh,

  Specification(s): missing_errors/invalid_included_subdomains, missing_errors/invalid_included_neighbors, missing_errors/invalid_included_boundary, missing_errors/invalid_excluded_boundary

  Design: ParsedGenerateSideset

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148148148148
• 15.39.243The system shall report an error if a sideset appears in both the list of sidesets to include and to exclude.

  Specification(s): overlap_included_excluded_boundary

  Design: ParsedGenerateSideset

  Issue(s): #28551

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.244The system shall report an error if the sideset to create appears in the list of sidesets to include.

  Specification(s): overlap_included_target_boundary

  Design: ParsedGenerateSideset

  Issue(s): #24354

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.245The system shall report an error if the sideset to create appears in the list of sidesets to exclude.

  Specification(s): overlap_excluded_target_boundary

  Design: ParsedGenerateSideset

  Issue(s): #28551

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.248The system shall report an error if a specified subdomain does not exist in the mesh.

  Specification(s): invalid_excluded_subdomain

  Design: ParsedSubdomainMeshGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.251The system shall report a reasonable error when stitching meshes together from a user-defined pattern when
  1. the boundary name does not exist

  Specification(s): errors/non_existent_boundary

  Design: PatternedMeshGenerator

  Issue(s): #11640#23312

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.255The system shall report an error if
  1. the user provides coordinates that are not in increasing order for the ID planes,
  2. the user provides a plane axis that is going outside the mesh,
  3. the user provides non-matching inputs for the number of planes and the ids to set between planes,
  4. the user does not provide enough planes,
  5. the planes cut the elements despite the allowed tolerance,
  6. some elements are outside the regions between the planes specified.

  Specification(s): errors/coordinates_in_bad_order, errors/out_of_mesh_plane, errors/non_matching_size_inputs, errors/not_enough_planes, errors/elements_being_cut, errors/elements_out_of_planes

  Design: PlaneIDMeshGenerator

  Issue(s): #19217

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234
• 15.39.259The system shall report an error if
  1. attempting to refine a block that does not exist in the mesh, and
  2. if specifying a vector of refinement levels that does not match the vector of subdomains to refine.

  Specification(s): errors/invalid_block, errors/wrong_size_inputs

  Design: RefineBlockGenerator

  Issue(s): #18686#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.39.261The system shall report an error if
  1. the specified boundary to be refined does not exist, and
  2. if specifying a vector of refinement levels that does not match the vector of boundaries to refine.

  Specification(s): errors/missing_boundary, errors/wrong_size_inputs

  Design: RefineSidesetGenerator

  Issue(s): #18913

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.39.264The system shall throw a reasonable error:
  1. when old blocks are provided that do not exist within the mesh
  2. and when the provided old and new blocks are not the same length.

  Specification(s): errors/missing, errors/inconsistent_size

  Design: RenameBlockGenerator

  Issue(s): #11640#14128#16885#17710

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.39.266The system shall report a reasonable error when renaming or renumbering blocks using deprecated syntax when
  1. both old block IDs and old block names are provided
  2. both new block IDs and new block names are provided
  3. the deprecated syntax for old block id and the new syntax for old block is used
  4. the deprecated syntax for old block name and the new syntax for old block is used
  5. the deprecated syntax for new block id and the new syntax for new block is used
  6. the deprecated syntax for new block name and the new syntax for new block is used

  Specification(s): deprecated_errors/old_block_id_and_name, deprecated_errors/new_block_id_and_name, deprecated_errors/old_block_and_id, deprecated_errors/old_block_and_name, deprecated_errors/new_block_and_id, deprecated_errors/new_block_and_name

  Design: RenameBlockGenerator

  Issue(s): #11640#14128#16885#17710

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234
• 15.39.269The system shall throw a reasonable error:
  1. when old boundaries are provided that do not exist within the mesh
  2. when the provided old and new boundaries are not the same length.
  3. when the user requests new boundary IDs outside the valid range of type BoundaryID.

  Specification(s): errors/missing, errors/inconsistent_size, errors/id_out_of_bounds

  Design: RenameBoundaryGenerator

  Issue(s): #11640#14128#16885#21268#27175

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234
• 15.39.273The system shall report an error if the subdomain to create sidesets around does not exist in the mesh

  Specification(s): invalid_block

  Design: SideSetsAroundSubdomainGenerator

  Issue(s): #11640#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.275The system shall have the ability to create new side sets between adjacent subdomains:
  1. on a mesh with several adjacent subdomains,
  2. where some subdomains are adjacent and not where paired subdomains are not adjacent, and
  3. between two subdomains in a mesh with two adjacent subdomains.
  4. between two subdomains in an unprepared mesh.
  5. only when the primary block exists in the mesh.
  6. only when the paired block exists in the mesh.

  Specification(s): group/adjacent_subs, group/nonadjacent_subs, group/two_subs, group/unprepared_input, group/invalid_primary_block, group/invalid_paired_block

  Design: SideSetsBetweenSubdomainsGenerator

  Issue(s): #11640#21861

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  234234234234234234
• 15.39.277The system shall issue an error when attempting to create side sets from a bounding box:
  1. when no elements are located within the specified bounding box,
  2. when the bounding box is larger than the domain so that no new side set is created, and
  3. when the bounding box fails to span over any nodes.
  4. if the incorrect boundary inputs are supplied.

  Specification(s): errors/no_elements_in_bounding_box, errors/no_side_sets_found, errors/no_nodes_found, errors/error_boundary_number

  Design: SideSetsFromBoundingBoxGenerator

  Issue(s): #11640#16813

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148148148148
• 15.39.278The system shall support assigning boundary identifiers based the bounding box of a subdomain
  1. if existing boundaries overlap and
  2. error if no nodes are located in the given bounding box.

  Specification(s): overlap/test_overlapping, overlap/test_overlapping_sidesets_error

  Design: SideSetsFromBoundingBoxGenerator

  Issue(s): #11640#16813

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  148236
• 15.39.284The system shall return errors if it detects ambiguous sideset specifications

  Specification(s): sidesets_ambiguity

  Design: SideSetsFromPointsGenerator

  Issue(s): #24619

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.290The system shall be able to generate meshes by stacking up existing meshes in
  1. two and
  2. three dimensions and
  3. error if the dimensions of the meshes to be stacked are not consistent.

  Specification(s): stack/2d, stack/3d, stack/error_dims

  Design: StackGenerator

  Issue(s): #11640

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunException

  148148148
• 15.39.293The system shall warn the user if boundary ID renumbering is disabled and it detects the same ID with different boundary names on the two meshes

  Specification(s): samename-warning

  Design: StitchedMeshGenerator

  Issue(s): #28049

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.39.300The system shall report an error if a restricted subdomain of the bounding box subdomain generation does not exist in the mesh

  Specification(s): invalid_restricted_subdomain

  Design: SubdomainBoundingBoxGenerator

  Issue(s): #22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.39.304The system shall report a reasonable error generating meshes when
  1. requesting an input mesh generator by parameter and the parameter is not valid
  2. requesting an input mesh generator parameter and the parameter is of the wrong type
  3. requesting an input mesh generator by name and the name is not valid
  4. requesting input mesh generators by parameter and the parameter is of the wrong type
  5. requesting an input mesh at an unallowed time
  6. building a sub generator at an unallowed time
  7. declaring a property on the mesh at an unallowed time
  8. requesting an input mesh generator by parameter that does not exist
  9. requesting input mesh generators by parameter that do not exist
  10. requesting an input mesh generator by name that does not exist
  11. requesting input mesh generators by name that do not exist
  12. failing to properly manage the memory of an input mesh generator
  13. declaring a property on the mesh multiple times
  14. coupling an input mesh generator in a parameter for a sub generator but not using said dependency
  15. coupling an input mesh generator in a sub generator but not declaring it as a dependency
  16. coupling an input mesh generator in a parameter but not using said mesh generator
  17. getting a mesh generator that does not exist
  18. forcibly setting the final mesh when said mesh does not exist
  19. an input mesh is not found because its dependencies are not properly declared
  20. a mesh was not generated

  Specification(s): errors/get_mesh_invalid, errors/get_mesh_wrong_type, errors/get_meshes_by_name_invalid, errors/get_meshes_by_name_wrong_type, errors/get_mesh_outside_construct, errors/sub_outside_construct, errors/declare_mesh_prop_outside_construct, errors/get_mesh_not_found, errors/get_meshes_not_found, errors/get_mesh_by_name_not_found, errors/get_meshes_by_name_not_found, errors/input_not_moved, errors/mesh_prop_double_declare, errors/unused_sub_input, errors/sub_no_declare_input, errors/unused_param_input, errors/missing_get, errors/missing_final, errors/not_constructed_yet, errors/generated_nullptr

  Design: MeshGenerator

  Issue(s): #19285#23447

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234234234234234234234234234234234234234234234
• 15.39.311The system shall have the capability of triangulating a polyline boundary
  1. within an input polyline
  2. returning errors if the polyline is not closed
  3. returning errors if the polyline is disconnected
  4. taking the boundary of a 2D input mesh
  5. taking a specified subset of an input polyline set
  6. taking a specified subset of a 2D input boundary
  7. respecting any specified interior 'hole' meshes
  8. assigning user-provided hole boundary names
  9. selectively stitching 'hole' meshes into the final mesh
  10. allowing deep nesting of triangulations within triangulations
  11. with optional Laplacian mesh smoothing.
  12. with optional non-uniform refinement based on a custom function.
  13. with optional non-uniform refinement based on an automatically generated function.
  14. with quadratic TRI3 elements using a non-stitched quadratic hole mesh.
  15. with quadratic TRI6 elements.
  16. with quadratic TRI7 elements.
  17. selectively stitching linear 'hole' meshes into the final quadratic TRI6 mesh after increasing the hole mesh element order
  18. selectively stitching linear 'hole' meshes into the final quadratic TRI7 mesh after increasing the hole mesh element order

  Specification(s): xydelaunay/basic, xydelaunay/open_line, xydelaunay/multi_line, xydelaunay/from_2d, xydelaunay/subdomain_1d, xydelaunay/subboundary_2d, xydelaunay/with_holes, xydelaunay/with_hole_names, xydelaunay/stitching, xydelaunay/nested, xydelaunay/smoothed, xydelaunay/area_func, xydelaunay/auto_area_func, xydelaunay/quadratic_hole_tri3, xydelaunay/quadratic_tri6, xydelaunay/quadratic_tri7, xydelaunay/quadratic_tri6_stitching_linear_hole, xydelaunay/quadratic_tri7_stitching_linear_hole

  Design: XYDelaunayGenerator

  Issue(s): #20192#26776#27545#27828

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): ExodiffRunExceptionCSVDiff

  234192192234234234234234234234234234234234234234234234
• 15.39.312The system shall throw an error when triangulating a polyline boundary
  1. if the input hole meshes contain subdomain name maps with conflicts
  2. if more than one element area limiting methods are specified by the user
  3. if the user specifies parameters for the auto area function when it is not used
  4. if the input hole meshes

  Specification(s): errors/err_conflicting_name_map, errors/err_redundant_area_limits, errors/err_unneeded_auto_area_func_params, errors/err_stiching_quadratic_holes

  Design: XYDelaunayGenerator

  Issue(s): #20192#26776#27545#27828

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234
• 15.39.319The system shall error
  1. if the input mesh is not 2D,
  2. if the given name of the triangle element block, created during mesh line cutting, already exists in the input mesh, in the element cutting mode,
  3. if the given name of the triangular element block, created during mesh line cutting, already exists in the input mesh in the node moving mode,
  4. if the input mesh does not contain the user-specified external boundary,
  5. if the input mesh does not contain the user-specified boundary to conform,
  6. if the size of the cut line parameters is not three,
  7. if the cut line parameters is not valid to define a line,
  8. if the external boundary id is not provided when the node moving method is used,
  9. if the triangle element improvement is enabled under the node moving mode.

  Specification(s): errors/err_non_2d_mesh, errors/err_pre_exist_block_name_elem, errors/err_pre_exist_block_name_node, errors/err_missing_external_bdy, errors/err_missing_bdy_to_conform, errors/err_wrong_line_params_size, errors/err_wrong_line_params_value, errors/err_no_external_boundary_id, errors/err_tri_improve_for_node_moving

  Design: XYMeshLineCutter

  Issue(s): #23844#22117

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148148148148148148148148148
• 15.39.321The system shall throw an error when tetrahedralizing a triangulated boundary
  1. if the input hole meshes contain subdomain name maps with conflicts

  Specification(s): errors/err_conflicting_name_map

  Design: XYZDelaunayGenerator

  Issue(s): #28297

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234

• rdg: Meshmodifiers
• 15.40.10The system shall produce an error when a boundary preserved marker is used with distributed mesh.

  Specification(s): error-distributed

  Design: CoupledVarThresholdElementSubdomainModifierVariableValueElementSubdomainModifier

  Issue(s): #15795#17100#17239#21383#27486

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  86

• rdg: Misc
• 15.42.10The system shall report an error when a material property is not defined on a boundary.

  Specification(s): bc_check

  Design: Problem system overview

  Issue(s): #9835#5309#9482

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.11The system shall report an error when a material property requested by a UserObject is not defined on a boundary.

  Specification(s): side_uo_check

  Design: Problem system overview

  Issue(s): #9835#5309#9482

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.12The system shall report an error when a material property requested by a DGKernel is not defined on a boundary.

  Specification(s): dgkernel_check_boundary

  Design: Problem system overview

  Issue(s): #9835#5309#9482

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.13The system shall report an error when a material property requested by a DGKernel is not defined on a subdomain.

  Specification(s): dgkernel_check_block

  Design: Problem system overview

  Issue(s): #9835#5309#9482

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.15The system shall produce an error when an object's discretization area is explicitly set to a value greater than the area of the underlying variable used by the object.

  Specification(s): variable_interface_error_block_set

  Design: Problem system overview

  Issue(s): #9889

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.16The system shall produce an error when an object's discretization area is greater than the area of the underlying variable used by the object.

  Specification(s): variable_interface_error_block_any

  Design: Problem system overview

  Issue(s): #9889

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.17The system shall produce an error when an object's discretization area is explicitly set to a different area than the area of a coupled variable used by the object.

  Specification(s): coupleable_error_block_set

  Design: Problem system overview

  Issue(s): #9889

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.18The system shall produce an error when an object's discretization area is different than an explicitly set variable on only defined on a different portion of the mesh.

  Specification(s): coupleable_error_block_set2

  Design: Problem system overview

  Issue(s): #9889

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.19The system shall produce an error when an object's discretization area is covers the whole mesh but a coupled variable only exists on a portion of the mesh.

  Specification(s): coupleable_error_block_any

  Design: Problem system overview

  Issue(s): #9889

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.20The system shall report an error if a boundary restricted object depends on a variable that is not defined on any portion of the boundary. These boundary restricted objects include
  1. nodal auxiliary kernels
  2. nodal user objects
  3. nodal boundary conditions
  4. integrated boundary conditions
  5. side user objects
  6. elemental auxiliary kernels

  Specification(s): error/nodal_aux, error/nodal_uo, error/nodal_bc, error/integrated_bc, error/side_uo, error/elemental_aux

  Design: AuxKernels SystemUserObject System

  Issue(s): #9734

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234234234234234
• 15.42.21The system shall report an error if a variable is coupled into a boundary restricted object, along whose boundary the variable is only partially defined.

  Specification(s): partial_coverage

  Design: AuxKernels SystemUserObject System

  Issue(s): #9734

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.22The system shall report an error if an object restricted on an internal boundarydepends on a variable that is not defined on any portion of the boundary.

  Specification(s): error

  Design: AuxKernels SystemUserObject System

  Issue(s): #9734

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.23The system shall report an error when the system solver is unable to find a converged solution.

  Specification(s): steady_no_converge

  Design: Executioner System

  Issue(s): #5144#5153

  Collection(s): FAILURE_ANALYSIS

  Type(s): RunApp

  234
• 15.42.24The system shall report an error message when a range-checked parameter is out of range.

  Specification(s): range_check_param

  Design: Problem system overview

  Issue(s): #2777

  Collection(s): FAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.25The system shall report an error when a null pointer-checked parameter is retrieved from the InputParameters object.

  Specification(s): checked_pointer_param_test

  Design: Problem system overview

  Issue(s): #10356

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.26The system shall report an error when multiple AuxVariables are added to the system with conflicting types.

  Specification(s): add_aux_variable_multiple_test

  Design: Problem system overview

  Issue(s): #1222

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.27The system shall report an error when multiple Scalar AuxVariables are added to the system with conflicting types.

  Specification(s): add_aux_scalar_variable_multiple_test

  Design: Problem system overview

  Issue(s): #9313

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.28The system shall report an error when multiple AuxVariables are added to the system with conflicting block-restriction.

  Specification(s): add_aux_variable_multiple_subdomain_test

  Design: Problem system overview

  Issue(s): #28568

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.29The system shall report an error when an attempt is made to instantiate a non-existent BoundaryCondition object.

  Specification(s): bad_bc_test

  Design: Problem system overview

  Issue(s): #10486

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.30The system shall report an error when a non-existent nonlinear variable name is used by a MooseObject.

  Specification(s): bad_bc_var_test

  Design: Problem system overview

  Issue(s): #11227

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.31The system shall report an error message when an invalid enumeration is supplied in any MooseEnum type.

  Specification(s): bad_enum_test

  Design: Problem system overview

  Issue(s): #489

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.32The system shall report an error message when an invalid Executioner is specified.

  Specification(s): bad_executioner_test

  Design: Problem system overview

  Issue(s): #12106

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.33The system shall report an error message when an invalid Kernel is specified.

  Specification(s): bad_kernel_test

  Design: Problem system overview

  Issue(s): #12106

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.34The system shall report an error message when a Kernel object attempts to access a non-existent variable.

  Specification(s): bad_kernel_var_test

  Design: Problem system overview

  Issue(s): #11227

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.35The system shall report an error when an invalid Material is specified.

  Specification(s): bad_material_test

  Design: Problem system overview

  Issue(s): #12106

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.36The system shall report an error when a previously undeclared variable is used in a parsed function expression.

  Specification(s): bad_parsed_function_vars_test

  Design: Problem system overview

  Issue(s): #4683

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.37The system shall report an error when a first order element is used with a second order discretization.

  Specification(s): bad_second_order_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  10
• 15.42.38The system shall report an error message when a deprecated input file block is used.

  Specification(s): deprecated_block_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.41The system shall report an error when conflicting domain restrictions are applied to a single object.

  Specification(s): double_restrict_uo_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.42The system shall report an error when the number of ids and corresponding block names are mismatched.

  Specification(s): dynamic_check_name_block_mismatch_test

  Design: Problem system overview

  Issue(s): #8596

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.43The system shall report an error when a duplicate name is provided for a set of unique block ids.

  Specification(s): dynamic_check_name_block_test

  Design: Problem system overview

  Issue(s): #8596

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.44The system shall report an error when the number of ids and corresponding boundary names are mismatched.

  Specification(s): dynamic_check_name_boundary_mismatch_test

  Design: Problem system overview

  Issue(s): #8596

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.45The system shall report an error when a duplicate name is provided for a set of unique boundary ids.

  Specification(s): dynamic_check_name_boundary_test

  Design: Problem system overview

  Issue(s): #8596

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.46The system shall report an error when the linear interpolation utility is supplied with bad domain values.

  Specification(s): linear_interp_material_check

  Design: Problem system overview

  Issue(s): #5886

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.47The system shall report an error when the Piecewise utility encounters an unexpected column data format.

  Specification(s): function_file_test1

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.48The system shall report an error when the Piecewise utility encounters an unexpected row data format.

  Specification(s): function_file_test2

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.49The system shall report an error when the Piecewise utility encounters inconsistent domain and range data.

  Specification(s): function_file_test3

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.50The system shall report an error when an invalid enumeration is supplied in the Piecewise utility.

  Specification(s): function_file_test4

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.51The system shall report an error when the Piecewise data is over-specified with the data file option.

  Specification(s): function_file_test5

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.52The system shall report an error when the Piecewise data is over-specified with row/column data.

  Specification(s): function_file_test6

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.53The system shall report an error when either the domain or range is missing when using the domain/range option in the Piecewise utility.

  Specification(s): function_file_test7

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.54The system shall report and error if the supplied domain/range pairs are not even in the Piecewise utility.

  Specification(s): function_file_test8

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.55The system shall report an error if no function is supplied in the Piecewise utility.

  Specification(s): function_file_test9

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.56The system shall report an error if the xy_data is supplied but the function is missing in the Piecewise utility.

  Specification(s): function_file_test10

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.57The system shall report an error when the number of columns appears incorrect in the Piecewise utility.

  Specification(s): function_file_test11

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.58The system shall report an error when an out of range y-column index is supplied in the Piecewise utility.

  Specification(s): function_file_test12

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.59The system shall report an error when an out of range x-column index is supplied in the Piecewise utility.

  Specification(s): function_file_test13

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.60The system shall report an error if too many rows are supplied when the data is expected to contain row information.

  Specification(s): function_file_test14

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.61The system shall report an error when an out of range x-row index is supplied in the Piecewise utility.

  Specification(s): function_file_test15

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.62The system shall report an error when an out of range y-row index is supplied in the Piecewise utility.

  Specification(s): function_file_test16

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.63The system shall report an error when the x and y index in file are equal in the Piecewise utility.

  Specification(s): function_file_test17

  Design: Problem system overview

  Issue(s): #2421

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.64The system shall report an error if one or more domain blocks do not have any active Kernels objects assigned.

  Specification(s): incomplete_kernel_block_coverage_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.65The system shall report an error if one or more variables do not have any active Kernel objects assigned.

  Specification(s): incomplete_kernel_variable_coverage_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.66The system shall report an error if one or more domain blocks do not have any active FVKernels objects assigned.

  Specification(s): incomplete_fvkernel_block_coverage_test

  Design: Problem system overview

  Issue(s): #1405#15196

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.67The system shall report an error if one or more variables do not have any active FVKernel objects assigned.

  Specification(s): incomplete_fvkernel_variable_coverage_test

  Design: Problem system overview

  Issue(s): #1405#15196

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.68The system shall report an error when an elemental variable (no continuity) is coupled to a variable with continuity.

  Specification(s): invalid_elemental_to_nodal_couple_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.69The system shall report an error when an active input block section is specified but missing.

  Specification(s): missing_active_section_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.70The system shall report an error when a material property is requested but not supplied on a mesh block.

  Specification(s): missing_coupled_mat_prop_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.71The system shall report an error when a coupled variable is supplied that was not added as a valid parameter.

  Specification(s): coupled_grad_without_declare

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.72The system shall report an error when the data file is non-existent or not-readable in the Piecewise utility.

  Specification(s): missing_function_file_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.73The system shall report an error when the coupled function does not exist or can not be parsed by a piecewise utility.

  Specification(s): missing_function_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.74The system shall report an error when one or more material properties are missing from any mesh block.

  Specification(s): missing_material_prop_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.75The system shall report an error when a material property is supplied on some blocks but missing on other blocks where it is requested.

  Specification(s): missing_material_prop_test2

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.76The system shall report an error when only "old" properties are supplied but current properties are requested.

  Specification(s): bad_stateful_material_only_old

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.77The system shall report an error when only "older" properties are supplied but current properties are requested.

  Specification(s): bad_stateful_material_only_older

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.78The system shall report an error when the mesh file cannot be found.

  Specification(s): missing_mesh_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.79The system shall report an error when a required parameter is not supplied in an Action.

  Specification(s): missing_req_par_action_obj_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.80The system shall report an error when a specific mesh required parameter is not supplied.

  Specification(s): missing_req_par_mesh_block_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.81The system shall report an error when the special "type" parameter is not supplied for a MooseObject.

  Specification(s): missing_req_par_moose_obj_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.82The system shall report an error when a required parameter is not supplied in a MooseObject.

  Specification(s): missing_required_param_in_kernel_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.83The system shall report an error when the variable parameter is missing from a residual object

  Specification(s): missing_var_parameter_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.84The system shall report an error when a required coupling parameter is missing.

  Specification(s): missing_required_coupled_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.85The system shall report an error when more than one preconditioner block is supplied.

  Specification(s): multi_precond_test

  Design: Problem system overview

  Issue(s): #1904

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.87The system shall abort the solve and report a floating point error when a NaN is produced during user computation with the Transient executioner.

  Specification(s): nan_no_trap_fpe_test_trans

  Design: Problem system overview

  Issue(s): #374#3614

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.88The system shall report an error when a nodal AuxKernel attempts to access a material property.

  Specification(s): nodal_material_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.89The system shall report an error when the same named parameter appears multiple times in the same input file.

  Specification(s): override_name_variable_test

  Design: Problem system overview

  Issue(s): #9617

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.90The system shall report an error when the coordinate transformation conflicts with the underlying element types.

  Specification(s): rz_3d_error_check_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.91The system shall report an error when solver and auxiliary variables are declared with the same name.

  Specification(s): same_name_variable_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.92The system shall report an error when an AuxKernel is applied outside of the domain where a restricted variable exists.

  Specification(s): subdomain_restricted_auxkernel_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.93The system shall report an error when a Kernel is applied outside of the domain where a restricted variable exists.

  Specification(s): subdomain_restricted_kernel_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.94The system shall report an error when an unused parameter is provided through the input file or an Action.

  Specification(s): unused_param_test

  Design: Problem system overview

  Issue(s): #709#759#4101

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.95The system shall report an error when an unused parameter is supplied on the command line.

  Specification(s): unused_param_test_cli

  Design: Problem system overview

  Issue(s): #709#759#4101

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.98The system shall report an error when a UserObject and a Postprocessor are added with the same names.

  Specification(s): uo_pps_name_collision_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.99The system shall report and error when a UserObject and a VectorPostprocessor are added with the same names.

  Specification(s): uo_vector_pps_name_collision_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.100The system shall report an error when an input file block associated with a pluggable system is asked to build an object from a different system.

  Specification(s): wrong_object_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  224
• 15.42.101The system shall report an error when an input file block associated with a pluggable system is misspelled.

  Specification(s): wrong_action_spelling

  Design: Problem system overview

  Issue(s): #20062

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.103The system shall report an error when a required variable is missing from the ICs input file block.

  Specification(s): ics_missing_variable

  Design: Problem system overview

  Issue(s): #534

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.104The system shall report an error when a boundary restriction is applied to a non-nodal variable discretization.

  Specification(s): ic_bnd_for_non_nodal

  Design: Problem system overview

  Issue(s): #534

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.105The system shall report an error when coupling to old temporal solution vectors in a Steady (no time) Executioner.

  Specification(s): old_integrity_check

  Design: Problem system overview

  Issue(s): #380

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.106The system shall report an error when coupling to a time derivative solution vector in a Steady (no time) Executioner.

  Specification(s): dot_integrity_check

  Design: Problem system overview

  Issue(s): #10810

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.107The system shall report an error when an older scalar solution variable is accessed in a Steady (no time) Executioner.

  Specification(s): scalar_old_integrity_check

  Design: Problem system overview

  Issue(s): #10810

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.108The system shall report an error when an older time derivative scalar solution variable is accessed in a Steady (no time) Executioner.

  Specification(s): scalar_dot_integrity_check

  Design: Problem system overview

  Issue(s): #10810

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.109The system shall report an error when a coupled variable is not defined in the same region as the variable performing the coupling.

  Specification(s): node_value_off_block

  Design: Problem system overview

  Issue(s): #2849

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  10
• 15.42.111The system shall report an error when performing nodal constraints when there is a mismatch in the number of constrained nodes.

  Specification(s): check_syntax_error

  Design: Problem system overview

  Issue(s): #4437

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  148
• 15.42.112The system shall report an error when requested to check the syntax in an input file but no input file is supplied.

  Specification(s): check_syntax_no_input

  Design: Problem system overview

  Issue(s): #4437

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.113The system shall report an error when multiple time schemes are specified in the same input file.

  Specification(s): multiple_time_int_check

  Design: Problem system overview

  Issue(s): #5463

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.114The system shall report an error when there is a mismatch between the parameter for an object and the type of object are mismatched.

  Specification(s): calling_wrong_feproblem_method

  Design: Problem system overview

  Issue(s): #6383

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.115The system shall report an error when the variables representing displacement are of a lower order than the mesh.

  Specification(s): wrong_displacement_order

  Design: Problem system overview

  Issue(s): #6561

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.117The system shall report an error when floating point input parameter types fail to parse as floating point numbers.

  Specification(s): bad_number

  Design: Problem system overview

  Issue(s): #10310

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.118The system shall report an error when a scalar variable is used where a spatial variable is expected.

  Specification(s): coupling_field_into_scalar

  Design: Problem system overview

  Issue(s): #10398

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.119The system shall report an error when a field variable is used where a scalar variable is expected.

  Specification(s): coupling_scalar_into_field

  Design: Problem system overview

  Issue(s): #10398

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.120The system shall report an error when an invalid coupled spatial variable is requested.

  Specification(s): coupling_nonexistent_field

  Design: Problem system overview

  Issue(s): #10398

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.121The system shall report an error when an invalid coupled scalar variable is requested.

  Specification(s): coupling_nonexistent_scalar

  Design: Problem system overview

  Issue(s): #10398

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.122The system shall report an error when an attempt is made to couple a variable with itself.

  Specification(s): coupling_itself

  Design: Problem system overview

  Issue(s): #10398

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.123The system shall report an error when an attempt is made to couple a variable with itself in coupled force term using automated differentiation.

  Specification(s): coupling_itself_ad

  Design: Problem system overview

  Issue(s): #18214

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.124The system shall report an error when an input file cannot be opened and read.

  Specification(s): missing_input

  Design: Problem system overview

  Issue(s): #10909

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.125The system shall report an error when a Kernel attempts to use an auxiliary variable.

  Specification(s): kernel_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.126The system shall report an error when a boundary condition object attempts to use an auxiliary variable.

  Specification(s): bc_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.127The system shall report an error when an AuxKernel specifies a non-existent variable.

  Specification(s): aux_kernel_with_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.128The system shall report an error when a scalar Kernel specifies a non-existent variable.

  Specification(s): scalar_kernel_with_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.129The system shall report an error when a nodal Kernel attempts to use an auxiliary variable.

  Specification(s): nodal_kernel_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.130The system shall report an error when a constraint attempts to use an auxiliary variable.

  Specification(s): constraint_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.131The system shall report an error when a scalar auxiliary Kernel attempts to use a solution variable.

  Specification(s): scalar_aux_kernel_with_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.132The system shall report an error when a DiracKernel attempts to use an auxiliary variable.

  Specification(s): dirac_kernel_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.133The system shall report an error when a discontinuous Galerkin Kernel attempts to use an auxiliary variable.

  Specification(s): dg_kernel_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.134The system shall report an error when an interface Kernel attempts to use an auxiliary variable.

  Specification(s): interface_kernel_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.135The system shall report an error when a Kernel attempts to retrieve an empty string variable.

  Specification(s): kernel_with_empty_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.136The system shall report an error when a vector Kernel attempts to use a scalar solution variable.

  Specification(s): vector_kernel_with_standard_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.137The system shall report an error when a Kernel attempts to use a vector solution variable.

  Specification(s): kernel_with_vector_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.138The system shall report an error if users try to get nodal values of non-nodal variables.

  Specification(s): coupled_nodal_for_non_nodal_variable

  Design: Coupleable

  Issue(s): #11623

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.139The system shall report an error if users try to get old nodal values of non-nodal variables.

  Specification(s): coupled_nodal_for_non_nodal_variable_old

  Design: Coupleable

  Issue(s): #11623

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.140The system shall report an error if users try to get older nodal values of non-nodal variables.

  Specification(s): coupled_nodal_for_non_nodal_variable_older

  Design: Coupleable

  Issue(s): #11623

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.141The system shall report an error if an object tries to get the name of a coupled constant.

  Specification(s): coupled_constant_yet_needs_name

  Design: Coupleable

  Issue(s): #22597

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.142The system shall have an integrity check that ensures an Executioner object exists in the system.

  Specification(s): missing_executioner

  Design: Executioner System

  Issue(s): #11586

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.143The system shall report an error when nodal boundary condition is applied on a non-nodal variable.

  Specification(s): nodal_bc_on_elemental_var

  Design: NonlinearSystem

  Issue(s): #14019

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.144The system shall report an error when a git-lfs file pointer is encountered for the mesh file.

  Specification(s): check_git_lfs_pointer

  Design: MooseUtils Namespace

  Issue(s): #17407

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.145The system shall report an error when a git-lfs file pointer is encountered for the mesh for a mesh generator.

  Specification(s): check_git_lfs_pointer_fmg

  Design: MooseUtils Namespace

  Issue(s): #17407

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.146The system shall report a helpful error when the dump parameter does not match any valid parameters

  Specification(s): dump_error_with_unrecogized_param

  Design: Problem system overview

  Issue(s): #26714

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.149The system shall throw an exception if a data file cannot be found in any of the designated directories.

  Specification(s): error

  Design: MooseObject

  Issue(s): #20839

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.153The system shall produce an error when the –no-deprecated-flag is passed and deprecated code is executed.

  Specification(s): expired_error

  Design: MooseApp

  Issue(s): #10745

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.168The system shall support throwing an error during a residual calculation, which will terminate the solve.

  Specification(s): parallel_error_residual_transient_non_zero_rank

  Design: MooseException

  Issue(s): #3777#9181

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.169The system shall support throwing an error during a Jacobian calculation, which will terminate the solve.

  Specification(s): parallel_error_jacobian_transient_non_zero_rank

  Design: MooseException

  Issue(s): #3777#9181

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.176The system shall verify equality among the current, old, and older solution vectors prior to running the simulation.

  Specification(s): equal_solutions

  Design: ICs System

  Issue(s): #1396

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.182A 3D simulation shall throw an exception if there is a zero element Jacobian, when use_displaced_mesh = true

  Specification(s): jacobian_zero

  Design: Assembly

  Issue(s): #9740

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.42.181

  234
• 15.42.183A 3D simulation shall throw an exception if there is a negative element Jacobian, when use_displaced_mesh = true

  Specification(s): jacobian_negative

  Design: Assembly

  Issue(s): #9740

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.42.181

  234
• 15.42.186A 2D simulation shall throw an exception if there is a zero element Jacobian, when use_displaced_mesh = true

  Specification(s): jacobian_zero_2D

  Design: Assembly

  Issue(s): #9740#10229

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  Prerequisite(s): 15.42.185

  234
• 15.42.196The system shall report an error if the user provides inconsistent parameter values to the mesh and problem for the parameters related to
  1. subdomain blocks
  2. coordinate system types

  Specification(s): bad_params/block, bad_params/coord_type

  Design: Mesh System

  Issue(s): #21975

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.42.206The system shall print an understandable message when a user-specified path/file does not exist.

  Specification(s): except01

  Design: Parser

  Issue(s): #15718

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.210The system shall report an error if the residual calculation contribution is assigned to the incorrect variable for
  1. on-diagonal and
  2. off-diagonal terms.

  Specification(s): error/test_soln_var_err, error/test_diag_sol_var_err

  Design: Kernels System

  Issue(s): 4cb5e2a9f87973dba738584db39f7db935b65ce5

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234234
• 15.42.227The system shall not accept a converged solution if the solution has been tagged as invalid.

  Specification(s): solution_invalid

  Design: SolutionInvalidity

  Issue(s): #22814

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunException

  234
• 15.42.229The system shall be able to count warnings through the solution invalidity interface and report them,
  1. unless the user specifies to silence them,
  2. and otherwise both in the console window and a json file.

  Specification(s): solution_invalid_warning/no_console_output, solution_invalid_warning/console_output

  Design: SolutionInvalidity

  Issue(s): #22814

  Collection(s): FUNCTIONALFAILURE_ANALYSIS

  Type(s): RunExceptionRunApp

  234234