Reconstructed Discontinuous Galerkin Failure Analysis Report

Introduction

The Software Requirement Specification (SRS) for Reconstructed Discontinuous Galerkin describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.

Dependencies

The Reconstructed Discontinuous Galerkin application is developed using MOOSE and is based on various modules, as such the SRS for Reconstructed Discontinuous Galerkin 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 Reconstructed Discontinuous Galerkin.

• rdg: Actions
• 11.1.2The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.1.4The system shall report an informative error when object parameters are constructed using legacy methods

  Specification(s): test

  Design: CheckLegacyParamsAction

  Issue(s): #19439

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

• rdg: Auxkernels
• 11.3.9The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.3.16The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.3.59The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  8989648989
• 11.3.70The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.3.76Error an AuxKernel object attemps to couple to the time derivative of an auxiliary variable.

  Specification(s): coupled_aux_time_derivative

  Design: AuxKernels SystemKernels SystemAuxVariable

  Issue(s): #442

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.3.80The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.3.90The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Bcs
• 11.4.28The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.4.53The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.4.51

  64

• rdg: Controls
• 11.6.7The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.9The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.10The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  5
• 11.6.11The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.12The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.22The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.41The TimePeriod object shall error when used with a steady state problem.

  Specification(s): steady_error

  Design: TimePeriod

  Issue(s): #5676

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.42The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.43The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.44The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.6.45The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Dampers
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.8.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: DGKernel Objects
• 11.9.15The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Dirackernels
• 11.10.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunApp

  6464
• 11.10.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.10.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.10.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 steady state 3D problem, reproducing the constantPointSource.
  4. in a transient problem with the vpp source value changing as the vpp changes.
  5. and shall report an error if the input arrays are not the same size

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

  Design: ReporterPointSource

  Issue(s): #15831#18528

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionCSVDiffExodiff

  6489898989

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

  Specification(s): cycle

  Design: Executor

  Issue(s): #5229#18180

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.12.3The system shall only have one root node in the Executor tree

  Specification(s): multi_root

  Design: Executor

  Issue(s): #5229#18180

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Functions
• 11.14.10The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.12The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  38383826
• 11.14.31The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.42The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.46The system shall error out 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464646464
• 11.14.47The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.14.50The PiecewiseMultilinear object will error if the supplied file fails to open.

  Specification(s): except1

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.51The PiecewiseMultiInterpolation object shall error if the supplied data is not monotonically increasing.

  Specification(s): except2

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.52The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.53The PiecewiseMultiInterpolation errors if the axes supplied are not independent.

  Specification(s): except4

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

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

  Specification(s): except5

  Design: PiecewiseMultilinear

  Issue(s): #2476

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.14.72The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Fvbcs
• 11.15.2The system shall error out 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.15.3The system shall error out 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Fviks
• 11.16.3The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.16.4The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.16.5The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Fvkernels
• 11.17.14The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

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

  Specification(s): never_warning

  Design: GapValueAuxMesh System

  Issue(s): #3901

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.18.51

  64

• rdg: Ics
• 11.20.2The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.4The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.32The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.20.42The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.43The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.20.44The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: InterfaceKernel Objects
• 11.22.31The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Interfaces
• 11.23.2The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.23.3The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.23.4The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.23.5The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.23.16The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.23.17The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.23.18The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.23.19The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.23.20The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464646464
• 11.23.22The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.23.23The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.23.24The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464

• rdg: Kernels
• 11.24.20The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.25The system will error and tell the user if they use derivative storage that is too small

  Specification(s): ad_max_dofs_per_elem_error

  Design: DualReal

  Issue(s): #5658

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.24.65The system shall report an error when a parsed function expression contains quote characters.

  Specification(s): parsed_func_error_check

  Design: Kernels System

  Issue(s): #1405

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.78The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.80The system shall issue an error for not fully supported distributed mesh with hybrid finite element method (HFEM) calculations.

  Specification(s): robin_distributed_mesh

  Design: DGKernels System

  Issue(s): #17447

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.24.110We 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.md

  Issue(s): #12601

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.113We 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.md

  Issue(s): #12601

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.117The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.118Time kernel requires a transient executioner

  Specification(s): bad_transient

  Design: TaggingInterface

  Issue(s): #9669

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.119The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.120The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.138The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.24.139The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Make Install
• 11.25.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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunCommandRunAppCheckFiles

  83595959595959

• rdg: Markers
• 11.26.13It 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.26.17The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

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

  Specification(s): test_err1

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.27.11

  64
• 11.27.14ADPiecewiseLinearInterpolationMaterial shall throw an error if x and xy_data are both specified

  Specification(s): test_err2

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.27.13

  64
• 11.27.15ADPiecewiseLinearInterpolationMaterial shall throw an error if x and y vectors are different lengths

  Specification(s): test_err3

  Design: ADPiecewiseLinearInterpolationMaterial

  Issue(s): #8265

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.27.14

  64
• 11.27.16ADPiecewiseLinearInterpolationMaterial 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.27.15

  64
• 11.27.24Duplicate 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.25A 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.27The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.32The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.33The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunApp

  64646464
• 11.27.34The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunApp

  64646464
• 11.27.41The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.42The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunApp

  64646464
• 11.27.43The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  89646464
• 11.27.44The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunApp

  896489646464
• 11.27.48The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.49The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.27.50The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.52The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464646464
• 11.27.56The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.27.5111.27.5411.27.55

  64
• 11.27.60The system shall error if a functor material property is declared as returning one type and is retrieved as returning a different type.

  Specification(s): inconsistent_types

  Design: Materials System

  Issue(s): #16809

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.27.61The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.62The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.66The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.27.69The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.27.71The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.72The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.74The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.82The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.83The system shall error is a material property is requested on a subdomain on which it is not defined.

  Specification(s): mat_block_boundary_check

  Design: Materials System

  Issue(s): 6683d503d6441165249f8d49c65b76722430019a

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.27.85The system shall error if material properties are not computed on all subdomains.

  Specification(s): check_test

  Design: Materials System

  Issue(s): 6683d503d6441165249f8d49c65b76722430019a

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.93The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.27.96The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.97The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.27.103The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.27.117The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.27.1011.27.6411.27.8411.27.8911.27.9011.27.10411.27.10611.27.116

  64

• rdg: Mesh
• 11.28.42The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464646464646464
• 11.28.67The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.28.68The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.28.74The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.28.80The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  16
• 11.28.86The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.28.88The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Mesh Modifiers
• 11.29.2The system shall support assigning boundary identifiers based on
  1. a nodal id,
  2. a spatial coordinate, and
  3. if the supplied location is outside of the domain.

  Specification(s): extra/test, extra/test_coord, extra/test_bad_coord

  Design: Mesh System

  Issue(s): #13814

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff
• 11.29.5The system shall support assigning boundary identifiers based the bounding box of a subdomain and error if
  1. if no elements are located in the given bounding box;
  2. if no sides are located in the given bounding box;
  3. if no nodes are located in the given bounding box; and
  4. if the incorrect boundary inputs are supplied.

  Specification(s): error/error_no_elements_in_bounding_box, error/error_no_side_sets_found, error/error_no_nodes_found, error/error_boundary_number

  Design: Mesh System

  Issue(s): #13814

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.29.6The 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: Mesh System

  Issue(s): #13814

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff
• 11.29.11The system shall error when adding nodeset identifiers given a bounding box and
  1. the supplied location is invalid and
  2. when multiple ids are provided for assignment.

  Specification(s): error/test_bad_coord, error/test_bad_boundaryid

  Design: Mesh System

  Issue(s): #13814

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

• rdg: Meshgenerators
• 11.30.8The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  48
• 11.30.9The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  48
• 11.30.14The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.30.24The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.30.32The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.38The system shall error out 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.50The system shall error when requesting
  1. a MeshGenerator by parameter and the parameter is not valid
  2. a MeshGenerator by parameter and the parameter is of the wrong type
  3. MeshGenerators by parameter and the parameter is not valid
  4. MeshGenerators by parameter and the parameter is of the wrong type

  Specification(s): tests/get_mesh_invalid, tests/get_mesh_wrong_type, tests/get_meshes_by_name_invalid, tests/get_meshes_by_name_wrong_type

  Design: MeshGenerator

  Issue(s): #19285

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.30.70The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.71The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.72The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.77The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  48
• 11.30.78The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  48
• 11.30.79The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  48
• 11.30.82The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.30.87The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.30.2711.30.5511.30.5911.30.8311.30.10911.30.124

  64
• 11.30.97The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.98The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.102The system shall error if the node to be moved cannot be found in the mesh.

  Specification(s): failure_missing

  Design: MoveNodeGenerator

  Issue(s): #18577

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.103The system shall error if the node position and node id arrays do not match in size

  Specification(s): failure_mismatch

  Design: MoveNodeGenerator

  Issue(s): #18577

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.30.114The system shall error if the specified boundary to be refined does not exist

  Specification(s): failureBoundary

  Design: RefineSidesetGenerator

  Issue(s): #18913

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.30.117The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.30.119The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

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

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

  Design: RenameBoundaryGenerator

  Issue(s): #11640#14128#16885

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.30.128The 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.

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

  Design: SideSetsFromBoundingBoxGenerator

  Issue(s): #11640

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  484848
• 11.30.135The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  484848

• rdg: Misc
• 11.32.7The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.8The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.9The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.10The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.12The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.13The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.14The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.15The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.16The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.17The 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

  64
• 11.32.18The 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

  64
