Framework Failure Analysis Report

Introduction

MOOSE and MOOSE-based applications are designed to operate as a library of functionality. While each library may be tailored for solving a certain set of equations, the ability to create arbitrary simulations exists. This flexibility exists by design within the framework, modules, and applications. With respect to performing failure analysis, the flexibility is detrimental since there lacks a well-defined problem to assess. To minimize the possibility of failure for a simulation, various automated methods exist for developers. This document discusses these features and includes a list of requirements associated with software failure analysis.

References

No citations exist within this document.

Failure Analysis

MOOSE has three primary methods for handling simulation failures that range from input errors to simulation convergence problems. These potential failures and the associated handling of the failure are ubiquitous across MOOSE and MOOSE-based applications. The next three sections detail the handling of these common sources of failures.

  1. Input file syntax failure,

  2. Input parameter errors, and

  3. Convergence failure.

To complement the automatic handling of these three failure mechanisms the MOOSE testing system includes a mechanism for creating tests to verify that errors are captured and reported correctly. This testing method is detailed in the Failure Testing section.

Input File Failure

The input file parsing (see Parser) system automatically handles syntax mistakes and reports them as errors. For example, consider the following input file that contains a missing closing bracket.

[Mesh]
  file = file.e
[]

[Executioner]
  type = Steady
(test/tests/parser/hit_error/hit_error.i)

If this input file is executed with the application, it will automatically report the error and associated line number where it occurred as follows.


hit_error.i:5: missing closing '[]' for section

Input Parameter Errors

The input parameter system (see InputParameters) is the second step in input file parsing. The system details the available inputs for an object. The system allows for parameters to be marked as required, provide a default, or check for correct range to name a few. For example, consider the validParams function below that defines a required parameter "D" that must be supplied in an input file.

InputParameters
CoeffParamDiffusion::validParams()
{
  InputParameters params = Diffusion::validParams();
  params.addRequiredParam<Real>("D", "The diffusivity coefficient.");
  return params;
}
(test/src/kernels/CoeffParamDiffusion.C)

If an input file does not include this parameter, as shown below then it will provide an error with details regarding the missing parameter.

[Kernels<<<{"href": "../syntax/Kernels/index.html"}>>>]
  [diffusion]
    type = CoeffParamDiffusion
    variable = u
  []
[]
(test/tests/utils/param_error/param_error.i)

param_error.i:10: missing required parameter 'Kernels/diffusion/D'
	Doc String: "The diffusivity coefficient."

Convergence Failure

MOOSE includes automatic methods to handle convergence failures during the numeric solve. If those attempts fail, it will exit with an error indicating of the failed solve and the reason. By default if a transient simulation fails to solve a time step, the timestep will automatically be cut and the solve re-attempted. This cutback will continue until the solve converges or if the minimum allowed timestep is reached.

For example, the following input when executed will demonstrate the behavior. This input file includes a custom TimeStepper block, but by default a similar behavior exists.

[Executioner<<<{"href": "../syntax/Executioner/index.html"}>>>]
  type = Transient
  num_steps = 10
  solve_type = PJFNK
  petsc_options_iname = '-pc_type -pc_hypre_type'
  petsc_options_value = 'hypre boomeramg'

  [./TimeStepper<<<{"href": "../syntax/Executioner/TimeStepper/index.html"}>>>]
    type = ConstantDT
    dt = 0.1
    cutback_factor_at_failure = 0.8
  [../]
[]
(test/tests/time_steppers/cutback_factor_at_failure/constant_dt_cutback.i)

When executed this input file at time step 3 fails to converge, the timestep ("dt") is cut by the supplied factor and the solve is re-attempted. In both the converged and non-converged iterations the reason for the resulting solve is displayed.


Time Step 3, time = 0.3, dt = 0.1
 0 Nonlinear |R| = 7.103698e-02
      0 Linear |R| = 7.103698e-02
      1 Linear |R| = 1.154171e-03
      2 Linear |R| = 4.325671e-06
      3 Linear |R| = 2.434939e-08
  Linear solve converged due to CONVERGED_RTOL iterations 3
 1 Nonlinear |R| = 2.429061e-08
      0 Linear |R| = 2.429061e-08
      1 Linear |R| = 2.035627e-10
      2 Linear |R| = 9.270880e-13
      3 Linear |R| = 6.368586e-15
  Linear solve converged due to CONVERGED_RTOL iterations 3
 2 Nonlinear |R| = 6.368769e-15
Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 2
 Solve Did NOT Converge!
