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 will defined problem to asses. 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

    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) automatically handles syntax mistakes are reports errors. For example, consider the following input file that contains a missing closing bracket.

    [Mesh]
      file = file.e
    []
    
    [Executioner]
      type = Steady
    
    (moose/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;
    }
    
    (moose/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]
      [diffusion]
        type = CoeffParamDiffusion
        variable = u
      []
    []
    
    (moose/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]
      type = Transient
      num_steps = 10
      solve_type = PJFNK
      petsc_options_iname = '-pc_type -pc_hypre_type'
      petsc_options_value = 'hypre boomeramg'
    
      [./TimeStepper]
        type = ConstantDT
        dt = 0.1
        cutback_factor_at_failure = 0.8
      [../]
    []
    
    (moose/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."
      []
    []
    
    (moose/test/tests/utils/param_error/tests)

    Failure Analysis Requirements

    • framework: Actions
    • 1.1.1The 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

    • framework: Auxkernels
    • 1.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

    • 1.3.17MOOSE 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

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

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

    • 1.3.75Error 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

    • framework: Controls
    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • 1.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

    • framework: Dampers
    • 1.8.1MOOSE 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

    • 1.8.2MOOSE 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

    • 1.8.3MOOSE 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

    • 1.8.4MOOSE 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

    • 1.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

    • 1.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

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

    • framework: DGKernel Objects
    • 1.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

    • framework: Functions
    • 1.13.10The 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

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

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

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

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

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

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

      Specification(s): except4

      Design: PiecewiseMultilinear

      Issue(s): #2476

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

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

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

    • framework: Fvbcs
    • 1.14.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

    • 1.14.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

    • framework: Fviks
    • 1.15.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

    • 1.15.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

    • 1.15.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

    • framework: Fvkernels
    • 1.16.2The system shall return a warning in non-optimized modes if a user supplies a material property with the same name from different block-restricted materials on neighboring subdomains when there are different sets of finite volume flux kernels on those same neighboring subdomains. This is because we have to support ghosting of material properties for block restricted finite volume flux kernels.

      Specification(s): overlapping-mats

      Design: Finite Volume Design Decisions in MOOSE

      Issue(s): #15894

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.16.7The system shall error if a user attempts to couple both finite volume and finite element variables into the same material.

      Specification(s): mat-error

      Design: Finite Volume Design Decisions in MOOSE

      Issue(s): #15894

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.16.10The system shall error in non-optimized modes if material dependencies for finite volume computations are not satisfied.

      Specification(s): deps-not-satisfied

      Design: Finite Volume Design Decisions in MOOSE

      Issue(s): #15894

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

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

    • framework: Geomsearch
    • 1.17.55The MOOSE penetration locator system shall error if penetration is not detected.

      Specification(s): never_warning

      Design: GapValueAuxMesh System

      Issue(s): #3901

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

      Prerequisite(s): 1.17.51

    • framework: Ics
    • 1.19.5The 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

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

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

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

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

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

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

    • framework: InterfaceKernel Objects
    • 1.21.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

    • framework: Kernels
    • 1.23.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

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

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

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

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

    • 1.23.102We 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

    • 1.23.105We 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

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

    • 1.23.109Time kernel requires a transient executioner

      Specification(s): bad_transient

      Design: TaggingInterface

      Issue(s): #9669

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

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

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

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

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

    • framework: Markers
    • 1.24.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

    • framework: Mesh
    • 1.26.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

    • 1.26.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

    • 1.26.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

    • 1.26.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

    • 1.26.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

    • 1.26.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

    • framework: Mesh Modifiers
    • 1.27.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

    • 1.27.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

    • 1.27.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

    • 1.27.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

    • 1.27.24The system shall error when renaming subdomains if
      1. the number of new subdomain identifiers is greater than the number of old subdomain identifiers;
      2. the supplied the block identifier name missing;
      3. the supplied the block identifier number missing;
      4. the number of old subdomain identifiers is greater than the number of ned subdomain identifiers;
      5. the supplied the new block identifier name missing; and
      6. the supplied the new block identifier number missing.

      Specification(s): error/except1, error/except2, error/except3, error/except4, error/except5, error/except6

      Design: Mesh System

      Issue(s): #13814

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • framework: Misc
    • 1.30.6The 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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    • 1.30.155A 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): 1.30.154

    • 1.30.156A 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): 1.30.154

    • 1.30.159A 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): 1.30.158

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

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

    • framework: Mortar
    • 1.31.2We shall tell the user that mortar doesn't currently work in 3D

      Specification(s): except

      Design: Constraints System

      Issue(s): #13080

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • framework: Multiapps
    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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

    • 1.32.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): 1.32.60

    • 1.32.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

    • framework: Outputs
    • 1.34.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

    • 1.34.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

    • 1.34.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): 1.34.54

    • 1.34.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

    • 1.34.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

    • 1.34.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

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

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

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

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

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

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

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

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

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

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

    • framework: Parser
    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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): 1.35.9

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • 1.35.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

    • framework: Problems
    • 1.42.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

    • 1.42.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

    • 1.42.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

    • 1.42.13Eigenvalue system requires SLEPc installed

      Specification(s): no_slepc

      Design: Eigenvalue

      Issue(s): #7398

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • framework: Reporters
    • 1.45.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

    • 1.45.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

    • 1.45.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

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • framework: Restart
    • 1.46.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): 1.46.2

    • 1.46.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): 1.46.4

    • 1.46.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

    • 1.46.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): 1.46.9

    • 1.46.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): 1.46.18

    • framework: Restrictable
    • 1.47.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

    • 1.47.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

    • 1.47.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

    • 1.47.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

    • 1.47.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

    • 1.47.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

    • 1.47.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

    • 1.47.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

    • 1.47.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

    • framework: Time Steppers
    • 1.54.9MOOSE 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

    • 1.54.10MOOSE 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

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

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

    • framework: Utils
    • 1.58.3The system shall error when a file and data are supplied simultaneously in the PiecewiseBilinear object.

      Specification(s): data_file_and_xyz_error

      Design: BilinearInterpolation

      Issue(s): #5991

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.58.4The system shall error when there is a mismatch in vector lengths in the PiecewiseBilinear object.

      Specification(s): size_xyz_error

      Design: BilinearInterpolation

      Issue(s): #5991

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.58.5The system shall error when there are insufficient parameters supplied for the PiecewiseBilinear object.

      Specification(s): xyz_error

      Design: BilinearInterpolation

      Issue(s): #5991

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.58.7The system shall prevent the user from copying InputParameters objects inside of MooseObject-derived objects.

      Specification(s): test

      Design: InputParameters

      Issue(s): #5439

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.58.12The system shall automatically report input errors when a required parameter is not specified.

      Specification(s): error

      Design: InputParameters

      Issue(s): #16410

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • framework: Vectorpostprocessors
    • 1.60.6The system shall error if the broadcast CSV data does not match on all ranks in a parallel job.

      Specification(s): tester_fail

      Design: CSVReader

      Issue(s): #9167

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.60.8The system shall issue an error if the CSVReader is used in a UserObjectTransfer because the former does not have any notion of "spatial" information.

      Specification(s): csv_reader_in_transfer

      Design: CSVReader

      Issue(s): #9860

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.60.18The system shall support sampling of a field variable at the centroid of every element in the domain
      1. for elemental FE variables and
      2. for FV variables,
      3. but not for nodal variables.

      Specification(s): element_value_sampler/monomial, element_value_sampler/fv, element_value_sampler/lagrange

      Design: ElementValueSampler

      Issue(s): #11594

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunExceptionCSVDiff

    • 1.60.27The histogram vector postprocessor shall generate an error if the vector postprocessor that it operates on does not have any declared vectors

      Specification(s): test_size0_err

      Design: HistogramVectorPostprocessor

      Issue(s): #18459

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.60.34The LeastSquaresFit vectorpostprocessor shall generate an error if a fit for a third-order polynomial is requested and only three data points are provided

      Specification(s): least_squares_csv3_order_err

      Design: LeastSquaresFitCSVReader

      Issue(s): #13498

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.60.43The system shall issue an error if material output samples are attempted for elements:
      1. but the material is restricted to a boundary, or
      2. the material is restricted to a block not containing the desired elements.

      Specification(s): errors/boundary_restrict, errors/block_restrict

      Design: MaterialVectorPostprocessor

      Issue(s): #8436

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.60.45The system shall issue an error when a nodal sampler is used on a field that does not have values defined at the nodes.

      Specification(s): not_nodal

      Design: NodalValueSampler

      Issue(s): #3087

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException

    • 1.60.50The system shall report an error when requested sample points do not fall within the mesh domain.

      Specification(s): error

      Design: PointValueSampler

      Issue(s): #3087#16099

      Collection(s): FAILURE_ANALYSISFUNCTIONAL

      Type(s): RunException