• 11.32.19The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.20The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.21The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.22The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.23The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.24The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.25The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.26The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.27The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.28The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.29The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.30The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  5
• 11.32.31The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.34The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.35The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.36The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.37The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.38The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.39The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.40The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.41The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.42The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.43The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.44The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.45The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.46The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.47The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.48The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.49The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.50The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.51The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.52The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.53The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.54The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.55The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.56The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.57The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.58The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.59The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.60The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.61The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.62The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.63The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.64The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.65The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.66The system shall report an error when the coupled function does not exist or can not be parsedfor the Piecewise utility.

  Specification(s): missing_function_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.67The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.68The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.69The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.70The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.71The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.72The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.73The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.74The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

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

  Specification(s): missing_var_in_kernel_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.32.76The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.77The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.79The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.80The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.81The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.82The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.83The system shall report an error when nonlinear and auxiliary variables are declared with the same name.

  Specification(s): same_name_variable_test

  Design: Problem system overview

  Issue(s): #1405

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.84The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.85The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.88The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.89The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.90The system shall report an error when an input file block associated with on 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  59
• 11.32.92The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.93The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.94The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.95The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.96The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.97The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.98The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  5
• 11.32.100The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  48
• 11.32.101The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.102The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.103The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.104The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.106The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.107The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.108The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.109The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.110The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.111The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.112The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.113The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.114The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.115The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.116The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.117The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.118The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.119The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.120The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.121The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.122The system shall report an error when a discontinuous Galerkin Kernel attempts to use a solution variable.

  Specification(s): dg_kernel_with_aux_var

  Design: Problem system overview

  Issue(s): #11039

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.123The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.124The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.125The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.126The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.127The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.128The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.129The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.130The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.131The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.132The system shall report an error when a git-lfs file pointer is encountered.

  Specification(s): check_git_lfs_pointer

  Design: MooseUtils Namespace

  Issue(s): #17407

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.135The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.139The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.149The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.150The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.156The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.162A 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.32.161

  64
• 11.32.163A 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.32.161

  64
• 11.32.166A 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.32.165

  64
• 11.32.177The 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.32.179The system shall 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): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464

• rdg: Multiapps
• 11.34.4The system shall detect input file problems with sub app input files.

  Specification(s): input_file

  Design: MultiApp System

  Issue(s): #4101#4113

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.5The system shall CLI argument problems related to sub app input files.

  Specification(s): unused_subapp_param

  Design: MultiApp System

  Issue(s): #4101#4113

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.6The system show error when the number of input files is great than one and doesn't match the number of provided sub app positions.

  Specification(s): positions

  Design: MultiApp System

  Issue(s): #1845#3556#5784

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.7The system show error when the number of input files is great than one and doesn't match the number of provided sub app positions when using CLI overrides.

  Specification(s): not_enough_positions

  Design: MultiApp System

  Issue(s): #1845#3556#5784

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.8The system shall error when the number of sub app input files doesn't match the number of provided positions files.

  Specification(s): not_enough_position_files

  Design: MultiApp System

  Issue(s): #1845#3556#5784

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.9The system shall error when both positions are provided in the input file along with a separate file of positions.

  Specification(s): both_positions

  Design: MultiApp System

  Issue(s): #1845#3556#5784

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.10The system shall error when the multiapp positions file is malformed.

  Specification(s): bad_positions

  Design: MultiApp System

  Issue(s): #1845#3556#5784

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.11The system shall error when the Multiapp parameter sub_cycling and catch_up are both set to true.

  Specification(s): sub_cycling_and_catch_up

  Design: MultiApp System

  Issue(s): #6127

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.16The system shall not support commandLine arguments from a file and an input at the same time

  Specification(s): input_and_from_file

  Design: MultiApp System

  Issue(s): #18596

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.17The system shall make sure the number of commandLine argument files either be only one or match the number of input files

  Specification(s): input_and_file

  Design: MultiApp System

  Issue(s): #18596

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.18The system shall provide at least one commandLine argument file when use parameter 'cli_args_files'

  Specification(s): no_cliarg_file

  Design: MultiApp System

  Issue(s): #18596

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.19The system shall not use an empty commandLine argument file

  Specification(s): empty_cliarg_file

  Design: MultiApp System

  Issue(s): #18596

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.20The system shall the total number of commandLine argument strings be only one or match the total number of sub apps

  Specification(s): inconsistent_cliargs_from_file

  Design: MultiApp System

  Issue(s): #18596

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.21The system shall the total number of commandLine argument strings from a file be only one or match the total number of positions

  Specification(s): positions_and_cliargs

  Design: MultiApp System

  Issue(s): #18596

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.24The MultiApp system shall error when the number of command line arguments supplied in the input file differs from the number if sub apps.

  Specification(s): wrong_size

  Design: MultiApp System

  Issue(s): #12576

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.28When sub-application solve does not converge, the system shall be able to either
  1. abort run,
  2. throw error if error_on_dtmin is not set, or
  3. continue run.

  Specification(s): solve_not_converge/abort, solve_not_converge/error, solve_not_converge/continue

  Design: FullSolveMultiApp

  Issue(s): #1940

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  896464
• 11.34.31The system shall error if the execution of a sub-application fails during the initial execution.

  Specification(s): initial_multiapp_failure

  Design: MultiApp System

  Issue(s): #7213

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.34.61The system should be able to check if users provide valid parameter to restart app using the latest solution

  Specification(s): parameter_error

  Design: TransientMultiApp

  Issue(s): #14056

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.34.60

  64
• 11.34.75The system shall error if provided relaxation factor that is less than or equal to 0 or greater than or equal to 2.

  Specification(s): bad_relax_factor

  Design: Executioner System

  Issue(s): #9115

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Nodalkernels
• 11.35.4The system shall be able to enforce an upper and lower bound on a variable using nodal NCP, nodal application of resultant forces,
  1. have no oscillations in the solution, and
  2. work with automatic differentiation, and
  3. have a non-singular matrix, and
  4. be incompataible with algebraic multigrid

  Specification(s): upper_and_lower_bound/exo, upper_and_lower_bound/ad_exo, upper_and_lower_bound/non_singular, upper_and_lower_bound/amg_fail

  Design: UpperBoundNodalKernel

  Issue(s): #2999

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunAppExodiff

  89648964

