Reconstructed Discontinuous Galerkin Failure Analysis Report
Introduction
The FAR for the Reconstructed Discontinuous Galerkin module describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.
Dependencies
The Reconstructed Discontinuous Galerkin module is developed using MOOSE and can itself be based on various MOOSE modules, as such the FAR for the Reconstructed Discontinuous Galerkin module is dependent upon the following documents.
Failure Analysis Requirements
The following is a complete list for all the requirements related to failure analysis for the Reconstructed Discontinuous Galerkin module.
- rdg: Actions
- 15.1.2The system shall error if the supplied order of scalar auxiliary variable is of an unknown order.
Specification(s): invalid_order_high
Design: AuxVariables System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Auxkernels
- 15.3.10The system shall
- emit a warning if a variational inequalities (VI) solver is not found when the bounds system is used.
- error if an unsupported variable type is provided to the constant bounds kernel
- error if the type of the dummy auxiliary variable does not match the bounded variable.
Specification(s): exceptions/solver, exceptions/bounded_variable_type, exceptions/mismatch_dummy
Design: ConstantBoundsAux
Issue(s): #14946
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.3.12The system shall report a reasonable error when copying standard variables into the components of an array variable when
- the variables have inconsistent sizes or
- when the variables have inconsistent types.
Specification(s): error/size, error/type
Design: BuildArrayVariableAux
Issue(s): #16402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.23The system shall error if a boundary restricted elemental auxiliary kernel is evaluated on an element with multiple boundary sides
Specification(s): boundary_restricted_error_test
Design: AuxKernels System
Issue(s): #5061
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.57Writing to auxiliary variables shall be limited to use from AuxKernels, ElementUserObjects, or NodalUserObjects.
Specification(s): multi_update_error
Design: AuxKernels SystemCoupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.59Writing to auxiliary variables shall be limited to use from AuxKernels, ElementUserObjects, or NodalUserObjects using variable values.
Specification(s): multi_update_deprecated_error
Design: AuxKernels SystemCoupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.60The writing to auxiliary variables shall enforce nodal/elemental consistency between the kernel variable and the writable variables.
Specification(s): multi_update_deprecated_error2
Design: AuxKernels SystemCoupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.61The writableCoupledValue API can only act on AuxVariables.
Specification(s): multi_update_deprecated_error3
Design: AuxKernels SystemCoupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.62The writing to auxiliary variables shall error out if a constant value is passed in as variable name.
Specification(s): multi_update_deprecated_error4
Design: AuxKernels SystemCoupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.65The MOOSE auxiliary system shall check compatibility between primary and writable coupled variables.
Specification(s): multi_update_elem_family_error
Design: AuxKernels SystemCoupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.74The system shall be able to detect wrong implicit dependencies of a function value postprocessor that depends on a function which depends on a second postprocessor.
Specification(s): pp_depend_indirect_wrong
Design: AuxKernels SystemPostprocessor System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.78The system shall be capable of initializing an auxiliary variable from an existing solution
- from data generated by a simulation
- and loaded using location,
- using a direct degree-of-freedom copy for identical meshes,
- with scaling the supplied data,
- 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
- 15.3.89The 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
- 15.3.95Error 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
- 15.3.99The system shall error if
- a time derivative is requested from a functor material property for which the functor time derivative not implemented
- a time derivative is requested but the variable is a nodal variable which is currently unsupported
- a time derivative for a finite element variable is to be saved in a finite volume variable
- a time derivative for a finite volume variable is to be saved in a finite element variable
Specification(s): errors/not_implemented_functor_matprop, errors/not_a_nodal_kernel, errors/implicit_fe_fv_conversion, errors/implicit_fv_fe_conversion
Design: AuxKernels SystemKernels SystemAuxVariableFunctions SystemMaterials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.101The system shall error if
- a second time derivative is requested but the variable is a nodal variable which is currently unsupported, and
- a second time derivative for a finite element variable is requested to be stored in a finite volume variable.
Specification(s): errors/not_a_nodal_kernel, errors/implicit_fe_fv_conversion
Design: AuxKernels SystemKernels SystemAuxVariableFunctions SystemMaterials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.3.111The system shall report a reasonable error when trying to sample element volumes into a non constant monomial variable
Specification(s): incorrect_type
Design: VolumeAux
Issue(s): #19307
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Bcs
- 15.5.31The system shall be able to determine if a non-scalable algorithm is being used for ghosting boundaries.
Specification(s): check
Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator
Issue(s): #15501
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.5.56The system shall produce an error within the PeriodicDistanceAux object when a point is provided that is outside the mesh domain.
Specification(s): auto_wrap_2d_test_error_check
Design: Periodic System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.5.54
- rdg: Controls
- 15.7.8The Control system shall error if an attempt to alter a non-controllable parameter is performed.
Specification(s): non_controllable_error
Design: Controls System
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.10The Control system shall error if an unknown parameter is supplied for control.
Specification(s): no_param_found
Design: Controls System
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.11The Control system shall error if a thread id greater than the number of threads available is supplied when retrieving a Control object.
Specification(s): tid_warehouse_error
Design: Controls System
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.12The Control system shall error if an attempt is made to disable the Executioner.
Specification(s): disable_executioner
Design: Controls System
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.13The Control system shall error if an invalid control name is supplied to the Control dependency resolution procedure.
Specification(s): non_existing_dependency
Design: Controls System
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.17The system shall forbid specifying parameters when reading a neural network from a torchscript file.
Specification(s): invalid-torchscript-error
Design: LibtorchNeuralNetControl
Issue(s): #19571
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.27The MOOSE control system shall be capable of restricting parameters to be controlled for specific execution flags.
Specification(s): error
Design: Controls System
Issue(s): #12576
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.46The 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
- 15.7.47The TimePeriod object shall error when the start and end time parameters are not the same length.
Specification(s): start_end_size_mismatch
Design: TimePeriod
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.48The TimePeriod object shall error when start and end time parameters differ in length than the supplied object list.
Specification(s): time_disable_size_mismatch
Design: TimePeriod
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.49The TimePeriod object shall error when a list of objects to control is omitted.
Specification(s): enable_disable_not_set
Design: TimePeriod
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.7.50The TimePeriod object shall error when start time is greater than the end time.
Specification(s): start_greater_than_end_error
Design: TimePeriod
Issue(s): #5676
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Dampers
- 15.9.1The system shall include the ability to reduce the change in nonlinear residual based on a maximum value on elements.
Specification(s): bounding_value_max
Design: BoundingValueElementDamper
Issue(s): #7856
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.9.2The system shall include the ability to reduce the change in nonlinear residual based on a minimum value on elements.
Specification(s): bounding_value_min
Design: BoundingValueElementDamper
Issue(s): #7856
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.9.3The system shall include the ability to reduce the change in nonlinear residual based on a maximum value on nodes.
Specification(s): bounding_value_max
Design: BoundingValueNodalDamper
Issue(s): #7856
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.9.4The system shall include the ability to reduce the change in nonlinear residual based on a minimum value on nodes.
Specification(s): bounding_value_min
Design: BoundingValueNodalDamper
Issue(s): #7856
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.9.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
- 15.9.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
- 15.9.10The system shall give an informative error if user code requests a variable from the warehouse with a bad key.
Specification(s): bad_key
Design: MaxIncrement
Issue(s): 5509fd360a4ca128a642b1c6603fa3f5205c05d8
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.9.13The Damper system shall error if the damping value is below a minimum.
Specification(s): min_general_damping
Design: Dampers System
Issue(s): #7856
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: DGKernel Objects
- 15.10.16The 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
- rdg: Dirackernels
- 15.11.3The system shall behave accordingly if the added point is not found, when point_not_found_behavior is set to
- ERROR or
- WARNING.
Specification(s): point_not_found/error, point_not_found/warning
Design: DiracKernels System
Issue(s): #17561
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.11.8DiracKernel objects shall report an error if a material property from a previous time step is requested:
- one step back, and
- two steps back.
Specification(s): check_errors/old, check_errors/older
Design: DiracKernels System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.11.12The DiracKernel system shall report an error if a location does not correspond with the supplied element id.
Specification(s): point_caching_error
Design: DiracKernels System
Issue(s): #2364
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.11.13The system shall support point sources with locations and values given by a Reporter
- in a steady state 2D problem, reading data from a reporter and reproducing the constantPointSource.
- in a steady state 2D problem, reading data from a vectorPostProcessor and reproducing the constantPointSource.
- in steady state 3D problem, reproducing the constantPointSource.
- in a transient problem with the vpp source value changing as the vpp changes.
- and shall report an error if the input arrays are not the same size
Specification(s): reporterPointSource/2dConstantReporter, reporterPointSource/2dConstantVPP, reporterPointSource/3dConstant, reporterPointSource/2dTransient, reporterPointSource/wrong_size_error
Design: ReporterPointSource
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionCSVDiffExodiff
- rdg: Executors
- 15.13.2The system shall error if the Executor system contains an infinite cycle
Specification(s): cycle
Design: Executor
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.13.3The system shall only have one root node in the Executor tree
Specification(s): multi_root
Design: Executor
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Functions
- 15.15.11The Material system shall error out if the number of functions supplied does not match the size of the vector function material properties.
Specification(s): vector_error
Design: GenericFunctionVectorMaterial
Issue(s): #18372
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.13The system shall include the ability to create functions from image files that errors if
- an unsupported file type is provided;
- if an invalid component value is supplied;
- if an invalid filename is provided; and
- 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
- 15.15.32The LinearCombinationFunction shall report an error if the parameters listing the functions differs in size than the list of coefficients.
Specification(s): except1
Design: LinearCombinationFunction
Issue(s): #4828
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.43The ParsedFunction object shall fail with a human readable error if a vals entry is supplied that is neither a valid postprocessor, scalar variable, function, or real number.
Specification(s): vals_error
Design: ParsedFunction
Issue(s): #14169
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.44The system should error if a field variable is passed into a parsed function object, as this capability is currently not supported.
Specification(s): nl_vars
Design: ParsedFunction
Issue(s): #15523
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.49The system shall error out if
- if the CSV reader object and the function expect the CSV data to be ordered differently
- if the desired column number in the CSV file is higher than the number of columns in the file
- if the data saught exceeds the row number in the CSV file
- if the number of blocks specified to a CSV reader reading block-data is 0
- if the number of nearest-neighbor regions specified to a CSV reader reading nearest-neighbor-region-data is 0
Specification(s): errors/read_type, errors/num_columns, errors/num_rows, errors/zero_blocks, errors/zero_voronoi
Design: PiecewiseConstantFromCSV
Issue(s): #19109
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.50The system shall issue a warning if
- if the desired column number in the CSV file is known to be a column holding point coordinates
- if the data file contains more points/rows than the reader needs
Specification(s): warnings/num_columns, warnings/too_much_data_in_file
Design: PiecewiseConstantFromCSV
Issue(s): #19109
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.53The 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
- 15.15.54The 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
- 15.15.55The 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
- 15.15.56The PiecewiseMultiInterpolation errors if the axes supplied are not independent.
Specification(s): except4
Design: PiecewiseMultilinear
Issue(s): #2476
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.15.57The 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
- 15.15.75The 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
- rdg: Fvbcs
- 15.17.4The 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
- 15.17.5The 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
- rdg: Fviks
- 15.18.4The 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
- 15.18.5The 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
- 15.18.6The 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
- rdg: Fvkernels
- 15.19.11The system shall error if conflictingly told to avoid and execute a flux kernel on the same boundary.
Specification(s): overlapping_lists
Design: Finite Volume Design Decisions in MOOSE
Issue(s): #20695
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.19.20The system shall suggest that the user add a finite volume variable if a finite volume object cannot retrieve one
Specification(s): var_except
Design: Finite Volume Design Decisions in MOOSE
Issue(s): #14549
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Geomsearch
- 15.20.55The system shall error in the penetration locator system if penetration is not detected.
Specification(s): never_warning
Design: GapValueAuxMesh System
Issue(s): #3901
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.20.51
- rdg: Globalparams
- 15.21.2The system shall error if a private / suppressed parameter is set in the input file.
Specification(s): test_suppress_ignore
Design: Parser
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Ics
- 15.22.2The system shall error if the wrong number of components are provided in a constant initial condition for array variables.
Specification(s): size_error
Design: ArrayConstantIC
Issue(s): #6881
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.4The system shall error if the wrong number of components are provided in a functionalized initial condition for array variables.
Specification(s): size_error
Design: ArrayFunctionIC
Issue(s): #6881
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.8The system shall report an error when multiple initial conditions are applied to the same boundary.
Specification(s): ics_on_same_boundary
Design: ICs System
Issue(s): #6580
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.9The system shall report an error when multiple initial conditions are applied to the same subdomain.
Specification(s): ics_on_same_block
Design: ICs System
Issue(s): #6580
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.10The system shall report an error when a global initial conditions overlap on the same variable.
Specification(s): ics_on_same_block_both_global
Design: ICs System
Issue(s): #6580
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.11The system shall report an error when a global and subdomain restricted initial conditions overlap on the same variable.
Specification(s): ics_on_same_block_first_global
Design: ICs System
Issue(s): #6580
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.32The system shall error if
- the postprocessor does not have execute_on initial
- the postprocessor for normalization is zero
Specification(s): errors/missing_initial, errors/zero_integral
Design: IntegralPreservingFunctionIC
Issue(s): #19476
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.40The system shall error if
- a solution is to be loaded at a block that does not exist in the source file.
Specification(s): errors/missing_block
Design: SolutionICSolutionUserObject
Issue(s): #24581
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.22.45The 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
- 15.22.46The 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
- 15.22.47The 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
- rdg: InterfaceKernel Objects
- 15.24.33The 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
- rdg: Interfaces
- 15.25.3The system shall report a reasonable error when retrieving a property of the mesh when the underlying types differ
Specification(s): get_wrong_type
Design: MeshMetaDataInterface
Issue(s): #23447
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.4The system shall report a reasonable error when requesting a Postprocessor from a parameter when
- the parameter is not found,
- the parameter does not represent a Postprocessor,
- the parameter is a single Postprocessor value and a greater index than zero is requested,
- and the parameter is a single Postprocessor value and a greater index than zero is requested.
Specification(s): param_errors/missing_parameter, param_errors/bad_parameter_type, param_errors/out_of_range_single, param_errors/out_of_range_vector
Design: PostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.5The system shall report a reasonable error when requesting a Postprocessor name from a parameter in which the postprocessor is a default value and not a name.
Specification(s): name_for_default_error
Design: PostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.6The system shall report a reasonable error when it is too early to request if a postprocesor exists
- by parameter name and
- by Postprocessor name.
Specification(s): has_errors/param, has_errors/name
Design: PostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.7The system shall report a reasonable error when requesting a Postprocessor value
- by parameter and the Postprocessor does not exist and
- by Postprocessor name and the Postprocessor does not exist.
Specification(s): missing_errors/by_param, missing_errors/by_name
Design: PostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.18The system shall report a reasonable error when requesting a Reporter value from a parameter when
- the parameter is not found and
- the parameter does not represent a Reporter
Specification(s): param_errors/missing_parameter, param_errors/bad_parameter_type
Design: ReporterInterface
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.19The system shall report a reasonable error when requesting a Reporter value when a Reporter with the same name exists with a different type.
Specification(s): other_type_requested_error
Design: ReporterInterface
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.20The system shall report a reasonable error when requesting a Reporter value
- by parameter and the Reporter value does not exist and
- by Reporter name and the Reporter value does not exist.
Specification(s): missing_errors/param, missing_errors/name
Design: ReporterInterface
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.21The system shall report a reasonable error when it is too early to request if a Reporter value exists
- by parameter name and
- by Reporter name.
Specification(s): has_errors/param, has_errors/name
Design: ReporterInterface
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.22The system shall report a reasonable error when requesting a UserObject when
- getting the name from a parameter and the parameter is not found,
- getting the name from a parameter and the parameter does not represent a name,
- getting the name from a parameter and the user object is not found,
- getting the UserObject by name and the user object is not found,
- getting the name from a paremeter and the provided object is not of the correct type, and
- getting the UserObject by name and the provided object is not of the correct type.
Specification(s): errors/missing_parameter, errors/bad_parameter_type, errors/not_found_by_param, errors/not_found_by_name, errors/bad_cast, errors/bad_cast_by_name
Design: UserObjectInterface
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.24The system shall report a reasonable error when requesting a VectorPostprocessor value from a parameter when
- the parameter is not found and
- the parameter does not represent a VectorPostprocessor.
Specification(s): param_errors/missing_parameter, param_errors/bad_parameter_type
Design: VectorPostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.25The system shall report a reasonable error when it is too early to request if a VectorPostprocessor exists
- by vector name and parameter name,
- by vector name and VectorPostprocessor name,
- by parameter name, and
- and by VectorPostprocessor name.
Specification(s): has_errors/value_param, has_errors/value_name, has_errors/param, has_errors/name
Design: VectorPostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.25.26The system shall report a reasonable error when requesting a VectorPostprocessor value
- by parameter and the VectorPostprocessor does not exist,
- by parameter and the VectorPostprocessor exists but the requested vector does not,
- by VectorPostprocessor name and the VectorPostprocessor does not exist, and
- by VectorPostprocessor name and the VectorPostprocessor exists but the requested vector does not.
Specification(s): missing_errors/by_param, missing_errors/by_param_vector, missing_errors/by_name, missing_errors/by_name_vector
Design: VectorPostprocessorInterface
Issue(s): #17512
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Kernels
- 15.26.19The system shall allow the user to override the automated generation of a full coupling matrix when doing global AD indexing, which for this test results in a new nonzero allocation because there is off-diagonal coupling.
Specification(s): trust_user_and_then_error
Design: Coupleable
Issue(s): #16396
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.26.36The system shall error if a user assigns a scalar and requests evaluation of scalar residuals, but does not override the quadrature point residual evaluation routine in their derived class.
Specification(s): override
Design: ADScalarLMKernel
Issue(s): #22174
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.26.73The 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
- 15.26.87The 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
- 15.26.117The system shall error if a derived object uses scalars and computes scalar residuals but does not override the quadrature point residual calculation routine.
Specification(s): override
Design: ScalarLMKernel
Issue(s): #22174
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.26.122We shall not be able to solve a problem where the physics Jacobians are very large compared to the jacobian from a Dirichlet BC (unity)
Specification(s): cant-solve-poorly-scaled
Design: FEProblemSolve
Issue(s): #12601
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.26.125We shall not be able to solve a problem where the physics has large changes over time if we only scale once
Specification(s): cant-solve-large-transient-changes
Design: FEProblemSolve
Issue(s): #12601
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.26.129The 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
- 15.26.130Time kernel requires a transient executioner
Specification(s): bad_transient
Design: TaggingInterface
Issue(s): #9669
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.26.131The 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
- 15.26.132The 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
- 15.26.150The 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
- 15.26.151The 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
- rdg: Make Install
- 15.27.2The system shall support the ability to "install" inputs:
- from a pre-determined user-readable location;
- copied using a MOOSE-based binary;
- verifying a successful copy operation;
- able to report an error if overwriting may occur using a MOOSE-based binary;
- able to link a binary to an installed location;
- able to successfully launch the TestHarness using a MOOSE-based binary;
- and cleaned up from a user-readable location.
Specification(s): test_copy_install/setup_fake_test_structure, test_copy_install/copy_tests, test_copy_install/check_files, test_copy_install/copy_warn_overwrite, test_copy_install/link_exec_installed, test_copy_install/run, test_copy_install/tear_down
Design: MooseApp
Issue(s): #19022
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunCommandRunAppRunExceptionCheckFiles
- rdg: Markers
- 15.28.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
- 15.28.17The marker shall create an error if the coordinate vectors are not all the same size
Specification(s): wrong_size_error
Design: Markers SystemReporterPointMarker
Issue(s): #18886
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Materials
- 15.29.13ADPiecewiseLinearInterpolationMaterial shall throw an error if x, y, and xy_data are all specified
Specification(s): test_err1
Design: ADPiecewiseLinearInterpolationMaterial
Issue(s): #8265
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.29.11
- 15.29.14ADPiecewiseLinearInterpolationMaterial shall throw an error if x and xy_data are both specified
Specification(s): test_err2
Design: ADPiecewiseLinearInterpolationMaterial
Issue(s): #8265
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.29.13
- 15.29.15ADPiecewiseLinearInterpolationMaterial shall throw an error if x and y vectors are different lengths
Specification(s): test_err3
Design: ADPiecewiseLinearInterpolationMaterial
Issue(s): #8265
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.29.14
- 15.29.16ADPiecewiseLinearInterpolationMaterial shall throw an error if xy_data vector is not a multiple of two
Specification(s): test_err4
Design: ADPiecewiseLinearInterpolationMaterial
Issue(s): #8265
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.29.15
- 15.29.24Duplicate positions in the coupled variable mapping to function parameters shall raise an error.
Specification(s): order_duplicate_error
Design: CoupledValueFunctionMaterial
Issue(s): #20193
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.25A number of positions in mapping to function parameters that does not match the number of coupled variable shall raise an error.
Specification(s): order_count_error
Design: CoupledValueFunctionMaterial
Issue(s): #20193
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.27The system shall issue an error when multiple materials properties with the same name are declared on the same block.
Specification(s): error
Design: Materials System
Issue(s): #6533
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.32The system shall issue an error when required derivative materials that are retrieved are never declared.
Specification(s): warn
Design: DerivativeMaterialInterface
Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.33The system shall handle a bad evaluation by
- passing a silent nan.
- throwing a warning and passing a silent nan.
- throwing an error.
- throwing an exception.
Specification(s): bad_evaluation/nan, bad_evaluation/warning, bad_evaluation/error, bad_evaluation/exception
Design: DerivativeMaterialInterface
Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.29.34The system shall handle a bad evaluation when using JIT by
- passing a silent nan.
- throwing a warning and passing a silent nan.
- throwing an error.
- throwing an exception.
Specification(s): bad_evaluation_jit/nan, bad_evaluation_jit/warning, bad_evaluation_jit/error, bad_evaluation_jit/exception
Design: DerivativeMaterialInterface
Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.29.41The system shall issue an error when required dual number derivative materials that are retrieved are never declared.
Specification(s): ad_warn
Design: DerivativeMaterialInterface
Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.42The system shall handle a bad evaluation using dual numbers by
- passing a silent nan.
- throwing a warning and passing a silent nan.
- throwing an error.
- throwing an exception.
Specification(s): ad_bad_evaluation/nan, ad_bad_evaluation/warning, ad_bad_evaluation/error, ad_bad_evaluation/exception
Design: DerivativeMaterialInterface
Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.29.43The system shall allow users to request derivatives with respect to function symbols other than MOOSE variables
- such as derivatives w.r.t. material properties
- and error out if derivatives w.r.t unknown symbols are requested
- and error out if derivatives MOOSE variables are requested in additional_derivative_symbols (as they are requested by default)
- and error out if any symbols are supplied more than once
Specification(s): additional_derivatives/mat_props, additional_derivatives/error_unknown, additional_derivatives/error_variable, additional_derivatives/error_duplicate
Design: DerivativeMaterialInterface
Issue(s): #4299#6360#5055#6901#5039#14975#15207#18402
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.29.44The system shall require explicitly coupled properties to exist
- for regular properties in ParsedMaterials
- and error out for non-existing for explicitly requested derivatives in ParsedMaterials
- for explicitly requested derivatives in ParsedMaterials
- for explicitly requested derivatives but optimized out derivatives in ParsedMaterials
- but provide for a user override to default non-existing properties to zero
- in DerivativeParsedMaterials
Specification(s): required_property/parsed_material, required_property/parsed_material_requested_non_existing_derivative, required_property/parsed_material_requested_existing_derivative, required_property/parsed_material_requested_optimized_out_derivative, required_property/allow_override, required_property/derivative_parsed_material
Design: DerivativeMaterialInterface
Issue(s): #18917
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.29.48The system shall issue a warning when a "discrete" material object is retrieved for use in a controlling material but it is set to auto-execute.
Specification(s): newton_warning
Design: Materials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.49The system shall verify that a material being retrieved is defined everywhere that the retrieving material is defined:
- on compatible blocks, and
- on compatible boundaries.
Specification(s): coverage_check/block_incompatible, coverage_check/boundary_incompatible
Design: Materials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.50The system shall issue a warning when a "discrete" material's "reset" method is not defined.
Specification(s): reset_warning
Design: Materials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.55The system shall error
- if the user requests conversions to both AD and regular material properties, as this is not supported,
- if the user inputs a different number of functors and material properties, as the conversion match one to one.
Specification(s): exception_checks/ad_and_regular, exception_checks/wrong_size
Design: MaterialFunctorConverter
Issue(s): #19420
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.57The system shall error with a clear parameter error if
- the names for the regular functors to be converted are going to overlap with the new automatic differentiation functors
- the names for the regular functors to be converted are going to overlap with the other new regular functors
- the names for the automatic differentiation functors to be converted are going to overlap with the new regular functors
- the names for the automatic differentiation functors to be converted are going to overlap with the other new automatic differentiation functors
- the number of automatic differentiation functors to convert does not match the number of names for the converted functors
- the number of regular functors to convert does not match the number of names for the converted functors
Specification(s): errors/reg_in_ad_out, errors/reg_in_reg_out, errors/ad_in_reg_out, errors/ad_in_ad_out, errors/size_ad_in, errors/size_reg_in
Design: FunctorADConverter
Issue(s): #19420
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.61The system shall error if multiple definitions are given for a functor material property on a given subdomain.
Specification(s): multiple_definitions
Design: GenericFunctorMaterial
Issue(s): #16809
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.65The system shall error if an automatic differentiation (AD) object requests a non-AD functor when the functor is AD. This prevents potential dropping of derivative information.
Specification(s): bad-functor-type-mixing
Design: Materials System
Issue(s): #16809
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.66The system shall error if a functor material property is declared with the same name as another functor.
Specification(s): prop_name_issue
Design: Materials System
Issue(s): #16809
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.67The system shall error if a functor vector material property is declared with the same name as another functor.
Specification(s): vector_prop_name_issue
Design: Materials System
Issue(s): #16809
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.71The system shall error if a user provides to the vector magnitude functor material both a vector functor parameter and
- x-component functor parameter
- y-component functor parameter
Specification(s): multiple_provided/x_functor, multiple_provided/y_functor
Design: VectorMagnitudeFunctorMaterial
Issue(s): #20360
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.74The system shall report the retrieval of material properties by names:
- on boundaries,
- on blocks,
- on the all mesh boundaries, and
- on the all mesh blocks.
Specification(s): get_prop_names/boundary, get_prop_names/block, get_prop_names/any_boundary, get_prop_names/any_block
Design: Materials System
Issue(s): #4420
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.76The system shall report an error if a material property is needed on the entire domain but is only supplied on a subset of the subdomains.
Specification(s): property_on_one_block
Design: Materials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.77The system shall report that a material property is available when it is defined on a subdomain.
Specification(s): hasMaterialProperty
Design: Materials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.79The system shall report and error when a boundary restricted material is not defined on the same boundary as a boundary restricted object using that property in a calculation.
Specification(s): property_not_on_boundary
Design: Materials System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.87The system shall error if material property calculations result in a cyclic dependency.
Specification(s): mat_cyclic_dep_error_test
Design: Materials System
Issue(s): 6683d503d6441165249f8d49c65b76722430019a
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.89The system shall error if material properties are not computed on all subdomains.
Specification(s): check_test
Design: Materials System
Issue(s): 6683d503d6441165249f8d49c65b76722430019a
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.93The system shall report an error if a requested material property does not exist for
- regular material properties
- AD material properties
Specification(s): nonexistent_material_property/regular, nonexistent_material_property/ad
Design: Materials System
Issue(s): #21867
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.98The optional material property system use from a material object shall return
- an accessible material for existing AD properties
- an accessible material for existing non-AD properties
- an inaccessible material for non-existing AD properties
- an inaccessible material for non-existing non-AD properties
Specification(s): material_error/ad_expected, material_error/non-ad_expected, material_error/ad_not_expected, material_error/non-ad_not_expected
Design: Materials System
Issue(s): #18999
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.101The system shall error if an existing variable shares the same name as an auxiliary variable used for material output
Specification(s): duplicate_variable_name
Design: Materials SystemOutput System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.102The system shall error if the supplied output options for material data output are not consistent with the list of available outputs.
Specification(s): invalid_outputs
Design: Materials SystemOutput System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.108The system shall support the calculation of a material property with a linear interpolation and error if
- x, y, and xy_data are all specified;
- x and xy_data are both specified;
- the x and y vectors are different lengths; and
- the xy_data vector length is not a multiple of two.
Specification(s): errors/err1, errors/err2, errors/err3, errors/err4
Design: PiecewiseLinearInterpolationMaterial
Issue(s): #13224
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.29.122The system shall report and error when invalid indices are requested when attempting to output material properties through auxiliary field variables.
Specification(s): except1
Design: Materials System
Issue(s): #4489
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.29.1015.29.6915.29.8815.29.9415.29.9515.29.10915.29.11115.29.121
- rdg: Mesh
- 15.30.45The system shall include the ability to generate an annular mesh that errors when
- the min radius is larger than the max radius;
- the min angle is greater than or equal to the max angle;
- the angle separation is larger than 360 degrees;
- the number of elements in the angular direction is too small due to the number of elements; and
- the number of elements in the angular direction is too small due to the maximum angle.
- shall throw an error if the quadrilateral and triangular subdomain ids are the same.
- shall throw an error if both radial positions and the number of radial elements are prescribed.
- shall throw an error if both radial positions and the radius growth parameter are prescribed.
- 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.30.62The system shall throw a warning if user-provided extra element id names do not exist on mesh.
Specification(s): mesh_only_with_unrecognized_elem_ids
Design: Mesh System
Issue(s): #23386
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.30.73The 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
- 15.30.74The system shall issue a diagnostic when a referenced node set does not exist in the mesh
Specification(s): test
Design: MooseMesh
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.30.82The system shall report a useful error when saving additional meshes when
- the requested names are not unique,
- the requested name uses a reserved name,
- trying to use the mesh-saving capability with the final mesh,
- the requested saved mesh does not exist, and when
- the requested saved mesh has already been retrieved.
Specification(s): save_in_name_error/repeat_save_in_name, save_in_name_error/save_in_name_as_main, save_in_name_error/save_in_name_for_final_mesh_generator, save_in_name_error/save_in_meshes_not_find, save_in_name_error/save_in_meshes_retreived_twice
Design: MeshGenerator
Issue(s): #23618
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.30.83The 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
- 15.30.89The 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
- 15.30.96The 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
- 15.30.98The parallel partitioning capability by subdomain shall report a reasonable error when a given subdomain does not exist
Specification(s): missing_block
Design: Partitioner System
Issue(s): #8672#8747#8950#8956
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Meshgenerators
- 15.31.4The system shall throw an error if real_scalar_metadata_names and real_scalar_metadata_values are different in size.
Specification(s): err_diff_real_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.5The system shall throw an error if uint_scalar_metadata_names and uint_scalar_metadata_values are different in size.
Specification(s): err_diff_uint_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.6The system shall throw an error if int_scalar_metadata_names and int_scalar_metadata_values are different in size.
Specification(s): err_diff_int_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.7The system shall throw an error if dof_id_type_scalar_metadata_names and dof_id_type_scalar_metadata_values are different in size.
Specification(s): err_diff_dof_id_type_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.8The system shall throw an error if subdomain_id_type_scalar_metadata_names and subdomain_id_type_scalar_metadata_values are different in size.
Specification(s): err_diff_subdomain_id_type_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.9The system shall throw an error if boolean_scalar_metadata_names and boolean_scalar_metadata_values are different in size.
Specification(s): err_diff_boolean_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.10The system shall throw an error if point_scalar_metadata_names and point_scalar_metadata_values are different in size.
Specification(s): err_diff_point_scalar_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.11The system shall throw an error if real_vector_metadata_names and real_vector_metadata_values are different in size.
Specification(s): err_diff_real_vector_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.12The system shall throw an error if uint_vector_metadata_names and uint_vector_metadata_values are different in size.
Specification(s): err_diff_uint_vector_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.13The system shall throw an error if int_vector_metadata_names and int_vector_metadata_values are different in size.
Specification(s): err_diff_int_vector_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.14The system shall throw an error if dof_id_type_vector_metadata_names and dof_id_type_vector_metadata_values are different in size.
Specification(s): err_diff_dof_id_type_vector_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.15The system shall throw an error if subdomain_id_type_vector_metadata_names and subdomain_id_type_vector_metadata_values are different in size.
Specification(s): err_diff_subdomain_id_type_vector_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.16The system shall throw an error if point_vector_metadata_names and point_vector_metadata_values are different in size.
Specification(s): err_diff_point_vector_size
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.17The system shall throw an error if real_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_real_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.18The system shall throw an error if uint_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_uint_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.19The system shall throw an error if int_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_int_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.20The system shall throw an error if dof_id_type_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_dof_id_type_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.21The system shall throw an error if subdomain_id_type_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_subdomain_id_type_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.22The system shall throw an error if boolean_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_boolean_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.23The system shall throw an error if point_scalar_metadata_names contains non-unique elements.
Specification(s): err_dup_point_scalar_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.24The system shall throw an error if real_vector_metadata_names contains non-unique elements.
Specification(s): err_dup_real_vector_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.25The system shall throw an error if uint_vector_metadata_names contains non-unique elements.
Specification(s): err_dup_uint_vector_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.26The system shall throw an error if int_vector_metadata_names contains non-unique elements.
Specification(s): err_dup_int_vector_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.27The system shall throw an error if dof_id_type_vector_metadata_names contains non-unique elements.
Specification(s): err_dup_dof_id_type_vector_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.28The system shall throw an error if subdomain_id_type_vector_metadata_names contains non-unique elements.
Specification(s): err_dup_subdomain_id_type_vector_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.29The system shall throw an error if point_vector_metadata_names contains non-unique elements.
Specification(s): err_dup_point_vector_name
Design: AddMetaDataGenerator
Issue(s): #23135
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.38The system shall error if missing a consistent positive or negative extrusion direction.
Specification(s): mixed_extrude
Design: AdvancedExtruderGenerator
Issue(s): #21273
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.45The system shall error when generating an annular mesh with equal-area elements when a growth ratio is also provided
Specification(s): conflicting_settings
Design: AnnularMeshGenerator
Issue(s): #20422
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.46The system shall error when generating an annual mesh with equal-area elements when radial positions are also provided
Specification(s): conflicting_settings_nr
Design: AnnularMeshGenerator
Issue(s): #20422
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.48The system shall only support the ability to add additional mesh generators from a user accessible programmatic interface when
- there exists a generator to append to
- such mesh generators take an input
- other mesh generators have been added to be appended to
Specification(s): errors/nothing_to_append_to, errors/no_input, errors/wrong_time
Design: MeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.49The system shall be capable of deleting
- all of the elements in a mesh based on subdomain ID,
- all of the elements in a mesh based on subdomain names and
- multiple blocks simultaneously in a mesh based on subdomain ID.
- blocks and assigning the new boundary even if the input mesh is not prepared.
- blocks and properly removing lower dimensional elements with a deleted element as their interior parent.
- blocks and retaining lower dimensional elements with a deleted interior parent if requested,
- blocks and erroring if a block does not exist.
Specification(s): block_deletion/all_by_block_ids, block_deletion/all_by_block_names, block_deletion/multiple_blocks, block_deletion/input_not_prepared, block_deletion/delete_interior_parents, block_deletion/preserve_exteriors, block_deletion/missing_block
Design: BlockDeletionGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.31.52The system shall return an error if the following unsupported features are present:
- the mesh is distributed in parallel
- the block to extract is uniformly refined
Specification(s): errors/distributed, errors/refined
Design: BlockToMeshConverterGenerator
Issue(s): #20880
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.54The system shall error if attempting to delete a non-existent boundary
Specification(s): invalid_boundary
Design: BoundaryDeletionGenerator
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.56The system shall produce an error when attempting to add a new mesh node set based on a bounding box
- where the bounding box fails to span any mesh nodes, and
- where multiple boundary IDs are supplied for a single bounding box.
Specification(s): errors/bad_coord, errors/test_bad_boundaryid
Design: BoundingBoxNodeSetGenerator
Issue(s): #11640
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.57The system shall be capable of splitting existing mesh boundary sets where their underlying subdomain changes
- on external boundaries, and
- on internal boundaries, and
- error when the boundary does not exist in the mesh.
Specification(s): boundary_type/external, boundary_type/internal, boundary_type/invalid_boundary
Design: BreakBoundaryOnSubdomainGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.31.64The system shall error if the mesh does not contain the specified block pair
Specification(s): invalid_block_pair
Design: BreakMeshByBlockGenerator
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.65The system shall error if the mesh does not contain the specified surrounding block
Specification(s): invalid_surrounding_block
Design: BreakMeshByBlockGenerator
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.67The system shall throw an error if the subdomains with different ID have duplicate names.
Specification(s): check_duplicate_subdomain_names
Design: MooseMesh
Issue(s): #23735
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.70The system shall throw an error if the length of the provided customized transition layer rarios does not match the number of the boundaries to be corrected.
Specification(s): err_transition_layer_ratios_length
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.71The system shall throw an error if the length of the provided customized circular verification tolerance does not match the number of the boundaries to be corrected.
Specification(s): err_custom_circular_tolerance_length
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.72The system shall throw an error if the provided boundaries are not in XY plane.
Specification(s): err_non_xy_plane
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.73The system shall throw an error if the provided boundary contains fewer than three nodes.
Specification(s): err_few_points
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.74The system shall throw an error if any nodes are moved twice for radius correction.
Specification(s): err_overlapped_transition_area
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.75The system shall throw an error if the provided boundary to correct is not circular.
Specification(s): err_non_circular
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.76The system shall throw an error if the provided boundaries are all full circles and the parameter to move the end nodes in the span direction is set to true.
Specification(s): err_full_cirles_and_span_direction
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.77The system shall throw an error if an input boundary does not exist in the input mesh.
Specification(s): err_boundary_not_found
Design: CircularBoundaryCorrectionGenerator
Issue(s): #23972
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.79The system shall error when trying to combine multiple meshes,
- but only one input is supplied with no positions, or
- but only one input is supplied with no positions file, or
- the number of meshes and the number of positions is mismatched, or
- the number of meshes and the number of positions in the file is mismatched.
Specification(s): errors/missing_pos, errors/missing_pos_file, errors/mismatch_pos, errors/mismatch_pos_from_file
Design: CombinerGenerator
Issue(s): #13412
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.84The system shall be able to give a clear error message about a cyclic graph in mesh generation.
Specification(s): error
Design: Mesh System
Issue(s): #21743
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.90The system shall be able to check if or not users ask for too many layers of ghosting elements.
Specification(s): check_nlayers
Design: DistributedRectilinearMeshGenerator
Issue(s): #11485
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.96The system shall error out if the number of cores for partition is larger than the total number of cores.
Specification(s): 3d_scomm_10_out
Design: DistributedRectilinearMeshGenerator
Issue(s): #15464
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.110The system shall error if the subdomain to explode was not found in the mesh
Specification(s): invalid_subdomain
Design: ExplodeMeshGenerator
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.114The system shall error on assigning boundary identifiers if the supplied location is outside of the domain.
Specification(s): test_bad_coord
Design: ExtraNodesetGenerator
Issue(s): #13814
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.127The system shall throw an error if either input vector of points include points that are not in XY plane.
Specification(s): non_xy_plane
Design: FillBetweenPointVectorsGenerator
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.128The system shall throw an error if either input vector of points include less than 2 points.
Specification(s): not_enough_points
Design: FillBetweenPointVectorsGenerator
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.129The system shall throw an error if the two input vectors have different length and QUAD4 elements option is selected.
Specification(s): quad_with_different_vector_sizes
Design: FillBetweenPointVectorsGenerator
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.134The system shall throw an error if the two input meshes are the same.
Specification(s): err_same_inputs
Design: FillBetweenSidesetsGenerator
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.135The system shall throw an error if one of the input boundary to generate a mesh in-between has multiple segments.
Specification(s): err_multiseg_boundary
Design: FillBetweenSidesetsGenerator
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.136The system shall throw an error if one of the input boundary to generate a mesh in-between is a closed loop.
Specification(s): err_closed_loop_boundary
Design: FillBetweenSidesetsGenerator
Issue(s): #20641
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.139The system shall generate an error when the objects used to generate a mesh results in an ambiguous end point
- due to a single graph with multiple end points, or
- due to multiple independent trees.
Specification(s): ambigious/single_graph, ambigious/independent_graphs
Design: Mesh System
Issue(s): #14058
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.144The system shall generate a warning if Mesh Generators are used with a mesh type that does not accept them
Specification(s): type_test
Design: GeneratedMeshGenerator
Issue(s): #13959
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.31.3015.31.4715.31.8515.31.11515.31.14015.31.19415.31.211
- 15.31.154The system shall error if the existing subdomain does not exist in the mesh
Specification(s): invalid_existing_subdomain
Design: MeshExtruderGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.156The system shall issue an error when mesh meta-data properties are requested but never declared.
Specification(s): meta_data_error_check
Design: MeshMetaDataInterface
Issue(s): #13841
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.157The system shall error if a invalid identifier is supplied when attempting to retrieve a restart meta data object.
Specification(s): get_meta_data_error_check
Design: MeshMetaDataInterface
Issue(s): #13841
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.161The system shall error if the node to be moved cannot be found in the mesh.
Specification(s): failure_missing
Design: MoveNodeGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.162The system shall error if the node position and node id arrays do not match in size
Specification(s): failure_mismatch
Design: MoveNodeGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.163The system shall error if both shifts and positions are specified
Specification(s): failure_overspecified
Design: MoveNodeGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.173The system shall throw an error if the starting and ending points of a section are overlapped while the section is supposed to be open.
Specification(s): err_crossed_curve
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.174The system shall throw an error if the oversampling algorithm exceeds its designated maximum sampling number.
Specification(s): err_max_oversample
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.175The system shall throw an error if the elements in section_bounding_t_values are not unique.
Specification(s): err_repeated_t_series
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.176The system shall throw an error if forced_closed_num_segments is provided but the starting and ending points of the curve are overlapped.
Specification(s): err_unneeded_forced_closed_num_segments_1
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.177The system shall throw an error if forced_closed_num_segments is provided but the curve to be generated is open.
Specification(s): err_unneeded_forced_closed_num_segments_2
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.178The system shall throw an error if elements in section_bounding_t_values do not change monotonically.
Specification(s): err_unsorted_t_series
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.179The system shall throw an error if size of nums_segments is not consistent with size of section_bounding_t_values.
Specification(s): err_bad_nums_segments
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.180The system shall throw an error if x_formula cannot be parsed as a function.
Specification(s): err_failed_parsing_x
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.181The system shall throw an error if y_formula cannot be parsed as a function.
Specification(s): err_failed_parsing_y
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.182The system shall throw an error if z_formula cannot be parsed as a function.
Specification(s): err_failed_parsing_z
Design: ParsedCurveGenerator
Issue(s): #22848
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.186The system shall error if one of the included subdomains does not exist in the mesh.
Specification(s): invalid_included_subdomains
Design: ParsedGenerateSideset
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.187The system shall error if one of the included neighbors does not exist in the mesh.
Specification(s): invalid_included_neighbors
Design: ParsedGenerateSideset
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.189The system shall error if a specified subdomain does not exist in the mesh.
Specification(s): invalid_excluded_subdomain
Design: ParsedSubdomainMeshGenerator
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.193The system shall report a reasonable error when stitching meshes together from a user-defined pattern when
- the boundary name does not exist
Specification(s): errors/non_existent_boundary
Design: PatternedMeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.199The system shall error if attempting to refine a block that does not exist in the mesh.
Specification(s): invalid_block
Design: RefineBlockGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.201The system shall error if the specified boundary to be refined does not exist
Specification(s): failureBoundary
Design: RefineSidesetGenerator
Issue(s): #18913
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.204The system shall throw a reasonable error:
- when old blocks are provided that do not exist within the mesh
- and when the provided old and new blocks are not the same length.
Specification(s): errors/missing, errors/inconsistent_size
Design: RenameBlockGenerator
Issue(s): #11640#14128#16885#17710
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.206The system shall report a reasonable error when renaming or renumbering blocks using deprecated syntax when
- both old block IDs and old block names are provided
- both new block IDs and new block names are provided
- the deprecated syntax for old block id and the new syntax for old block is used
- the deprecated syntax for old block name and the new syntax for old block is used
- the deprecated syntax for new block id and the new syntax for new block is used
- the deprecated syntax for new block name and the new syntax for new block is used
Specification(s): deprecated_errors/old_block_id_and_name, deprecated_errors/new_block_id_and_name, deprecated_errors/old_block_and_id, deprecated_errors/old_block_and_name, deprecated_errors/new_block_and_id, deprecated_errors/new_block_and_name
Design: RenameBlockGenerator
Issue(s): #11640#14128#16885#17710
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.209The system shall throw a reasonable error:
- when old boundaries are provided that do not exist within the mesh
- and when the provided old and new boundaries are not the same length.
Specification(s): errors/missing, errors/inconsistent_size
Design: RenameBoundaryGenerator
Issue(s): #11640#14128#16885#21268
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.213The system shall error if the subdomain to create sidesets around does not exist in the mesh
Specification(s): invalid_block
Design: SideSetsAroundSubdomainGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.215The system shall have the ability to create new side sets between adjacent subdomains:
- on a mesh with several adjacent subdomains,
- where some subdomains are adjacent and not where paired subdomains are not adjacent, and
- between two subdomains in a mesh with two adjacent subdomains.
- between two subdomains in an unprepared mesh.
- only when the primary block exists in the mesh.
- only when the paired block exists in the mesh.
Specification(s): group/adjacent_subs, group/nonadjacent_subs, group/two_subs, group/unprepared_input, group/invalid_primary_block, group/invalid_paired_block
Design: SideSetsBetweenSubdomainsGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.31.217The system shall issue an error when attempting to create side sets from a bounding box:
- when no elements are located within the specified bounding box,
- when the bounding box is larger than the domain so that no new side set is created, and
- when the bounding box fails to span over any nodes.
- if the incorrect boundary inputs are supplied.
Specification(s): errors/no_elements_in_bounding_box, errors/no_side_sets_found, errors/no_nodes_found, errors/error_boundary_number
Design: SideSetsFromBoundingBoxGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.218The system shall support assigning boundary identifiers based the bounding box of a subdomain
- if existing boundaries overlap and
- error if no nodes are located in the given bounding box.
Specification(s): overlap/test_overlapping, overlap/test_overlapping_sidesets_error
Design: SideSetsFromBoundingBoxGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.31.224The system shall return errors if it detects ambiguous sideset specifications
Specification(s): sidesets_ambiguity
Design: SideSetsFromPointsGenerator
Issue(s): #24619
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.230The system shall be able to generate meshes by stacking up existing meshes in
- two and
- three dimensions and
- error if the dimensions of the meshes to be stacked are not consistent.
Specification(s): stack/2d, stack/3d, stack/error_dims
Design: StackGenerator
Issue(s): #11640
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.31.238The system shall error if a restricted subdomain of the bounding box subdomain generation does not exist in the mesh
Specification(s): invalid_restricted_subdomain
Design: SubdomainBoundingBoxGenerator
Issue(s): #22117
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.242The system shall report a reasonable error generating meshes when
- requesting an input mesh generator by parameter and the parameter is not valid
- requesting an input mesh generator parameter and the parameter is of the wrong type
- requesting an input mesh generator by name and the name is not valid
- requesting input mesh generators by parameter and the parameter is of the wrong type
- requesting an input mesh at an unallowed time
- building a sub generator at an unallowed time
- declaring a property on the mesh at an unallowed time
- requesting an input mesh generator by parameter that does not exist
- requesting input mesh generators by parameter that do not exist
- requesting an input mesh generator by name that does not exist
- requesting input mesh generators by name that do not exist
- failing to properly manage the memory of an input mesh generator
- declaring a property on the mesh multiple times
- coupling an input mesh generator in a parameter for a sub generator but not using said dependency
- coupling an input mesh generator in a sub generator but not declaring it as a dependency
- coupling an input mesh generator in a parameter but not using said mesh generator
- getting a mesh generator that does not exist
- forcibly setting the final mesh when said mesh does not exist
- an input mesh is not found because its dependencies are not properly declared
Specification(s): errors/get_mesh_invalid, errors/get_mesh_wrong_type, errors/get_meshes_by_name_invalid, errors/get_meshes_by_name_wrong_type, errors/get_mesh_outside_construct, errors/sub_outside_construct, errors/declare_mesh_prop_outside_construct, errors/get_mesh_not_found, errors/get_meshes_not_found, errors/get_mesh_by_name_not_found, errors/get_meshes_by_name_not_found, errors/input_not_moved, errors/mesh_prop_double_declare, errors/unused_sub_input, errors/sub_no_declare_input, errors/unused_param_input, errors/missing_get, errors/missing_final, errors/not_constructed_yet
Design: MeshGenerator
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.249The system shall have the capability of triangulating a polyline boundary
- within an input polyline
- returning errors if the polyline is not closed
- returning errors if the polyline is disconnected
- taking the boundary of a 2D input mesh
- taking a specified subset of an input polyline set
- taking a specified subset of a 2D input boundary
- respecting any specified interior 'hole' meshes
- assigning user-provided hole boundary names
- allowing deep nesting of triangulations within triangulations
- with optional Laplacian mesh smoothing.
Specification(s): xydelaunay/basic, xydelaunay/open_line, xydelaunay/multi_line, xydelaunay/from_2d, xydelaunay/subdomain_1d, xydelaunay/subboundary_2d, xydelaunay/with_holes, xydelaunay/with_hole_names, xydelaunay/nested, xydelaunay/smoothed
Design: XYDelaunayGenerator
Issue(s): #20192
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.31.256The system shall throw an error if the input mesh is not 2D.
Specification(s): err_non_2d_mesh
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.257The system shall throw an error if the given name of the triangle element block, created during mesh line cutting, already exists in the input mesh, in the element cutting mode.
Specification(s): err_pre_exist_block_name_elem
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.258The system shall throw an error if the given name of the triangular element block, created during mesh line cutting, already exists in the input mesh in the node moving mode.
Specification(s): err_pre_exist_block_name_node
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.259The system shall throw an error if the size of the cut line parameters is not three.
Specification(s): err_wrong_line_params_size
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.260The system shall throw an error if the cut line parameters is not valid to define a line.
Specification(s): err_wrong_line_params_value
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.261The system shall throw an error if the external boundary id is not provided when the node moving method is used.
Specification(s): err_no_external_boundary_id
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.31.262The system shall throw an error if the triangle element improvement is enabled under the node moving mode.
Specification(s): err_tri_improve_for_node_moving
Design: XYMeshLineCutter
Issue(s): #23844
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Misc
- 15.33.7The system shall report an error when a material property is not defined on a boundary.
Specification(s): bc_check
Design: Problem system overview
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.8The system shall report an error when a material property requested by a UserObject is not defined on a boundary.
Specification(s): side_uo_check
Design: Problem system overview
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.9The system shall report an error when a material property requested by a DGKernel is not defined on a boundary.
Specification(s): dgkernel_check_boundary
Design: Problem system overview
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.10The system shall report an error when a material property requested by a DGKernel is not defined on a subdomain.
Specification(s): dgkernel_check_block
Design: Problem system overview
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.12The system shall produce an error when an object's discretization area is explicitly set to a value greater than the area of the underlying variable used by the object.
Specification(s): variable_interface_error_block_set
Design: Problem system overview
Issue(s): #9889
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.13The system shall produce an error when an object's discretization area is greater than the area of the underlying variable used by the object.
Specification(s): variable_interface_error_block_any
Design: Problem system overview
Issue(s): #9889
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.14The system shall produce an error when an object's discretization area is explicitly set to a different area than the area of a coupled variable used by the object.
Specification(s): coupleable_error_block_set
Design: Problem system overview
Issue(s): #9889
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.15The system shall produce an error when an object's discretization area is different than an explicitly set variable on only defined on a different portion of the mesh.
Specification(s): coupleable_error_block_set2
Design: Problem system overview
Issue(s): #9889
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.16The system shall produce an error when an object's discretization area is covers the whole mesh but a coupled variable only exists on a portion of the mesh.
Specification(s): coupleable_error_block_any
Design: Problem system overview
Issue(s): #9889
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.17The system shall error if a boundary restricted object depends on a variable that is not defined on any portion of the boundary. These boundary restricted objects include
- nodal auxiliary kernels
- nodal user objects
- nodal boundary conditions
- integrated boundary conditions
- side user objects
- elemental auxiliary kernels
Specification(s): error/nodal_aux, error/nodal_uo, error/nodal_bc, error/integrated_bc, error/side_uo, error/elemental_aux
Design: AuxKernels SystemUserObject System
Issue(s): #9734
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.18The system shall error if a variable is coupled into a boundary restricted object, along whose boundary the variable is only partially defined.
Specification(s): partial_coverage
Design: AuxKernels SystemUserObject System
Issue(s): #9734
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.19The system shall error if an object restricted on an internal boundarydepends on a variable that is not defined on any portion of the boundary.
Specification(s): error
Design: AuxKernels SystemUserObject System
Issue(s): #9734
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.20The system shall report an error when the system solver is unable to find a converged solution.
Specification(s): steady_no_converge
Design: Executioner System
Collection(s): FAILURE_ANALYSIS
Type(s): RunApp
- 15.33.21The 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
- 15.33.22The 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
- 15.33.23The 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
- 15.33.24The 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
- 15.33.25The 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
- 15.33.26The 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
- 15.33.27The 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
- 15.33.28The 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
- 15.33.29The 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
- 15.33.30The 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
- 15.33.31The 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
- 15.33.32The 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
- 15.33.33The 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
- 15.33.34The 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
- 15.33.37The 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
- 15.33.38The 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
- 15.33.39The 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
- 15.33.40The 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
- 15.33.41The 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
- 15.33.42The 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
- 15.33.43The 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
- 15.33.44The 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
- 15.33.45The 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
- 15.33.46The 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
- 15.33.47The 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
- 15.33.48The 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
- 15.33.49The 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
- 15.33.50The 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
- 15.33.51The 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
- 15.33.52The 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
- 15.33.53The 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
- 15.33.54The 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
- 15.33.55The 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
- 15.33.56The 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
- 15.33.57The 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
- 15.33.58The 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
- 15.33.59The 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
- 15.33.60The 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
- 15.33.61The 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
- 15.33.62The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.63The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.64The 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
- 15.33.65The 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
- 15.33.66The 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
- 15.33.67The 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
- 15.33.68The 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
- 15.33.69The 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
- 15.33.70The 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
- 15.33.71The 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
- 15.33.72The 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
- 15.33.73The 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
- 15.33.74The 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
- 15.33.75The 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
- 15.33.76The 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
- 15.33.77The 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
- 15.33.78The system shall report an error when a required parameter is not supplied in a MooseObject.
Specification(s): missing_required_param_in_kernel_test
Design: Problem system overview
Issue(s): #1405
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.79The system shall report an error when the variable parameter is missing from a residual object
Specification(s): missing_var_parameter_test
Design: Problem system overview
Issue(s): #1405
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.80The 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
- 15.33.81The 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
- 15.33.83The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.84The 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
- 15.33.85The 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
- 15.33.86The 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
- 15.33.87The 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
- 15.33.88The 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
- 15.33.89The 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
- 15.33.90The system shall report an error when an unused parameter is provided through the input file or an Action.
Specification(s): unused_param_test
Design: Problem system overview
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.91The system shall report an error when an unused parameter is supplied on the command line.
Specification(s): unused_param_test_cli
Design: Problem system overview
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.94The 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
- 15.33.95The 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
- 15.33.96The system shall report an error when an input file block associated with a pluggable system is asked to build an object from a different system.
Specification(s): wrong_object_test
Design: Problem system overview
Issue(s): #1405
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.97The system shall report an error when an input file block associated with a pluggable system is misspelled.
Specification(s): wrong_action_spelling
Design: Problem system overview
Issue(s): #20062
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.99The 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
- 15.33.100The 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
- 15.33.101The 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
- 15.33.102The 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
- 15.33.103The 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
- 15.33.104The 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
- 15.33.105The 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
- 15.33.107The 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
- 15.33.108The 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
- 15.33.109The 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
- 15.33.110The 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
- 15.33.111The 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
- 15.33.113The 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
- 15.33.114The 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
- 15.33.115The 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
- 15.33.116The 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
- 15.33.117The 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
- 15.33.118The 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
- 15.33.119The system shall report an error when an attempt is made to couple a variable with itself in coupled force term using automated differentiation.
Specification(s): coupling_itself_ad
Design: Problem system overview
Issue(s): #18214
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.120The 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
- 15.33.121The 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
- 15.33.122The 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
- 15.33.123The 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
- 15.33.124The 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
- 15.33.125The 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
- 15.33.126The 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
- 15.33.127The 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
- 15.33.128The 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
- 15.33.129The 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
- 15.33.130The 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
- 15.33.131The 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
- 15.33.132The 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
- 15.33.133The 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
- 15.33.134The 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
- 15.33.135The 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
- 15.33.136The 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
- 15.33.137The system shall report an error if an object tries to get the name of a coupled constant.
Specification(s): coupled_constant_yet_needs_name
Design: Coupleable
Issue(s): #22597
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.138The 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
- 15.33.139The 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
- 15.33.140The 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
- 15.33.143The system shall throw an exception if a data file cannot be found in any of the designated directories.
Specification(s): error
Design: MooseObject
Issue(s): #20839
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.147The 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
- 15.33.160The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.161The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.168The 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
- 15.33.174A 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): 15.33.173
- 15.33.175A 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): 15.33.173
- 15.33.178A 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.33.177
- 15.33.187The system shall error if the user provides inconsistent parameter values to the mesh and problem for the parameters related to
- subdomain blocks
- coordinate system types
Specification(s): bad_params/block, bad_params/coord_type
Design: Mesh System
Issue(s): #21975
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.194The 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
- 15.33.197The system shall error if the residual calculation contribution is assigned to the incorrect variable for
- on-diagonal and
- 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
- 15.33.211The system shall not accept a converged solution if the solution has been tagged as invalid.
Specification(s): solution_invalid
Design: SolutionInvalidity
Issue(s): #22814
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.33.212The system shall allow overriding the solution validity checks.
Specification(s): allow_solution_invalid
Design: SolutionInvalidity
Issue(s): #22814
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Mortar
- 15.34.78The system shall error if a nonlinear variable is applied for sigma instead of an auxiliary variable.
Specification(s): auxiliary
Design: PenaltyPeriodicSegmentalConstraint
Issue(s): #22174
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Multiapps
- 15.35.5The system shall detect input file problems with sub app input files.
Specification(s): input_file
Design: MultiApp System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.6The system shall CLI argument problems related to sub app input files.
Specification(s): unused_subapp_param
Design: MultiApp System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.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.
Specification(s): positions
Design: MultiApp System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.8The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.9The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.10The 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.11The system shall error when the multiapp positions file is malformed.
Specification(s): bad_positions
Design: MultiApp System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.12The 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
- 15.35.17The 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
- 15.35.18The 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
- 15.35.19The 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
- 15.35.20The 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
- 15.35.21The 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
- 15.35.22The 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
- 15.35.26The 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
- 15.35.30When sub-application solve does not converge, the system shall be able to either
- abort run,
- throw error if error_on_dtmin is not set, or
- 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
- 15.35.33The 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
- 15.35.63The 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): 15.35.62
- 15.35.78The 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
- 15.35.81The system shall error if the reset times specified for a multiapp are not sorted, as this likely indicates a user error in their input
Specification(s): not_sorted_times
Design: MultiApp System
Issue(s): #1970
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.86The system shall error if
- both outputting in position and displacing applications are requested at the same time, as displaced apps are already output in position
- a translation is requested on a spherical or cylindrical coordinate mesh, as this is not expected to be a valid transformation
- displacing applications and moving applications at a certain time are both requested as this combination of features is not implemented
Specification(s): errors/output_and_run_in_position, errors/invalid_frame_for_translation, errors/move_apps_not_supported
Design: MultiApp System
Issue(s): #19121
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.35.101The system shall issue a warning if the parent app and the child app time become de-synchronized, except when using sub-cycling or resetting mechanisms which naturally handle or create desynchronization
Specification(s): warning
Design: TransientMultiApp
Issue(s): #22338
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Nodalkernels
- 15.36.4The system shall be able to enforce an upper and lower bound on a variable using nodal NCP, nodal application of resultant forces,
- have no oscillations in the solution, and
- work with automatic differentiation, and
- have a non-singular matrix, and
- be incompataible with algebraic multigrid
Specification(s): upper_and_lower_bound/exo, upper_and_lower_bound/ad_exo, upper_and_lower_bound/non_singular, upper_and_lower_bound/amg_fail
Design: UpperBoundNodalKernel
Issue(s): #2999
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunExceptionExodiff
- rdg: Outputs
- 15.37.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
- 15.37.56If 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
- 15.37.57If 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): 15.37.56
- 15.37.62The 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
- 15.37.63The 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
- 15.37.64The system shall reserve names for output objects:
- "none" and
- "all."
Specification(s): reserved/none_reserved, reserved/all_reserved
Design: Output System
Issue(s): #1927
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.37.71The 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
- 15.37.121The system shall support the disabling of an output object by restricting the execution settings.
Specification(s): no_output
Design: Output System
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.37.132The 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
- 15.37.133The 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
- 15.37.134The 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
- 15.37.135The 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
- 15.37.155The 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
- The 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
- The 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
- 15.37.181The 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
- rdg: Parser
- 15.38.2The system shall produce an error when the active parameter refers to a non-exiseant block.
Specification(s): active_section_missing
Design: Parser
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.38.3The system shall produce an error when the inactive parameter refers to a non-existent block.
Specification(s): inactive_section_missing
Design: Parser
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.38.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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.38.5The system shall honor the active or inactive parameters at the top (root) level.
Specification(s): top_level
Design: Parser
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.38.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): 15.38.9
- 15.38.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
- 15.38.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
- 15.38.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
- 15.38.17The system shall support for multiple input files, which are merged into one input specification for a simulation
- where no parameters overlap
- where input files may override parameters in previous inputs
- while locating input errors in the correct file
- 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunExceptionExodiff
- 15.38.18The system shall raise an error if no input files were specified after the -i option
Specification(s): no_file
Design: Parser
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.38.24The system shall support vector size checking on input parameter vectors:
- for ints,
- for Reals.
Specification(s): vector_len_checks/realvectorlength, vector_len_checks/intvectorlength
Design: InputParameters
Issue(s): #3988
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.38.25The system shall support vector element checking:
- against constant expressions,
- against other unsigned int vector elements,
- against other long vector elements,
- against other int vector elements, and
- 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
- 15.38.26The 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
- 15.38.27The 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
- rdg: Partitioners
- 15.39.2The block-weighted partitioner shall report a reasonable error when
- the input blocks do not match the size of the input weights
- an input block is not found in the mesh
Specification(s): errors/size_mismatch, errors/missing_block
Design: BlockWeightedPartitioner
Issue(s): #13675
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.39.20The system shall error if an out of range rank is given to SingleRankPartitioner
Specification(s): test_error
Design: SingleRankPartitioner
Issue(s): #18729
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Positions
- 15.42.3The system shall error if
- the positions objects to use for creating multiapps are not initialized, or
- the size of the current positions does not match the number of initial positions.
Specification(s): error/not_init, error/size_changed
Design: Positions
Issue(s): #23587
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Postprocessors
- 15.43.5The system shall issue an error when the dependent "change ofFixedPoint" calculation
- "with respect to initial" isn't calculated at the initial step and
- "with respect to previous" isn't calculated at the previous step.
Specification(s): change_over_fixed_point_error/change_with_respect_to_initial_error_dependent, change_over_fixed_point_error/change_with_respect_to_initial_error_this
Design: ChangeOverFixedPointPostprocessor
Issue(s): #10327
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.7The system shall issue an error when the dependent "change of time" calculation
- "with respect to initial" isn't calculated at the initial step and
- "with respect to previous" isn't calculated at the previous step.
Specification(s): change_over_time_error/change_with_respect_to_initial_error_dependent, change_over_time_error/change_with_respect_to_initial_error_this
Design: ChangeOverTimePostprocessor
Issue(s): #10327
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.41The system shall report and error when the target value is lower than one of the sampled endpoints.
Specification(s): below_min
Design: FindValueOnLine
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.42The system shall report and error when the target value is greater than one of the sampled endpoints.
Specification(s): above_max
Design: FindValueOnLine
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.47The system shall report and error when the sampling line extends beyond the mesh bounding box.
Specification(s): line_out_of_bounds
Design: FindValueOnLine
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.48The system shall report and error when the line sampling algorithm fails to converge within the desired depth.
Specification(s): depth_exceeded
Design: FindValueOnLine
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.99The system shall report a reasonable error when trying to obtain information from the PerfGraph for a section that does not exist
Specification(s): missing
Design: PerfGraphData
Issue(s): #11551
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.101The system shall report an error when a field variable sample location is outside of the domain.
Specification(s): error
Design: PointValue
Issue(s): #3475
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.111The system shall report an error when a requested parameter for reporting does not exist
- with a wildcard in the name and
- a complete name/
Specification(s): error_report/bad_name_error, error_report/no_param_error
Design: Postprocessor System
Issue(s): #4604#5680#9087#6934
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.43.119The system shall support computing the average of a material property over a side on the mesh.
- if the material property is of
Realtype - if the material property is of
RealVectorValuetype - if the material property is of
std::vector<Real>type - if the material property is of
RankTwoTensortype - if the material property is of
RankThreeTensortype - if the material property is of
RankFourTensortype - And shall error out if the index components do not match the dimension of the supplied property
Specification(s): side_average_material_property/real, side_average_material_property/realvector, side_average_material_property/stdvec, side_average_material_property/ranktwo, side_average_material_property/rankthree, side_average_material_property/rankfour, side_average_material_property/error
Design: SideAverageMaterialProperty
Issue(s): #18649
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionCSVDiff
- if the material property is of
- 15.43.128The system shall support computing the integral of a material property over a side on the mesh.
- if the material property is of
Realtype - if the material property is of
RealVectorValuetype - if the material property is of
RankTwoTensortype - And shall error out if the index components do not match the dimension of the supplied property
Specification(s): side_integral_material_property/real, side_integral_material_property/realvector, side_integral_material_property/ranktwo, side_integral_material_property/error
Design: SideIntegralMaterialProperty
Issue(s): #18649
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionCSVDiff
- if the material property is of
- 15.43.138The Postprocessor that returns a single specified component of a VectorPostprocessor shall generate an error if the requested component is out of the range of the vector
Specification(s): vpp_component_range_err
Design: VectorPostprocessorComponent
Issue(s): #11439
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.43.137
- rdg: Preconditioners
- 15.44.7The system shall error if a user has forgotten a variable in their field splits.
Specification(s): missing_var_in_split
Design: FSP
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Problems
- 15.46.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
- 15.46.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
- 15.46.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
- 15.46.13Eigenvalue system requires SLEPc installed
Specification(s): no_slepc
Design: Eigenvalue
Issue(s): #7398
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.46.38The system shall support compatibility of solve type and constant-matrices flag
Specification(s): check_solve_type
Design: Eigenvalue
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.46.37
- 15.46.59The system shall require all grouped variables to be included in the convergence check.
Specification(s): converge_on_group_error
Design: ReferenceResidualProblem
Issue(s): #9151
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.46.68The system shall treat convergence with a zero reference residual value as requiring zero residual value for convergence.
Specification(s): zero_tolerance_ref
Design: ReferenceResidualProblem
Issue(s): #9151
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.46.70When using ReferenceResidualProblem the system shall throw an error
- if the reference tag is not a residual vector tag.
- if the reference tag does not exist.
- if the reference vector is not provided when using local normalization.
- if the reference vector is provided is not a residual vector tag.
Specification(s): error/wrong_vector_tag_type, error/no_tag, error/no_reference_vector, error/not_residual_tag
Design: ReferenceResidualProblem
Issue(s): #9151
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Reporters
- 15.49.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
- 15.49.4The system shall report a reasonable error when declaring a Reporter value and
- the parameter that contains the name was not found,
- the parameter that contains the name is not of the correct type,
- a Reporter with the same name has already been declared, and
- 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
- 15.49.7The system shall throw an error when producing constant reporter values if
- no values are specified,
- no names are specified,
- or the number of values and names are not equal.
Specification(s): errors/no_values, errors/no_names, errors/mismatch
Design: ConstantReporter
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Restart
- 15.50.4The system shall error when
- a simulation is started with multiple processors but
- 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): 15.50.2
- 15.50.5The system shall error when
- a simulation is started with multiple threads but
- 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): 15.50.4
- 15.50.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
- 15.50.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): 15.50.9
- 15.50.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): 15.50.18
- rdg: Restrictable
- 15.51.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
- 15.51.3The system shall include an interface that provides a method for returning all associated subdomains:
- as a list of names or
- as a list of ids.
Specification(s): ids/blocks, ids/hasBlocks
Design: BlockRestrictable Interface
Issue(s): #2096
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.51.4The system shall include an interface that provides methods for indicating if the supplied subdomain identifier(s) exists on the object:
- if a single subdomain is supplied ant the object is not restricted;
- if a single subdoman is supplied and the object is restricted to a set of subdomains; and
- 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
- 15.51.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:
- the method shall return true if the property subdomains match with the object subdomains and
- 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
- 15.51.6The system shall include an interface that provides a method for returning all associated boundaries:
- as a list of names or
- as a list of ids.
Specification(s): ids/boundary, ids/boundaryIDs
Design: BoundaryRestrictable Interface
Issue(s): #2149
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.51.7The system shall include an interface that provides methods for indicating if the supplied boundary identifier(s) exists on the object:
- if a single boundary is supplied and the object is restricted to a set of boundaries and
- if multiple boundaries are supplied.
Specification(s): has/hasBoundary, has/isBoundarySubset
Design: BoundaryRestrictable Interface
Issue(s): #2149
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.51.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:
- the method shall return true if the property boundaries match with the object boundaries and
- 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
- 15.51.9The system shall error if an object restricted to subdomains is created without valid data
- regarding the problem being solved or
- 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
- 15.51.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
- rdg: Samplers
- 15.52.3The system shall include a random number sampling system that errors
- if the number of rows is altered during sample access,
- if the number of columns is altered during sample access,
- if the number of random number generator seeds is set after object construction,
- if the number of rows is set to zero,
- if the number of columns is set to zero,
- if the number of random number generator seeds is set to zero,
- if the number of entries in the global sample matrix exceeds the maximum allowed,
- if the number of entries in the local sample matrix exceeds the maximum allowed, and
- if the number of entries in the local sample matrix row exceeds the maximum allowed.
Specification(s): errors/setNumberOfRows, errors/setNumberOfCols, errors/setNumberOfRandomSeeds, errors/zero_rows, errors/zero_cols, errors/zero_seeds, errors/getGlobalSamples_max, errors/getLocalSamples_max, errors/getNextLocalRow_max
Design: Sampler
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.52.4The system shall error when the expected size of a sampler is altered and accessed prior to initialization by accessing the
- the global sample matrix;
- the local sample matrix;
- the local sample matrix row;
- the total row count;
- the local row count;
- the first local row index;
- the last local row index;
- the column count.
Specification(s): reinit_errors/getGlobalSamples, reinit_errors/getLocalSamples, reinit_errors/getNextLocalRow, reinit_errors/getNumberOfRows, reinit_errors/getNumberOfLocalRows, reinit_errors/getLocalRowBegin, reinit_errors/getLocalRowEnd, reinit_errors/getNumberOfCols
Design: Sampler
Issue(s): #13906
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Scaling
- 15.54.2The system shall not allow ignoring of particular variable automatic scaling factors if they are grouped with other variables for scaling
Specification(s): fail_with_group
Design: NonlinearSystem
Issue(s): #19573
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Tag
- 15.56.2The system shall throw an error when the variable orders and families for the tagged and the auxiliary output variables do not match.
Specification(s): tag_vector_error
Design: TaggingInterface
Issue(s): #9669
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.56.8An error will be thrown when the different number of array components are used in the aux and coupled varibles.
Specification(s): array_value_size_error
Design: TagVectorArrayVariableValueAux
Issue(s): #21839
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.56.9An error will be thrown when the different FE family are used in the aux and coupled varibles.
Specification(s): array_value_fe_type_error
Design: TagVectorArrayVariableValueAux
Issue(s): #21839
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Time Integrators
- 15.57.3The system shall report an error if an explicit solver fails to converge with
- first-order, forward Euler,
- with mass lumping, and
- with mass lumping and preconditioning.
Specification(s): errors/diverged, errors/diverged_lumped, errors/diverged_lump_prec
Design: ActuallyExplicitEuler
Issue(s): #10837
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.57.23The system shall provide an informative error message when a user uses an invalid solve type for an explicit time integrator.
Specification(s): invalid_solve_type
Design: ExplicitSSPRungeKutta
Issue(s): #18646
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Time Steppers
- 15.58.3The system shall error if trying to take a negative time step.
Specification(s): error_negative
Design: TimeStepper System
Issue(s): #1953
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.58.10The system shall check that a timestep limiting function has been defined when a user specifies the 'force_step_every_function_point' parameter as true.
Specification(s): hit_knot_err1
Design: IterationAdaptiveDT
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.58.11The system shall check that a timestep limiting function has been defined when a user specifies a value for the 'max_function_change' parameter.
Specification(s): hit_knot_err2
Design: IterationAdaptiveDT
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.58.27The system shall check that
- the postprocessors limiting the timesteps do not become negative
Specification(s): check_positive_limiter/pps
Design: IterationAdaptiveDT
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.58.33The system shall provide meaningful error message when:
- time stepper name(s) provided for lower_bound dosen't exist,
- no time steppers are active to compute a timestep,
- the syntax for multiple time steppers is used without an additional nested block for the time stepper
- the corresponding rejectStep() function is called when solve fails
Specification(s): error_message/lower_bound, error_message/active_timesteppers, error_message/input_hierarchy, error_message/rejectStep
Design: TimeStepper SystemAddTimeStepperActionComposeTimeStepperAction
Issue(s): #23740
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.58.34The system shall support the ability to choose time step sizes based on a sequence of increasing numbers:
- beginning at the default start time,
- beginning at an earlier time than the sequence numbers,
- beginning at a time somewhere in-between existing sequence numbers, and
- when reading the sequence from an ExodusII formatted input file.
- that must be sorted in ascending order,
- that must be sorted in strictly ascending order,
- when reading the sequence from a comma-separated input file.
Specification(s): time_sequence/timesequence_no_start_time, time_sequence/timesequence_earlier_start_time, time_sequence/timesequence_later_start_time, time_sequence/exodustimesequence, time_sequence/not_sorted, time_sequence/not_sorted_strictly, time_sequence/csvtimesequence
Design: TimeSequenceStepper
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.58.37The system shall support the ability to run a calculation for the purpose of creating a time sequence restart file suitable for failure:
- when writing the checkpoint file,
- 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
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionExodiff
- 15.58.38The 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
- rdg: Transfers
- 15.59.1The system shall output a warning if a transfer that only matches node ids is used in combinated with a coordinate transformation.
Specification(s): both-transformed
Design: Transfers System
Issue(s): #12293
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.5The system shall report a warning when transferring a variable (for main app) and postprocessor (for subapp) for applications that both have non-identity transformations into the reference space.
Specification(s): both-transformed
Design: Transfers System
Issue(s): #12293
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.12The system shall error if the user does not provide sufficient information to determine the originator and destination of transfer information.
Specification(s): need_multi_app
Design: Transfers System
Issue(s): #19451
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.13The system shall error if the user provides a mix of non-deprecated and deprecated parameters.
Specification(s): mixing_parameters
Design: Transfers System
Issue(s): #19451
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.14The system shall error if the user provides nonsensical direction parameters.
Specification(s): bad_spelling
Design: Transfers System
Issue(s): #19451
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.31The system shall error if
- both nearest positions algorithm and asking for origin points to be contained within an app domain are requested as this is not supported.
Specification(s): errors/from_main_app
Design: MultiAppGeneralFieldUserObjectTransfer
Issue(s): #23587
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.32The system shall be able to detect indetermination in a transfer due to floating point decisions on which node is the nearest, even when using the nearest position option.
Specification(s): overlap_nearest_position
Design: MultiAppGeneralFieldUserObjectTransfer
Issue(s): #23587
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.34The system shall be able to detect indetermination in a transfer due to
- equidistant source nearest nodes in different problems
- the furthest of the nearest nodes desired being equidistant to the target point as the next furthest
Specification(s): overlap/equidistant_problems, overlap/too_many_nearest_points
Design: MultiAppGeneralFieldNearestNodeTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.38The system shall return an error if
- the user attempts transferring to a non-zeroth order elemental variables while restricting the transfer to a boundary
Specification(s): errors/write_elem_high_order
Design: MultiAppGeneralFieldShapeEvaluationTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.41The system shall error if performing a transfer of data evaluating the finite element solution if:
- the evaluation point does not exist
Specification(s): errors/missed_point
Design: MultiAppGeneralFieldShapeEvaluationTransfer
Issue(s): #1836
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.43The system shall return an error if
- a different number of variables is specified for the source and target variables of the transfer.
- the user forgot to input the component to transfer for the source array variable
- the user forgot to input the component to transfer for the target array variable
- the user specified a source variable component to transfer that is larger than the variable size
- the user specified a target variable component to transfer to that is larger than the variable size
Specification(s): errors/wrong_variable_numbers, errors/forgot_source_array_component, errors/forgot_target_array_component, errors/too_big_source_component, errors/too_big_target_component
Design: MultiAppGeneralFieldShapeEvaluationTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.44The system shall be able to detect indetermination in a transfer due to
- overlapping origin child application, causing multiple shape evaluations to be valid
- multiple source problems sending valid values for a given target point
- when using the closest app rather than the first valid value to chose a value
Specification(s): overlap/origin_mesh, overlap/multiple_received_values, overlap/nearest_app
Design: MultiAppGeneralFieldShapeEvaluationTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.52The system shall error if a parent node/element is not contained within any sub application domains/meshes when this condition is explicitly requested by the user.
Specification(s): 3d_1d_err
Design: MultiAppGeneralFieldUserObjectTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.55The system shall emit a warning if
- parameters meant for extrapolation of transfers are passed with no expansion of the bounding box, as this is likely unintended.
Specification(s): warnings/nearest_app
Design: MultiAppGeneralFieldUserObjectTransfer
Issue(s): #23587
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.56The system shall error if
- a nearest-point algorithm is used for sending app-based data from a main app to multi-apps as the data naturally lives near only one of the positions,
- a nearest-point algorithm is requested for use at the same time as nearest-app algorithm.
Specification(s): errors/from_main_app, errors/nearest_position_and_app
Design: MultiAppGeneralFieldUserObjectTransfer
Issue(s): #23587
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.58The system shall return an error if
- more than one variable are specified as the transfer only takes.
Specification(s): errors/too_many_vars
Design: MultiAppGeneralFieldUserObjectTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.59The system shall be able to detect indetermination in a transfer due to
- overlapping origin child application, causing multiple shape evaluations to be valid
Specification(s): overlap/origin_mesh
Design: MultiAppGeneralFieldUserObjectTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.61The system shall error if
- source block restriction is used at the same time as an extrapolation option, without explicitly specifying an extrapolation constant, as both are semantically incompatible so the user must explicitly request it to allow it.
Specification(s): errors/from_block_and_extrapolation
Design: MultiAppGeneralFieldUserObjectTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.64The system shall check execute_on for PP in sub app
Specification(s): test_execute_on
Design: MultiAppConservativeTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.59.1515.59.6315.59.7415.59.8215.59.8315.59.8615.59.8715.59.8815.59.8915.59.9015.59.9215.59.9315.59.16715.59.173
- 15.59.66The system shall check execute_on for PP in parent app
Specification(s): subs_execute_on
Design: MultiAppConservativeTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.59.65
- 15.59.68The system shall check execute_on for vector PP in parent app
Specification(s): nearest_point_execute_on
Design: MultiAppConservativeTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.59.67
- 15.59.76The system shall error if a variable, during a direct copy of auxiliary field variables, does not exist
- in the sub-application when transferring form it and
- in the parent application when transferring for it.
Specification(s): errors/error_from_sub_to_parent, errors/error_to_sub_to_parent
Design: MultiAppCopyTransfer
Issue(s): #13754
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.80The system shall error if a nodal variable is requested to be transfered
- with block-restriction on the origin mesh.
- with block restriction on the target mesh.
Specification(s): errors/error_from_nodal, errors/error_to_nodal
Design: MultiAppCopyTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.81The system shall error if a variable is required to be transferred
- with an invalid source block for the to_multiapp direction.
- with an invalid source block for the from_multiapp direction.
- with an invalid target block for the to_multiapp direction.
- with an invalid target block for the from_multiapp direction.
Specification(s): block_ids/invalid_from_block_to_app, block_ids/invalid_from_block_from_app, block_ids/invalid_to_block_to_app, block_ids/invalid_to_block_from_app
Design: MultiAppCopyTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.84The system shall error when the MultiAppCopyTransfer object is used on non-identical meshes.
Specification(s): different_mesh
Design: MultiAppCopyTransfer
Issue(s): #7757
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.85The system shall error when the MultiAppCopyTransfer object is used on meshes with different variable types.
Specification(s): different_variable_type
Design: MultiAppCopyTransfer
Issue(s): #7757
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.104The system shall error if performing a transfer of data using the finite element solution if:
- the evaluation point does not exist and
- if the execution settings do not match between the parent and sub-applications.
- if the execution settings do not match with any of two sibling sub-applications.
Specification(s): errors/missed_point, errors/mismatch_exec_on, errors/mismatch_exec_on_sibling
Design: MultiAppShapeEvaluationTransfer
Issue(s): #1836
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.59.118The system shall error if the specified source boundary was not found in the mesh for the from_multiapp direction.
Specification(s): invalid_source_boundary_from_app
Design: MultiAppNearestNodeTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.119The system shall error if the specified target boundary was not found in the mesh for the from_multiapp direction.
Specification(s): invalid_target_boundary_from_app
Design: MultiAppNearestNodeTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.120The system shall error if the specified source boundary was not found in the mesh for the to_multiapp direction.
Specification(s): invalid_source_boundary_to_app
Design: MultiAppNearestNodeTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.121The system shall error if the specified target boundary was not found in the mesh for the to_multiapp direction.
Specification(s): invalid_target_boundary_to_app
Design: MultiAppNearestNodeTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.123The system shall report an error if a data transfer is requested for a data variable that is not defined.
Specification(s): test_error
Design: MultiAppPostprocessorInterpolationTransfer
Issue(s): #1737
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.59.122
- 15.59.124The system shall report an error if a variable is specified that is not LINEAR LAGRANGE or CONSTANT MONOMIAL
Specification(s): fetype_error
Design: MultiAppPostprocessorInterpolationTransfer
Issue(s): #1737
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.59.122
- 15.59.125The system shall report an error if parameters for an unsupported direction are provided for the transfer between sub-app scalars and a main app field variablea.
Specification(s): direction_error
Design: MultiAppPostprocessorInterpolationTransfer
Issue(s): #1737
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.128The system shall error during the transfer of scalar variable and postprocessor data if the number of sub-applications differs from the order of the scalar variable if
- the order is too large and
- the order is too small.
Specification(s): error/sub_to_parent_wrong_order, error/sub_to_parent_wrong_positions
Design: MultiAppPostprocessorToAuxScalarTransfer
Issue(s): #2340
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.138The system shall support the ability to transfer reporter data and error if an invalid sub-application number is supplied when transferring data
- to a sub-application,
- from a sub-application.
- from multiple sub-applications.
Specification(s): errors/to_app, errors/from_app, errors/from_multi_app
Design: MultiAppReporterTransferMultiAppCloneReporterTransfer
Issue(s): #16055
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.140If processors do not contain a sub-application and reporter clone transfer is requested, the system shall
- be able to transfer if reporter types are specified and
- error if types are not specified.
Specification(s): clone_type/type_specified, clone_type/error
Design: MultiAppReporterTransferMultiAppCloneReporterTransfer
Issue(s): #16055
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): JSONDiffRunException
- 15.59.143The system shall error if the variable order does not match when transferring scalar variables to an application from sub-applications.
Specification(s): sub_to_parent_wrong_order
Design: MultiAppScalarToAuxScalarTransfer
Issue(s): #9444
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.145The system shall error if the variable order does not match when transferring scalar variables from an application to sub-applications.
Specification(s): parent_to_sub_wrong_order
Design: MultiAppScalarToAuxScalarTransfer
Issue(s): #9444
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.150MultiAppUserObjectTransfer shall generate an error if a parent node/element is not contained within any sub application domains.
Specification(s): 3d_1d_err
Design: MultiAppUserObjectTransfer
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.152The system shall error if an invalid block is specified for the to_multiapp direction.
Specification(s): invalid_block_to_app
Design: MultiAppUserObjectTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.153The system shall error if an invalid block is specified for the from_multiapp direction.
Specification(s): invalid_block_from_app
Design: MultiAppUserObjectTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.154The system shall error if an invalid boundary is specified for the to_multiapp direction.
Specification(s): invalid_boundary_to_app
Design: MultiAppUserObjectTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.155The system shall error if an invalid boundary is specified for the from_multiapp direction.
Specification(s): invalid_boundary_from_app
Design: MultiAppUserObjectTransfer
Issue(s): #22817
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.159The system shall throw an error when attempting to transfer all components of an array field variable sampled groups of points to sub-application post-processor values if
- the source variable is not an array variable,
- an array variable component is specified, and
- the number of sub-applications is not divisible by the number array variable components.
Specification(s): array_sample_errors/not_array, array_sample_errors/component_specified, array_sample_errors/wrong_size
Design: MultiAppVariableValueSampleTransfer
Issue(s): #1737#16099#20816#20913
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.163The systen shall error out if more than one sub-applications are in the same distance from an element.
Specification(s): same_distance_error
Design: MultiAppVariableValueSampleTransfer
Issue(s): #1737#16099#20816#20913
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.59.164The systen shall error out if the MultiAppVariableValueSamplePostprocessorTransfer transfers postprocessor values on sub-applications to a primary variable on the main application.
Specification(s): from_multiapp_set_primary_var_error
Design: MultiAppVariableValueSampleTransfer
Issue(s): #1737#16099#20816#20913
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Userobjects
- 15.61.4The terminator system shall output a custom info, warning, or error message.
Specification(s): terminator_message_1
Design: Terminator
Issue(s): #17000
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.5The terminator system shall check the compatibility of the suplied parameters.
Specification(s): terminator_message_2
Design: Terminator
Issue(s): #17000
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.6The terminator system shall check that if a message is supplied, an appropriate error level for reporting that message is also used.
Specification(s): terminator_message_3
Design: Terminator
Issue(s): #17000
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.8The system shall check that postprocessors providing data for a terminator meant to force a failure in a solve or a time step are executed often enough to be able to update the criterion.
Specification(s): check_execution
Design: Terminator
Issue(s): #24479
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.12The system shall evaluate the quality of all the mesh elements and report
- a warning when the "warning" option is selected,
- an error when the "error" option is selected, or
- a message when the selected metric does not apply to the element type being examined.
Specification(s): quality_checks/failure_warning, quality_checks/failure_error, quality_checks/bypass_warning
Design: ElementQualityChecker
Issue(s): #10377
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunAppRunException
- 15.61.20The system shall produce an error when a boundary preserved marker is used with distributed mesh.
Specification(s): error-distributed
Design: CoupledVarThresholdElementSubdomainModifier
Issue(s): #15795#17100#17239#21383
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.37The system shall error when computing layered averages of a variable if
- the bounding box is set along with the number of layers or
- sample interpolate and
- if neither the bounds or number of layers are set.
Specification(s): errors/bounds_and_num_layers, errors/bounds_and_interp, errors/no_bounds_or_num_layers
Design: LayeredAverage
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.52The system shall not allow both the block and boundary parameter to be specified for layered side integrals.
Specification(s): layered_side_average_error_check
Design: LayeredSideIntegralLayeredSideAverage
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.59The system shall report an error when points are not specified in an input file nor an external file when computing nearest point layered averages
Specification(s): error_missing_point_spec
Design: NearestPointLayeredAverage
Issue(s): #12356
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.61.3415.61.4315.61.4515.61.5315.61.5615.61.5715.61.7115.61.7215.61.7315.61.7415.61.7515.61.8415.61.85
- 15.61.60The system shall report an error when points are specified both in an input file and an external file when computing nearest point layered averages
Specification(s): error_conflicting_point_spec
Design: NearestPointLayeredAverage
Issue(s): #12356
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.61.3415.61.4315.61.4515.61.5315.61.5615.61.5715.61.7115.61.7215.61.7315.61.7415.61.7515.61.8415.61.85
- 15.61.61The system shall report an error when there is not enough coordinates specified in an external file specifing the point for computing nearest point layered averages
Specification(s): error_not_enough_points_in_a_file
Design: NearestPointLayeredAverage
Issue(s): #12356
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 15.61.3415.61.4315.61.4515.61.5315.61.5615.61.5715.61.7115.61.7215.61.7315.61.7415.61.7515.61.8415.61.85
- 15.61.65The system shall error if user-set direction bounds conflict with block-type bound specifications
Specification(s): error_duplicate_block_specs
Design: NearestPointLayeredAverage
Issue(s): #19122
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.66The system shall error if a direction bound is missing
Specification(s): error_missing_bound
Design: NearestPointLayeredAverage
Issue(s): #19122
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.67The system shall error if the maximum bound is lower than the minimum bound
Specification(s): error_invalid_bounds
Design: NearestPointLayeredAverage
Issue(s): #19122
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.76The system shall provide means to detect unresolved dependency in evaluations of user objects and auxiliary kernels
Specification(s): state_detection
Design: FEProblemBase
Issue(s): #22802
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.82The system shall error if a user attempts to use nonlocal residual objects without appropriate coupling specified in a preconditioning object. These residual objects include
- kernels
- boundary conditions
Specification(s): diagonal/kernels, diagonal/bcs
Design: ShapeElementUserObject
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.85The system shall error if the boundary is not specified when computing the average value of a variable on a boundary.
Specification(s): test
Design: SideAverageValue
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.87The system shall error if the lower-d variable is not properly defined on a boundary.
Specification(s): lower_d_test_error
Design: SideAverageValue
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.88The system shall error if the side average value of a variable is requested on a boundary that is the centerline of an axisymmetric model.
Specification(s): rz_centerline_side
Design: SideAverageValue
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.96The system shall prevent nodal user objects from obtaining writable references to elemental variables.
Specification(s): nodal_error
Design: Coupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.97The system shall prevent elemental user objects from obtaining writable references to nodal variables.
Specification(s): elemental_error
Design: Coupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.99The system shall enforce that all variables an object obtains a writable reference to are defined on all of the object's blocks
Specification(s): block_error
Design: Coupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.101The system shall error out if multiple objects with overlapping block restrictions try to access a variable for writing
Specification(s): block2_error
Design: Coupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.102The system shall error out if multiple objects, of which at least one is not block restricted, try to access a variable for writing
Specification(s): block2_error2
Design: Coupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.61.104The system shall make sure that variables written to by boundary restricted user objects are available along the entire boundary.
Specification(s): boundary_error
Design: Coupleable
Issue(s): #22563
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Utils
- 15.62.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
- 15.62.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
- 15.62.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
- 15.62.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
- 15.62.8The system shall throw an error while creating a LibtorchArtificialNeuralNet when encountering
- an unsupported activation function;
- the wrong number of activation functions;
- a non-supported optimizer.
Specification(s): libtorch-nn-errors/wrong-activation, libtorch-nn-errors/wrong-activation-number, libtorch-nn-errors/wrong-optimizer
Design: LibtorchArtificialNeuralNet
Issue(s): #19571
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.62.16The mesh system shall report a reasonable error when using a subdomain name that is reserved for internal use
Specification(s): get_subdomain_id_any
Design: MooseMesh
Issue(s): #17710
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.62.17The 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
- 15.62.18The PerfGraph shall report a reasonable error when
- registering a section without a name
- registering a section without a live message
- requesting the ID of a section that does not exist
- requesting the section info for a section that does not exist
Specification(s): errors/register_no_section, errors/register_no_live_message, errors/section_id_missing, errors/section_info_missing
Design: PerfGraph
Issue(s): #15444
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Variables
- 15.63.3The system shall report a reasonable error when defining a variable with multiple components not as an array variable.
Specification(s): array_false_error
Design: ArrayMooseVariable
Issue(s): #19564
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.63.16The system shall error if a user requests a constant monomial finite element variable type with either a non-monomial family or non-constant order.
Specification(s): bad_order
Design: Variables System
Issue(s): #9836
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.63.25The system shall report an error when users couple constant values and variables together
Specification(s): two_coupled_default_fail_mixed_input
Design: Coupleable
Issue(s): #11920
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.63.26The system shall report an error when requested default vector value is out of range and
- accessed by name or
- accessed by index.
Specification(s): catch_out_of_bound_default_access/coupledValue, catch_out_of_bound_default_access/coupled
Design: Coupleable
Issue(s): #11920
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- rdg: Vectorpostprocessors
- 15.64.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
- 15.64.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
- 15.64.18The system shall support sampling of a field variable at the centroid of every element in the domain
- for elemental FE variables and
- for FV variables,
- for finite volume variables mixed with finite element variables,
- but not for nodal variables.
Specification(s): element_value_sampler/monomial, element_value_sampler/fv, element_value_sampler/mixed_fe_fv, element_value_sampler/lagrange
Design: ElementValueSampler
Issue(s): #11594
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunExceptionCSVDiff
- 15.64.28The 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
- 15.64.35The 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
- 15.64.44The system shall issue an error if material output samples are attempted for elements:
- but the material is restricted to a boundary, or
- 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
- 15.64.47The 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
- 15.64.52The system shall report an error when requested sample points do not fall within the mesh domain.
Specification(s): error
Design: PointValueSampler
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 15.64.60The system shall error if the points are specified in more than one manner for a spatial vector postprocessor.
Specification(s): missing_pts
Design: SpatialUserObjectVectorPostprocessor
Issue(s): #19831
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException