Reconstructed Discontinuous Galerkin Requirements Traceability Matrix

This template follows INL template TEM-214, "IT System Requirements Traceability Matrix."

commentnote

This document serves as an addendum to Framework Requirements Traceability Matrix and captures information for Requirement Traceability Matrix (RTM) specific to the Reconstructed Discontinuous Galerkin module.

Introduction

Minimum System Requirements

In general, the following is required for MOOSE-based development:

A POSIX compliant Unix-like operating system. This includes any modern Linux-based operating system (e.g., Ubuntu, Fedora, Rocky, etc.), or a Macintosh machine running either of the last two MacOS releases.

HardwareInformation
CPU Architecturex86_64, ARM (Apple Silicon)
Memory8 GB (16 GBs for debug compilation)
Disk Space30GB

LibrariesVersion / Information
GCC8.5.0 - 12.2.1
LLVM/Clang10.0.1 - 16.0.6
Intel (ICC/ICX)Not supported at this time
Python3.7 - 3.11
Python Packagespackaging pyaml jinja2

System Purpose

The MOOSE rDG module is a library for the implementation of simulation tools that solve convection-dominated problems using the class of so-called reconstructed discontinuous Galerkin (rDG) methods. The specific rDG method implemented in this module is rDG(P0P1), which is equivalent to the second-order cell-centered finite volume method (FVM). Cell-centered FVMs are regarded as a subset of rDG methods in the case when the baseline polynomial solution in each element is a constant monomial. The FVMs are the most widely used numerical methods in areas such as computational fluid dynamics (CFD) and heat transfer, computational acoustics, and magnetohydrodynamics (MHD).

System Scope

The purpose of this software is to provide capability to MOOSE-based applications to use a second-order, cell-centered finite volume method (FVM). This module provides a systematic solution for implementing all required components in a second-order FVM such as slope reconstruction, slope limiting, numerical flux, and proper boundary conditions. Additionally, this module provides an implementation of these components for the scalar advection equation.

Assumptions and Dependencies

The Reconstructed Discontinuous Galerkin module is developed using MOOSE and can itself be based on various MOOSE modules, as such the RTM for the Reconstructed Discontinuous Galerkin module is dependent upon the files listed at the beginning of this document.

Pre-test Instructions/Environment/Setup

Ideally all testing should be performed on a clean test machine following one of the supported configurations setup by the test system engineer. Testing may be performed on local workstations and cluster systems containing supported operating systems.

The repository should be clean prior to building and testing. When using "git" this can be done by doing a force clean in the main repository and each one of the submodules:


git clean -xfd
git submodule foreach 'git clean -xfd'

All tests must pass in accordance with the type of test being performed. This list can be found in the Software Test Plan.

Changelog Issue Revisions

Errors in changelog references can sometimes occur as a result of typos or conversion errors. If any need to be noted by the development team, they will be noted here.

The changelog for all code residing in the MOOSE repository is located in the MOOSE RTM.

System Requirements Traceability