• rdg: Outputs
• 11.36.31The system shall error when specifying an invalid table fit width option.

  Specification(s): console_fit_width_error

  Design: Console

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.54If the user requested the output of a displaced problem and there is none present, the system shall fallback to using the non-displaced problem.

  Specification(s): non_displaced_fallback

  Design: Output System

  Issue(s): #11309

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.55If the user asks for no displaced mesh to be created, even though displacements are provided in the mesh block, the system shall not create a displaced mesh

  Specification(s): mesh_use_displaced_mesh_false

  Design: Mesh System

  Issue(s): #12580

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.36.54

  64
• 11.36.60The system shall error when two outputs with the same name are created.

  Specification(s): duplicate_objects

  Design: Output System

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.61The system shall error when two outputs produce a file with the same name.

  Specification(s): duplicate_output_files

  Design: Output System

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.62The system shall reserve names for output objects:
  1. "none" and
  2. "all."

  Specification(s): reserved/none_reserved, reserved/all_reserved

  Design: Output System

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.36.69The system shall error if the supplied names for including or excluding variables is invalid.

  Specification(s): invalid_hide

  Design: Exodus

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.114The system shall support the disabling of an output object by restricting the execution settings.

  Specification(s): no_output

  Design: Output System

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.125The system shall provide an API for retrieving an output object by type and name.

  Specification(s): getOutput

  Design: OutputWarehouse

  Issue(s): #2885

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.126The system shall provide an API for retrieving all output objects of a type.

  Specification(s): getOutputs

  Design: OutputWarehouse

  Issue(s): #2885

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.127The system shall provide an API for retrieving output objects for the given names and type.

  Specification(s): getOutputs_with_names

  Design: OutputWarehouse

  Issue(s): #2885

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.128The system shall provide an API for retrieving all output object names of a type.

  Specification(s): getOutputNames

  Design: OutputWarehouse

  Issue(s): #2885

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.148The system shall error if an invalid output name is provided within the postprocessor input file block.

  Specification(s): invalid_outputs

  Design: Output SystemOutputInterface

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.151The system shall error if a postprocessor variable is listed for suppression and inclusion within an output object block in the input file.

  Specification(s): test_hidden_shown

  Design: Output SystemOutputInterface

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.171The system shall error if a variable is marked for output and output suppression.

  Specification(s): test_hidden_shown

  Design: Output System

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.36.172The system shall error if a variable is perscribed for output but does not exist.

  Specification(s): test_nonexistent

  Design: Output System

  Issue(s): #1927

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Parser
• 11.37.2The system shall produce an error when the active parameter refers to a non-exiseant block.

  Specification(s): active_section_missing

  Design: Parser

  Issue(s): #9411#9571

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.3The system shall produce an error when the inactive parameter refers to a non-existent block.

  Specification(s): inactive_section_missing

  Design: Parser

  Issue(s): #9411#9571

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.4The system shall produce an error when both the active and inactive parameters are present in the same block.

  Specification(s): inactive_active_combo

  Design: Parser

  Issue(s): #9411#9571

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.5The system shall honor the active or inactive parameters at the top (root) level.

  Specification(s): top_level

  Design: Parser

  Issue(s): #9411#9571

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.10The system shall produce an error when a SubApp command line override index is not valid.

  Specification(s): cli_override_error_check

  Design: CommandLine

  Issue(s): #2137

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.37.9

  64
• 11.37.13The system shall report an error if the supplied input file is not formatted correctly.

  Specification(s): error

  Design: InputParameters

  Issue(s): #16410

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.15The system shall error if a user supplies an odd number of entries, implying an unbalanced key-value set, to a map parameter.

  Specification(s): odd_entries

  Design: Parser

  Issue(s): #14894

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.16The system shall error if a user supplies syntax in a map parameter that cannot be cast to the requested mapped type.

  Specification(s): bad_value

  Design: Parser

  Issue(s): #14894

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.17The system shall support for multiple input files, which are merged into one input specification for a simulation
  1. where no parameters overlap
  2. where input files may override parameters in previous inputs
  3. while locating input errors in the correct file
  4. and inform the user of parameters from earlier files being overidden by later files

  Specification(s): merging/two_inputs, merging/three_inputs_override, merging/three_inputs_error, merging/three_inputs_override_message

  Design: Parser

  Issue(s): #17989#18221

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunAppExodiff

  64648989
• 11.37.18The system shall raise an error if no input files were specified after the -i option

  Specification(s): no_file

  Design: Parser

  Issue(s): #17989#18221

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.23The system shall support vector size checking on input parameter vectors:
  1. for ints,
  2. for Reals.

  Specification(s): vector_len_checks/realvectorlength, vector_len_checks/intvectorlength

  Design: InputParameters

  Issue(s): #3988

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.37.24The system shall support vector element checking:
  1. against constant expressions,
  2. against other unsigned int vector elements,
  3. against other long vector elements,
  4. against other int vector elements, and
  5. against other Real vector elements.

  Specification(s): vector_elem_checks/all_element_check, vector_elem_checks/elementcompare_unsigned_int, vector_elem_checks/elementcompare_long, vector_elem_checks/elementcompare_int, vector_elem_checks/elementcompare_real

  Design: InputParameters

  Issue(s): #3988

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464646464
• 11.37.25The system shall support vector bounds checking on input parameter vectors.

  Specification(s): outofbounds

  Design: InputParameters

  Issue(s): #3988

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.37.26The system shall support checking for non-empty input parameter vectors.

  Specification(s): checkempty

  Design: InputParameters

  Issue(s): #3988

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Partitioners
• 11.38.2The block-weighted partitioner shall report a reasonable error when
  1. the input blocks do not match the size of the input weights
  2. an input block is not found in the mesh

  Specification(s): errors/size_mismatch, errors/missing_block

  Design: BlockWeightedPartitioner

  Issue(s): #13675

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.38.20The system shall error if an out of range rank is given to SingleRankPartitioner

  Specification(s): test_error

  Design: SingleRankPartitioner

  Issue(s): #18729

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Postprocessors
• 11.41.5The system shall issue an error when the dependent "change ofFixedPoint" calculation
  1. "with respect to initial" isn't calculated at the initial step and
  2. "with respect to previous" isn't calculated at the previous step.

  Specification(s): change_over_fixed_point_error/change_with_respect_to_initial_error_dependent, change_over_fixed_point_error/change_with_respect_to_initial_error_this

  Design: ChangeOverFixedPointPostprocessor

  Issue(s): #10327

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.41.7The system shall issue an error when the dependent "change of time" calculation
  1. "with respect to initial" isn't calculated at the initial step and
  2. "with respect to previous" isn't calculated at the previous step.

  Specification(s): change_over_time_error/change_with_respect_to_initial_error_dependent, change_over_time_error/change_with_respect_to_initial_error_this

  Design: ChangeOverTimePostprocessor

  Issue(s): #10327

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.41.39The system shall report and error when the target value is lower than one of the sampled endpoints.

  Specification(s): below_min

  Design: FindValueOnLine

  Issue(s): #6389#7864

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.41.40The system shall report and error when the target value is greater than one of the sampled endpoints.

  Specification(s): above_max

  Design: FindValueOnLine

  Issue(s): #6389#7864

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.41.45The system shall report and error when the sampling line extends beyond the mesh bounding box.

  Specification(s): line_out_of_bounds

  Design: FindValueOnLine

  Issue(s): #6389#7864

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.41.46The system shall report and error when the line sampling algorithm fails to converge within the desired depth.

  Specification(s): depth_exceeded

  Design: FindValueOnLine

  Issue(s): #6389#7864

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.41.91The system shall report a reasonable error when trying to obtain information from the PerfGraph for a section that does not exist

  Specification(s): missing

  Design: PerfGraphData

  Issue(s): #11551

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.41.93The system shall report an error when a field variable sample location is outside of the domain.

  Specification(s): error

  Design: PointValue

  Issue(s): #3475

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.41.103The system shall report an error when a requested parameter for reporting does not exist
  1. with a wildcard in the name and
  2. a complete name/

  Specification(s): error_report/bad_name_error, error_report/no_param_error

  Design: Postprocessor System

  Issue(s): #4604#5680#9087#6934

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.41.111The system shall support computing the average of a material property over a side on the mesh.
  1. if the material property is of Real type
  2. if the material property is of RealVectorValue type
  3. if the material property is of std::vector<Real> type
  4. if the material property is of RankTwoTensor type
  5. if the material property is of RankThreeTensor type
  6. if the material property is of RankFourTensor type
  7. And shall error out if the index components do not match the dimension of the supplied property

  Specification(s): side_average_material_property/real, side_average_material_property/realvector, side_average_material_property/stdvec, side_average_material_property/ranktwo, side_average_material_property/rankthree, side_average_material_property/rankfour, side_average_material_property/error

  Design: SideAverageMaterialProperty

  Issue(s): #18649

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionCSVDiff

  89898989648989
• 11.41.119The system shall support computing the integral of a material property over a side on the mesh.
  1. if the material property is of Real type
  2. if the material property is of RealVectorValue type
  3. if the material property is of RankTwoTensor type
  4. And shall error out if the index components do not match teh dimension of the supplied property

  Specification(s): side_integral_material_property/real, side_integral_material_property/realvector, side_integral_material_property/ranktwo, side_integral_material_property/error

  Design: SideIntegralMaterialProperty

  Issue(s): #18649

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionCSVDiff

  89896489
• 11.41.129The Postprocessor that returns a single specified component of a VectorPostprocessor shall generate an error if the requested component is out of the range of the vector

  Specification(s): vpp_component_range_err

  Design: VectorPostprocessorComponent

  Issue(s): #11439

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.41.128

  64

• rdg: Problems
• 11.44.3The system shall error out when Problem block type is not specified.

  Specification(s): with_problem_block_with_wrong_type

  Design: Problem system overview

  Issue(s): #12002

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.44.11Eigenvalue system should not allow users to use inhomogeneous nodal boundary conditions

  Specification(s): wrong_dirichlet_value_eigen

  Design: Eigenvalue

  Issue(s): #7398

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.44.12Eigenvalue system should use homogeneous boundary conditions only

  Specification(s): wrong_NodalBC_type_eigen

  Design: Eigenvalue

  Issue(s): #7398

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.44.13Eigenvalue system requires SLEPc installed

  Specification(s): no_slepc

  Design: Eigenvalue

  Issue(s): #7398

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.44.38The system shall support compatibility of solve type and constant-matrices flag

  Specification(s): check_solve_type

  Design: Eigenvalue

  Issue(s): #18493#21056

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.44.37

  64