Aborting as solve did not converge

Time Step 3, time = 0.28, dt = 0.08
 0 Nonlinear |R| = 7.103698e-02
      0 Linear |R| = 7.103698e-02
      1 Linear |R| = 8.875771e-04
      2 Linear |R| = 3.163939e-06
      3 Linear |R| = 1.554863e-08
  Linear solve converged due to CONVERGED_RTOL iterations 3
 1 Nonlinear |R| = 1.565086e-08
      0 Linear |R| = 1.565086e-08
      1 Linear |R| = 1.120313e-10
      2 Linear |R| = 4.275206e-13
      3 Linear |R| = 2.854434e-15
  Linear solve converged due to CONVERGED_RTOL iterations 3
 2 Nonlinear |R| = 2.874867e-15
Nonlinear solve converged due to CONVERGED_FNORM_RELATIVE iterations 2
 Solve Converged!

Failure Testing

In general, failures are tested using a test type of RunException (see Framework Software Test Plan). An example of such as test is provided below, which is a test that exists for the previous input parser example in Input Parameter Errors. By default all RunException tests are listed below in the list in of requirements (Failure Analysis Requirements) that comprise failure analysis.

[Tests]
  issues = '#16410'
  design = utils/InputParameters.md
  [error]
    type = RunException
    input = param_error.i
    expect_err = "param_error.i:10: missing required parameter 'Kernels/diffusion/D'"

    requirement = "The system shall automatically report input errors when a required parameter is not specified."
  []
[]
(test/tests/utils/param_error/tests)

Failure Analysis Requirements

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

    Specification(s): invalid_order_high

    Design: AuxVariables System

    Issue(s): #960#2294#4668

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): mismatch

    Design: Adaptivity System

    Issue(s): #14531

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Bcs
  • 1.7.27The system shall error in debug mode if an integrated boundary condition is being executed outside the domain of definition of variable, without explicitly allowing this.

    Specification(s): error

    Design: MeshModifiers

    Issue(s): #29360

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5
  • 1.7.33The system shall be able to determine if a non-scalable algorithm is being used for ghosting boundaries.

    Specification(s): check

    Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

    Issue(s): #15501

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.7.60The 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#29825

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.7.58

    56
  • 1.7.75The system shall throw an error if
    1. multiple solver systems are being used as it is currently unsupported,
    2. additional parameters are passed when using the automatic periodic boundary detection option,
    3. the primary boundary of a periodic boundary condition does not exist on the mesh, or
    4. the secondary boundary of a periodic boundary condition does not exist on the mesh,
    5. the primary and secondary boundaries on an orthogonal mesh do not match when applying a X,Y or Z translation.

    Specification(s): exceptions/multi_sys, exceptions/bad_params, exceptions/bad_primary, exceptions/bad_secondary, exceptions/not_matching_translation

    Design: Periodic System

    Issue(s): #22496

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: ConstantBounds

    Issue(s): #14946

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunAppRunException

    565656
  • framework: Chaincontrols
  • 1.9.5The system shall report an error if an invalid symbol is used in the parsed chain control.

    Specification(s): invalid_symbol

    Design: ParsedChainControl

    Issue(s): #28948

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.9.8The system shall report an error if a value other than 0 or 1 is requested to be converted to a boolean chain control data.

    Specification(s): invalid_input_value

    Design: RealToBoolChainControl

    Issue(s): #28948

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.9.13The system shall be able to use a chain control to terminate a simulation
    1. by throwing an error.
    2. gracefully.
    3. when the data has a value of false.

    Specification(s): tests/throw_error, tests/no_throw_error, tests/terminate_on_false

    Design: TerminateChainControl

    Issue(s): #28948

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunAppRunException

    565656
  • 1.9.15The system shall report an error if the wrong type of input data is provided to a unit trip chain control.

    Specification(s): wrong_type

    Design: UnitTripChainControl

    Issue(s): #28948

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bounding_value_max

    Design: BoundingValueElementDamper

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bounding_value_min

    Design: BoundingValueElementDamper

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bounding_value_max

    Design: BoundingValueNodalDamper

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bounding_value_min

    Design: BoundingValueNodalDamper

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): interacting_node_elem1

    Design: BoundingValueElementDamper

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): interacting_node_elem2

    Design: BoundingValueElementDamper

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bad_key

    Design: MaxIncrement

    Issue(s): 5509fd360a4ca128a642b1c6603fa3f5205c05d8

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.14.13The Damper system shall error if the damping value is below a minimum.

    Specification(s): min_general_damping

    Design: Dampers System

    Issue(s): #7856

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): error_stateful_dg_adaptivity

    Design: DGKernels System

    Issue(s): #10977

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Executioners
  • 1.17.22The system shall report an error if the user specifies nonlinear convergence parameters that are not used.

    Specification(s): unused_nl_convergence_params

    Design: Executioner System

    Issue(s): #24128

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: TaggingInterface

    Issue(s): #26285

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    565656
  • 1.17.28The system shall support execution using the PETSc non-linear divergence tolerance.

    Specification(s): test

    Design: Executioner System

    Issue(s): #13991

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    42
  • 1.17.29The system shall consider a nonlinear solve diverged if the nonlinear residual exceeds the absolute divergence tolerance while iterating

    Specification(s): test_abs_divtol

    Design: FEProblemSolve

    Issue(s): #16474

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.17.34The system shall consider a nonlinear solve diverged if the nonlinear residual oscillates by a user-controlled number of times.

    Specification(s): nl_pingpong

    Design: FEProblemSolve

    Issue(s): #16376

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Executors
  • 1.18.2The system shall report an error if the Executor system contains an infinite cycle

    Specification(s): cycle

    Design: Executor

    Issue(s): #5229#18180

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.18.3The system shall only have one root node in the Executor tree

    Specification(s): multi_root

    Design: Executor

    Issue(s): #5229#18180

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): vector_error

    Design: GenericFunctionVectorMaterial

    Issue(s): #18372

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: ImageFunctionImageMesh

    Issue(s): #5927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except1

    Design: LinearCombinationFunction

    Issue(s): #4828

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): vals_error

    Design: ParsedFunction

    Issue(s): #14169

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): nl_vars

    Design: ParsedFunction

    Issue(s): #15523

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: PiecewiseConstant

    Issue(s): #2272#25058

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: PiecewiseConstantFromCSV

    Issue(s): #19109

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: PiecewiseConstantFromCSV

    Issue(s): #19109

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.20.57The PiecewiseMultilinear object will error if the supplied file fails to open.

    Specification(s): except1

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.20.58The PiecewiseMultiInterpolation object shall error if the supplied data is not monotonically increasing.

    Specification(s): except2

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except3

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.20.60The PiecewiseMultiInterpolation errors if the axes supplied are not independent.

    Specification(s): except4

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except5

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): nonexistent_var_err

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): fvbcs_internal

    Design: FVNeumannBC

    Issue(s): #16882

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): fvbcs_disconnected_from_variable

    Design: FVNeumannBC

    Issue(s): #16882

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): run_except1

    Design: FVInterfaceKernels System

    Issue(s): #17087

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): run_except2

    Design: FVInterfaceKernels System

    Issue(s): #17087

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): run_except3

    Design: FVInterfaceKernels System

    Issue(s): #17087

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Geomsearch
  • 1.27.57The system shall report an error in the penetration locator system if penetration is not detected.

    Specification(s): never_warning

    Design: GapValueAuxMesh System

    Issue(s): #3901

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.27.53

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

    Specification(s): test_suppress_ignore

    Design: Parser

    Issue(s): #437#8761

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): size_error

    Design: ArrayConstantIC

    Issue(s): #6881

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): size_error

    Design: ArrayFunctionIC

    Issue(s): #6881

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_boundary

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_block

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_block_both_global

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_block_first_global

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.30.31The system shall be able to initialize a variable using functors, notably
    1. postprocessors,
    2. functor material properties,
    3. functions,
    4. but not other variables,
    5. or postprocessors that are not executed before initial conditions are set.

    Specification(s): functor/from_pp, functor/from_fmat, functor/from_function, functor/from_var, functor/from_pp_not_initialized

    Design: FunctorIC

    Issue(s): #29980

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): CSVDiffRunException

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

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

    Design: IntegralPreservingFunctionIC

    Issue(s): #19476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): errors/missing_block

    Design: SolutionICSolutionUserObject

    Issue(s): #24581

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): comp_x_error

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): comp_y_error

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): comp_z_error

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): error_stateful_ik_adaptivity

    Design: InterfaceKernels System

    Issue(s): #10977

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): trust_user_and_then_error

    Design: Coupleable

    Issue(s): #16396

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): override

    Design: ADScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): parsed_func_error_check

    Design: BodyForce

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.34.63

    56
  • 1.34.68The system shall handle unique cases when trying to compute conservative advection
    1. by throwing an error when no velocity is given,
    2. by throwing an error when no velocity is given when using AD,
    3. by throwing a deprecation warning when no velocity is given when using AD,
    4. by throwing a deprecation warning when velocity is given when using AD,

    Specification(s): error/no_velocity, error/ad_no_velocity, error/deprecated_velocity, error/ad_deprecated_velocity

    Design: ConservativeAdvection

    Issue(s): #11852

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): robin_adpatation

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.34.98The system shall issue an error for lower-dimensional variables undefined on all boundaries in a boundary condition with hybrid finite element method (HFEM) calculations.

    Specification(s): lower_d_variable_block_restriction

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): override

    Design: ScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): test

    Design: Kernels System

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.34.139Time kernel requires a transient executioner

    Specification(s): bad_transient

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.34.140The kernel can be only assigned to the existing vector tags in the system

    Specification(s): bad_vector_tag

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.34.141The kernel can be only assigned to the existing matrix tags in the system

    Specification(s): bad_matrix_tag

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): comp_error

    Design: VectorBodyForce

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ad_comp_error

    Design: ADVectorFunctionDirichletBC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Markers
  • 1.37.15It shall not be possible to specify Markers to run on the displaced mesh.

    Specification(s): displaced_error

    Design: Markers System

    Issue(s): #11430

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): wrong_size_error

    Design: Markers SystemReporterPointMarker

    Issue(s): #18886

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Mortar
  • 1.46.80The system shall report an error if a nonlinear variable is applied for sigma instead of an auxiliary variable.

    Specification(s): auxiliary

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Multiapps
  • 1.47.2The system shall report a reasonable error when the type of application in a MultiApp input is not a valid application type

    Specification(s): wrong_sub_application_type

    Design: Application SystemCreateApplicationBlockAction

    Issue(s): #26474

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.7The system shall detect input file problems with sub app input files.

    Specification(s): input_file

    Design: MultiApp System

    Issue(s): #4101#4113

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.8The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.9The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.10The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.11The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.12The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.13The system shall report an error when the multiapp positions file is malformed.

    Specification(s): bad_positions

    Design: MultiApp System

    Issue(s): #1845#3556#5784

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.14The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.19The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.20The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.21The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.22The system shall not use an empty commandLine argument file

    Specification(s): empty_cliarg_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.23The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.24The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.32The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.36When 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.
    4. throw an error if the user-selected maximum level of nesting of applications is reached

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

    Design: FullSolveMultiApp

    Issue(s): #1940

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): ExodiffRunException

    56805656
  • 1.47.39The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.71The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.47.70

    56
  • 1.47.87The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.90The system shall report an error if the reset times specified for a multiapp are not sorted, as this likely indicates a user error in their input

    Specification(s): not_sorted_times

    Design: MultiApp System

    Issue(s): #1970

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.47.95The system shall report an error if
    1. both outputting in position and displacing applications are requested at the same time, as displaced apps are already output in position
    2. a translation is requested on a spherical or cylindrical coordinate mesh, as this is not expected to be a valid transformation
    3. displacing applications and moving applications at a certain time are both requested as this combination of features is not implemented

    Specification(s): errors/output_and_run_in_position, errors/invalid_frame_for_translation, errors/move_apps_not_supported

    Design: MultiApp System

    Issue(s): #19121

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    565656
  • 1.47.110The system shall issue a warning if the parent app and the child app time become de-synchronized, except when using sub-cycling or resetting mechanisms which naturally handle or create desynchronization

    Specification(s): warning

    Design: TransientMultiApp

    Issue(s): #22338

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Parser
  • 1.52.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.52.9

    56
  • 1.52.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.16The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.17The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.18The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunAppRunExceptionExodiff

    80568056
  • 1.52.19The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.20The system shall support parameter duplication check for multiple input files, which are later merged into one.

    Specification(s): dup_check

    Design: Parser

    Issue(s): #25994

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.28The system shall throw an exception if the given input cannot be parsed into a vector of size-3 vectors.

    Specification(s): parse_vector_value_error

    Design: Parser

    Issue(s): #24337

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.30The system shall return a usage message when the vector of MultiMooseEnums includes an empty entry.

    Specification(s): vmme_empty

    Design: InputParameters

    Issue(s): #28487

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.31The system shall return an error message when an invalid entry is supplied in a vector of MultiMooseEnums.

    Specification(s): vmme_invalid

    Design: InputParameters

    Issue(s): #28487

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.32The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.52.33The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656565656
  • 1.52.34The system shall support vector bounds checking on input parameter vectors.

    Specification(s): outofbounds

    Design: InputParameters

    Issue(s): #3988

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.52.35The system shall support checking for non-empty input parameter vectors.

    Specification(s): checkempty

    Design: InputParameters

    Issue(s): #3988

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Physics
  • 1.56.3The system shall return an error if
    1. a variable is defined both in the shorthand physics syntax and the regular syntax but with different block restrictions,
    2. parameters for the variable are specified to the shorthand physics syntax but then ignored due to a pre-existing variable definition,
    3. a variable initial condition is defined both in the shorthand physics syntax and the regular syntax for the same variable on the same blocks,
    4. a time derivative is specified with a block restriction in the regular syntax, while the shorthand physics syntax seeks to define it without a block restriction.

    Specification(s): errors/variable_block_res_conflicting, errors/variable_parameter_ignored, errors/ic_conflicting, errors/td_defined_on_not_enough_blocks

    Design: Physics system

    Issue(s): #30533

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56565656
  • 1.56.5The system shall error if the physics is specified as a transient, when the executioner is designed for steady solves.

    Specification(s): fv

    Design: Physics system

    Issue(s): #25642

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.56.7The system shall return an error
    1. if the system specified to the Physics does not exist
    2. if more systems than needed are specified to a Physics action.

    Specification(s): errors/wrong_systems, errors/too_many_systems

    Design: Physics system

    Issue(s): #29019

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • framework: Positions
  • 1.57.3The system shall report an error if
    1. the positions objects to use for creating multiapps are not initialized, or
    2. the size of the current positions does not match the number of initial positions.

    Specification(s): error/not_init, error/size_changed

    Design: Positions

    Issue(s): #23587

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • framework: Preconditioners
  • 1.59.8The system shall report an error if a user has forgotten a variable in their field splits.

    Specification(s): missing_var_in_split

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.59.10The system shall error if there is an inconsistent covering of degrees of freedom in a nested field split.

    Specification(s): nested_error

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Problems
  • 1.61.3The system shall report an error when Problem block type is not specified.

    Specification(s): with_problem_block_with_wrong_type

    Design: Problem system overview

    Issue(s): #12002

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.12Eigenvalue system should not allow users to use inhomogeneous nodal boundary conditions

    Specification(s): wrong_dirichlet_value_eigen

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.13Eigenvalue system should use homogeneous boundary conditions only

    Specification(s): wrong_NodalBC_type_eigen

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.14Eigenvalue system requires SLEPc installed

    Specification(s): no_slepc

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 1.61.30The system shall error if a user requests a standard eigenvalue solve when there are objects marked to contribute to the Bx vector or B matrix.

    Specification(s): error_eigen_non_generalized

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.43The system shall support compatibility of solve type and constant-matrices flag

    Specification(s): check_solve_type

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.61.42

    56
  • 1.61.45The system shall error if the user wants the Bx norm provided by a postprocessor but the postprocessor is not executed during residual evaluations.

    Specification(s): missing_bx_norm_exec_linear

    Design: Eigenvalue

    Issue(s): #28993

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.65The system shall inform the user when the nonlinear-eigen system solve failed.

    Specification(s): eigen_problem_solve_fail

    Design: Problem system overview

    Issue(s): #27084

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.68The system shall fail to find a converged solution when basing convergence on individual variable reference quantities with poor scaling.

    Specification(s): scaled_bad

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.71The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.80The system shall treat convergence with a zero reference residual value as requiring zero residual value for convergence.

    Specification(s): zero_tolerance_ref

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.61.82When using ReferenceResidualProblem the system shall throw an error
    1. if the reference tag is not a residual vector tag.
    2. if the reference tag does not exist.
    3. if the reference vector is not provided when using local normalization.
    4. if the reference vector is provided is not a residual vector tag.

    Specification(s): error/wrong_vector_tag_type, error/no_tag, error/no_reference_vector, error/not_residual_tag

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56565656
  • framework: Quadrature
  • 1.62.4The system shall ensure that for per-block specified quadrature orders exactly one order is given per specified block.

    Specification(s): per-block-order-error

    Design: Quadrature System

    Issue(s): #24820

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Reporters
  • 1.64.3The system shall report an error if an invalid name is provided when retrieving aggregate value.

    Specification(s): error

    Design: Reporter System

    Issue(s): #11323

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.64.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56565656
  • 1.64.8The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    565656
  • 1.64.23The system shall support reporting a reasonable error when trying to output restartable data in human-readable form for a data type that does not have an output specialization

    Specification(s): unimplemented_error

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Restart
  • 1.65.2The system shall report a reasonable error when using advanced stateful restart when
    1. a stateful property for a single material object is removed
    2. a stateful property for a single material object is added
    3. a previously checkpointed stateful property is declared in a new material
    4. the type of a restored stateful property has changed
    5. the requested state of a restored stateful property has changed

    Specification(s): errors/remove_prop, errors/add_prop, errors/object_rename, errors/different_type, errors/different_state

    Design: Materials System

    Issue(s): #25840

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.65.11.65.15

    5656565656
  • 1.65.6The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionExodiff

    Prerequisite(s): 1.65.4

    5656
  • 1.65.7The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionExodiff

    Prerequisite(s): 1.65.6

    5555
  • 1.65.12The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.65.14The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.65.13

    56
  • 1.65.25The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 1.65.24

    56
  • 1.65.26The system shall issue a useful error message stating that initial conditions should not be used when restarting.

    Specification(s): restart_error_with_ics

    Design: RestartableDataIO

    Issue(s): #21423

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.65.43The system shall be able to restart a scalar variable in the presence of other variables with the standard sequence of:
    1. run initial input
    2. run restart input
    3. run restart input with two initial conditions

    Specification(s): restarting/part1, restarting/part2, restarting/part3

    Design: MooseVariableBase

    Issue(s): #17471

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionExodiff

    805680
  • framework: Restrictable
  • 1.66.2The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    565656
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.66.9The system shall report an 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    5656
  • 1.66.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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Scaling
  • 1.69.3The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.69.7The system shall display a very poor condition number for an ill-conditioned system.

    Specification(s): bad

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Tag
  • 1.71.3The 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): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.71.9An error will be thrown when the different number of array components are used in the aux and coupled varibles.

    Specification(s): array_value_size_error

    Design: TagVectorArrayVariableValueAux

    Issue(s): #21839

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • 1.71.10An error will be thrown when the different FE family are used in the aux and coupled varibles.

    Specification(s): array_value_fe_type_error

    Design: TagVectorArrayVariableValueAux

    Issue(s): #21839

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56
  • framework: Times
  • 1.74.2The system shall report an error when
    1. times are gathered with a fixed time interval with no start and end times provided, while using a steady executioner.

    Specification(s): error_reporting/time_interval_steady_no_times

    Design: Times

    Issue(s): #24696#25352

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    56