Functional Requirements

  • rdg: Actions
  • 15.2.1The system shall allow the shortcut syntax specifying an AuxKernel
    1. nested under an AuxVariable, and
    2. it shall produce the same output as with the standard syntax.

    Specification(s): syntax/nested, syntax/standard

    Design: AddAuxKernelAction

    Issue(s): #20753

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): invalid_order_high

    Design: AuxVariables System

    Issue(s): #960#2294#4668

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.2.3The system shall support calculations with an auxiliary scalar variable represented with a 21st order monomial function.

    Specification(s): high_order_scalar

    Design: AuxVariables System

    Issue(s): #960#2294#4668

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.2.4The system shall be capable of reporting Action object dependencies.

    Specification(s): test_show_actions_dependency

    Design: MOOSE Action System

    Issue(s): #11971

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.2.5The system shall be capable of reporting Action object task information.

    Specification(s): test_show_actions_tasks

    Design: MOOSE Action System

    Issue(s): #11971

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.2.6The system shall support the detailed on-screen output of all of the Reporters that were declared and requested, including type, producer, context, and consumers.

    Specification(s): test

    Design: Reporter System

    Issue(s): #17605

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.2.7The system shall be able to retrieve other Action objects from within another Action object.

    Specification(s): get_actions

    Design: MOOSE Action System

    Issue(s): #7905

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.2.8The Action system shall allow Action objects to create other Action objects.

    Specification(s): test_meta_action

    Design: MOOSE Action System

    Issue(s): #1478

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.2.9The Action system shall allow the creation of Action objects with multiple tasks.

    Specification(s): circle_quads

    Design: MOOSE Action System

    Issue(s): #10619

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Batch Material
  • 15.5.1The batch material system shall provide the capability for gathering and serializing variable and material property values for batch property computation.

    Specification(s): test

    Design: BatchMaterial

    Issue(s): #21225

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Batch Property Derivative
  • 15.6.1The batch property derivative shall be able to gather, serialize material property values and receives material property derivatives for batch property computation.

    Specification(s): test

    Design: BatchPropertyDerivative

    Issue(s): #26920

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Bcs
  • 15.7.1The system shall support Neumann type boundary conditions for a 1D problem.

    Specification(s): test

    Design: NeumannBC

    Issue(s): #1654

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.2The system shall support Neumann type boundary conditions for a 1D problem using an imported mesh.

    Specification(s): from_cubit

    Design: NeumannBC

    Issue(s): #1654

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • The system shall support Neumann type boundary conditions using automatic differentiation for a 1D problem
    1. using a generated mesh.
    2. and shall be able to produce the exact Jacobian
    3. using an imported mesh.

    Specification(s): ad/test, ad/jac, ad/from_cubit

    Design: ADNeumannBC

    Issue(s): #1654

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • 15.7.4The system shall support setting AD Dirichlet type boundary conditions, supplied as a function, directly to the solution vector prior to the solve.

    Specification(s): bc_function_nodal_test

    Design: ADFunctionDirichletBC

    Issue(s): #13261

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.5The system shall support setting AD Dirichlet type boundary conditions directly to the solution vector prior to the solve.

    Specification(s): bc_preset_nodal_test

    Design: ADDirichletBC

    Issue(s): #13261

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.6The system shall support setting AD Dirichlet type boundary conditions, supplied as a function, directly to the solution vector prior to the solve and have perfect Jacobians.

    Specification(s): bc_function_nodal_test-jac

    Design: ADFunctionDirichletBC

    Issue(s): #13261

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.7The system shall support setting AD Dirichlet type boundary conditions directly to the solution vector prior to the solve and have perfect Jacobians.

    Specification(s): bc_preset_nodal_test-jac

    Design: ADDirichletBC

    Issue(s): #13261

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.8We shall be able to produce the expected result using ADKernel, ADNodalBC, and ADIntegratedBC

    Specification(s): test

    Design: ADFunctionDirichletBCADDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.9We shall be able to produce the exact Jacobian using ADKernel, ADNodalBC, and ADIntegratedBC with a first order variable

    Specification(s): jac

    Design: ADFunctionDirichletBCADDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.10We shall be able to produce the exact Jacobian using ADKernel, ADNodalBC, and ADIntegratedBC with a second order variable

    Specification(s): 2nd_order_jac

    Design: ADFunctionDirichletBCADDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.11We shall be able to produce the expected result using ADVectorKernel, ADVectorNodalBC, and ADVectorIntegratedBC

    Specification(s): vector_test

    Design: ADVectorFunctionDirichletBCADVectorDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.12We shall be able to produce the exact Jacobian using ADVectorKernel, ADVectorNodalBC, and ADVectorIntegratedBC with a first order variable

    Specification(s): vector_jac

    Design: ADVectorFunctionDirichletBCADVectorDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.13We shall be able to produce the exact Jacobian using ADVectorKernel, ADVectorNodalBC, and ADVectorIntegratedBC with a second order variable

    Specification(s): 2nd_order_vector_jac

    Design: ADVectorFunctionDirichletBCADVectorDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.14The system shall be able to couple a lower-dimensional variable into a boundary condition for a higher-dimensional variable.

    Specification(s): couple_lower

    Design: Coupleable

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.15The system shall be able to compute the residual and Jacobian together when boundary conditions couple in variables defined on lower-dimensional blocks.

    Specification(s): resid_and_jac_together

    Design: Coupleable

    Issue(s): #19444

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • The system shall support Dirichlet type boundary conditions defined by a function
    1. using automatic differentiation.
    2. using automatic differentiation and shall be able to produce the exact Jacobian.

    Specification(s): ad/test, ad/test-jac

    Design: ADFunctionDirichletBC

    Issue(s): #13261

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • The system shall support Neumann type boundary conditions defined by a function
    1. using automatic differentiation.
    2. using automatic differentiation and shall be able to produce the exact Jacobian.

    Specification(s): ad/test, ad/test-jac

    Design: ADFunctionNeumannBC

    Issue(s): #12903

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • 15.7.18The system shall support matching variable values on a boundary using automatic differentiation

    Specification(s): test

    Design: ADMatchedValueBC

    Issue(s): #18212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.19The system shall produce the exact Jacobian for BC matching variable values on a boundary using automatic differentiation

    Specification(s): jacobian

    Design: ADMatchedValueBC

    Issue(s): #18212

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.7.20The system shall be able to impose a nodal boundary condition constraint that involves nonlocal degrees of freedom and
    1. get the expected result in which the average value of the solution is zero, and
    2. exhibit a perfect Jacobian.

    Specification(s): test/residual, test/jacobian

    Design: BCs System

    Issue(s): #23940

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • The system shall support the application of Dirichlet type boundary conditions using the penalty method using the AD system
    1. with a constant value on the boundary.
    2. with a constant value on the boundary and shall be able to produce the exact Jacobian.
    3. with a value on the boundary set by a function.
    4. with a value on the boundary set by a function and shall be able to produce the exact Jacobian.

    Specification(s): ad/penalty_dirichlet_bc_test, ad/penalty_dirichlet_bc_test-jac, ad/function_penalty_dirichlet_bc_test, ad/function_penalty_dirichlet_bc_test-jac

    Design: ADPenaltyDirichletBCADFunctionPenaltyDirichletBC

    Issue(s): #12903

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • 15.7.22The system shall support Neumann type boundary conditions defined by a function
    1. for vector variables with automatic differentiation and
    2. be able to produce the exact Jacobian.

    Specification(s): vector/test, vector/test-jac

    Design: ADVectorFunctionNeumannBC

    Issue(s): #22327

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • 15.7.23The system shall provide array vacuum boundary condition.

    Specification(s): test

    Design: ArrayVacuumBC

    Issue(s): #6881

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.24The system shall support setting Dirichlet type boundary conditions, supplied as a function, directly to the solution vector prior to the solve.

    Specification(s): bc_function_nodal_test

    Design: FunctionDirichletBC

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.25The system shall support setting Dirichlet type boundary conditions directly to the solution vector prior to the solve.

    Specification(s): bc_preset_nodal_test

    Design: DirichletBC

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.26The system shall support the creation of BoundaryCondition objects that support conditional activation.

    Specification(s): test

    Design: BCs System

    Issue(s): #1771

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.27The system shall support the creation of BoundaryCondition objects that couple to nonlinear variables.

    Specification(s): test

    Design: BCs System

    Issue(s): #656

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.28The system shall support coupled Neumann type boundary conditions.

    Specification(s): test

    Design: CoupledVarNeumannBC

    Issue(s): #13502#26413

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.29The system shall enable scaling of the Neumann type boundary conditions.

    Specification(s): on_off

    Design: CoupledVarNeumannBC

    Issue(s): #15421

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.30When coupling nonlinear variables into a Neumann type boundary condition, the system shall
    1. generate accurate results
    2. generate a perfect Jacobian
    3. generate accurate results using automatic differentiation
    4. generate a perfect Jacobian using automatic differentiation

    Specification(s): nonlinear/exo, nonlinear/jac, nonlinear/ADexo, nonlinear/ADjac

    Design: CoupledVarNeumannBC

    Issue(s): #13502#26413

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

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

    Specification(s): check

    Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

    Issue(s): #15501

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.7.32The system shall make sure that boundaries are actually distributed.

    Specification(s): check_one_step

    Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

    Issue(s): #15501

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.7.33The system shall support periodic boundary conditions in a parallel generated 2D mesh.

    Specification(s): 2d

    Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

    Issue(s): #15501

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.34The system shall support periodic boundary conditions in a parallel generated 3D mesh.

    Specification(s): 3d

    Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

    Issue(s): #15501

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.35The system shall support periodic boundary conditions in a parallel generated 1D mesh.

    Specification(s): 1d

    Design: AddPeriodicBCActionDistributedRectilinearMeshGenerator

    Issue(s): #15501

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.36The system shall support Dirichlet type boundary conditions defined by a function.

    Specification(s): test

    Design: FunctionDirichletBC

    Issue(s): #1214

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.37The system shall support applying a function of space-time as a Neumann boundary condition.

    Specification(s): test

    Design: FunctionNeumannBC

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.38The system shall support Dirichlet type boundary conditions defined by a functor.

    Specification(s): test

    Design: FunctorDirichletBC

    Issue(s): #25758

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.39The system shall support Neumann boundary conditions defined by a functor.

    Specification(s): test

    Design: FunctorNeumannBC

    Issue(s): #25132

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.40The system shall support applying a material property as a Neumann boundary condition.

    Specification(s): test

    Design: MatNeumannBC

    Issue(s): #17791

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.41The system shall support applying a material property as a Neumann boundary condition using AD.

    Specification(s): ad_test

    Design: MatNeumannBC

    Issue(s): #17791

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.42The system shall support matching variable values on a boundary.

    Specification(s): test

    Design: BCs System

    Issue(s): #656

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.43The system shall support the ability to create convective flux boundary conditions.

    Specification(s): convective_flux_bc_test

    Design: BCs System

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.44The system shall support a vacuum boundary condition for neutron diffusion on the boundary.

    Specification(s): vacuumbc_test

    Design: BCs System

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.45The system shall support Neumann type boundary conditions where the specified value is defined as the value of a vector, , in the direction of the boundary outward facing normal, (i.e., ).

    Specification(s): vector_neumann_test

    Design: BCs System

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.46The system shall support the 'no boundary condition' type boundary condition (Griffiths, 1997).

    Specification(s): weak_gradient_bc_test

    Design: BCs System

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.47The system shall be capable of computing the nodal normals for triangle elements.

    Specification(s): circle_tris

    Design: NodalNormals System

    Issue(s): #1871

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.48The system shall be capable of computing the nodal normals for quadrilateral elements.

    Specification(s): circle_quads

    Design: NodalNormals System

    Issue(s): #1871

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.49The system shall be capable of computing the nodal normals for first order hexahedron elements.

    Specification(s): cylinder_hexes

    Design: NodalNormals System

    Issue(s): #1871

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.50The system shall be capable of computing the nodal normals for second order hexahedron elements.

    Specification(s): cylinder_hexes_2nd

    Design: NodalNormals System

    Issue(s): #1871

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.51The system shall be capable of computing the first order nodal normals for second order hexahedron elements.

    Specification(s): cylinder_hexes_1st_2nd

    Design: NodalNormals System

    Issue(s): #1871

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.52The system shall be capable of computing the nodal normals for quadrilateral elements on a square domain.

    Specification(s): small_sqaure

    Design: NodalNormals System

    Issue(s): #1871

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.53The system shall support the application of Dirichlet type boundary conditions using the penalty method.

    Specification(s): test_penalty_dirichlet_bc

    Design: PenaltyDirichletBC

    Issue(s): #5268

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.54The system shall support the application of Dirichlet type boundary conditions, defined by a function, using the penalty method.

    Specification(s): test_function_penalty_dirichlet_bc

    Design: PenaltyDirichletBC

    Issue(s): #5268

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.55The system shall support periodic boundary conditions with transforms defined as functions.

    Specification(s): all_periodic_trans_test

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.56The system shall support periodic boundary conditions with transforms that are computed automatically in the 'x' and 'y' directions.

    Specification(s): auto_wrap_2d_test

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.57The system shall support periodic boundary conditions with transforms that are computed automatically in the 'x' and 'y' directions using a non-generated mesh.

    Specification(s): auto_wrap_2d_test_non_generated

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): auto_wrap_2d_test_error_check

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 15.7.56

  • 15.7.59The system shall support periodic boundary conditions with transforms that are computed automatically in the 'x', 'y', and 'z' directions.

    Specification(s): auto_wrap_3d_test

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.60The system shall support periodic boundary conditions on orthogonal boundaries with transforms defined as functions.

    Specification(s): orthogonal_pbc_on_square_test

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.61The system shall support periodic boundary conditions on parallel boundaries with transforms defined as functions.

    Specification(s): parallel_pbc_using_trans_test

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.62The system shall support periodic boundary conditions with mesh adaptivity.

    Specification(s): testlevel1

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.63The system shall support periodic boundary conditions with transforms prescribed as a translation.

    Specification(s): testperiodic

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.64The system shall support periodic boundary conditions on vector variables with transforms prescribed as a translation.

    Specification(s): testperiodic_vector

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.65The system shall support periodic boundary conditions with displacements.

    Specification(s): testperiodic_dp

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.66The system shall support periodic boundary conditions on a trapezoid domain with transforms prescribed as functions.

    Specification(s): testtrapezoid

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.67The system shall support calls to periodic distance and bounds methods on the mesh when periodic boundary conditions are not used.

    Specification(s): trapezoid_non_periodic

    Design: MooseMesh

    Issue(s): #11939

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.68The system shall support periodic boundary conditions on a wedge domain with transforms prescribed as functions.

    Specification(s): testwedge

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.69The system shall support periodic boundary conditions for a single variable on a wedge domain with transforms prescribed as functions.

    Specification(s): testwedgesys

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.70The system shall support periodic boundary conditions for input meshes that have repeated element ids.

    Specification(s): auto_dir_repeated_id

    Design: Periodic System

    Issue(s): #935#1530

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.71When using periodic boundary detection, the system shall not attempt to add periodic boundary conditions to scalar variables.

    Specification(s): no_add_scalar

    Design: AddPeriodicBCAction

    Issue(s): #11417

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.72The system shall support the application of a Neumann boundary condition computed via Postprocessor object.

    Specification(s): test

    Design: PostprocessorNeumannBC

    Issue(s): #5680

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.73The system shall be able to compute the residual and the Jacobian of each nodal BC and integrated BC together.

    Specification(s): resid_jac_together

    Design: NonlinearSystem

    Issue(s): #23487

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.74The system shall properly compute second derivatives within BoundaryCondition objects.

    Specification(s): test_lap_bc

    Design: BCs System

    Issue(s): #6327

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.75The system shall support creating sidesets from nodesets for hexahedron elements to use with Boundary Condition objects.

    Specification(s): test_hex

    Design: Mesh SystemBCs System

    Issue(s): #687

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.76The system shall support creating sidesets from nodesets for tetrahedron elements to use with Boundary Condition objects.

    Specification(s): test_tet

    Design: Mesh SystemBCs System

    Issue(s): #687

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.77The system shall include the ability to apply a Neumann boundary condition according to a sin function.

    Specification(s): sinneumann_test

    Design: SinNeumannBC

    Issue(s): 0d86cfce0b83e2efaa0647d8e1f1ca5e755872fc

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.78The system shall include the ability to apply a Dirichlet boundary condition according to a sin function.

    Specification(s): sindirichlet_test

    Design: SinDirichletBC

    Issue(s): 0d86cfce0b83e2efaa0647d8e1f1ca5e755872fc

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.79The system shall be able to apply penalty Dirichlet boundary conditions to all three components of a vector variable in a three-dimensional diffusion simulation.

    Specification(s): test

    Design: VectorPenaltyDirichletBC

    Issue(s): #27772

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.7.80BoundaryCondition objects shall support retrieval of VectorPostprocessor data.

    Specification(s): test

    Design: BCs System

    Issue(s): #9285

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Bounds
  • 15.8.1The system shall include the ability to compute a nodal field variable with a constant upper and lower bounds.

    Specification(s): constant_bounds

    Design: ConstantBounds

    Issue(s): #951#14946

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.8.2The system shall include the ability to compute a field variable with a lower bound given by variable's old value.

    Specification(s): old_value_bounds

    Design: ConstantBounds

    Issue(s): #951#14946

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.8.3The system shall include the ability to compute a constant monomial field variable with constant upper and lower bounds.

    Specification(s): constant_bounds_elem

    Design: ConstantBounds

    Issue(s): #951#14946

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.8.4The system shall be able to impose constant upper and lower bounds on a finite volume variable.

    Specification(s): constant_bounds_fv

    Design: ConstantBounds

    Issue(s): #951#14946

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

    Design: ConstantBounds

    Issue(s): #14946

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionRunApp

  • rdg: Controls
  • 15.10.1The Control system shall include a means to control input parameters added by MOOSE action systems.

    Specification(s): test

    Design: Controls System

    Issue(s): #22068

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.2The Control system shall allow a boolean parameter to be controlled with a function.

    Specification(s): single

    Design: Controls SystemBoolFunctionControl

    Issue(s): #15402

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.3The Control system shall be capable of activating or deactivating MOOSE objects using a conditional function.

    Specification(s): test

    Design: Controls SystemConditionalFunctionEnableControl

    Issue(s): #5676#13295

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.4The MOOSE control system shall allow parameters from differing objects, with differing names to be associated and changed together.

    Specification(s): direct

    Design: Controls System

    Issue(s): #9087#5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.5The MOOSE control system shall allow parameters from objects to be assigned aliases for the purpose of changing the value.

    Specification(s): alias

    Design: Controls System

    Issue(s): #9087#5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.6The system shall allow controlling piecewise functions and material properties.

    Specification(s): controlled_piecewise

    Design: PiecewiseLinearPiecewiseLinearInterpolationMaterial

    Issue(s): #15321

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.7The Control system shall support explicitly defined dependencies.

    Specification(s): test

    Design: Controls System

    Issue(s): #9483#5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): non_controllable_error

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.10.9The Control system shall error if multiple controllable parameters exists, but only a single parameter is expected to be controlled.

    Specification(s): multiple_params_found_warning

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): no_param_found

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): tid_warehouse_error

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): disable_executioner

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): non_existing_dependency

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.10.14The system shall be able to read a neural network from a torchscript file and use it to control a transient process.

    Specification(s): run-torch-script

    Design: LibtorchNeuralNetControl

    Issue(s): #19571

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.15The system shall be able to read a neural network from a parameter file and use it to control a transient process.

    Specification(s): run-with-torch-parameters

    Design: LibtorchNeuralNetControl

    Issue(s): #19571

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.10.16The system shall be able to run with a libtorch controller without having a neural net initialized in it.

    Specification(s): run-without-nn

    Design: LibtorchNeuralNetControl

    Issue(s): #19571

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): invalid-torchscript-error

    Design: LibtorchNeuralNetControl

    Issue(s): #19571

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.10.18The Control system shall support the modification of a single parameter using the objects base class name, object name, and parameter name.

    Specification(s): base_object_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.19The Control system shall support the modification of multiple parameters using the objects base class and the parameter name.

    Specification(s): base_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.20The Control system shall include a means to output information regarding the controlled parameters.

    Specification(s): test

    Design: Controls SystemControlOutput

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.21The Control system shall include a means to output information regarding the controlled parameters, including only showing information regarding a parameter if it has changed since the last output.

    Specification(s): clear

    Design: Controls SystemControlOutput

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.22The system shall include a command line flag for displaying controllable parameter information.

    Specification(s): cli_args

    Design: Controls SystemControlOutput

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.23The Control system shall include a means to output information regarding the objects with controllable parameters.

    Specification(s): active

    Design: Controls SystemControlOutput

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.24The Control system shall be able to control an input parameter to make a postprocessor match a target value,
    1. using the principle of Proportional Integral Derivative control,
    2. allowing the Proportional Integral Derivative control to have limits for its maximum and minimum output,
    3. allowing the Proportional Integral Derivative control to have limits for its absolute maximum rate of change of control variable,
    4. using a input postprocessor in lieu of an input parameter,
    5. with integral windup control, resetting the integral term if the error crosses zero,
    6. keeping the PID process within a single timestep,
    7. and resetting the PID process correctly if the solver fails during a Picard/coupling iteration.

    Specification(s): pid/basic, pid/min_max_limits, pid/abs_max_rate_change, pid/basic_postprocessor, pid/windup, pid/picard, pid/resistance_to_solver_fails

    Design: Controls SystemPIDTransientControl

    Issue(s): #17271

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.25The Control system shall allow a scalar parameter to be controlled with a function.

    Specification(s): single

    Design: Controls SystemRealFunctionControl

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.26The Control system shall allow multiple scalar parameters to be controlled with a function.

    Specification(s): multiple

    Design: Controls SystemRealFunctionControl

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): error

    Design: Controls System

    Issue(s): #12576

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.10.28The Control system shall allow multiple parameters to be changed by the parameter name alone using input syntax format.

    Specification(s): param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.29The Control system shall allow multiple parameters to be changed given the object and parameter names using input syntax format.

    Specification(s): object_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.30The Control system shall allow for a single parameter to be changes given the input syntax, object name, and parameter name.

    Specification(s): system_object_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.31The Control system shall allow for multiple parameters to be changed given input syntax and a parameter name.

    Specification(s): system_asterisk_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.32The Control system shall allow multiple parameters to be changed by the parameter name alone using a tag.

    Specification(s): param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.33The Control system shall allow multiple parameters to be changed given a tag and parameter names, given a tag assigned across input blocks.

    Specification(s): object_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.34The Control system shall allow for a single parameter to be changes given a tag and parameter name, given a tag assigned to a single object.

    Specification(s): system_object_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.35The Control system shall allow for multiple parameters to be changed given a tag and a parameter name, given a tag assigned within a single input block on multiple objects.

    Specification(s): system_asterisk_param

    Design: Controls System

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.36The Control system shall be capable of activating or deactivating AuxKernel objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.37The Control system shall be capable of activating or deactivating AuxScalarKernel objects with time, given identical start end times.

    Specification(s): multi_same_times

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.38The Control system shall be capable of activating or deactivating AuxScalarKernel objects with time, given differing start end times.

    Specification(s): multi_different_times

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.39The system shall be capable of activating and/or deactivating boundary contributions to the residual with time
    1. for contributions from finite element nodes,
    2. for contributions integrated over a finite element side,
    3. for contributions from automatic differentiation, and
    4. perform the activation/deactivation with a single control.

    Specification(s): tests/dirichlet, tests/integrated, tests/ad, tests/enable_disable

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.40The Control system shall be capable of activating or deactivating Constraint objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.41The system shall support disabling an object using an input parameter.

    Specification(s): enable_false

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.42The system shall support enabling an object using an input parameter.

    Specification(s): enable_true

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.43The system shall be capable of activating or deactivating Damper objects with time via the Control system.

    Specification(s): control

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.44The Control system shall be capable of activating or deactivating DGKernel objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.45The Control system shall be capable of activating or deactivating DiracKernel objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): steady_error

    Design: TimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): start_end_size_mismatch

    Design: TimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): time_disable_size_mismatch

    Design: TimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): enable_disable_not_set

    Design: TimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): start_greater_than_end_error

    Design: TimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.10.51The system shall be capable of activating or deactivating volume residual contributions with time:
    1. for non-automatic differentiation and
    2. automatic differentiation terms.

    Specification(s): test/non_ad, test/ad

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.52The system shall be capable of activating or deactivating materials in the input file depending on time.

    Specification(s): test

    Design: TimePeriod

    Issue(s): #5676#18994

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.53The Control system shall be capable of activating or deactivating MultiApp objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.54The Control system shall be capable of activating or deactivating NodalKernel objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.55The Control system shall be capable of activating or deactivating ScalarKernel objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.56The Control system shall be capable of activating or deactivating Transfer objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.10.57The Control system shall be capable of activating or deactivating UserObject objects with time.

    Specification(s): test

    Design: Controls SystemTimePeriod

    Issue(s): #5676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.58The system shall be able to enable/disable an object based on whether the simulation time hits the times specified in a times object.

    Specification(s): times_to_hit

    Design: TimesEnableControl

    Issue(s): #28141

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.59The system shall be able to enable/disable an object based on whether the simulation time passes the times specified in a times object.

    Specification(s): times_to_pass

    Design: TimesEnableControl

    Issue(s): #28141

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.10.58

  • 15.10.60The system shall support controlling a parameter via a REST API with a parameter type of a
    1. boolean
    2. double precision number
    3. integer
    4. string
    5. vector of double precision numbers
    6. vector of integers
    7. vector of strings

    Specification(s): control/bool, control/real, control/int, control/string, control/vec_real, control/vec_int, control/vec_string

    Design: Controls SystemWebServerControl

    Issue(s): #23359#27909

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.10.61The system shall support retreiving a postprocessor value via a REST API

    Specification(s): get_postprocessor

    Design: Controls SystemWebServerControl

    Issue(s): #23359#27909

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.10.62The system shall support connecting to a REST API via a port

    Specification(s): connect_port

    Design: Controls SystemWebServerControl

    Issue(s): #23359#27909

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.10.63The system shall support changing controllable parameters via a REST API in a manner that is parallel consistent

    Specification(s): parallel_consistent

    Design: Controls SystemWebServerControl

    Issue(s): #23359#27909

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

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

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

    Design: Controls SystemWebServerControl

    Issue(s): #23359#27909

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: Controls SystemWebServerControl

    Issue(s): #23359#27909

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • rdg: Coord Type
  • 15.11.1The system shall support cylindrical coordinates with the radial direction in the 'x' direction.

    Specification(s): rz-y-rotation

    Design: Problem system overview

    Issue(s): #4531#6629

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.11.2The system shall support cylindrical coordinates with the radial direction in the 'y' direction.

    Specification(s): rz-x-rotation

    Design: Problem system overview

    Issue(s): #4531#6629

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.11.3The system shall support cylindrical coordinates with the radial direction in the 'x' direction with discontinous Galkerin and integrated boundary conditions.

    Specification(s): rz-integrated-y-rotation

    Design: Problem system overview

    Issue(s): #4531#6629

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.11.4The system shall support cylindrical coordinates with the radial direction in the 'y' direction with discontinous Galkerin and integrated boundary conditions.

    Specification(s): rz-integrated-x-rotation

    Design: Problem system overview

    Issue(s): #4531#6629

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.11.5The system shall support cylindrical coordinates with a general axis.

    Specification(s): rz_general

    Design: Mesh System

    Issue(s): #24339

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: DGKernel Objects
  • 15.13.1The system shall support solving 1D advection using the discontinous Galerkin method.

    Specification(s): test

    Design: ConservativeAdvectionDGConvection

    Issue(s): #869

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.2The system shall support solving 2D diffusion using the discontinuous Galerkin method.

    Specification(s): test

    Design: DGFunctionDiffusionDirichletBCDGDiffusion

    Issue(s): #869

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.3The system shall support solving 2D diffusion using the discontinuous Galerkin method with p-refinement.

    Specification(s): p_refinement_test

    Design: DGFunctionDiffusionDirichletBCDGDiffusion

    Issue(s): #869#24141

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.4The system shall support solving 2D diffusion using the discontinuous Galerkin method with constant monomial shape functions.

    Specification(s): constMonomial

    Design: DGFunctionDiffusionDirichletBCDGDiffusion

    Issue(s): #21314

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.5DGKernels shall coexist with stateful material properties

    Specification(s): stateful_props

    Design: DGKernels System

    Issue(s): #11766

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.13.6The system shall not perform memory allocation automatic scaling when computing values using discontinuous finite element methods.

    Specification(s): no_mallocs_during_scaling

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.13.7When objects that need one layer of coupling (like DGKernels) are added via action, we shall ensure that we have added a proper relationship manager and thus incur no mallocs during calls to MatSetValues. We will not apply algebraic ghosting nor reinitialize system vectors in serial, but we will reinitialize the matrix sparsity

    Specification(s): proper_ghosting_with_action_serial

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.8When objects that need one layer of coupling (like DGKernels) are added via action, we shall ensure that we have added a proper relationship manager and thus incur no mallocs during calls to MatSetValues. We will also apply algebraic ghosting in parallel which will require reinitializing the system; the sparsity pattern will also have to be reinitialized

    Specification(s): proper_ghosting_with_action_parallel

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.9If a RelationshipManager with sufficient coverage has already been added through a MooseObjectAction, then the CouplingFunctorCheck action shall not add any relationship managers, avoiding reinitialization of system vectors and the system matrix

    Specification(s): no_additional_rms

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.10This test shall have one more rm than its replicated counter part because of the geometric-only GhostPointNeighbors rm, also demonstrating no mallocs. Sparsity will be reinitialized but not vectors

    Specification(s): proper_ghosting_with_action_serial_distributed

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.11This test shall have one more rm than its replicated counter part because of the geometric-only GhostPointNeighbors rm, also demonstrating no mallocs. Sparsity and vectors will both be reinitialized

    Specification(s): proper_ghosting_with_action_parallel_distributed

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.12This test shall have one more rm than its replicated counter part because of the geometric-only GhostPointNeighbors rm, also demonstrating no addition of rms by the CouplingFunctorCheckAction

    Specification(s): no_additional_rms_distributed

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.13The system shall support solving 3D diffusion using the discontinuous Galerkin method.

    Specification(s): test

    Design: DGFunctionDiffusionDirichletBCDGDiffusion

    Issue(s): #869

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.14The system shall support solving 3D diffusion using the discontinuous Galerkin method with p-refinement.

    Specification(s): p_refinement_test

    Design: DGFunctionDiffusionDirichletBCDGDiffusion

    Issue(s): #869#24141

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.15We shall be able to use constant monomials with AD

    Specification(s): exo

    Design: ADDGKernel

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.13.16MOOSE should support AD in DG Kernels

    Specification(s): test

    Design: ADDGKernel

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.17Adaptivity shall work with dg kernels as long as stateful properties are not used.

    Specification(s): dg_adaptivity

    Design: DGKernels System

    Issue(s): #10977

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): error_stateful_dg_adaptivity

    Design: DGKernels System

    Issue(s): #10977

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.13.19The system shall be able to solve the advection diffusion equation using the discontinuous Galerkin method.

    Specification(s): resid

    Design: DGKernels System

    Issue(s): #8408

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.20The system shall compute the correct Jacobian for the advection diffusion equation using the discontinuous Galerkin method.

    Specification(s): jac

    Design: DGKernels System

    Issue(s): #8408

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.13.21The DGKernel system shall support restriction to subdomains, in 1D.

    Specification(s): 1D_test

    Design: DGKernels System

    Issue(s): #6042

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.22The DGKernel system shall support restriction to subdomains, in 2D.

    Specification(s): 2D_test

    Design: DGKernels System

    Issue(s): #6042

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.23The DGKernel system shall operate with displaced meshes.

    Specification(s): test

    Design: DGKernels System

    Issue(s): #3536

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.24The example side-discontinuous kernels shall have correct analytic Jacobians.

    Specification(s): jacobian

    Design: HFEMTestJumpHFEMTrialJump

    Issue(s): #20191

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.13.25The DGCoupledDiffusion object shall compute the correct Jacobian.

    Specification(s): jacobian_test

    Design: DGKernels System

    Issue(s): #629

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 15.13.26The system shall be ablve to solve an advection-diffusion problem discretized with discontinuous Galerkin, using some hand-coded Jacobians and automatic differentiation Jacobians.

    Specification(s): test

    Design: ADConservativeAdvectionADDGAdvectionADConservativeAdvectionBCMatDiffusionDGDiffusionDGFunctionDiffusionDirichletBC

    Issue(s): #24055

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.13.27The system shall be able to use variables when initializing stateful material properties on neighbor materials used for the discontinuous Galerkin method.

    Specification(s): run

    Design: Materials System

    Issue(s): #19735

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Executioners
  • 15.15.1The Executioner system shall support the ability to create custom objects with custom execution callbacks.

    Specification(s): test

    Design: Executioner System

    Issue(s): #1491

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.2The Executioner system shall support the creation of custom objects with arbitrary execution flags.

    Specification(s): test

    Design: Executioner System

    Issue(s): #7489

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.15.3The system shall be able to detect steady-states using the auxiliary system solution.

    Specification(s): aux-ss

    Design: Transient

    Issue(s): #19955#23840

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.4The system shall be able to solve an eigenvalue problem using something other than the L2 norm of Bx for normalization and a native eigenvalue solver.

    Specification(s): testb

    Design: EigenProblem

    Issue(s): #20095

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.15.5The system shall be able to solve an eigenvalue problem using the L2 norm of Bx and the sign of its first nonzero entry for normalization with a SLEPc eigenvalue solver.

    Specification(s): test11

    Design: EigenProblem

    Issue(s): #20095

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.15.6The system shall be able to solve an eigenvalue problem using the sign of the first nonzero entry of Bx combined with something other than the L2 norm of Bx for normalization with a SLEPc eigenvalue solver.

    Specification(s): test7

    Design: EigenProblem

    Issue(s): #20095

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.15.5

  • 15.15.7The system shall be able to solve an eigenvalue problem using something other than the L2 norm of Bx for normalization and a SLEPc eigenvalue solver.

    Specification(s): test4

    Design: EigenProblem

    Issue(s): #20095

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.15.6

  • 15.15.8The system shall support solving an Eigen value problem using the inverse power method.

    Specification(s): test_inverse_power_method

    Design: InversePowerMethod

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.9The system shall support solving an Eigen value problem using Newton's method.

    Specification(s): test_nonlinear_eigen

    Design: NonlinearEigen

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.10The system shall support solving an Eigen value problem using Newton's method in parallel.

    Specification(s): test_nonlinear_eigen_parallel

    Design: NonlinearEigen

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.11The system shall support the use of material properties during an Eigen problem solve.

    Specification(s): test_nonlinear_eigen_material

    Design: Executioner System

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.12The system shall be capable of solving a diffusion problem using an Eigen value solver.

    Specification(s): test_normal_eigenkernel

    Design: MassEigenKernel

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.13The system shall be capable of solving a nonlinear diffusion problem using an Eigen value solver.

    Specification(s): test_another_nonlinear_eigen

    Design: Executioner System

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.14The system shall be capable of solving a coupled nonlinear diffusion problem using an Eigen value solver.

    Specification(s): test_coupled_nonlinear_eigen

    Design: Executioner System

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.15The system shall be capable of using coupled variables in the EigenKernel object.

    Specification(s): test_deficient_B_eigen

    Design: Executioner System

    Issue(s): #2350

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.16The system shall support adaptive solves for steady-state execution.

    Specification(s): test_steady_adapt

    Design: Executioner System

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.17The system shall be able to detect steady state conditions during execution.

    Specification(s): test_steady_state_check

    Design: Executioner System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.18The system shall be capable of solving a steady state diffusion problem.

    Specification(s): test_steady

    Design: Executioner System

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.19The system shall be capable of solving a transient diffusion problem.

    Specification(s): test_transient

    Design: Executioner System

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.20The system shall print automatic scaling factors if specified.

    Specification(s): test_print_automatic_scaling_factors_true

    Design: Executioner System

    Issue(s): #13795

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.21The system shall not print automatic scaling factors if not specified.

    Specification(s): test_print_automatic_scaling_factors_false

    Design: Executioner System

    Issue(s): #13795

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.22The system shall provide a capability to solve a problem iteratively with a tagged residual vector for
    1. linear and
    2. nonlinear problems.

    Specification(s): tagged_residual/diffusion, tagged_residual/nonlinear

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.23The system shall provide a capability to solve a problem iteratively with a tagged solution vector being coupled in
    1. kernels and/or
    2. materials.

    Specification(s): tagged_solution_vector/var, tagged_solution_vector/material

    Design: TaggingInterface

    Issue(s): #17586

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

    Design: TaggingInterface

    Issue(s): #26285

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.15.25The system shall correctly compute Jacobians when boundary conditions are disabled.

    Specification(s): full_jacobian_thread_active_bcs

    Design: Executioner System

    Issue(s): #12627

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.15.26The Executioner system shall support the PETSc non-linear divergence tolerance.

    Specification(s): test

    Design: Executioner System

    Issue(s): #13991

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): test_abs_divtol

    Design: FEProblemSolve

    Issue(s): #16474

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.28The system shall perform n non linear iterations before checking for non linear divergence

    Specification(s): nl_forced_its

    Design: FEProblemSolve

    Issue(s): #16474

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.29The system shall force the prescribed number of non linear iterations even if convergence tolerance is already satisfied.

    Specification(s): 2d_diffusion_test

    Design: FEProblemSolve

    Issue(s): #16474

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.30The system shall perform many non linear iterations before checking for non linear divergence

    Specification(s): many_nl_forced_its

    Design: FEProblemSolve

    Issue(s): #19591

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.31The system shall perform many non linear iterations before checking for non linear divergence using reference residual

    Specification(s): many_nl_forced_its_ref_res

    Design: FEProblemSolve

    Issue(s): #19591

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): nl_pingpong

    Design: FEProblemSolve

    Issue(s): #16376

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.33The system shall compute the solution of rank-deficient linear equations if the right hand side is within the range of the linear operator.

    Specification(s): test_singular

    Design: Executioner System

    Issue(s): #7866#7790

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.15.34The system shall compute the solution of rank-deficient linear equations if the right hand side has components that are orthogonal to the range of the linear operator.

    Specification(s): test_singular_contaminated

    Design: Executioner System

    Issue(s): #7866#7790

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.15.35Executioner objects shall be capable of coupling to Postprocessor values.

    Specification(s): pp_binding

    Design: Executioner System

    Issue(s): #10603

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.36The system shall allow executioners to do setups before initializing the problem.

    Specification(s): test

    Design: Executioner System

    Issue(s): #18004

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.15.37The system shall correctly evaluate Jacobians with coupled problems and the LINEAR solve type

    Specification(s): linear_with_full_smp

    Design: Executioner System

    Issue(s): #14065

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.38The system shall not change the system time during steady-state execution.

    Specification(s): test_steady_time

    Design: Executioner System

    Issue(s): #12772

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.39The system shall be able to set the system time for steady-state execution.

    Specification(s): test_steady_set_time

    Design: Executioner System

    Issue(s): #12772

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.40The system shall support controlling what objects are executing based on start and end times.

    Specification(s): test

    Design: TimePeriod

    Issue(s): #5560

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.41The system shall support explicit definition of execution times.

    Specification(s): testsynctimes

    Design: Executioner System

    Issue(s): #1781

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.15.42The system shall support output using a time interval.

    Specification(s): test_time_out_interval

    Design: Executioner System

    Issue(s): #1781

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Executors
  • 15.16.1The system shall be able to utilize a modular/nested system of execution

    Specification(s): test

    Design: Executor

    Issue(s): #5229#18180

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): cycle

    Design: Executor

    Issue(s): #5229#18180

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): multi_root

    Design: Executor

    Issue(s): #5229#18180

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.16.4The system shall be able to experimentally use the executor system instead of an executioner.

    Specification(s): test_executor_interface

    Design: Executor

    Issue(s): #5229#18180

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Fixedbugs
  • 15.17.1The Material objects provided on all subdomains shall satisfy requests for objects on all subdomains.

    Specification(s): test

    Design: Materials System

    Issue(s): #8575

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Functions
  • 15.18.1Generate the fine tabulated function data for the coarsened_piecewise_linear test

    Specification(s): prepare_data

    Design: CoarsenedPiecewiseLinear

    Issue(s): #2272

    Collection(s): FUNCTIONAL

    Type(s): RunCommand

  • 15.18.2The Function system shall include an object that creates a function based on x- and y-data pairs, reduces the number of data points based on a user supplied cut-off and returns a linearly interpolated value from the coarsened data.

    Specification(s): coarsened_piecewise_linear

    Design: CoarsenedPiecewiseLinear

    Issue(s): #2272

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.18.1

  • 15.18.3The Function system shall include a constant function.

    Specification(s): test

    Design: ConstantFunction

    Issue(s): #1678

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.4The Function system shall include the ability to set default values for input parameters expecting a function name.

    Specification(s): test

    Design: Functions System

    Issue(s): #2880

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.5The Function system shall include the ability to read comma or space separated data and perform linear interpolation using the supplied data.

    Specification(s): index

    Design: Functions SystemPiecewiseLinear

    Issue(s): cf61044773b14d5560e583867462fe9831dd1f3e

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.6The Function system shall include the ability to pick rows or columns from comma or space separated data based on row or column headers.

    Specification(s): title

    Design: Functions SystemPiecewiseLinear

    Issue(s): #21186

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.7The system shall be able to initialize a variable with values computed using a user-specified function
    1. using the function directly.
    2. with a scaling factor applied to the function.

    Specification(s): test/basic, test/scaling

    Design: FunctionIC

    Issue(s): f792fc7ff9f8d8dfa8b3272117745fc422295ca1

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.8The Function object shall include a callback executed during each timestep.

    Specification(s): test

    Design: Functions System

    Issue(s): #1017

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.9The Material system shall support defining properties within the input file that are associated with functions.

    Specification(s): scalar

    Design: GenericFunctionMaterial

    Issue(s): #1335

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.10The Material system shall support defining vector properties within the input file that are associated with functions.

    Specification(s): vector

    Design: GenericFunctionVectorMaterial

    Issue(s): #18372

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): vector_error

    Design: GenericFunctionVectorMaterial

    Issue(s): #18372

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.12The system shall allow for piecewise functions to directly set the x and y data internally.

    Specification(s): hardcoded_piecewise_linear

    Design: PiecewiseLinear

    Issue(s): #14220

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

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

    Design: ImageFunctionImageMesh

    Issue(s): #5927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.14The system shall include the ability to define a function based on a 2D image and initialize a nodal variable.

    Specification(s): 2d

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.15The system shall include the ability to define a function based on a 2D image and initialize a elemental variable.

    Specification(s): 2d_elemental

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.16The system shall include the ability to define a function based on a stack of images and initialize a nodal variable.

    Specification(s): 3d

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.17The system shall include the ability to define a function based on a subset stack of images and initialize a nodal variable.

    Specification(s): 3d_subset

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.18The system shall allow the image data within the ImageFunction object to be set as one of two values based on a threshold value.

    Specification(s): threshold

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.19The system shall be capable of initializing a variable from image data and perform initial adaptivity based on the data.

    Specification(s): threshold_adapt

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.20The system shall be capable of initializing a variable from image data and perform initial adaptivity based on the data, in parallel.

    Specification(s): threshold_adapt_parallel

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.21The system shall be capable of initializing a variable from image data and perform initial adaptivity based on the data, in parallel and produce Nemesis output files.

    Specification(s): threshold_adapt_parallel_check_files

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 15.18.22The system shall be capable of limiting the supplied data to the ImageFunction object to a single component of the RGB image data.

    Specification(s): component

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.23The system shall be capable of shifting and scaling the supplied image data to the ImageFunction object.

    Specification(s): shift_and_scale

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.24The system shall be capable of operating on domains that are larger than the image size in the ImageFunction object.

    Specification(s): subset

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.25The system shall be capable of flipping image data along the vertical axis in the ImageFunction object.

    Specification(s): flip

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.26The system shall be capable of flipping image data along vertical axis and shifting the origin using the ImageFunction object.

    Specification(s): flip_dual

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.27The system shall be capable of flipping image data along vertical and horizontal axis within the ImageFunction object.

    Specification(s): flip_quad

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.28The system shall be capable of operating on domains that are smaller than the image size within the ImageFunction object.

    Specification(s): crop

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.29The system shall be capable of generating a 3D mesh based on a stack of 2D images using the ImageMesh object.

    Specification(s): image_mesh_3d

    Design: ImageMesh

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.30The system shall be capable of generating a 2D mesh based on an image using the ImageMesh object.

    Specification(s): image_mesh_2d

    Design: ImageMesh

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • The system shall perform shift and scale options independently using the ImageFunction object.

    Specification(s): moose_logo

    Design: ImageFunction

    Issue(s): #3544#5927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): except1

    Design: LinearCombinationFunction

    Issue(s): #4828

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.33The LinearCombinationFunction shall be capable of computing the sum of function values, each multiplied by a scale factor.

    Specification(s): lcf1

    Design: LinearCombinationFunction

    Issue(s): #4828

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.34The LinearCombinationFunction shall be capable of computing the sum of function gradients, each multiplied by a scale factor.

    Specification(s): lcf_grad

    Design: LinearCombinationFunction

    Issue(s): #4828

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.35The LinearCombinationFunction shall be capable of computing the sum of vector functions, each multiplied by a scale factor.

    Specification(s): lcf_vector

    Design: LinearCombinationFunction

    Issue(s): #4828

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.36The Function system shall support the creation of objects that execute a function defined within the input file.

    Specification(s): steady

    Design: ParsedFunction

    Issue(s): #1902

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.37The ParsedFunction object shall be capable of defining function within the input file for use with the method of manufactured solutions.

    Specification(s): transient

    Design: ParsedFunction

    Issue(s): #1902

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.38The Function system shall support the creation of objects that execute a vector function defined within the input file.

    Specification(s): vector

    Design: ParsedFunction

    Issue(s): #2273

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.39The Function system shall support the creation of objects that execute a function defined within the input file that includes a scalar variable.

    Specification(s): scalar

    Design: ParsedFunction

    Issue(s): #5041

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.40The ParsedFunction object shall support the use of other functions specified by their names in its expression.

    Specification(s): function

    Design: ParsedFunction

    Issue(s): #12179

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.41The ParsedFunction object shall support the use of functions, scalar expressions and postprocessor expressions specified by their names in its expression at the same time.

    Specification(s): combined

    Design: ParsedFunction

    Issue(s): #12179

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.42The Function system shall support the creation of objects that execute a curl of a vector function defined within the input file.

    Specification(s): function_curl

    Design: ParsedFunction

    Issue(s): #13041

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): vals_error

    Design: ParsedFunction

    Issue(s): #14169

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): nl_vars

    Design: ParsedFunction

    Issue(s): #15523

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.45The Function system shall provide the ability to take a base function and periodically repeat that function according to a user-defined period in time or in the x, y, or z direction, or a combination of those

    Specification(s): periodic_function

    Design: PeriodicFunction

    Issue(s): #23202

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.46The system shall include an object that creates a function based on x- and y-data pairs and returns an explicit value from the supplied data when queried (i.e., linear interpolation is not performed).

    Specification(s): piecewise_constant

    Design: PiecewiseConstant

    Issue(s): #2272#25058

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.47The system shall include an object that creates a function based on x- and y-data pairs and returns an explicit value from the supplied data when queried (i.e., linear interpolation is not performed) in a simple simulation, with both negative and positive values.

    Specification(s): piecewise_constant_simple

    Design: PiecewiseConstant

    Issue(s): #2272#25058

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.48The system shall be able to compute a piecewise constant function based on x- and y-data loaded from a JSON file.

    Specification(s): piecewise_constant_from_json

    Design: PiecewiseConstant

    Issue(s): #2272#25058

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

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

    Design: PiecewiseConstant

    Issue(s): #2272#25058

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.50The Function system shall include a function that can obtain data from a CSV file
    1. with data sorted by element ids
    2. with data sorted by node ids
    3. with data at given locations and using nearest neighbor interpolation between those data points
    4. using nearest neighbor interpolation with a random tesselation
    5. with data at given locations and using nearest neighbor interpolation between those data points, with periodic boundaries
    6. with data sorted by blocks and with constant values on each block,
    7. with multiple CSV files read on every execution of the user object.

    Specification(s): csv_read/element, csv_read/node, csv_read/voronoi, csv_read/random_voronoi, csv_read/periodic_voronoi, csv_read/block, csv_read/multiple_files

    Design: PiecewiseConstantFromCSV

    Issue(s): #19109

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

    Design: PiecewiseConstantFromCSV

    Issue(s): #19109

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: PiecewiseConstantFromCSV

    Issue(s): #19109

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.53The Function system shall include an object that creates a function based on x- and y-data pairs and does not extrapolate.

    Specification(s): no_extrap

    Design: PiecewiseLinear

    Issue(s): #20024

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.54The Function system shall include an object that creates a function based on x- and y-data pairs and does extrapolate.

    Specification(s): extrap

    Design: PiecewiseLinear

    Issue(s): #20024

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.55The system shall be capable of linear interpolating data generated by a VectorPostprocessor object.

    Specification(s): test_spatial_data

    Design: PiecewiseLinearFromVectorPostprocessor

    Issue(s): #8713

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.56The system shall be capable of linear interpolating data generated by a VPP with respect to time.

    Specification(s): test_time_data

    Design: PiecewiseLinearFromVectorPostprocessor

    Issue(s): #14700

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): except1

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except2

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except3

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except4

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): except5

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.62The PiecewiseMultilinear object shall perform interpolation on a 1D domain.

    Specification(s): oneDa

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.63The PiecewiseMultilinear object shall perform interpolation on a 1D domain that compares to an equivalent known function.

    Specification(s): oneDb

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.64The PiecewiseMultilinear object shall perform interpolation of time-dependent data.

    Specification(s): time

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.65The PiecewiseMultilinear object shall perform interpolation on a 2D domain.

    Specification(s): twoDa

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.18.66The PiecewiseMultilinear object shall perform interpolation on a 2D domain that compares to an equivalent known function.

    Specification(s): twoDb

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.67The PiecewiseMultilinear object shall perform constant interpolation on a 2D domain.

    Specification(s): twoD_const

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.68The PiecewiseMultilinear object shall perform interpolation on a 3D domain with time-dependent data.

    Specification(s): fourDa

    Design: PiecewiseMultilinear

    Issue(s): #2476

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.69The Function object shall support the ability to couple Postprocessor values.

    Specification(s): test_pp_function_test

    Design: Postprocessor System

    Issue(s): #1199

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.70The SolutionFunction object shall be capable of evaluating a solution read from XDA mesh and solution files.

    Specification(s): test

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.71The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file with temporal interpolation.

    Specification(s): exodus_interp_test

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.72The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file.

    Specification(s): exodus_test

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.73The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file and rotated 45 degrees about the z-axis.

    Specification(s): rot1

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.74The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file and rotated 45 degrees about the y-axis.

    Specification(s): rot2

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.75The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file and rotated 90 degrees about the z-axis and 45 degress about the x-axis.

    Specification(s): rot3

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.76The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file and rotated 45 degrees about the z-axis for a 2D domain.

    Specification(s): rot4

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.77The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file and scaled by a factor in the x and y directions as well as translated in the x-direction.

    Specification(s): scale_transl

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.18.78The SolutionFunction object shall be capable of evaluating a solution read from an Exodus file and scaled by a factor of two in the x and y directions.

    Specification(s): scale_mult

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): nonexistent_var_err

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.18.80The system shall be capable of evaluating the gradient of a solution
    1. created in a simulation
    2. and read from another.

    Specification(s): solution_function/grad_p1, solution_function/grad_p2

    Design: SolutionFunction

    Issue(s): fc620eb2a4580a2320e03e6e89ad092dd2f4123b

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Functormaterials
  • 15.19.1The system shall support the output of functor material data as field variables including
    1. outputting a functor property, defined within a functor material;
    2. outputting a functor property with automatic differentiation, defined within a functor material.

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

    Design: FunctorMaterialsOutput System

    Issue(s): #19382

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.19.2The system shall be able to parse an expression of functors to compute a functor material property.

    Specification(s): test

    Design: ParsedFunctorMaterial

    Issue(s): #24380

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.19.3The system shall be able to
    1. use the average of the values of a functor on an element's face to compute the element value, which can be smoother, and
    2. use the average of the values of a functor at an element's neighbors to compute the element value, which can be smoother, and
    3. use a heuristic based on a functor's value on an element and the maximum values on the element's neighbors to compute a new element value that removes a checkerboard pattern.

    Specification(s): smoother/face, smoother/neighbors, smoother/checkerboard

    Design: FunctorSmoother

    Issue(s): #25452

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.19.4The system shall be able to compute the time derivatives of functors, and make them available as functor material properties.

    Specification(s): test

    Design: GenericFunctorTimeDerivativeMaterial

    Issue(s): #28755

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.19.5The system should be able to add a generic functor material without a suffix for the properties.

    Specification(s): no_suffix

    Design: GenericFunctorMaterial

    Issue(s): #27440

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.19.6The system should be able to add a generic functor material with a suffix for the names of the properties.

    Specification(s): suffix

    Design: GenericFunctorMaterial

    Issue(s): #27440

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • rdg: Functors
  • 15.20.1The system shall be able to accurately evaluate a finite element variable through the functor system in a finite volume Dirichlet boundary condition.

    Specification(s): exo

    Design: Functor system

    Issue(s): #19420

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.20.2The system shall compute the correct Jacobian when evaluating a finite element variable through the functor system in a finite volume Dirichlet boundary condition.

    Specification(s): jac

    Design: Functor system

    Issue(s): #19420

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.20.3The system shall be able to use a variable, function, functor material property, and a post-processor in a functor parameter.

    Specification(s): test

    Design: Functor system

    Issue(s): #25012

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.20.4The system shall be able to evaluate functors at nodes, element centers, and quadrature points, and match an expected analytic solution.

    Specification(s): analytic

    Design: Functor system

    Issue(s): #16809#19420

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.20.5The system shall be able to solve a diffusion problem with a second order reaction term in which one operand is evaluated with the current solution state and the other operand is evaluated
    1. with the current solution state, and
    2. show a perfect Jacobian, or
    3. with the previous nonlinear iteration solution state, and
    4. show a perfect Jacobian.

    Specification(s): functors/no_lag, functors/no_lag_jac, functors/lag, functors/lag_jac

    Design: Materials System

    Issue(s): #23630

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • rdg: Fvbcs
  • 15.21.1The system shall allow the use of functors to set Dirichlet boundary values for FV.

    Specification(s): fv_functor_dirichlet

    Design: FVFunctorDirichletBC

    Issue(s): #21374

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.21.2The system shall allow the use of functors to set Dirichlet boundary values for FV evaluated on the other side of the sideset.

    Specification(s): other_side

    Design: FVFunctorDirichletBC

    Issue(s): #25933

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.21.3The system shall provide a boundary condition to satisfy neumann boundary conditions with a functor

    Specification(s): test

    Design: FVFunctorNeumannBC

    Issue(s): #21632

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.21.4The system shall run a simple 1D diffusion problem with a Neumann BC value.

    Specification(s): fv_neumann

    Design: FVNeumannBC

    Issue(s): #16477

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): fvbcs_internal

    Design: FVNeumannBC

    Issue(s): #16882

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): fvbcs_disconnected_from_variable

    Design: FVNeumannBC

    Issue(s): #16882

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.21.7The system shall run a simple 1D diffusion problem with a Dirichlet BC value set by a postprocessor.

    Specification(s): fv_pp_dirichlet

    Design: FVPostprocessorDirichletBC

    Issue(s): #16477

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Fvics
  • 15.22.1The system shall support setting initial conditions of finite volume field variables to a constant value.

    Specification(s): one-domain

    Design: FVICs System

    Issue(s): #25824

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.22.2The system shall support setting initial conditions of subdomain restricted finite volume field variables to a constant value.

    Specification(s): multiple-domains

    Design: FVICs System

    Issue(s): #25824

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.22.3The system shall support the initialization of a finite volume variable from an exodus file.

    Specification(s): parsed_function

    Design: FVICs System

    Issue(s): #25824

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.22.4The system shall support the definition of a function initial condition for a finite volume variable.

    Specification(s): parsed_function

    Design: FVICs System

    Issue(s): #25824

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Fviks
  • 15.23.1The system shall be able to solve a diffusion problem with finite volumes with the domain split in half and force the two variables living on each side of the domain to match on the interface., when the residual and Jacobian are computed:
    1. separately
    2. together

    Specification(s): continuity/continuity, continuity/continuity_together

    Design: FVTwoVarContinuityConstraint

    Issue(s): #17638

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.23.2The system shall be able to solve a diffusion problem with the domain split in half and two finite volume variables living on each side.

    Specification(s): diffusion

    Design: FVDiffusionInterface

    Issue(s): #17638

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.23.3The system shall be able to solve a diffusion problem with the domain split in half and two finite volume variables living on each side and interpolating the diffusivities using a harmonic mean.

    Specification(s): diffusion-harmonic

    Design: FVDiffusionInterface

    Issue(s): #21923

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.23.4The system shall be able to solve a block-restricted diffusion problem where the variables live on different nonlinear systems.

    Specification(s): diffusion-multisystem

    Design: FVDiffusionInterfaceProblem system overview

    Issue(s): #25599

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): run_except1

    Design: FVInterfaceKernels System

    Issue(s): #17087

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): run_except2

    Design: FVInterfaceKernels System

    Issue(s): #17087

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): run_except3

    Design: FVInterfaceKernels System

    Issue(s): #17087

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.23.8The system shall be able to solve a diffusion problem with finite volumes with the domain split in half and show first order convergence due to its treatment of coefficient discontinuities both
    1. with an interfacing object
    2. without an interfacing object

    Specification(s): first_order_convergence/with-ik, first_order_convergence/without-ik

    Design: FVOneVarDiffusionInterface

    Issue(s): #17087

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.23.9The system shall be able to solve a diffusion problem with finite volumes with the domain split in half and show second order convergence due to the harmonic interpolation of the diffusion coeffcient

    Specification(s): harmonic

    Design: FVOneVarDiffusionInterface

    Issue(s): #17087

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.23.10The system shall be able to compute the residual and Jacobian together for a finite volume interface kernel.

    Specification(s): resid_and_jac

    Design: FVOneVarDiffusionInterface

    Issue(s): #19444

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Geomsearch
  • 15.25.1The system shall be capable of computing the distance between two disjoint boundaries on a 1D domain.

    Specification(s): test

    Design: PenetrationAux

    Issue(s): #1693

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.2The system shall be capable of computing the distance as well as transfer data between interior boundaries on a 2D domain.

    Specification(s): test

    Design: PenetrationAuxGapValueAux

    Issue(s): #2713

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.3The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 2D.

    Specification(s): pl_test1

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.4The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 2D using second order elements.

    Specification(s): pl_test1q

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.5The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 2D using a tangential tolerance of for the distance.

    Specification(s): pl_test1tt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.6The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 2D using a tangential tolerance of for the distance and second order elements.

    Specification(s): pl_test1qtt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.7The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 2D.

    Specification(s): pl_test2

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.8The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 2D with second order elements.

    Specification(s): pl_test2q

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.9The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 2D using a tangential tolerance for the distance.

    Specification(s): pl_test2tt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.10The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 2D using a tangential tolerance for the distance and second order elements.

    Specification(s): pl_test2qtt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.11The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D.

    Specification(s): pl_test3

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.12The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D and second order elements.

    Specification(s): pl_test3q

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.13The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D using a tangential tolerance of for the distance.

    Specification(s): pl_test3tt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.14The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D using a tangential tolerance of for the distance and second order elements.

    Specification(s): pl_test3qtt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.15The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D using normal smoothing for the distance.

    Specification(s): pl_test3ns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.16The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D using normal smoothing for the distance and second order elements.

    Specification(s): pl_test3qns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.17The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D using nodal normal based smoothing for the distance.

    Specification(s): pl_test3nns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.18The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 2D using nodal normal based smoothing for the distance and second order elements.

    Specification(s): pl_test3qnns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.19The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D.

    Specification(s): pl_test4

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.20The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using second order elements.

    Specification(s): pl_test4q

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.21The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using a tangential tolerance of for the distance.

    Specification(s): pl_test4tt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.22The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using a tangential tolerance of for the distance and second order elements.

    Specification(s): pl_test4qtt

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.23The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using normal smoothing for the distance.

    Specification(s): pl_test4ns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.24The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using normal smoothing for the distance and second order elements.

    Specification(s): pl_test4qns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.25The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using nodal normal based smoothing.

    Specification(s): pl_test4nns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.26The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 2D using nodal normal based smoothing and second order elements.

    Specification(s): pl_test4qnns

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.27The systems shall be capable of performing simulations with geometric penetration
    1. computed within one simulation
    2. that are restarted from a another.

    Specification(s): restart/part1, restart/part2

    Design: PenetrationAux

    Issue(s): #852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.28The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces in 2D.

    Specification(s): test

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.29The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces in 2D with triangular elements.

    Specification(s): 2d_triangle

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.30The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 3D.

    Specification(s): pl_test1

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.31The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 3D using second order elements.

    Specification(s): pl_test1q

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.32The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 3D using a tangential tolerance of for the distance.

    Specification(s): pl_test1tt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.33The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces of a moving interface in 3D using a tangential tolerance of for the distance and second order elements.

    Specification(s): pl_test1qtt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.34The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 3D.

    Specification(s): pl_test2

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.35The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 3D with second order elements.

    Specification(s): pl_test2q

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.36The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 3D using a tangential tolerance for the distance.

    Specification(s): pl_test2tt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.37The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces of a moving interface in 3D using a tangential tolerance for the distance and second order elements.

    Specification(s): pl_test2qtt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.38The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 3D.

    Specification(s): pl_test3

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.39The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 3D and second order elements.

    Specification(s): pl_test3q

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.40The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and convex disjoint surfaces of a moving interface in 3D using a tangential tolerance of for the distance and second order elements.

    Specification(s): pl_test3tt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.41The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 3D.

    Specification(s): pl_test4

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.42The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 3D using second order elements.

    Specification(s): pl_test4q

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.43The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between a flat and concave disjoint surfaces of a moving interface in 3D using a tangential tolerance of for the distance.

    Specification(s): pl_test4tt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.44The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two disjoint surfaces:
    1. with nodal normal based smoothing;
    2. with nodal normal based smoothing and a specified tangential tolerance;
    3. with a specified normal smoothing distance;
    4. with a specified normal smoothing distance and a specified tangential tolerance;
    5. with second-order elements and third-order quadrature; and
    6. with second-order elements and third-order quadrature and a specified tangential tolerance.

    Specification(s): disjoint/pl_test3nns, disjoint/pl_test3nnstt, disjoint/pl_test3ns, disjoint/pl_test3nstt, disjoint/pl_test3qns, disjoint/pl_test3qnstt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.45The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two overlapping surfaces:
    1. with nodal normal based smoothing;
    2. with nodal normal based smoothing and a specified tangential tolerance;
    3. with a specified normal smoothing distance;
    4. with a specified normal smoothing distance and a specified tangential tolerance;
    5. with second-order elements and third-order quadrature; and
    6. with second-order elements and third-order quadrature and a specified tangential tolerance.

    Specification(s): overlapping/pl_test4nns, overlapping/pl_test4nnstt, overlapping/pl_test4ns, overlapping/pl_test4nstt, overlapping/pl_test4qns, overlapping/pl_test4qnstt

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.46The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, overlapping surfaces in 3D.

    Specification(s): test

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.47The PenetrationAux object shall be capable of computing the distance, tangential distance, normal, closest point, side id, and element id between two parallel, disjoint surfaces in 2D with tetrahedron elements.

    Specification(s): 3d_tet

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.48The system shall be able to find contact points on a geometry where the contact point search leads to element Jacobian computations too far from the element for the Jacobian to be non-negative.

    Specification(s): rings_facing_each_other

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.25.49The NearestNodeDistanceAux object shall be capable of computing the shortest distance between a boundary and subdomain.

    Specification(s): test

    Design: NearestNodeDistanceAux

    Issue(s): #3964

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.50The NearestNodeDistanceAux shall be capable of computing the shortest distance between two boundaries.

    Specification(s): test

    Design: NearestNodeDistanceAux

    Issue(s): #1570

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.51The NearestNodeDistanceAux shall be capable of computing the shortest distance between two boundaries with adaptivity.

    Specification(s): adapt

    Design: NearestNodeDistanceAux

    Issue(s): #1570

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.52The system shall support a means for updating the geometric search patch dynamically that may be disabled.

    Specification(s): never

    Design: GapValueAuxMesh System

    Issue(s): #3901

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.53The system shall support a means for updating the geometric search patch dynamically that automatically determines when an update to the patch shall occur.

    Specification(s): auto

    Design: GapValueAuxMesh System

    Issue(s): #3901

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.54The system shall support a means for updating the geometric search patch dynamically that updates the patch prior to each solve.

    Specification(s): always

    Design: GapValueAuxMesh System

    Issue(s): #3901

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.55The system shall support a means for updating the geometric search patch dynamically that updates the patch prior to each iteration.

    Specification(s): nonlinear_iter

    Design: GapValueAuxMesh System

    Issue(s): #3901

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.25.54

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

    Specification(s): never_warning

    Design: GapValueAuxMesh System

    Issue(s): #3901

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 15.25.52

  • 15.25.57The system shall be able to perform patch updates on every non-linear iteration while performing uniform coarsening and refinement from grid sequencing.

    Specification(s): always-grid-sequencing

    Design: Mesh SystemGapValueAuxFEProblemBase

    Issue(s): #14166

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.58The PenetrationAux object shall compute the distance between two boundaries in 3D that overlap.

    Specification(s): test

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.59The PenetrationAux object shall compute, in parallel, the distance between two boundaries in 3D that overlap.

    Specification(s): parallel_test

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.25.115.25.215.25.2815.25.4615.25.4915.25.5015.25.58

  • 15.25.60The nonlinear system shall be able to augment its sparsity based on constraints when we have a quadrature nearest-node locator.

    Specification(s): quadrature_locator_plus_constraint

    Design: GeometricSearchData

    Issue(s): #5234

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.25.61The NearestNodeDistanceAux object shall compute the shortest distance between nodes on two overlapping boundaries using a constant monomial auxiliary variable.

    Specification(s): qnnl

    Design: NearestNodeDistanceAux

    Issue(s): #1462

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.62Volumetric AD assembly data shall be properly sized when reinitializing faces

    Specification(s): qnnl_ad

    Design: NearestNodeDistanceAux

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.63The PenetrationAux object shall compute the distance between two overlapping boundaries using a constant monomial auxiliary variable.

    Specification(s): qpl

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.25.64The PenetrationAux object shall compute the distance between two overlapping boundaries using a constant monomial auxiliary variable in 1D.

    Specification(s): 1d_qpl

    Design: PenetrationAux

    Issue(s): 5478df0f0897ed7ac3dd3a3de1785a7948c75cfe

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Globalparams
  • 15.26.1The system shall include an input file syntax that supports defining global options.

    Specification(s): global_param_test

    Design: Parser

    Issue(s): #437#8761

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): test_suppress_ignore

    Design: Parser

    Issue(s): #437#8761

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.26.3The system shall not apply global parameter options onto suppressed parameters.

    Specification(s): test_ignore

    Design: Parser

    Issue(s): #437#8761

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Ics
  • 15.28.1The system shall allow to set constant initial conditions for an array variable.

    Specification(s): array_constant_ic

    Design: ArrayConstantIC

    Issue(s): #6881

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): size_error

    Design: ArrayConstantIC

    Issue(s): #6881

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.28.3The system shall allow to set initial conditions for an array variable based on functions.

    Specification(s): array_constant_ic

    Design: ArrayFunctionIC

    Issue(s): #6881

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): size_error

    Design: ArrayFunctionIC

    Issue(s): #6881

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.28.5The system shall support setting initial conditions on boundaries.

    Specification(s): test

    Design: ICs System

    Issue(s): #534

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.6Generates a rectangular IC

    Specification(s): test

    Design: BoundingBoxIC

    Issue(s): #11034

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.7BoundingBoxIC shall have a diffuse interface option.

    Specification(s): diffuse

    Design: BoundingBoxIC

    Issue(s): #13331

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): ics_on_same_boundary

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_block

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_block_both_global

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ics_on_same_block_first_global

    Design: ICs System

    Issue(s): #6580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.28.12The system shall support setting different values for each coefficient of higher-order scalar values.

    Specification(s): test

    Design: ICs System

    Issue(s): #2085

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.13The system shall support setting initial conditions of field variables to a constant value.

    Specification(s): test

    Design: ICs System

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.14The system shall support setting initial conditions of subdomain restricted field variables to a constant value.

    Specification(s): subdomain_test

    Design: ICs System

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.15The system shall provide current node or element pointers when possible when evaluating initial conditions at a point in the domain.

    Specification(s): test

    Design: ICs System

    Issue(s): #4953

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.16The system shall allow setting field initial condition from an user object

    Specification(s): ic_depend_on_uo

    Design: InitialConditionUserObjectInterface

    Issue(s): #8810

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.17The system shall allow setting scalar initial condition from an user object

    Specification(s): scalar_ic_from_uo

    Design: ScalarInitialConditionUserObjectInterface

    Issue(s): #13357

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.28.18The system shall allow nodal initial condition objects to couple to other nodal variables for computing values for the current variable.

    Specification(s): test

    Design: ICs System

    Issue(s): #534

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.19The system shall allow elemental initial condition objects to couple to other elemental variables for computing values for the current variable.

    Specification(s): monomial

    Design: ICs System

    Issue(s): #534

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.20The system shall write output files containing nodal solutions in ExodusII format suitable for restart.

    Specification(s): nodal_var_1

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.21The system shall be able to populate nodal initial conditions from a previous solution file in ExodusII format.

    Specification(s): nodal_var_2

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.28.20

  • 15.28.22The system shall write output files containing elemental solutions in ExodusII format suitable for restart.

    Specification(s): elem_var_1

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.23The system shall be able to populate elemental initial conditions from a previous solution file in ExodusII format.

    Specification(s): elem_var_2

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.28.22

  • 15.28.24The system shall write output files containing elemental array variable solutions in ExodusII format suitable for restart.

    Specification(s): array_elem_var_1

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.25The system shall be able to populate elemental array variable initial conditions from a previous solution file in ExodusII format.

    Specification(s): array_elem_var_2

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.28.24

  • 15.28.26The system shall write output files containing nodal array variable solutions in ExodusII format suitable for restart.

    Specification(s): array_nodal_var_1

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.27The system shall be able to populate nodal array variable initial conditions from a previous solution file in ExodusII format.

    Specification(s): array_nodal_var_2

    Design: ICs System

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.28.26

  • 15.28.28The system shall support setting gradient values for shape functions that support them.

    Specification(s): parsed_function

    Design: ICs System

    Issue(s): #3312

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.29The system shall support using a spline function to set both value and gradient values in an initial condition.

    Specification(s): spline_function

    Design: ICs System

    Issue(s): #3312

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.30The system shall support setting a scalar initial condition by evaluating a function.

    Specification(s): test

    Design: ICs System

    Issue(s): #6309

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.28.31The system shall support setting initial conditions for the Hermite set of shape functions.

    Specification(s): test

    Design: ICs System

    Issue(s): #1493

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

    Design: IntegralPreservingFunctionIC

    Issue(s): #19476

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.28.33The system shall be able to apply a normalized sinusoidal initial condition.

    Specification(s): sinusoidal

    Design: IntegralPreservingFunctionIC

    Issue(s): #19476

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.34The system shall support initial conditions on second order Lagrange variables in 3D space.

    Specification(s): 3d_second_order

    Design: ICs System

    Issue(s): #1493

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.35The system shall allow initial conditions to retrieve post-processor values.

    Specification(s): test

    Design: InitialConditionPostprocessorInterface

    Issue(s): #17692

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.28.36The system shall generate parallel agnostic random initial conditions

    Specification(s): test

    Design: RandomIC

    Issue(s): #5567#11901

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.37The system shall generate threaded agnostic random initial conditions

    Specification(s): test_threaded

    Design: RandomIC

    Issue(s): #5567#11901

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.28.515.28.615.28.1215.28.1315.28.1515.28.1815.28.3015.28.3115.28.3515.28.3615.28.48

  • 15.28.38The system shall be able to initialize a variable from an ExodusII file.

    Specification(s): exodus

    Design: SolutionICSolutionUserObject

    Issue(s): #24581

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.39The system shall be able to initialize a scalar variable from an ExodusII file.

    Specification(s): exodus_scalar

    Design: SolutionICSolutionUserObject

    Issue(s): #24581

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): errors/missing_block

    Design: SolutionICSolutionUserObject

    Issue(s): #24581

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.28.41The system shall allow to set constant vector-valued initial conditions.

    Specification(s): vector_constant_ic

    Design: VectorConstantIC

    Issue(s): #12311

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.42The system shall allow to set constant vector-valued initial conditions when adding vector variables.

    Specification(s): vector_short_constant_ic

    Design: VectorConstantIC

    Issue(s): #12311

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.43The system shall allow vector-valued initial conditions be set using a vector function for the following element families:
    1. vector Lagrange,
    2. Nedelec,
    3. and Raviart-Thomas.

    Specification(s): vector_function_ic/lagrange, vector_function_ic/nedelec, vector_function_ic/raviart

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.28.44The system shall allow vector-valued initial conditions be set using a function by components.

    Specification(s): vector_function_ic_comp

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): comp_x_error

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): comp_y_error

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): comp_z_error

    Design: VectorConstantIC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.28.48The system should supply a special convenience "zero" variable that can be indexed like a normal coupled variable.

    Specification(s): test

    Design: FEProblemBase

    Issue(s): #11202

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • rdg: Indicators
  • 15.29.1The system shall include the ability to compute the square of the difference between a solution variable and an analytical function for the purpose of performing automatic mesh adaptivity.

    Specification(s): analytical

    Design: AnalyticalIndicator

    Issue(s): #1275#16069

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.29.2The system shall include the ability to compute the square of the difference between a FV solution variable and an analytical function for the purpose of performing automatic mesh adaptivity.

    Specification(s): analytical_fv

    Design: AnalyticalIndicator

    Issue(s): #1275#16069

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.29.3The system shall include the ability to compute the square of the change in the gradient of a variable across element boundaries for the purpose of performing automatic mesh adaptivity.

    Specification(s): test

    Design: GradientJumpIndicator

    Issue(s): #1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.29.4The system shall include the ability to compute the square of the change in the gradient of a finite volume variable across element boundaries for the purpose of performing automatic mesh adaptivity.

    Specification(s): fv

    Design: GradientJumpIndicator

    Issue(s): #1275

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.29.5The system shall include the ability to compute the square of the change in the Laplacian of a variable across element boundaries for the purpose of performing automatic mesh adaptivity:
    1. with a penalty based flux boundary condition;
    2. with a weakly imposed flux boundary condition; and
    3. for transient calculations.

    Specification(s): group/test_biharmonic, group/test_biharmonic_weak_bc, group/test_biharmonic_transient

    Design: LaplacianJumpIndicator

    Issue(s): #1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.29.6The system shall include the ability to compute the square of the change in a variable across element boundaries for the purpose of performing automatic mesh adaptivity:

    Specification(s): test

    Design: ValueJumpIndicator

    Issue(s): #1275#16069

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.29.7The system shall include the ability to compute the square of the change in a FV variable across element boundaries for the purpose of performing automatic mesh adaptivity:

    Specification(s): fv

    Design: ValueJumpIndicator

    Issue(s): #1275#16069

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: InterfaceKernel Objects
  • 15.30.1Interface kernels shall provide integrated conditions between subdomains, and shall work with boundary restricted materials with stateful properties.

    Specification(s): interface_diffusion

    Design: InterfaceKernels System

    Issue(s): #11258#869

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.2The interface diffusion penalty method should reproduce the analytic solution
    1. using a hand-coded Jacobian
    2. using a Jacobian computed via automatic differentiation

    Specification(s): interface_diffusion_penalty/hand-coded, interface_diffusion_penalty/ad

    Design: InterfaceKernels System

    Issue(s): #11765

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.30.1

  • 15.30.3The InterfaceKernel system shall use with interface material in 1D.

    Specification(s): interface_diffusion_penalty_with_jump_material

    Design: InterfaceKernels System

    Issue(s): #12066

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.30.1

  • 15.30.4The system shall support the evaluation of neighboring quantities on elements containing different shape functions.

    Specification(s): mixed_shapes_test

    Design: InterfaceKernels System

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.5The system shall produce correct Jacobians for coupled flux on an interface.

    Specification(s): jacobian_test

    Design: InterfaceKernels System

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 15.30.6The system shall support produce correct Jacobians when evaluating neighboring quantities on elements containing different shape functions.

    Specification(s): mixed_shapes_jacobian_test

    Design: InterfaceKernels System

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 15.30.7The system shall produce correct Jacobians for single variable coupled flux on an interface.

    Specification(s): single_variable_jacobian_test

    Design: InterfaceKernels System

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 15.30.8Save-in shall record the correct residuals and Jacobians representing the interface kernel. This applies the DirichletBC to side a (block 0) of the interface.

    Specification(s): ik_save_in

    Design: InterfaceKernels System

    Issue(s): #9854

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.9Save-in shall record the correct residuals and Jacobians representing the interface kernel. This applies the DirichletBC to side b (block 1) of the interface.

    Specification(s): ik_save_in_other_side

    Design: InterfaceKernels System

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.10The interface reaction kernel should reproduce the analytic solution

    Specification(s): reaction_1D_steady_CSVDiff

    Design: InterfaceReaction

    Issue(s): #13365

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.30.11The interface reaction kernel should work with interface diffusion kernel

    Specification(s): reaction_1D_steady_ExoDiff

    Design: InterfaceReaction

    Issue(s): #13365

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.30.10

  • 15.30.12The result of an interface reaction kernel computed using automatic differentiation shall match the analytic solution in a steady-state simulation

    Specification(s): matreaction_1D_steady_CSVDiff

    Design: ADMatInterfaceReaction

    Issue(s): #27736

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.30.13The result of an interface reaction kernel computed using automatic differentiation shall be consistent with the results of the non-AD transient interface reaction test.

    Specification(s): matreaction_1D_transient_CSVDiff

    Design: ADMatInterfaceReaction

    Issue(s): #27736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.14The solution should be discontinued at the interface due to the reaction taking place

    Specification(s): reaction_1D_transient

    Design: InterfaceReaction

    Issue(s): #13365

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.15The Jacobian from InterfaceReaction shall be perfect

    Specification(s): reaction_1D_transient_Jac

    Design: InterfaceReaction

    Issue(s): #13365

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.30.16The system shall ensure that interfacial materials are sorted such that consumers execute after producers.

    Specification(s): sort_interface_materials

    Design: Materials System

    Issue(s): #17171

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.17The system shall not try to reinit a displaced interface, leading to failed point inversions, if a displaced interface kernel has not been added to the simulation.

    Specification(s): no_failed_point_inversions

    Design: InterfaceKernels System

    Issue(s): #18175

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.18The InterfaceKernel system shall operate with coupled variables in 2D. This uses a penalty implementation that is optimally convergent.

    Specification(s): test

    Design: InterfaceKernels System

    Issue(s): #7885

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.19Allow the interface to impose the same time derivative on two neighboring variables. This uses a penalty implementation that is optimally convergent.

    Specification(s): test_dot

    Design: InterfaceKernels System

    Issue(s): #12372

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.20The InterfaceKernel system shall use with interface material in 2D.

    Specification(s): test_jump_material

    Design: InterfaceKernels System

    Issue(s): #12066

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.21The Jacobian evaluation for InterfaceKernel objects in 2D shall be analytically correct.

    Specification(s): jacobian_test

    Design: InterfaceKernels System

    Issue(s): #7437

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

    Prerequisite(s): 15.30.1815.30.36

  • 15.30.22The finite difference preconditioner shall work in parallel.

    Specification(s): parallel_fdp_test

    Design: FDP

    Issue(s): #10375

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.30.1815.30.36

  • 15.30.23The InterfaceKernel system shall support Vector Finite Elements in 2D.

    Specification(s): vector_2d

    Design: InterfaceKernels System

    Issue(s): #13354

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.24The system shall not perform memory allocation for automatic scaling when computing values.

    Specification(s): no_mallocs_during_scaling

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.30.25The InterfaceKernel system shall operate with coupled variables in 3D. This uses a penalty implementation that is optimally convergent.

    Specification(s): coupled_3d

    Design: InterfaceKernels System

    Issue(s): #7885

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.26The InterfaceKernel system shall support Vector Finite Elements in 3D.

    Specification(s): vector_3d

    Design: InterfaceKernels System

    Issue(s): #13354

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.27The InterfaceKernel system shall use with interface material in 3D.

    Specification(s): test_jump_material

    Design: InterfaceKernels System

    Issue(s): #12066

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.28The system shall be able to solve a simple interfacial source problem using automatic differentiation in which the source term depends on the gradient jump of a coupled variable.

    Specification(s): exo

    Design: Automatic Differentiation

    Issue(s): #15307

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.29The system shall be able to couple variable gradients at interfaces and have an accurate Jacobian provided through automatic differentiation.

    Specification(s): jac

    Design: Automatic Differentiation

    Issue(s): #15307

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.30.30The system shall be able to solve a simple interfacial source problem using automatic differentiation in which the slope on the left-hand side of the interface has a slope greater by two than the slope on the right-hand side.

    Specification(s): exo

    Design: Automatic Differentiation

    Issue(s): #15307

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.31The system shall be able to couple variables at interfaces and have an accurate Jacobian provided through automatic differentiation.

    Specification(s): jac

    Design: Automatic Differentiation

    Issue(s): #15307

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.30.32The system shall be able to solve a simple interfacial source problem using automatic differentiation and vector variables in which the slope on the left-hand side of the interface has a slope greater by two than the slope on the right-hand side.

    Specification(s): exo

    Design: Automatic Differentiation

    Issue(s): #15307

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.33The system shall be able to couple vector variables at interfaces and have an accurate Jacobian provided through automatic differentiation.

    Specification(s): jac

    Design: Automatic Differentiation

    Issue(s): #15307

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.30.34Adaptivity shall work with interface kernels as long as stateful properties are not used.

    Specification(s): ik_adaptivity

    Design: InterfaceKernels System

    Issue(s): #10977

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): error_stateful_ik_adaptivity

    Design: InterfaceKernels System

    Issue(s): #10977

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.30.36The system shall be able to execute interfacial conditions on sidesets generated by gmsh.

    Specification(s): test

    Design: InterfaceKernels System

    Issue(s): #15203

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.37The system shall support Dirichlet and Neumann interface conditions.

    Specification(s): matchedvalue

    Design: InterfaceKernels System

    Issue(s): #7437

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.38The system shall support penalty interface conditions.

    Specification(s): penalty

    Design: InterfaceKernels System

    Issue(s): #7437

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.30.37

  • 15.30.39The system shall support matched-value interface with different variable coefficients with automatic differentiation.

    Specification(s): variable_coeffs_AD

    Design: InterfaceKernels System

    Issue(s): #7437

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.40The system shall support matched-value interface with different variable coefficients.

    Specification(s): variable_coeffs

    Design: InterfaceKernels System

    Issue(s): #7437

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.30.39

  • 15.30.41When computing residuals and jacobians on an interface, the system shall be able to use element information from the displaced mesh when requested

    Specification(s): displaced

    Design: InterfaceKernels System

    Issue(s): #14876

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.42When computing residuals and jacobians on an interface, the system shall be able to use element information from the reference mesh

    Specification(s): undisplaced

    Design: InterfaceKernels System

    Issue(s): #14876

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.30.43The system shall be able to compute the residual and the Jacobian of each interface kernel together.

    Specification(s): resid_jac_together

    Design: NonlinearSystem

    Issue(s): #23487

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Linearfvkernels
  • 15.33.1The system shall display first-order convergence for advection problems with upwind interpolation solved using a linear finite volume system on a one-dimensional domain.

    Specification(s): mms-1d-upwind

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.2The system shall display second-order convergence for advection problems with linear interpolation solved using a linear finite volume system on a one-dimensional domain.

    Specification(s): mms-1d-linear

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.3The system shall display first-order convergence for advection problems with upwind interpolation solved using a linear finite volume system on a two-dimensional orthogonal mesh.

    Specification(s): mms-2d-upwind

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.4The system shall display second-order convergence for advection problems with linear interpolation solved using a linear finite volume system on a two-dimensional orthogonal mesh.

    Specification(s): mms-2d-linear

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.5The system shall display first-order convergence for advection problems with upwind interpolation solved using a linear finite volume system on a two-dimensional nonorthogonal mesh.

    Specification(s): mms-2d-upwind-tris

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.6The system shall display first-order convergence for advection problems with linear interpolation solved using a linear finite volume system on a two-dimensional nonorthogonal mesh.

    Specification(s): mms-2d-linear-tris

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.7The system shall display second-order convergence for advection problems with linear interpolation solved using a linear finite volume system on a two-dimensional orthogonal mesh in cylindrical coordinate system.

    Specification(s): mms-2d-rz

    Design: LinearFVAdvectionLinearFVAdvectionDiffusionOutflowBC

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.8The system shall display second-order convergence for anisotropic diffusion problems with a central differencing scheme solved using a linear finite volume system on a two-dimensional orthogonal mesh.

    Specification(s): mms-anisotropic-diffusion-2d-orthogonal

    Design: LinearFVAnisotropicDiffusion

    Issue(s): #27280

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.9The system shall display second-order convergence for anisotropic diffusion problems with a central differencing scheme solved using a linear finite volume system on a two-dimensional nonorthogonal mesh.

    Specification(s): mms-anisotropic-diffusion-2d-nonorthogonal

    Design: LinearFVAnisotropicDiffusion

    Issue(s): #27280

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.10The system shall display second-order convergence for diffusion problems with Dirichlet boundary conditions using a linear finite volume system on a block-restricted two-dimensional orthogonal mesh.

    Specification(s): mms-diffusion

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.11The system shall display second-order convergence for advection-diffusion-reaction problems with an outflow boundary condition using a linear finite volume system on a block-restricted two-dimensional orthogonal mesh.

    Specification(s): mms-adr

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.12The system should be able to exactly solve a problem with a constant source and diffusion and reaction kernels restricted to two different subdomains.

    Specification(s): diff-react-exact

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.33.13The system shall display second-order convergence for advection-diffusion-reaction problems with Dirichlet boundary conditions using a linear finite volume system on a one-dimensional domain.

    Specification(s): mms-adr-1d-dirichlet

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.14The system shall display second-order convergence for advection-diffusion-reaction problems with an outflow boundary condition using a linear finite volume system on a one-dimensional domain.

    Specification(s): mms-adr-1d-outflow

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.15The system shall display second-order convergence for advection-diffusion-reaction problems with Dirichlet boundary conditions using a linear finite volume system on a two-dimensional orthogonal mesh.

    Specification(s): mms-adr-2d-dirichlet

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.16The system shall display second-order convergence for advection-diffusion-reaction problems with outflow boundary conditions using a linear finite volume system on a two-dimensional orthogonal mesh.

    Specification(s): mms-adr-2d-outflow

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.17The system shall display second-order convergence for diffusion problems with a central differencing scheme solved using a linear finite volume system on a one-dimensional domain.

    Specification(s): mms-diffusion-1d-cd

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.18The system shall display second-order convergence for diffusion problems with a central differencing scheme solved using a linear finite volume system on a two-dimensional orthogonal mesh.

    Specification(s): mms-diffusion-2d-orthogonal

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.19The system shall display second-order convergence for diffusion problems with a central differencing scheme solved using a linear finite volume system on a two-dimensional nonorthogonal mesh.

    Specification(s): mms-diffusion-2d-nonorthogonal

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.20The system shall display second-order convergence for diffusion problems with a central differencing scheme solved using a linear finite volume system on an orthogonal mesh in cylindrical coordinate system.

    Specification(s): mms-diffusion-2d-rz

    Design: LinearFVDiffusion

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.33.21The system shall be able to solve reaction problems using a linear finite volume system on a one-dimensional domain.

    Specification(s): reaction-1d

    Design: LinearFVReaction

    Issue(s): #25722

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Markers
  • 15.35.1The system shall include the ability to mark a mesh subdomain for uniform refinement.

    Specification(s): test

    Design: Markers System

    Issue(s): #6665

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.2The adaptivity system shall create an auxiliary field variable that marks elements for refinement adjacent to a boundary.

    Specification(s): adjacent

    Design: Markers SystemBoundaryMarker

    Issue(s): #1275#24645

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.3The adaptivity system shall create an auxiliary field variable that marks elements for refinement within a given distance of a boundary.

    Specification(s): distance

    Design: Markers SystemBoundaryMarker

    Issue(s): #1275#24645

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.4The adaptivity system shall create an auxiliary field variable that marks elements for refinement adjacent to any of a given set of boundaries.

    Specification(s): multiple

    Design: Markers SystemBoundaryMarker

    Issue(s): #1275#24645

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.5The adaptivity system shall create an auxiliary field variable that marks elements for refinement within a rectangular region.

    Specification(s): mark_only

    Design: Markers SystemBoxMarker

    Issue(s): #1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.6The adaptivity system shall adapt the mesh within a rectangular region.

    Specification(s): mark_and_adapt

    Design: Markers SystemBoxMarker

    Issue(s): #1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.7The system shall include the ability to combine multiple mesh refinement markers into a single value.

    Specification(s): test

    Design: ComboMarker

    Issue(s): #1303

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.8The system shall include the ability to mark elements within a subdomain to be unchanged for mesh adaptivity.

    Specification(s): test

    Design: Adaptivity SystemBoxMarker

    Issue(s): #1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.9The system shall include a means for setting mesh refinement flags based on percent of error for a sorted vector of error values computed for each finite element.

    Specification(s): test

    Design: Errorfractionmarker

    Issue(s): #1301

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.10The system shall include the ability to use the same error extremes during all calculations of error fraction values during mesh adaptivity.

    Specification(s): no_clear

    Design: Errorfractionmarker

    Issue(s): #9914

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.11The system shall include a means for setting mesh refinement flags based on percent of error for a sorted vector of error values computed for each finite element using FV variables

    Specification(s): fv

    Design: Errorfractionmarker

    Issue(s): #16069

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.12The system shall include a means for computing mesh refinement flags based on an absolute values of error.

    Specification(s): test

    Design: ErrorToleranceMarker

    Issue(s): #1301#1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.13The system shall include a means for performing mesh adaptivity based on an absolute values of error.

    Specification(s): adapt_test

    Design: ErrorToleranceMarker

    Issue(s): #1301#1275

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): displaced_error

    Design: Markers System

    Issue(s): #11430

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.35.15The system shall support the ability to mark elements for mesh adaptivity based on a bounding box with arbitrary orientation.

    Specification(s): obm

    Design: OrientedBoxMarker

    Issue(s): #2514

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.16The system shall support access to finite element quadrature point locations during the calculation of refinement marker flags.

    Specification(s): test

    Design: Markers System

    Issue(s): #3279

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.17The adaptivity system shall create an auxiliary field variable that marks elements containing the points from the reporter for refinement.

    Specification(s): mark_only

    Design: Markers SystemReporterPointMarker

    Issue(s): #18886

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): wrong_size_error

    Design: Markers SystemReporterPointMarker

    Issue(s): #18886

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.35.19The marker shall be used for adaptivity for a moving point, being able to coarsen elements the point moves out of but not coarsen elements if it contains point.

    Specification(s): adaptivity

    Design: Markers SystemReporterPointMarker

    Issue(s): #18886

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.35.20The system shall support the capability of creating a tool for marking finite elements for mesh refinement, for example:
    1. adding elements within the intersection of two circles;
    2. adding elements within the intersection of two circles and removing elements outside the circles; and
    3. performing adaptivity when a non-uniform initial condition is defined.

    Specification(s): group/two_circle_marker, group/two_circle_marker_coarsen, group/two_circle_marker_gaussian_ic

    Design: Markers System

    Issue(s): #8890

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.21The system shall support marking the entire finite element mesh for refinement.

    Specification(s): test

    Design: UniformMarker

    Issue(s): #1566

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.22The system shall include the ability to mark elements within a finite element mesh for adaptivity based on if the value of a variable is within a specific range.

    Specification(s): test

    Design: ValueRangeMarker

    Issue(s): #1815

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.35.23The system shall include the ability to mark elements within a finite element mesh for adaptivity based on if the value of a variable is above or below a threshold.

    Specification(s): test

    Design: ValueThresholdMarker

    Issue(s): #1313

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Minimal App
  • 15.41.1The system shall support the programmatic creation of a simulation tools without the need of an input file.

    Specification(s): minimal

    Design: MooseApp

    Issue(s): #6126

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Mortar
  • 15.43.1The system shall support the use of constrains using the mortar method in 1D.

    Specification(s): test

    Design: NodalEqualValueConstraintOneDEqualValueConstraintBC

    Issue(s): #4211

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.2We shall be able to enforce periodic boundary conditions on 3d domains using mortar constraints.

    Specification(s): 3d_periodic_mortar

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.3The system shall assemble primary/secondary AD mortar constraints coupled to scalar variables.

    Specification(s): penalty_periodic_simple2d

    Design: ADPenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.4The system shall assemble lower variable AD mortar constraints coupled to scalar variables.

    Specification(s): periodic_simple2d

    Design: ADPenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.5The system shall assemble primary/secondary AD mortar constraints coupled to 3d scalar variables.

    Specification(s): penalty_periodic_simple3d

    Design: ADPenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.6The system shall assemble lower variable AD mortar constraints coupled to 3d scalar variables.

    Specification(s): periodic_simple3d

    Design: ADPenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.7AD mortar surfaces coupled with scalar variables can handle nonuniform conductivity.

    Specification(s): penalty_periodic_checker2d

    Design: ADPenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.8The system shall assemble AD mortar constraints with multiple distinct coupled scalar variables.

    Specification(s): testperiodicsole

    Design: ADPenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.9The system shall be able to compute the gap between secondary and primary bodies using the mortar method and auxiliary kernels
    1. when the gap auxiliary variable and mesh are both first order
    2. when the gap auxiliary variable is first order and the mesh is second order
    3. when the gap auxiliary variable and mesh are both second order

    Specification(s): gap/first_order, gap/mismatched_order, gap/second_order

    Design: WeightedGapAux

    Issue(s): #20001

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.10The system shall be able to run mortar auxiliary kernels when no constraints are present in the simulation.

    Specification(s): no_constraint

    Design: WeightedGapAux

    Issue(s): #20214

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.43.11The system shall be able to construct a mortar mesh when coincident nodes exist on one or more mortar boundaries.

    Specification(s): coincident

    Design: Constraints System

    Issue(s): #21680

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.43.12We shall be able to enforce solution continuity on a conforming mesh for one variable

    Specification(s): conforming

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.13We shall be able to enforce solution gradient continuity on a conforming mesh for one variable

    Specification(s): equalgradient

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.14We shall be able to enforce solution continuity on a conforming mesh for two variables

    Specification(s): conforming_two_var

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.15We shall be able to enforce solution continuity on a conforming mesh for one variable using second order shape functions for both primal and lagrange variables. Note that this may be a relatively unstable discretization

    Specification(s): conforming-2nd-order

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.16We shall be able to produce the expected result for a solution continuity test case using the mortar method, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): soln-continuity

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.17We shall be able to produce the expected result for a solution continuity test case using the first order dual basis.

    Specification(s): dual-soln-continuity

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.18We shall be able to produce the expected result for a solution continuity test case using the second order dual basis.

    Specification(s): dual-soln-continuity-2nd-order

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.19We shall be able to produce the expected result for a fine mesh solution continuity test case using the mortar method, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): soln-continuity-fine

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.20The Jacobian for the solution continuity test case shall be perfect

    Specification(s): soln-continuity-jac

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 15.43.16

  • 15.43.21We shall be able to produce the expected result for a solution continuity test case using the Petrov-Galerkin approach for mortar.

    Specification(s): soln-continuity-pg

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.22The system shall be able to prolong and restrict stateful material properties because of mesh adaptivity in the presense of lower dimensional subdomains that do not have materials and when stateful properties are needed on boundaries (because of integrated boundary conditions)

    Specification(s): sequencing-stateful-soln-continuity

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.23We shall be able to produce the expected result for a solution continuity test case with the first order dual basis using VCP.

    Specification(s): vcp

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.24We shall be able to produce the expected result for a solution continuity test case with the second order dual basis using VCP.

    Specification(s): vcp-2nd-order

    Design: Constraints System

    Issue(s): #13080#15215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.25The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a HEX8 mesh with curved geometry, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_sphere_hex8

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.26The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a HEX20 mesh with curved geometry, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_sphere_hex20

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.27The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a HEX27 mesh with curved geometry, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_sphere_hex27

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.28The system shall generate a debug mortar mesh the parameter debug_mesh is passed to a mortar constraint

    Specification(s): continuity_sphere_hex27-debug-mesh

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.29The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a TET4 conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_tet4

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.30The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a TET10 conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_tet10

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.31The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a TET14 conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_tet14

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.32The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a TET4 non-conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_nonconforming_tet

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.33The system shall be able to produce the expected result for a solution continuity test case using the mortar method on a mesh with mixed element types, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_mixed

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.34The system shall be able to produce the expected result for a solution continuity test case using the penalty-based mortar method on a TET4 conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_penalty_tet4

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.35The system shall be able to produce the expected result for a solution continuity test case using the penalty-based mortar method on a TET10 conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_penalty_tet10

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.36The system shall be able to produce the expected result for a solution continuity test case using the penalty-based mortar method on a TET14 conforming mesh, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_penalty_tet14

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.37The system shall be able to produce the expected result for a solution continuity test case using the penalty-based mortar method on a HEX8 mesh with curved geometry, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_penalty_sphere_hex8

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.38The system shall be able to produce the expected result for a solution continuity test case using the penalty-based mortar method on a HEX20 mesh with curved geometry, e.g. the primal variable values across the mortar interface shall be the same.

    Specification(s): continuity_penalty_sphere_hex20

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.39The system shall be able to produce the same result using the penalty-based mortar method with and without automatic differentiation.

    Specification(s): continuity_penalty_sphere_hex20_ad

    Design: Constraints SystemEqualValueConstraintPenaltyEqualValueConstraint

    Issue(s): #13080#21329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.40The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 1 for a mortar solution continuity problem with conforming and non-conforming (HEX8) geometric discretization when using a first order basis for the temperature variable and a zeroth order basis for the Lagrange multiplier.

    Specification(s): p1p0

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.41The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 2 for a mortar solution continuity problem with conforming and non-conforming (HEX8) geometric discretization when using a first order basis for the temperature variable and a first order basis for the Lagrange multiplier.

    Specification(s): p1p1

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.42The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 1.5 for a mortar solution continuity problem with conforming and non-conforming (HEX8) geometric discretization when using a first order basis for the temperature variable and a first order dual basis for the Lagrange multiplier.

    Specification(s): p1p1dual

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.43The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 1 for a mortar solution continuity problem with conforming and non-conforming (HEX27) geometric discretization when using a second order basis for the temperature variable and a zeroth order basis for the Lagrange multiplier.

    Specification(s): p2p0

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.44The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 2 for a mortar solution continuity problem with conforming and non-conforming (HEX27) geometric discretization when using a second order basis for the temperature variable and a first order basis for the Lagrange multiplier.

    Specification(s): p2p1

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.45The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 3 for a mortar solution continuity problem with conforming and non-conforming (HEX27) geometric discretization when using a second order basis for the temperature variable and a second order basis for the Lagrange multiplier.

    Specification(s): p2p2

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.46The system shall be able to perform gap heat transfer to couple conduction equations, on either side of the mortar interface, discretized with the finite volume method with
    1. first order accuracy
    2. second order accuracy

    Specification(s): fv/first_order, fv/second_order

    Design: Constraints System

    Issue(s): #21599

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.47The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 3 for a mortar gap-conductance problem with equal, coarse-secondary, and coarse-primary geometric discretizations when using a second order basis for the temperature variable and a second order basis for the Lagrange multiplier.

    Specification(s): p2p2

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.48The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 2 for a mortar gap-conductance problem with equal, coarse-secondary, and coarse-primary geometric discretizations when using a second order basis for the temperature variable and a first order basis for the Lagrange multiplier.

    Specification(s): p2p1

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.49The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 1 for a mortar gap-conductance problem with equal, coarse-secondary, and coarse-primary geometric discretizations when using a second order basis for the temperature variable and a zeroth order basis for the Lagrange multiplier.

    Specification(s): p2p0

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.50The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 2 for a mortar gap-conductance problem with equal, coarse-secondary, and coarse-primary geometric discretizations when using a first order basis for the temperature variable and a first order basis for the Lagrange multiplier.

    Specification(s): p1p1

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.51The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 1 for a mortar gap-conductance problem with equal, coarse-secondary, and coarse-primary geometric discretizations when using a first order basis for the temperature variable and a zeroth order basis for the Lagrange multiplier.

    Specification(s): p1p0

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.52The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 3 for a mortar solution continuity problem with an equal geometric discretization when using a second order basis for the temperature variable and a second order basis for the Lagrange multiplier.

    Specification(s): p2p2

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.53The system shall be able to demonstrate asymptotically correct convergence rates of 3 and 2 for a mortar solution continuity problem with an equal geometric discretization when using a second order basis for the temperature variable and a first order basis for the Lagrange multiplier.

    Specification(s): p2p1

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.54The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 1 for a mortar solution continuity problem with an equal geometric discretization when using a second order basis for the temperature variable and a zeroth order basis for the Lagrange multiplier.

    Specification(s): p2p0

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.55The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 2 for a mortar solution continuity problem with an equal geometric discretization when using a first order basis for the temperature variable and a first order basis for the Lagrange multiplier.

    Specification(s): p1p1

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.56The system shall be able to demonstrate asymptotically correct convergence rates of 2 and 1 for a mortar solution continuity problem with an equal geometric discretization when using a first order basis for the temperature variable and a zeroth order basis for the Lagrange multiplier.

    Specification(s): p1p0

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 15.43.57We shall be able to couple variables between boundary auxiliary kernels and mortar constraints.

    Specification(s): gap-conductance-bnd-aux-kernel

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.58We shall be able to use boundary-restricted material properties in mortar constraints.

    Specification(s): gap-conductance-bnd-material

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.59We shall be able to do gap conductance on a dynamic mesh using auxiliary displacements, computing the residual and Jacobian
    1. separately
    2. together

    Specification(s): dynamic_mortar_gap_conductance/separate, dynamic_mortar_gap_conductance/together

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.60The Jacobian for the dynamic aux displacement gap conductance test case shall be perfect when computing the residual and Jacobian
    1. separately
    2. together

    Specification(s): dynamic_gap_jacobian/separate, dynamic_gap_jacobian/together

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.43.61We shall be able to do gap conductance on a dynamic mesh using auxiliary displacements on a fine mesh

    Specification(s): dynamic_gap_conductance_fine

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.62We shall generate the exact expected analytic solution for the gap conductance problem

    Specification(s): linear_exact_verification

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.63We shall be able to produce the expected result for a gap conductance test case using the mortar method. Specifically, this test yields lagrange multipliers that are correctly proportional to the delta of temperature across the gap, e.g. the heat flux

    Specification(s): real_mortar_gap_conductance

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.64The Jacobian for the gap conductance test case shall be perfect

    Specification(s): gap_jacobian

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 15.43.63

  • 15.43.65We shall be able to produce the expected result for a gap conductance test case using the mortar method on a fine mesh. Specifically, this test yields lagrange multipliers that are correctly proportional to the delta of temperature across the gap, e.g. the heat flux

    Specification(s): gap_conductance_fine

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.66The system shall give access to the locations in physical space of mortar segment element quadrature points.

    Specification(s): exo

    Design: Constraints System

    Issue(s): #16177

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.67The system shall compute an exact Jacobian for a simulation involving the physical space location of mortar quadrature points.

    Specification(s): jac

    Design: Constraints System

    Issue(s): #16177

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.43.68We shall be able to enforce periodic boundary conditions on a non-uniform mesh using the mortar method

    Specification(s): exo

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.43.69The Jacobian for mortar enforcement of periodic boundary conditions shall be perfect

    Specification(s): jac

    Design: Constraints System

    Issue(s): #13080

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.43.70The system shall assemble primary/secondary mortar constraints coupled to scalar variables in a two dimensional problem.

    Specification(s): penalty_periodic_simple2d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.71The penalty periodic segmental constraint is independent of the designation of primary and secondary surfaces.

    Specification(s): periodic_simple2d_flip

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.72The system shall assemble lower dimensional variable mortar constraints coupled to scalar variables in a two dimensional problem.

    Specification(s): periodic_simple2d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.73The system shall assemble primary/secondary mortar constraints coupled to scalar variables in a three dimensional problem.

    Specification(s): penalty_periodic_simple3d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.74The system shall assemble lower variable mortar constraints coupled to scalar variables in a three dimensional problem.

    Specification(s): periodic_simple3d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.75The system shall allow field split preconditioning with scalar variables and produce the same results as a non-split linear solve.

    Specification(s): penalty_periodic_split

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.76The coupled scalar variable for mortar surfaces can be an auxiliary variable for debugging.

    Specification(s): periodic_aux2d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.77Mortar surfaces coupled with scalar variables can handle nonuniform conductivity.

    Specification(s): penalty_periodic_checker2d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.78Mortar surfaces coupled with scalar variables can handle nonuniform conductivity using Lagrange multipliers.

    Specification(s): periodic_checker2d

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.79The system shall be able to assemble mortar constraints with multiple distinct coupled scalar variables.

    Specification(s): testperiodicsole

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.43.80The system shall report an error if a nonlinear variable is applied for sigma instead of an auxiliary variable.

    Specification(s): auxiliary

    Design: PenaltyPeriodicSegmentalConstraint

    Issue(s): #22174

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • rdg: Nodalkernels
  • 15.45.1The system shall include ability to include contributions to the residual nodes of a finite element mesh
    1. on a single and
    2. multiple threads.

    Specification(s): group/test, group/threaded

    Design: NodalKernels System

    Issue(s): #3029

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.2The system shall be able to enforce a lower bound on a variable using nodal NCP, nodal application of resultant forces,
    1. have no oscillations in the solution, and
    2. have a non-singular matrix

    Specification(s): lower_bound/exo, lower_bound/non_singular

    Design: LowerBoundNodalKernel

    Issue(s): #2999

    Collection(s): FUNCTIONAL

    Type(s): ExodiffRunApp

  • 15.45.3The system shall be able to enforce an upper bound on a variable using nodal NCP, nodal application of resultant forces,
    1. have no oscillations in the solution, and
    2. have a non-singular matrix

    Specification(s): upper_bound/exo, upper_bound/non_singular

    Design: UpperBoundNodalKernel

    Issue(s): #2999

    Collection(s): FUNCTIONAL

    Type(s): ExodiffRunApp

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

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

    Design: UpperBoundNodalKernel

    Issue(s): #2999

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): ExodiffRunExceptionRunApp

  • 15.45.5The system shall be able to enforce an upper and lower bound on a variable using a variational inequality
    1. reduced space active set solver, which
    2. is compatible with algebraic multigrid, and
    3. a semi-smooth solver, which
    4. is also compatible with algebraic multigrid
    5. The reduced space active set method shall work with a matrix-free approximation of the Jacobian, and the function evaluations corresponding to the nonlinear residual and the base for finite-differencing shall be equivalent.

    Specification(s): vi/rsls, vi/rsls_amg, vi/ssls, vi/ssls_amg, vi/rsls_pjfnk

    Design: ConstantBounds

    Issue(s): #2999

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.6The system shall show violation of bounds when a non-variational-inequality solver is used

    Specification(s): unbounded

    Design: ConstantBounds

    Issue(s): #2999

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.7The system shall support the use of Crank-Nicolson time integration scheme.

    Specification(s): test

    Design: TimeIntegrator System

    Issue(s): #3029#5883#5949

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.8The system shall include ability to include contributions to the residual nodes of a finite element mesh using an LU preconditioner.

    Specification(s): test

    Design: NodalKernels System

    Issue(s): #3029#10620

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.9The system shall include ability to include contributions to the residual nodes of a finite element mesh and compute the correct Jacobian terms for
    1. subdomain and
    2. boundary restricted terms.

    Specification(s): group/block_jacobian_test, group/bc_jacobian_test

    Design: NodalKernels System

    Issue(s): #3029#10620

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.45.10The system shall not duplicate computation of kernels on a node that is shared between two subdomains.

    Specification(s): exo

    Design: NodalKernels System

    Issue(s): #16265

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.11The system shall support the application of Dirichlet type boundary conditions using the penalty method for nodesets.

    Specification(s): test

    Design: PenaltyDirichletNodalKernel

    Issue(s): #14092

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.45.12The system shall apply scaling to residuals and Jacobians for volumetric PDE terms applied at nodes

    Specification(s): scaling

    Design: NonlinearSystem

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Parser
  • 15.47.1The system shall support active/inactive parameters to selectively enable/disable subblocks within all input file blocks.

    Specification(s): inactive_active

    Design: Parser

    Issue(s): #9411#9571

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.2The system shall produce an error when the active parameter refers to a non-exiseant block.

    Specification(s): active_section_missing

    Design: Parser

    Issue(s): #9411#9571

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): inactive_section_missing

    Design: Parser

    Issue(s): #9411#9571

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): inactive_active_combo

    Design: Parser

    Issue(s): #9411#9571

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): top_level

    Design: Parser

    Issue(s): #9411#9571

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.47.6The system shall support the ability to override input file parameters from the command line.

    Specification(s): test

    Design: CommandLine

    Issue(s): #581

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.7The system shall support the ability to globally change MultiApp input file syntax from the command line.

    Specification(s): cli_override_all

    Design: CommandLine

    Issue(s): #2137

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.8The system shall support the ability to change a whole MultiApp's (multiple SubApps) input file syntax from the command line.

    Specification(s): cli_override_group

    Design: CommandLine

    Issue(s): #2137

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.9The system shall support the ability to change individual SubApp input file syntax from the command line.

    Specification(s): cli_override_single

    Design: CommandLine

    Issue(s): #2137

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): cli_override_error_check

    Design: CommandLine

    Issue(s): #2137

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 15.47.9

  • 15.47.11The system shall output all registered objects in HIT format.

    Specification(s): hit_registry

    Design: MooseApp

    Issue(s): #10952

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.47.12The system shall output all registered objects in single line format.

    Specification(s): registry

    Design: MooseApp

    Issue(s): #10952

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): error

    Design: InputParameters

    Issue(s): #16410

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.47.14The system shall support including other input files in an input file

    Specification(s): include

    Design: Parser

    Issue(s): #9755#20125

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.15The system shall be able to read input file syntax and write into map parameters.

    Specification(s): test

    Design: Parser

    Issue(s): #14894

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): odd_entries

    Design: Parser

    Issue(s): #14894

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bad_value

    Design: Parser

    Issue(s): #14894

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: Parser

    Issue(s): #17989#18221

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): ExodiffRunExceptionRunApp

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

    Specification(s): no_file

    Design: Parser

    Issue(s): #17989#18221

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): dup_check

    Design: Parser

    Issue(s): #25994

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.47.21The system shall support parameter substitution in input files using command line variable expressions.

    Specification(s): param_substitution_cli

    Design: Parser

    Issue(s): #5649

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.22The system shall support parameter substitution in input files using variable expressions from within the same input file.

    Specification(s): param_substitution_in_file

    Design: Parser

    Issue(s): #5649

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.47.21

  • 15.47.23The system shall support unit conversion in input files using variable expressions.

    Specification(s): unit_conversion

    Design: Parser

    Issue(s): #14827

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.47.24The system shall report the unit conversions performed at parse time when running in debug mode.

    Specification(s): debug_units

    Design: Parser

    Issue(s): #25362

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.47.25The system shall support reading in jagged double-indexed arrays from the input file using two delimiters for columns and rows respectively.

    Specification(s): parse_double_index

    Design: Parser

    Issue(s): #6442

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.47.26The system shall support reading in jagged triple-indexed arrays from the input file using two delimiters for columns and rows respectively.

    Specification(s): parse_triple_index

    Design: Parser

    Issue(s): #21930

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.47.27The system shall support reading in a vector of size-3 vectors.

    Specification(s): parse_vector_value

    Design: Parser

    Issue(s): #24337

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): parse_vector_value_error

    Design: Parser

    Issue(s): #24337

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.47.29The system shall support vectors of MultiMooseEnums as input parameters.

    Specification(s): vmme

    Design: InputParameters

    Issue(s): #28487

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): vmme_empty

    Design: InputParameters

    Issue(s): #28487

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): vmme_invalid

    Design: InputParameters

    Issue(s): #28487

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: InputParameters

    Issue(s): #3988

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: InputParameters

    Issue(s): #3988

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): outofbounds

    Design: InputParameters

    Issue(s): #3988

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): checkempty

    Design: InputParameters

    Issue(s): #3988

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • rdg: Phi Zero
  • 15.50.1The system shall be able to construct zero objects for shape functions and shape function gradients consistent with the maximum number ofshape functions and quadrature points in the simulation.

    Specification(s): phi_zero_linear

    Design: PhiZero

    Issue(s): #15204

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.50.2The system shall be able to construct zero objects for shape functions and shape function gradients consistent with the maximum number ofshape functions and quadrature points in the simulation. This test checks the size of zero objects when using second-order elements and second order-variables.

    Specification(s): phi_zero_quadratic

    Design: PhiZero

    Issue(s): #15204

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 15.50.1

  • rdg: Physics
  • 15.51.1The system shall error if the physics is specified as a transient, when the executioner is designed for steady solves.

    Specification(s): fv

    Design: Physics system

    Issue(s): #25642

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.51.2The system shall be able to solve a source-less diffusion equation with a continuous Galerkin discretization with a shorthand syntax.

    Specification(s): cg

    Design: DiffusionCG

    Issue(s): #25642

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.51.3The system shall be able to solve a source-less diffusion equation with a continuous Galerkin discretization with automatic differentiation with a shorthand syntax.

    Specification(s): cg_ad

    Design: DiffusionCG

    Issue(s): #25642

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.51.4The system shall be able to solve a source-less diffusion equation with a cell-centered finite volume discretization with a shorthand syntax.

    Specification(s): fv

    Design: DiffusionFV

    Issue(s): #25642

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • rdg: Positions
  • 15.52.1The system shall be able to create multiapps from positions objects.

    Specification(s): test

    Design: Positions

    Issue(s): #23587

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.52.2The system shall be able to create multiapps from positions objects using their initial positions.

    Specification(s): initial_positions

    Design: Positions

    Issue(s): #23587

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

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

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

    Design: Positions

    Issue(s): #23587

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.52.4The system shall be able to load positions from
    1. a parameter in the input file,
    2. a text file,
    3. element centroids from a mesh, with or without block restriction,
    4. default element quadrature points from a mesh, with or without block restriction,
    5. centroids of groups of elements in the mesh,
    6. a reporter with data in the expected vector of points format,
    7. triplets on functors that are evaluated to obtain positions,
    8. one or more multiapp positions,
    9. and one or more multiapp mesh centroids.

    Specification(s): test/input, test/file, test/mesh_elements, test/mesh_quadrature_points, test/blocks_and_extra_ids, test/reporter, test/functors, test/multiapps, test/multiapps_centroids

    Design: Positions

    Issue(s): #23587

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.52.5The system shall be able to perform
    1. simple linear operations such as scaling, translation and rotation to positions, and
    2. a distribution, through translations, of positions from one set of positions onto another.

    Specification(s): operations/transform, operations/distribution

    Design: Positions

    Issue(s): #23587

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • rdg: Preconditioners
  • 15.54.1The system shall support the disabling of an automatically created preconditioning object when performing a Newton solve.

    Specification(s): manual

    Design: CreateExecutionerAction

    Issue(s): #13411

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.2The system shall automatically create the correct preconditioning object when performing a Newton solve.

    Specification(s): auto

    Design: CreateExecutionerAction

    Issue(s): #13411

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.54.1

  • 15.54.3The system shall output the PETSc preconditioner type requested in the executioner options.

    Specification(s): petsc_pre_description

    Design: CreateExecutionerAction

    Issue(s): #13411

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.54.2

  • 15.54.4The system shall produce a perfect coloring for the Jacobian when using the finite difference preconditioner.

    Specification(s): jacobian_fdp_coloring_full_test

    Design: FDP

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 15.54.5The system shall produce a perfect Jacobian when using the stadard finite difference preconditioner.

    Specification(s): jacobian_fdp_standard_test

    Design: FDP

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

    Prerequisite(s): 15.54.4

  • 15.54.6The system shall detect missing off-diagonal Jacobian entries when using a full finite different preconditioner.

    Specification(s): jacobian_fdp_coloring_diagonal_test_fail

    Design: FDP

    Issue(s): #13232

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

    Prerequisite(s): 15.54.5

  • 15.54.7The system shall support the use of field split preconditioner on
    1. a single subdomain and
    2. multiple subdomains.
    3. vector variables
    4. array variables

    Specification(s): group/test, group/fsp_image, group/vector, group/array

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.8The system shall report an error if a user has forgotten a variable in their field splits.

    Specification(s): missing_var_in_split

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.54.9The system shall support nested field splits.

    Specification(s): nested

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): nested_error

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.54.11The system shall be able to selectively remove degrees of freedom from a field spit by variable by boundary.

    Specification(s): unside_by_var

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.12The system shall support the use of HMG (high performance MG)

    Specification(s): hmg

    Design: HMG

    Issue(s): #16210

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.13The system shall support the use of HMG (high performance MG) for 3D problems

    Specification(s): hmg_3D

    Design: HMG

    Issue(s): #16210

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.14The system shall support the use of strumpack (sparse direct solver) for 3D problems

    Specification(s): hmg_strumpack

    Design: HMG

    Issue(s): #16501

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.15The system shall support the ability to use multiple cycles within hypre during preconditioning with PETSc.

    Specification(s): test

    Design: Preconditioning System

    Issue(s): #1048

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.16The system shall support the use of a physics based preconditioner
    1. without and
    2. with mesh adaptivity.

    Specification(s): pbp/test, pbp/pbp_adapt_test

    Design: PBP

    Issue(s): #1048#18777

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.17The system shall support the ability to add arbitrary options to the solver when using a physics based precondioner.

    Specification(s): check_petsc_options_test

    Design: PBP

    Issue(s): #1048#18777

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.54.18The system shall support the ability to control the variable solve order when using a physics base preconditioner.

    Specification(s): lots_of_variables

    Design: PBP

    Issue(s): #1048#18777

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.19The system shall support the ability to use the conjugate gradient method for preconditioning with PETSc.

    Specification(s): test

    Design: Preconditioning System

    Issue(s): #8681

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.20Convergence matches previous version of MOOSE without the preconditioner reuse system

    Specification(s): without_reuse

    Design: NonlinearSystem

    Issue(s): #21868

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.54.21Preconditioner is reused until the linear iterations exceed the value of reuse_preconditioner_max_its upon which the system recalculates the preconditioner

    Specification(s): with_reuse

    Design: NonlinearSystem

    Issue(s): #21868

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.54.22A new preconditioner is formed if the system of equations changes for example here through mesh refinement

    Specification(s): mesh_refinement

    Design: NonlinearSystem

    Issue(s): #21868

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.54.23The system shall support the use of a single matrix preconditioner
    1. without and
    2. with mesh adaptivity.

    Specification(s): smp/smp_test, smp/smp_adapt_test

    Design: SMP

    Issue(s): #1048

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.24The system shall support the ability to group variables when using a single matrix preconditioner.

    Specification(s): smp_group_test

    Design: SMP

    Issue(s): #1048

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.54.25The system shall converge when using the VCP interface with AMG as the preconditioner.

    Specification(s): condense_amg_test

    Design: VCP

    Issue(s): #15215

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.54.26The system shall converge while computing the full inverse of the coupling matrix.

    Specification(s): condense_amg_test_dinv

    Design: VCP

    Issue(s): #15215

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.54.27The system shall converge while using LU as the solver.

    Specification(s): no-condense_amg_test

    Design: VCP

    Issue(s): #15215

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • rdg: Problems
  • 15.56.1The system shall allow the creation of a custom problem through a user-defined Action.

    Specification(s): no_problem_block

    Design: Problem system overview

    Issue(s): #12002

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.2The system shall support the creation of a custom problem with parameters in Problem block.

    Specification(s): with_problem_block_without_type

    Design: Problem system overview

    Issue(s): #12002

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.3The system shall report an error when Problem block type is not specified.

    Specification(s): with_problem_block_with_wrong_type

    Design: Problem system overview

    Issue(s): #12002

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.4The system shall support the creation of a custom problem through Problem block with type specified.

    Specification(s): with_problem_block_with_type

    Design: Problem system overview

    Issue(s): #12002

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.5The system shall support the ability to extend the basic "Problem" interface.

    Specification(s): test

    Design: Problem system overview

    Issue(s): #12060

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.6The system shall have a capability to dump the equivalent input file syntax for all objects added by a given action.

    Specification(s): add_mat_and_kernel

    Design: DumpObjectsProblem

    Issue(s): #8875

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.7The system shall have a capability to dump the equivalent input file syntax for all objects created by the problem.

    Specification(s): add_all

    Design: DumpObjectsProblem

    Issue(s): #8875

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.8The system shall include the support for Eigen value calculations that utilize
    1. an array of residual contributions;
    2. multiple variables; and
    3. multiple variables with Eigen values include in preconditioning matrix.

    Specification(s): eigen/array_kernel, eigen/two_variables, eigen/two_variables_precond_include_eigen_kernels

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.9Eigenvalue system should support standard eigenvalue problems

    Specification(s): test

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.10Eigenvalue system should support generalized eigenvalue problems

    Specification(s): gipm_test

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.11Eigenvalue system should support IntegratedBC

    Specification(s): gipm_ibc

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): wrong_dirichlet_value_eigen

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.13Eigenvalue system should use homogeneous boundary conditions only

    Specification(s): wrong_NodalBC_type_eigen

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.14Eigenvalue system requires SLEPc installed

    Specification(s): no_slepc

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.15Eigenvalue system should be able to solve a nonlinear eigenvalue problem

    Specification(s): nonlinear_power

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.16Eigenvalue system should be able to solve a nonlinear eigenvalue problem using Newton

    Specification(s): monolith_newton

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.17The system shall be able to solve nonlinear eigenvalue problems with hanging node constraints.

    Specification(s): nonlinear_hanging_nodes

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.18Eigenvalue system should be able to solve a deficient eigenvalue problem

    Specification(s): ne_deficient

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.19Eigenvalue system should be able to compute a nonlinear eigenvalue problem

    Specification(s): nonlinear_laplace

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.20Eigenvalue system should be able to compute a coupled nonlinear eigenvalue problem

    Specification(s): coupled_system

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.21Eigenvalue system should be able to handle scalar kernels

    Specification(s): eigen_scalar_kernel

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.22Eigenvalue system should be able to handle DG kernels

    Specification(s): dg_krylovschur

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.23Eigenvalue system shall support Picard iteration using eigenvalue executioner as a parent.

    Specification(s): eigen_as_parent

    Design: Eigenvalue

    Issue(s): #15513

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.24Eigenvalue system shall support Picard iteration using eigenvalue executioner as a parent and output eigen vectors as an exodus file.

    Specification(s): eigen_as_parent_exodus

    Design: Eigenvalue

    Issue(s): #15513

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.56.23

  • 15.56.25Eigenvalue system shall support Picard iteration using eigenvalue executioner as a sub app.

    Specification(s): eigen_as_sub

    Design: Eigenvalue

    Issue(s): #15513

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.26Eigenvalue system shall support Picard iteration using eigenvalue executioner as a sub app and output eigen vectors as an exodus file.

    Specification(s): eigen_as_sub_exodus

    Design: Eigenvalue

    Issue(s): #15513

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 15.56.25

  • 15.56.27Eigenvalue system should be able scale eigenvector such that postprocessor is a certain value

    Specification(s): scaled_eigenvector

    Design: Eigenvalue

    Issue(s): #14500

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.28The system shall be able to automatically condition a nonlinear eigen-solve based on diagonal entries in the preconditioning matrix.

    Specification(s): coupled-system-auto-scaling

    Design: Eigenvalue

    Issue(s): #15048

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.29The system shall be able to automatically scale a nonlinear eigen-solve based on entries in the non-eigen residual vector.

    Specification(s): coupled-system-resid-auto-scaling

    Design: Eigenvalue

    Issue(s): #15048

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): error_eigen_non_generalized

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.31The system shall provide an initial guess to Newton if users request.

    Specification(s): newton_intial_guess

    Design: Eigenvalue

    Issue(s): #15513#12767#14292

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.32The system shall support eigenvalue execution without free power iterations.

    Specification(s): newton_no_free_power

    Design: Eigenvalue

    Issue(s): #17026

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.33The system shall provide an option to output the eigenvalue as its inverse.

    Specification(s): inverse_eigenvalue_postprocessor

    Design: Eigenvalue

    Issue(s): #15513#12767#14292

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.34The system shall provide an option to output the eigenvalue on screen as its inverse.

    Specification(s): output_inverse_eigenvalue

    Design: Eigenvalue

    Issue(s): #15513#12767#14292

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.35The system shall support extra power iterations.

    Specification(s): extra_power_iterations

    Design: Eigenvalue

    Issue(s): #15513#12767#14292

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.36The system shall support extra power iterations and check eigenvalue.

    Specification(s): extra_power_iterations_csv

    Design: Eigenvalue

    Issue(s): #15513#12767#14292

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.56.35

  • 15.56.37The system shall support eigenvalue calculations with an initial condition including the initial solution vector and the initial eigenvalue.

    Specification(s): newton_with_exact_initialization

    Design: Eigenvalue

    Issue(s): #20454

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.38The system shall support eigenvalue calculations with an initial condition set by restarting a checkpoint file.

    Specification(s): restart

    Design: Eigenvalue

    Issue(s): #27621

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 15.56.31

  • 15.56.39The system shall support use of matrix-vector multiplication as residual evaluation for eigenvalue calculations

    Specification(s): ne_array_mo

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.40The system shall support use of matrix-vector multiplication as residual evaluation for eigenvalue calculations when hanging nodes (constraints) are present.

    Specification(s): ne_array_hanging_nodes

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.41The system shall support evaluation of auxiliary variables on linear with the matrix-only eigenvalue solve type

    Specification(s): ne_mo_with_linear_aux

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.42The system shall support use of matrix-vector multiplication as residual evaluation for eigenvalue calculations with constant matrices

    Specification(s): const_mats

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.56.39

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

    Specification(s): check_solve_type

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 15.56.42

  • 15.56.44The system shall support use of matrix-vector multiplication as residual evaluation for coupled eigenvalue problems

    Specification(s): ne_coupled_mo

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.45The system shall support use of matrix-vector multiplication with full-coupled matrices (by default) as residual evaluation for coupled eigenvalue problems

    Specification(s): ne_coupled_mo_full

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.56.44

  • 15.56.46The system shall support use of matrix-vector multiplication as residual evaluation for non-homogeneous problems

    Specification(s): non-homogeneous

    Design: Eigenvalue

    Issue(s): #18493#21056

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.47Eigen solver should work with a physics-based preconditioner

    Specification(s): newton_pbp

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.48The system shall support a physics-based preconditioner with using JFNK

    Specification(s): JFNK_pbp

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.56.47

  • 15.56.49Eigen solver should work with a physics-based preconditioner with a shell preconditioning matrix

    Specification(s): newton_pbp_shell_precond

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.56.48

  • 15.56.50Eigen solver should work with a physics-based preconditioner with a PETSc shell matrix

    Specification(s): newton_pbp_shell_precond_shell_matrix

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 15.56.49

  • 15.56.51Eigen solver should work with a physics-based preconditioner with including eigen kernels in the preconditioning matrix

    Specification(s): newton_pbp_precond_include_eigen_kernels

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 15.56.49

  • 15.56.52The system shall support an code coupling interface that can trigger external solves.

    Specification(s): external_steady

    Design: ExternalProblem

    Issue(s): #12024

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.53The system shall support an code coupling interface that can trigger external solves for transient simulations.

    Specification(s): external_transient

    Design: ExternalProblem

    Issue(s): #12024

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.54The system shall be able to update the ghosted auxiliary solution from an externally defined problem such that there will be up-to-date solution values in objects like
    1. auxiliary kernels
    2. postprocessors

    Specification(s): update_ghosted_aux_soln/auxkernels, update_ghosted_aux_soln/pps

    Design: ExternalProblem

    Issue(s): #17534

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.55The system shall support different coordinate systems on different subdomains within the mesh.

    Specification(s): test

    Design: Problem system overview

    Issue(s): #1216

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.56The system shall support the ability to disable the check for PDE operators in all or some parts of the domain.

    Specification(s): no_coverage_check

    Design: Problem system overview

    Issue(s): #2291

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.57The system shall support the ability to limit the check for active kernels to only some parts of the domain.

    Specification(s): kernel_coverage_only_list

    Design: Problem system overview

    Issue(s): #28117

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.58The system shall support the ability to disable the check for active kernels in some parts of the domain.

    Specification(s): kernel_coverage_skip_list

    Design: Problem system overview

    Issue(s): #28117

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.59The system shall support the ability to disable the check for active materials in all parts of the domain.

    Specification(s): no_material_coverage_check

    Design: Problem system overview

    Issue(s): #5306

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.60The system shall support the ability to enable the check for active materials only in some parts of the domain.

    Specification(s): material_coverage_only_list

    Design: Problem system overview

    Issue(s): #28117

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.61The system shall support the ability to disable the check for active materials in some parts of the domain.

    Specification(s): material_coverage_skip_list

    Design: Problem system overview

    Issue(s): #28117

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.62The system shall support the ability to disable the check for the existence of all dependent properties within a domain.

    Specification(s): test

    Design: Problem system overview

    Issue(s): #5306

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.63The system shall have the ability to disable the actual nonlinear system solve in a simulation.

    Specification(s): test

    Design: Problem system overview

    Issue(s): #1978

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): eigen_problem_solve_fail

    Design: Problem system overview

    Issue(s): #27084

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.65The system shall have the ability to disable the nonlinear-eigen system solve in a simulation.

    Specification(s): eigen_problem_skip_solve

    Design: Problem system overview

    Issue(s): #27084

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 15.56.64

  • 15.56.66The system shall have the ability to base convergence on the comparison of individual variables to reference quantities of those variables.

    Specification(s): base

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): scaled_bad

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.68The system shall have the ability to automatically scale a originally poorly scaled problem and achieve convergence based on individual reference quantities

    Specification(s): scaled_good

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.56.69The system shall have the ability to base system convergence on the convergence of a subset of variables.

    Specification(s): converge_on

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): converge_on_group_error

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.71The system shall support wildcards for choosing the variables to base convergence on.

    Specification(s): wildcard

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.72The system shall have the ability to base convergence on the comparison of L2 normalization of the residual for individual variables to the sum of the L2 normalization of the absolute value of the residual contributions of those variables.

    Specification(s): abs_ref

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.73The system shall have the ability to base convergence on the comparison of L2 normalization of the residual for individual variables to the sum of the L2 normalization of the absolute value of the residual contributions of those variables using an acceptable tolerance past a given number of nonlinear iterations.

    Specification(s): abs_ref_acceptable

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.56.74The system shall have the ability to base convergence on the comparison of L2 normalization of the residual for individual variables locally divided by the absolute value of the residual contributions of those variables.

    Specification(s): local_normalization

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.75The system shall have the ability to base convergence on the comparison of Linf normalization of the residual for individual variables locally divided by the absolute value of the residual contributions of those variables.

    Specification(s): local_linf_normalization

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.76The system shall have the ability to base convergence on the comparison of Linf normalization of the residual for individual variables to the sum of the Linf normalization of the absolute value of the residual contributions of those variables.

    Specification(s): linf_normalization

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.77The system shall have the ability to base convergence on the comparison of L2 normalization of the residual for individual variables to the sum of the L2 normalization of the absolute value of the residual contributions of those variables using AD.

    Specification(s): ad_abs_ref

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.56.78The system shall have the ability to default to the traditional convergence checks if no reference vector is provided in ReferenceResidualProblem.

    Specification(s): no_ref

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): zero_tolerance_ref

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.80The system shall treat convergence with a zero reference residual value as converged if the residual is below the relative tolerance.

    Specification(s): zero_rel_tolerance_ref

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

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

    Design: ReferenceResidualProblem

    Issue(s): #9151

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.56.82The system shall be able to output to console which object it is creating.

    Specification(s): test

    Design: Problem system overview

    Issue(s): #25853

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • rdg: Quadrature
  • 15.57.1The system shall support the use of Gauss-Lobatto quadrature for numerical integration.

    Specification(s): gauss_lobatto

    Design: Quadrature System

    Issue(s): 8f90ad2609945db87dc89c5e06a5a1554eb8f4a6

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.57.2The system shall support the ability to manually increase the quadrature order used for numerical integration on the entire mesh.

    Specification(s): order3

    Design: Quadrature System

    Issue(s): #3380

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.57.3The system shall support the ability to manually specify the quadrature order used for numerical integration on a per-block basis with face quadrature between blocks preferring the higher-order between the two sides.

    Specification(s): per-block-order

    Design: Quadrature System

    Issue(s): #14055

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.57.4The system shall ensure that for per-block specified quadrature orders exactly one order is given per specified block.

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

    Design: Quadrature System

    Issue(s): #24820

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.57.5The system shall support the ability for objects to increase quadrature order in code during runtime.

    Specification(s): code-order-bump

    Design: Quadrature System

    Issue(s): #14055

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.57.6The system shall support the ability to control the volumetric and side quadrature orders used for numerical integration on the entire mesh.

    Specification(s): elem5_side7

    Design: Quadrature System

    Issue(s): #3380

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.57.7The system shall support the ability to allow object code to increase the quadrature order used for numerical integration on a per-block basis.

    Specification(s): material-bumps-block-order

    Design: Quadrature System

    Issue(s): #14055#15072

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.57.8The system shall support the ability to force positive quadrature weights.

    Specification(s): weights

    Design: SetupQuadratureAction

    Issue(s): #19066

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Relationship Managers
  • 15.58.1The CouplingFunctorCheckAction shall add a default coupling functor if it's needed and hasn't already been added by another Action

    Specification(s): run

    Design: RelationshipManager

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.58.2The system shall be able to indicate when libMesh Ghosting Functors are in use.

    Specification(s): test

    Design: RelationshipManager

    Issue(s): #13206

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.58.3The system shall ghost additional solution information when running in parallel with an active RelationshipManager

    Specification(s): evaluable_neighbors_replicated

    Design: RelationshipManager

    Issue(s): #10455#11981

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.58.4The system shall ghost additional neighboring elements surrounding a partition when running in parallel with DistributedMesh

    Specification(s): edge_neighbor

    Design: RelationshipManager

    Issue(s): #10455#11981

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.58.5The system shall ghost additional neighboring elements surrounding a partition when running in parallel with DistributedMesh with 3D

    Specification(s): edge_neighbor_3D

    Design: RelationshipManager

    Issue(s): #10455#11981

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.58.6The system shall be able to ghost elements for algebraic relationships.

    Specification(s): all_systems_evaluable

    Design: RelationshipManager

    Issue(s): #14536

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.58.7The system shall ghost additional neighboring elements without also supplying solution information when a developer registers a RelationshipManager with an optional second argument to restrict functionality

    Specification(s): geometric_edge_neighbor

    Design: RelationshipManager

    Issue(s): #10455

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.58.8The system shall ghost additional neighboring elements without also supplying solution information when a developer registers a RelationshipManager with an optional second argument to restrict functionality in 3D

    Specification(s): geometric_edge_neighbor_3D

    Design: RelationshipManager

    Issue(s): #10455

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.58.9The system shall not add a relationship manager ghosting boundaries that are a subset of the boundaries ghosted by another relationship manager.

    Specification(s): test

    Design: RelationshipManager

    Issue(s): #28330

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.58.10The system shall allow multiple active objectsto manage ghosting for the same object using
    1. replicated and
    2. distributed parallelism of the mesh.

    Specification(s): evaluable_neighbors/replicated, evaluable_neighbors/distributed

    Design: RelationshipManager

    Issue(s): #10455#11981

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • rdg: Reporters
  • 15.59.1The system shall be able to accumulate reporter values over time steps into a vector reporter value.

    Specification(s): accumulate_reporter

    Design: AccumulateReporter

    Issue(s): #18469#20467

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.2The system shall have a system for computing and retrieving aggregate values of arbitrary type.

    Specification(s): base

    Design: Reporter System

    Issue(s): #11323

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.59.3The system shall report an error if an invalid name is provided when retrieving aggregate value.

    Specification(s): error

    Design: Reporter System

    Issue(s): #11323

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: Reporter System

    Issue(s): #11323

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.59.5The system shall support the mixing of computing and retreiving aggregate values of arbitrary types with the Postprocessor and VectorPostprocessor system.

    Specification(s): special_types

    Design: Reporter System

    Issue(s): #11323

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 15.59.6The system shall be able to produce arbitrary integer, real number, dof_id_types and string scalar/vector values for use in other calculations.

    Specification(s): constant_reporter

    Design: ConstantReporter

    Issue(s): #16055#20467

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

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

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

    Design: ConstantReporter

    Issue(s): #16055#20467

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.59.8The system shall output aggregate simulation information to JSON format
    1. when the aggregate value is declared after object construction
    2. and with other values declared at construction time.

    Specification(s): declareInitialSetup/initialSetup_only, declareInitialSetup/initialSetup_with_info

    Design: Reporter SystemJSON

    Issue(s): #16584

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.9The system shall support getting a reference to an aggregate calculation before it is created.

    Specification(s): decalareInitialSetup_with_get

    Design: Reporter SystemJSON

    Issue(s): #17468

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.10The system shall be able to produce elememental statistics of a variable for use in other calculations.

    Specification(s): elem_stats

    Design: ElementVariableStatistics

    Issue(s): #24678

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.11The system shall be able to report the variable integral parsed by extra IDs to the JSON format:
    1. single variable integral with single extra ID
    2. single variable integral with multiple extra IDs
    3. multiple variable integrals with multiple extra IDs

    Specification(s): test/default, test/multi_ids, test/multi_ids_multi_vars

    Design: ExtraIDIntegralReporter

    Issue(s): #19617

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.12The system shall include the ability to report iteration information:
    1. that outputs all information be default;
    2. that outputs specific information;
    3. automatically disables items based on execution;

    Specification(s): info/default, info/limit, info/steady

    Design: IterationInfo

    Issue(s): #11323

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.13The system shall include the ability to report mesh information:
    1. that outputs all information be default and
    2. that outputs specific information.

    Specification(s): info/default, info/limit

    Design: MeshInfo

    Issue(s): #11323#16886#16887

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.14The system shall support the output of mesh metadata in a human-readable form.

    Specification(s): test

    Design: MeshMetaDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.15The system shall be able to produce nodal statistics of a variable for use in other calculations.

    Specification(s): nodal_stats

    Design: NodalVariableStatistics

    Issue(s): #24678

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.16The system shall include the ability to report performance information
    1. in JSON format
    2. and shall provide a tool to post process said information

    Specification(s): test/run, test/verify

    Design: PerfGraphReporter

    Issue(s): #16256

    Collection(s): FUNCTIONAL

    Type(s): RunCommandRunApp

  • 15.59.17The system shall include the ability to serialize report performance information with the recover system

    Specification(s): recover_initial

    Design: PerfGraphReporter

    Issue(s): #16256

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.59.18The system shall include the ability to report performance information from a recovered solve
    1. in JSON format
    2. and shall provide a tool to post process said information

    Specification(s): recover/run, recover/verify

    Design: PerfGraphReporter

    Issue(s): #16256

    Collection(s): FUNCTIONAL

    Type(s): RunCommandRunApp

    Prerequisite(s): 15.59.17

  • 15.59.19The system shall support the output of restartable data in a human-readable form.

    Specification(s): test

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.20The system shall support excluding names when outputting restartable data in a human-readable form.

    Specification(s): exclude

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.21The system shall support omitting data values for data that is missing an output method when outputting restartable data in human-readable form.

    Specification(s): allow_unimplemented

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

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

    Specification(s): unimplemented_error

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.59.23The system shall support a detailed output including state flags when outputting restartable data in a human-readable form.

    Specification(s): detailed

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 15.59.24The system shall support the output of restartable meta data in a human-readable form.

    Specification(s): map

    Design: RestartableDataReporter

    Issue(s): #26304

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • rdg: Restrictable
  • 15.61.1The system shall include an interface to allow objects to be restricted to subdomains.

    Specification(s): block_solution_working

    Design: BlockRestrictable Interface

    Issue(s): #2096

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.61.2The system shall report an error if an object is restricted to a set of subdomains that differs from a dependant object.

    Specification(s): block_undefined_var_block

    Design: BlockRestrictable Interface

    Issue(s): #2096

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BlockRestrictable Interface

    Issue(s): #2096

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BlockRestrictable Interface

    Issue(s): #2096

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BlockRestrictable Interface

    Issue(s): #2096

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BoundaryRestrictable Interface

    Issue(s): #2149

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BoundaryRestrictable Interface

    Issue(s): #2149

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BoundaryRestrictable Interface

    Issue(s): #2149

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: BlockRestrictable Interface

    Issue(s): #2411

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.61.10The system shall support the ability to restrict user defined calculations to sides of a subdomain.

    Specification(s): test

    Design: BlockRestrictable Interface

    Issue(s): #2411

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): block

    Design: MooseMesh

    Issue(s): #2757

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • rdg: Scalar Kernels
  • 15.63.1We shall be able to couple a scalar variable into AD objects and do some meaningful physics: depleting boundary source diffusion problem

    Specification(s): exo

    Design: ScalarKernels System

    Issue(s): #13703

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.63.2We shall be able to couple a scalar variable into AD objects and get the correct Jacobian

    Specification(s): jac

    Design: ScalarKernels System

    Issue(s): #13703

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.63.3The system shall be able to correctly compute the Jacobian of an ADScalarKernel using automatic differentiation.

    Specification(s): jacobian

    Design: ScalarKernels System

    Issue(s): #18535

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 15.63.4The system shall provide the ability to compute the time derivative of a scalar variable and have its Jacobian computed using automatic differentiation, and
    1. applied using standard kernel variable interfaces, or
    2. applied using coupling interfaces.

    Specification(s): dot/test, dot/test_coupled

    Design: ADScalarTimeDerivative

    Issue(s): #18535

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • rdg: Scaling
  • 15.64.1The system shall be able to include array variables in automatic scaling calculations.

    Specification(s): test

    Design: Systems overviewNonlinearSystemBase

    Issue(s): #26616

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.64.2The system shall ignore particular variable automatic scaling factors

    Specification(s): ignore

    Design: NonlinearSystem

    Issue(s): #19573

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

    Specification(s): fail_with_group

    Design: NonlinearSystem

    Issue(s): #19573

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 15.64.4The system shall be able to automatically compute scaling factors based on Jacobian
    1. data solely along the diagonal
    2. data both on- and off-diagonal

    Specification(s): auto_scaling/on_diag, auto_scaling/off_diag

    Design: NonlinearSystemBase

    Issue(s): #16212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.64.5The system shall be able to produce the same results without automatic scaling as with automatic scaling.

    Specification(s): not_scaled

    Design: NonlinearSystemBase

    Issue(s): #16212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.64.6The system shall be able to automatically scale variables and produce a good condition number from a naturally ill-conditioned system using
    1. automatic and
    2. manual prescribed settings.

    Specification(s): scaling/automatic, scaling/manual

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): bad

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 15.64.8When using scaling, the system shall
    1. compute the correct results when the residual and Jacobian are computed separately
    2. compute the correct results when the residual and Jacobian are computed together
    3. compute the correct Jacobian when the residual and Jacobian are computed separately
    4. compute the correct Jacobian when the residual and Jacobian are computed together

    Specification(s): scaling/resid_separate, scaling/resid_together, scaling/jac_separate, scaling/jac_together

    Design: FVIntegralValueConstraint

    Issue(s): #19444

    Collection(s): FUNCTIONAL

    Type(s): ExodiffPetscJacobianTester

  • 15.64.9The system shall be able to conduct residual based automatic scaling such that the largest residual vector component corresponding to each variable has magnitude unity
    1. in a one variable problem
    2. and in a two variable problem.

    Specification(s): residual-based/one-var, residual-based/two-var

    Design: NonlinearSystem

    Issue(s): #14397

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.64.10The system shall be able to conduct jacobian based automatic scaling such that the largest jacobian diagonal component corresponding to each variable has magnitude unity
    1. in a one variable problem
    2. and in a two variable problem

    Specification(s): jacobian-based/one-var, jacobian-based/two-var

    Design: NonlinearSystem

    Issue(s): #14397

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.64.11The system shall be able to include scalar variables in automatic scaling grouping calculations.

    Specification(s): test

    Design: Systems overviewNonlinearSystemBase

    Issue(s): #22042

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 15.64.12The system shall print current variable automatic scaling factors

    Specification(s): up-to-date-scale-factors

    Design: NonlinearSystem

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

Usability Requirements

Performance Requirements

System Interface Requirements

References

  1. D. F. Griffiths. The `No Boundary Condition' outflow boundary condition. International Journal of Numerical Methods in Fluids, 24(4):393–411, 1997. URL: http://tinyurl.com/y77au2k.[BibTeX]