• 11.44.58The system shall require all grouped variables to be included in the convergence check.

  Specification(s): converge_on_group_error

  Design: ReferenceResidualProblem

  Issue(s): #9151

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Reporters
• 11.47.3The system shall error if an invalid name is provided when retrieving aggregate value.

  Specification(s): error

  Design: Reporter System

  Issue(s): #11323

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.47.4The system shall report a reasonable error when declaring a Reporter value and
  1. the parameter that contains the name was not found,
  2. the parameter that contains the name is not of the correct type,
  3. a Reporter with the same name has already been declared, and
  4. a Reporter with the same name but a different type has been requested.

  Specification(s): errors/missing_param, errors/bad_param, errors/already_declared, errors/requested_different_type

  Design: Reporter System

  Issue(s): #11323

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64646464
• 11.47.7The system shall throw an error when producing constant reporter values if
  1. no values are specified,
  2. no names are specified,
  3. or the number of values and names are not equal.

  Specification(s): errors/no_values, errors/no_names, errors/mismatch

  Design: ConstantReporter

  Issue(s): #16055#20467

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464

• rdg: Restart
• 11.48.4The system shall error when
  1. a simulation is started with multiple processors but
  2. restarted with a different number processors.

  Specification(s): parallel_error/error1, parallel_error/error2

  Design: DataIORestartable

  Issue(s): #2306

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  Prerequisite(s): 11.48.2

  6464
• 11.48.5The system shall error when
  1. a simulation is started with multiple threads but
  2. restarted with a different number threads.

  Specification(s): thread_error/with_threads, thread_error/threads_error

  Design: DataIORestartable

  Issue(s): #2306

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  Prerequisite(s): 11.48.4

  6363
• 11.48.8The system shall produce an error when an attempt is made to serialize a type without a serialization (dataStore) routine when that data is declared as restartable.

  Specification(s): pointer_store_error

  Design: DataIORestartable

  Issue(s): #1169

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.48.10The system shall produce an error when an attempt is made to deserialize a type without a deserialization (dataLoad) routine when that data is declared as restartable during a restart or recover operation.

  Specification(s): pointer_load_error2

  Design: DataIORestartable

  Issue(s): #1169

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.48.9

  64
• 11.48.19The system shall issue a useful error message stating the valid options when a user requests an invalid time step number or keyword.

  Specification(s): restart_use_end_error_check

  Design: RestartableDataIO

  Issue(s): #5748

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.48.18

  64

• rdg: Restrictable
• 11.49.2The system shall error if an object is restricted to a set of subdomains that differs from a dependant object.

  Specification(s): block_undefined_var_block

  Design: BlockRestrictable Interface

  Issue(s): #2096

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.49.3The system shall include an interface that provides a method for returning all associated subdomains:
  1. as a list of names or
  2. as a list of ids.

  Specification(s): ids/blocks, ids/hasBlocks

  Design: BlockRestrictable Interface

  Issue(s): #2096

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.49.4The system shall include an interface that provides methods for indicating if the supplied subdomain identifier(s) exists on the object:
  1. if a single subdomain is supplied ant the object is not restricted;
  2. if a single subdoman is supplied and the object is restricted to a set of subdomains; and
  3. if multiple boundaries are supplied and the object is restricted to a set of subdomains.

  Specification(s): has/hasBlocks_ANY_BLOCK_ID, has/blockIDs, has/isBlockSubset

  Design: BlockRestrictable Interface

  Issue(s): #2096

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464
• 11.49.5The system shall include an interface that provides a method for indicating if the supplied material property exists on the same subdomains as the object:
  1. the method shall return true if the property subdomains match with the object subdomains and
  2. the method shall return false if the property subdomains dot not match with the object subdomains.

  Specification(s): mat/hasBlockMaterialProperty_true, mat/hasBlockMaterialProperty_false

  Design: BlockRestrictable Interface

  Issue(s): #2096

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.49.6The system shall include an interface that provides a method for returning all associated boundaries:
  1. as a list of names or
  2. as a list of ids.

  Specification(s): ids/boundary, ids/boundaryIDs

  Design: BoundaryRestrictable Interface

  Issue(s): #2149

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.49.7The system shall include an interface that provides methods for indicating if the supplied boundary identifier(s) exists on the object:
  1. if a single boundary is supplied and the object is restricted to a set of boundaries and
  2. if multiple boundaries are supplied.

  Specification(s): has/hasBoundary, has/isBoundarySubset

  Design: BoundaryRestrictable Interface

  Issue(s): #2149

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.49.8The system shall include an interface that provides a method for indicating if the supplied material property exists on the same boundaries as the object:
  1. the method shall return true if the property boundaries match with the object boundaries and
  2. the method shall return false if the property boundaries dot not match with the object boundaries.

  Specification(s): mat/hasBoundaryMaterialProperty_true, mat/hasBoundaryMaterialProperty_false

  Design: BoundaryRestrictable Interface

  Issue(s): #2149

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.49.9The system shall error if an object restricted to subdomains is created without valid data
  1. regarding the problem being solved or
  2. information regarding the finite element mesh.

  Specification(s): errors/fe_problem_null, errors/mesh_null

  Design: BlockRestrictable Interface

  Issue(s): #2411

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464
• 11.49.11The system shall issue an error when a referenced subdomain does not exist in the mesh.

  Specification(s): block

  Design: MooseMesh

  Issue(s): #2757

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Samplers
• 11.50.3The system shall include a random number sampling system that errors
  1. if the number of rows is altered during sample access,
  2. if the number of columns is altered during sample access,
  3. if the number of random number generator seeds is set after object construction,
  4. if the number of rows is set to zero,
  5. if the number of columns is set to zero,
  6. if the number of random number generator seeds is set to zero,
  7. if the number of entries in the global sample matrix exceeds the maximum allowed,
  8. if the number of entries in the local sample matrix exceeds the maximum allowed, and
  9. if the number of entries in the local sample matrix row exceeds the maximum allowed.

  Specification(s): errors/setNumberOfRows, errors/setNumberOfCols, errors/setNumberOfRandomSeeds, errors/zero_rows, errors/zero_cols, errors/zero_seeds, errors/getGlobalSamples_max, errors/getLocalSamples_max, errors/getNextLocalRow_max

  Design: Sampler

  Issue(s): #13906#16482

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464646456456464
• 11.50.4The system shall error when the expected size of a sampler is altered and accessed prior to initialization by accessing the
  1. the global sample matrix;
  2. the local sample matrix;
  3. the local sample matrix row;
  4. the total row count;
  5. the local row count;
  6. the first local row index;
  7. the last local row index;
  8. the column count.

  Specification(s): reinit_errors/getGlobalSamples, reinit_errors/getLocalSamples, reinit_errors/getNextLocalRow, reinit_errors/getNumberOfRows, reinit_errors/getNumberOfLocalRows, reinit_errors/getLocalRowBegin, reinit_errors/getLocalRowEnd, reinit_errors/getNumberOfCols

  Design: Sampler

  Issue(s): #13906

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  6464646464646464

• rdg: Scaling
• 11.52.2The system shall not allow ignoring of particular variable automatic scaling factors if they are grouped with other variables for scaling

  Specification(s): fail_with_group

  Design: NonlinearSystem

  Issue(s): #19573

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Tag
• 11.54.2The system shall throw an error when the variable orders and families for the tagged and the auxiliary output variables do not match.

  Specification(s): tag_vector_error

  Design: TaggingInterface

  Issue(s): #9669

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Time Integrators
• 11.55.3The system shall report an error if an explicit solver fails to converge with
  1. first-order, forward Euler,
  2. with mass lumping, and
  3. with mass lumping and preconditioning.

  Specification(s): errors/diverged, errors/diverged_lumped, errors/diverged_lump_prec

  Design: ActuallyExplicitEuler

  Issue(s): #10837

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464
• 11.55.23The system shall provide an informative error message when a user uses an invalid solve type for an explicit time integrator.

  Specification(s): invalid_solve_type

  Design: ExplicitSSPRungeKutta

  Issue(s): #18646

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Time Steppers
• 11.56.9The system shall check that a timestep limiting function has been defined when a user specifies the 'force_step_every_function_point' parameter as true.

  Specification(s): hit_knot_err1

  Design: IterationAdaptiveDT

  Issue(s): #5535

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.56.10The system shall check that a timestep limiting function has been defined when a user specifies a value for the 'max_function_change' parameter.

  Specification(s): hit_knot_err2

  Design: IterationAdaptiveDT

  Issue(s): #5535

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.56.28The system shall support the ability to choose time step sizes based on a sequence of increasing numbers:
  1. beginning at the default start time,
  2. beginning at an earlier time than the sequence numbers,
  3. beginning at a time somewhere in-between existing sequence numbers, and
  4. when reading the sequence from an ExodusII formatted input file.
  5. that must be sorted in ascending order,
  6. that must be sorted in strictly ascending order,
  7. when reading the sequence from a comma-separated input file.

  Specification(s): time_sequence/timesequence_no_start_time, time_sequence/timesequence_earlier_start_time, time_sequence/timesequence_later_start_time, time_sequence/exodustimesequence, time_sequence/not_sorted, time_sequence/not_sorted_strictly, time_sequence/csvtimesequence

  Design: TimeSequenceStepper

  Issue(s): #9698#6353#6795

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  89648964898989
• 11.56.31The system shall support the ability to run a calculation for the purpose of creating a time sequence restart file suitable for failure:
  1. when writing the checkpoint file,
  2. when restarting where the time sequence is different prior to the failure.

  Specification(s): restart_failure/timesequence_restart_failure_1, restart_failure/timesequence_restart_failure2

  Design: TimeSequenceStepper

  Issue(s): #9698#6353#6795

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionExodiff

  6464
• 11.56.32The system shall report an error if the initial time step size is calculated to be zero.

  Specification(s): test

  Design: TimeStepper System

  Issue(s): #10553

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64

• rdg: Transfers
• 11.57.1The system shall error if the user does not provide sufficient information to determine the originator and destination of transfer information.

  Specification(s): need_multi_app

  Design: Transfers System

  Issue(s): #19451

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.57.2The system shall error if the user provides a mix of non-deprecated and deprecated parameters.

  Specification(s): mixing_parameters

  Design: Transfers System

  Issue(s): #19451

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.57.6The system shall check execute_on for PP in sub app

  Specification(s): test_execute_on

  Design: MultiAppConservativeTransfer

  Issue(s): #12948#17231

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.57.311.57.511.57.1611.57.2011.57.2111.57.2411.57.2511.57.2611.57.2711.57.2811.57.3011.57.3111.57.9411.57.96

  64
• 11.57.8The system shall check execute_on for PP in master app

  Specification(s): subs_execute_on

  Design: MultiAppConservativeTransfer

  Issue(s): #12948#17231

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.57.7

  64
• 11.57.10The system shall check execute_on for vector PP in master app

  Specification(s): nearest_point_execute_on

  Design: MultiAppConservativeTransfer

  Issue(s): #12948#17231

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.57.9

  64
• 11.57.18The system shall error if a variable, during a direct copy of auxiliary field variables, does not exist
  1. in the sub-application when transferring form it and
  2. in the master application when transferring for it.

  Specification(s): errors/error_from_sub_to_master, errors/error_to_sub_to_master

  Design: MultiAppCopyTransfer

  Issue(s): #13754

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.57.22The system shall error when the MultiAppCopyTransfer object is used on non-identical meshes.

  Specification(s): different_mesh

  Design: MultiAppCopyTransfer

  Issue(s): #7757

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.57.23The system shall error when the MultiAppCopyTransfer object is used on meshes with different variable types.

  Specification(s): different_variable_type

  Design: MultiAppCopyTransfer

  Issue(s): #7757

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.57.42The system shall error if preforming a transfer of data using the finite element solution if:
  1. the evaluation point does not exist and
  2. if the execution settings do not match between the master and sub-applications.

  Specification(s): errors/missed_point, errors/mismatch_exec_on

  Design: MultiAppMeshFunctionTransfer

  Issue(s): #1836

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionRunApp

  6464
• 11.57.56The system shall report an error if a data transfer is requested for a data variable that is not defined.

  Specification(s): test_error

  Design: MultiAppPostprocessorInterpolationTransfer

  Issue(s): #1737

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.57.55

  64
• 11.57.57The system shall report an error if a variable is specified that is not LINEAR LAGRANGE or CONSTANT MONOMIAL

  Specification(s): fetype_error

  Design: MultiAppPostprocessorInterpolationTransfer

  Issue(s): #1737

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.57.55

  64
• 11.57.58The system shall report an error if parameters for an unsupported direction are provided for the transfer between sub-app scalars and a main app field variablea.

  Specification(s): direction_error

  Design: MultiAppPostprocessorInterpolationTransfer

  Issue(s): #1737

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.57.61The system shall error during the transfer of scalar variable and postprocessor data if the number of sub-applications differs from the order of the scalar variable if
  1. the order is too large and
  2. the order is too small.

  Specification(s): error/sub_to_master_wrong_order, error/sub_to_master_wrong_positions

  Design: MultiAppPostprocessorToAuxScalarTransfer

  Issue(s): #2340

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.57.71The system shall support the ability to transfer reporter data and error if an invalid sub-application number is supplied when transferring data
  1. to a sub-application,
  2. from a sub-application.
  3. from multiple sub-applications.

  Specification(s): errors/to_app, errors/from_app, errors/from_multi_app

  Design: MultiAppReporterTransferMultiAppCloneReporterTransfer

  Issue(s): #16055

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  646464
• 11.57.73If processors do not contain a sub-application and reporter clone transfer is requested, the system shall
  1. be able to transfer if reporter types are specified and
  2. error if types are not specified.

  Specification(s): clone_type/type_specified, clone_type/error

  Design: MultiAppReporterTransferMultiAppCloneReporterTransfer

  Issue(s): #16055

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunExceptionJSONDiff

  7364
• 11.57.76The system shall error if the variable order does not match when transferring scalar variables to an application from sub-applications.

  Specification(s): sub_to_master_wrong_order

  Design: MultiAppScalarToAuxScalarTransfer

  Issue(s): #9444

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.57.78The system shall error if the variable order does not match when transferring scalar variables from an application to sub-applications.

  Specification(s): master_to_sub_wrong_order

  Design: MultiAppScalarToAuxScalarTransfer

  Issue(s): #9444

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException
• 11.57.83MultiAppUserObjectTransfer shall generate an error if a master node/element is not contained within any sub application domains.

  Specification(s): 3d_1d_err

  Design: MultiAppUserObjectTransfer

  Issue(s): #10313#19056

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  Prerequisite(s): 11.57.80

  64
• 11.57.90The systen shall error out if more than one sub-applications are in the same distance from an element.

  Specification(s): same_distance_error

  Design: MultiAppVariableValueSampleTransfer

  Issue(s): #1737#16099#20816#20913

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64
• 11.57.91The systen shall error out if the MultiAppVariableValueSamplePostprocessorTransfer transfers postprocessor values on sub-applications to a primary variable on the main application.

  Specification(s): from_multiapp_set_primary_var_error

  Design: MultiAppVariableValueSampleTransfer

  Issue(s): #1737#16099#20816#20913

  Collection(s): FAILURE_ANALYSISFUNCTIONAL

  Type(s): RunException

  64