Framework Requirements Traceability Matrix

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

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

MOOSE is a tool for solving complex coupled Multiphysics equations using the finite element method. MOOSE uses an object-oriented design to abstract data structure management, parallelism, threading and compiling while providing an easy to use interface targeted at engineers that may not have a lot of software development experience. MOOSE will require extreme scalability and flexibility when compared to other FEM frameworks. For instance, MOOSE needs the ability to run extremely complex material models, or even third-party applications within a parallel simulation without sacrificing parallelism. This capability is in contrast to what is often seen in commercial packages, where custom material models can limit the parallel scalability, forcing serial runs in the most severe cases. When comparing high-end capabilities, many MOOSE competitors target modest-sized clusters with just a few thousand processing cores. MOOSE, however, will be required to routinely executed on much larger clusters with scalability to clusters available in the top 500 systems (top500.org). MOOSE will also be targeted at smaller systems such as high-end laptop computers.

The design goal of MOOSE is to give developers ultimate control over their physical models and applications. Designing new models or solving completely new classes of problems will be accomplished by writing standard C++ source code within the framework's class hierarchy. Scientists and engineers will be free to implement completely new algorithms using pieces of the framework where possible, and extending the framework's capabilities where it makes sense to do so. Commercial applications do not have this capability, and instead opt for either a more rigid parameter system or a limited application-specific metalanguage.

System Scope

MOOSE's scope is to provide a set of interfaces for building Finite Element Method (FEM) simulations. Abstractions to all underlying libraries are provided.

Solving coupled problems where competing physical phenomena impact one and other in a significant nonlinear fashion represents a serious challenge to several solution strategies. Small perturbations in strongly-coupled parameters often have very large adverse effects on convergence behavior. These adverse effects are compounded as additional physics are added to a model. To overcome these challenges, MOOSE employs three distinct yet compatible systems for solving these types of problems.

First, an advanced numerical technique called the Jacobian-Free Newton-Krylov (JFNK) method is employed to solve the most fully-coupled physics in an accurate, consistent way. An example of this would be the effect of temperature on the expansion or contraction of a material. While the JFNK numerical method is very effective at solving fully-coupled equations, it can also be computationally expensive. Plus, not all physical phenomena in a given model are truly coupled to one another. For instance, in a reactor, the speed of the coolant flow may not have any direct effect on the complex chemical reactions taking place inside the fuel rods. We call such models "loosely-coupled". A robust, scalable system must strike the proper balance between the various modeling strategies to avoid performing unnecessary computations or incorrectly predicting behavior in situations such as these.

MOOSE's Multiapp system will allow modelers to group physics into logical categories where MOOSE can solve some groups fully-coupled and others loosely-coupled. The Multiapp system goes even further by also supporting a "tightly-coupled" strategy, which falls somewhere between the "fully-coupled" and "loosely-coupled" approaches. Several sets of physics can then be linked together into logical hierarchies using any one of these coupling strategies, allowing for several potential solution strategies. For instance, a complex nuclear reactor model might consist of several tightly-coupled systems of fully-coupled equations.

Finally, MOOSE's Transfers system ties all of the physics groups contained within the Multiapp system together and allows for full control over the flow of information among the various groups. This capability bridges physical phenomena from several different complementary scales simultaneously. When these three MOOSE systems are combined, myriad coupling combinations are possible. In all cases, the MOOSE framework handles the parallel communication, input, output and execution of the underlying simulation. By handling these computer science tasks, the MOOSE framework keeps modelers focused on doing research.

MOOSE innovates by building advanced simulation capabilities on top of the very best available software technologies in a way that makes them widely accessible for innovative research. MOOSE is equally capable of solving small models on common laptops and the very biggest FEM models ever attempted—all without any major changes to configuration or source code. Since its inception, the MOOSE project has focused on both developer and computational efficiency. Improved developer efficiency is achieved by leveraging existing algorithms and technologies from several leading open-source packages. Additionally, MOOSE uses several complementary parallel technologies (both the distributed-memory message passing paradigm and shared-memory thread-based approaches are used) to lay an efficient computational foundation for development. Using existing open technologies in this manner helps the developers reduce the scope of the project and keeps the size of the MOOSE code base maintainable. This approach provides users with state-of-the-art finite element and solver technology as a basis for the advanced coupling and solution strategies mentioned previously.

MOOSE's developers work openly with other package developers to make sure that cutting-edge technologies are available through MOOSE, providing researchers with competitive research opportunities. MOOSE maintains a set of objects that hide parallel interfaces while exposing advanced spatial and temporal coupling algorithms in the framework. This accessible approach places developmental technology into the hands of scientists and engineers, which can speed the pace of scientific discovery.

Assumptions and Dependencies

The software should be designed with the fewest possible constraints. Ideally the software should run on a wide variety of evolving hardware so it should follow well-adopted standards and guidelines. The software should run on any POSIX compliant system. The software will also make use FEM and numerical libraries that run on POSIX systems as well. The main interface for the software will be command line based with no assumptions requiring advanced terminal capabilities such as coloring and line control.

Pre-test Instructions/Environment/Setup

Ideally all testing should be performed on a clean test machine following one of the supported configurations set up 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

  • framework: Actions
  • 2.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

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

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

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

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

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

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

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

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

  • framework: Batch Material
  • 2.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

  • framework: Batch Property Derivative
  • 2.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

  • framework: Bcs
  • 2.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

  • 2.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): PetscJacobianTesterExodiff

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): PetscJacobianTesterExodiff

  • 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): PetscJacobianTesterExodiff

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

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

  • 2.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): PetscJacobianTesterExodiff

  • 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): PetscJacobianTesterExodiff

  • 2.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): PetscJacobianTesterExodiff

  • 2.7.23The system shall provide array vacuum boundary condition.

    Specification(s): test

    Design: ArrayVacuumBC

    Issue(s): #6881

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

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

  • 2.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): PetscJacobianTesterExodiff

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.7.45The system shall support Neumann type boundary conditions where the specified value is defined as the value of a vector, vv, in the direction of the boundary outward facing normal, n^\hat{n} (i.e., vâ‹…n^v\cdot\hat{n}).

    Specification(s): vector_neumann_test

    Design: BCs System

    Issue(s): 16769b212846275cd8b12e5a89b9e98f3ab7ca83

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.7.56

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.7.80BoundaryCondition objects shall support retrieval of VectorPostprocessor data.

    Specification(s): test

    Design: BCs System

    Issue(s): #9285

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • framework: Bounds
  • 2.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

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

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

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

  • 2.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): RunAppRunException

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.10.58

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

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

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

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

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

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

  • framework: Coord Type
  • 2.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

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

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

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

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

  • framework: Dgkernels
  • 2.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

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

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

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

  • 2.13.5DGKernels shall coexist with stateful material properties

    Specification(s): stateful_props

    Design: DGKernels System

    Issue(s): #11766

    Collection(s): FUNCTIONAL

    Type(s): RunApp

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

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

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

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

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

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

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

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

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

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

  • 2.13.16MOOSE should support AD in DG Kernels

    Specification(s): test

    Design: ADDGKernel

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

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

  • 2.13.23The DGKernel system shall operate with displaced meshes.

    Specification(s): test

    Design: DGKernels System

    Issue(s): #3536

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

  • framework: Executioners
  • 2.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

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

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

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

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

  • 2.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): 2.15.5

  • 2.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): 2.15.6

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Executors
  • 2.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

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

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

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

  • framework: Fixedbugs
  • 2.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

  • framework: Functions
  • 2.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

  • 2.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): 2.18.1

  • 2.18.3The Function system shall include a constant function.

    Specification(s): test

    Design: ConstantFunction

    Issue(s): #1678

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Functormaterials
  • 2.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

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

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

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

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

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

  • framework: Functors
  • 2.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

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

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

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

  • 2.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): PetscJacobianTesterExodiff

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

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

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

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

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

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

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

  • framework: Fvics
  • 2.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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Fvkernels
  • 2.24.1The system shall support block restriction of finite volume variables and kernels, and shall properly handle material evaluation in block-restricted settings, in a one-dimensional example.

    Specification(s): 1d

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.2The system shall allow definition of a functor material property with the same name by different block-restricted materials on neighboring subdomains even when there are different sets of finite volume flux kernels on those same neighboring subdomains.

    Specification(s): overlapping-mats

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16809

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.3The system shall support simultaneous block restriction of finite volume and finite element variables and have coupling of the finite volume variables into the finite element equations.

    Specification(s): distinct-mats

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.2

  • 2.24.4The system shall compute a perfect Jacobian when coupling block-restricted finite volume variables into block-restricted finite element calculations.

    Specification(s): jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.24.5The system shall allow different materials to define the same material property name on different sides of an interface when the finite volume physics is the same on both sides of the interface.

    Specification(s): just-mat-blk-restriction

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.6The system shall compute a perfect Jacobian when different materials define the same material property on different sides of a interface and the finite volume physics are the same on both sides of the interface.

    Specification(s): just-mat-blk-restriction-jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.24.7The system shall be able to force execution of flux kernels on all external boundaries.

    Specification(s): force_all_boundaries

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20695

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.8The system shall be able to force execution of flux kernels on one (or several) external boundary(ies).

    Specification(s): force_external_boundary

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20695

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.9The system shall be able to force execution of flux kernels on all but one (or several) external boundary(ies).

    Specification(s): ignore_post_forcing

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20695

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.8

  • 2.24.10The system shall be able to avoid executing on one (or several) internal boundary(ies) or sidesets.

    Specification(s): ignore_internal_boundaries

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20695

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.11The system shall report an error if conflictingly told to avoid and execute a flux kernel on the same boundary.

    Specification(s): overlapping_lists

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20695

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.24.12The system shall be able to impose a constraint on the domain integral of a variable.

    Specification(s): integral

    Design: FVIntegralValueConstraint

    Issue(s): #20607#23745

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.13The system shall be able to impose a constraint where the value of the constraint is provided by a postprocessor.

    Specification(s): integral_transient

    Design: FVIntegralValueConstraint

    Issue(s): #20607#23745

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.14The system shall be able to impose a constraint on a single point value of a variable.

    Specification(s): point_value

    Design: FVPointValueConstraint

    Issue(s): #20607#23745

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.15The system shall be able to impose bounds for the values of a variable.

    Specification(s): bound

    Design: FVBoundedValueConstraint

    Issue(s): #20607#23745

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.16The system shall be able to couple both finite element and finite volume variables, as functors, into functor material property calculations.

    Specification(s): fe-and-fv-with-functors

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16809

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.17The system shall support coupling of a finite volume variable into a finite element calculation.

    Specification(s): coupled-gold

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.16

  • 2.24.18The system shall compute a perfect Jacobian when coupling a finite volume variable into a finite element calculation.

    Specification(s): jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15894

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.24.19The system shall allow a finite volume object to consume a material property that depends on another material property that is computed in a material that couples in a finite element variable.

    Specification(s): dep-in-same-mat-as-coupled-fe

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16809

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.17

  • 2.24.20The system shall suggest that the user add a finite volume variable if a finite volume object cannot retrieve one

    Specification(s): var_except

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.24.21The system shall be able to perform finite volume simulations with adaptivity and give correct results

    Specification(s): adapt

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.22The system shall be able to combat a singular solve, resulting from two term boundary expansion during gradient computation, by reverting to a one term boundary expansion.

    Specification(s): steady-coarse

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16822

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.23The system shall display second order convergence when there is some skewness due to mismatch between cell levels.

    Specification(s): steady-mms

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.24The system shall be able to solve anisotropic diffusion problems using the finite volume method.

    Specification(s): fv_anisotropic_diffusion

    Design: FVAnisotropicDiffusion

    Issue(s): #21832

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.25The system shall be able to solve the Burgers equation in 1D using the FV method

    Specification(s): fv_burgers

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.26The system shall run a 2D linear advection problems using the finite volume method a regular mesh.

    Specification(s): fv_2D_constant_scalar_advection

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.27The system shall be able to produce correct mathematical results for a coupled-reaction problem
    1. using both finite element and finite volume discretizations with
    2. the correct Jacobian entries.

    Specification(s): test/exo, test/jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.24.28The system shall be able to compute the second time derivative of a variable when using the finite volume method and automatic differentiation.

    Specification(s): csv

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #18178

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.24.29The system shall be able to couple variables at faces when using the finite volume method.

    Specification(s): exo

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.30The system shall have an accurate Jacobian when coupling variables at faces and using the finite volume method.

    Specification(s): jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.24.31The system shall support caching of functor evaluations performed with boundary face arguments.

    Specification(s): ssf_caching

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20470

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.32The system shall run a simple 2D linear diffusion problem using the finite volume method with Dirichlet boundary conditions on a regular mesh.

    Specification(s): dirichlet

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.33The system shall run a simple 2D linear diffusion problem in RZ coordinates using the finite volume method with Dirichlet boundary conditions on a regular mesh.

    Specification(s): dirichlet_rz

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.34The system shall be able to compute a full Jacobian matrix when performing finite volume computations

    Specification(s): dirichlet_full_jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.32

  • 2.24.35The system shall run a simple 2D linear diffusion problem using the finite volume method with Neumann and Dirichlet boundary conditions on a regular mesh, computing the Jacobian and residual:
    1. separately
    2. together

    Specification(s): neumann/neumann, neumann/neumann_together

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.36The system shall run a simple 2D transient linear diffusion problem using the finite volume method with Dirichlet boundary conditions on a regular mesh.

    Specification(s): transient

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.37The system shall be able to solve a finite-volume-only problem
    1. on an unrefined mesh
    2. and on a mesh that has been refined to have the same amount of elements and achieve identical results

    Specification(s): refinement/no_refinement, refinement/refinement

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.38The system shall be able solve a three-dimensional diffusion problem using the finite volume method.

    Specification(s): 3d_dirichlet

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.39The system shall be able solve a one-dimensional diffusion problem using the finite volume method.

    Specification(s): 1d_dirichlet

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.40The system shall correctly account for differences between gradient and divergence operators in cylindrical coordinates.

    Specification(s): unstructured-rz

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15063

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.41The system shall be able to perform Laplacian-based adaptivity with finite volume variables.

    Specification(s): gradient-jump

    Design: GradientJumpIndicator

    Issue(s): #20705

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.24.42The system shall be able to impose the constraint that the average value of a variable on a boundary be a prescribed value.

    Specification(s): constrained

    Design: FVBoundaryIntegralValueConstraint

    Issue(s): #23745

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.43The system shall be able to to solve an advection-diffusion equation with a dirichlet condition on the left boundary and a zero gradient condition on the right boundary and display second order convergence with the finite volume method.

    Specification(s): test

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.44The system shall, while using an advective outflow boundary condition, demonstrate second order convergence if a two term Taylor series is used to approximate boundary face values and reduced order convergence if a one term Taylor series is used. These converges rates shall be observed with
    1. a weighted averaging advection interpolation, and
    2. a min-mod advection interpolation scheme.

    Specification(s): outflow/average, outflow/minmod

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549#24466

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.45The system shall be able to do one-term and two-term Taylor expansions for extrapolating finite volume solutions to boundary faces, and these extrapolations should be usable by flux kernels at inflow/outflow boundaries to produce first and second order accurate solutions respectively as measured by an L2 norm.

    Specification(s): extrapolate

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16169#14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.46The system shall display first order convergence with an upwind limiter.

    Specification(s): UpwindLimiter

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.47The system shall display second order convergence with a central-differencing limiter.

    Specification(s): CentralDifferenceLimiter

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.48The system shall display second order convergence with a Van-Leer limiter.

    Specification(s): VanLeerLimiter

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.49The system shall display second order convergence with a min-mod limiter.

    Specification(s): MinModLimiter

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.50The system shall display second order convergence with a second-order-upwind limiter.

    Specification(s): SOULimiter

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.51The system shall display second order convergence with a QUICK limiter.

    Specification(s): QUICKLimiter

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.52The system shall provide a Kurganov-Tadmor scheme for evaluating convective intercell fluxes
    1. with central difference interpolation of face values and resulting second order convergence
    2. with upwind interpolation of face values and resulting first order convergence
    3. with central difference interpolation with Van-Leer limiting of face values and resulting two and a half order convergence

    Specification(s): kt/KTLimitedCD, kt/KTLimitedUpwind, kt/KTLimitedVanLeer

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.53The system shall display second order convergence when applying weakly enforced matching Dirichlet and flux conditions.

    Specification(s): broken-domain

    Design: FVInterfaceKernels SystemFVBCs System

    Issue(s): #16756

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.54The system shall be able to solve the diffusion equation in 2D axisymmetric coordinates using the finite volume method, and display a second order convergence rate.

    Specification(s): diffusion

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.55The system shall be able to solve a pure advection problem in 1D cylindrical coordinates using the finite volume method, and display a second order convergence rate.

    Specification(s): advection

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.56The system shall be able to solve a advection-reaction problem in 2D axisymmetric coordinates using the finite volume method, and display a second order convergence rate.

    Specification(s): advection-reaction

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.57The system shall be able to solve a advection-diffusion-reaction problem in 2D axisymmetric coordinates using the finite volume method, and display a second order convergence rate.

    Specification(s): advection-diffusion-reaction

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.58The system shall be able to implement advection through an element based kernel, that leverages the system's ability to reconstruct gradients, and demonstrate second order convergence on a cartesian coordinate system.

    Specification(s): cartesian

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15066

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.59The system shall be able to retrieve and usefinite volume variable gradients in materials using a coupling interface and reproduce element-based advection results based on direct use of the variable gradient in a Cartesian coordinate system.

    Specification(s): mat-cartesian

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16963

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.60The system shall be able to implement advection through an element based kernel, that leverages the system's ability to reconstruct gradients, and demonstrate second order convergence in an axisymmetric coordinate system.

    Specification(s): rz

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15066

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.61The system shall be able to retrieve and usefinite volume variable gradients in materials using a coupling interface and reproduce element-based advection results based on direct use of the variable gradient in an axisymmetric coordinate system.

    Specification(s): mat-rz

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16963

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.62The system shall display first order convergence,
    1. when using a simple arithmetic average to determine the face values of discontinuous diffusion coefficients on a regular tri mesh.
    2. when using a simple arithmetic average to determine the face values of discontinuous diffusion coefficients on a quad mesh.

    Specification(s): average/tris, average/quads

    Design: FVDiffusion

    Issue(s): #21923

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.63The system shall display
    1. close to second order convergence, when using a simple harmonic average to determine the face values of discontinuous diffusion coefficients on a regular tri mesh.
    2. second order convergence, when using a simple harmonic average to determine the face values of discontinuous diffusion coefficients on a quad mesh.

    Specification(s): harmonic/tris, harmonic/quads

    Design: FVDiffusion

    Issue(s): #21923

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.64The system shall be able to solve a coupled mass and momentum-type two equation system, which includes advection and diffusion.

    Specification(s): exo

    Design: FVKernels System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.65The system shall exhibit second order convergence for the unknown in a coupled mass and momentum-type two equation system.

    Specification(s): mms

    Design: FVKernels System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.66The system shall display second order convergence, when using face side neighbors to compute face midpoint values during gradient reconstruction.

    Specification(s): compact

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #15063

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.67The system shall display first order convergence with regular face averaging in an advection diffusion problem.

    Specification(s): average

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16239

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.68The system shall display second order convergence with skew-corrected face averaging for the diffusion term in an advection diffusion problem.

    Specification(s): skewcorrected

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16239

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.69The system shall display second order convergence with skew-corrected face averaging for the diffusion and advection terms in an advection diffusion problem.

    Specification(s): skewcorrected-advection

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16239

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.70The system shall display first order convergence, when averaging face side neighbors to compute face midpoint values during gradient reconstruction.

    Specification(s): average

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16239

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.71The system shall display second order convergence, when skewness-corrected averaging to compute face midpoint values during gradient reconstruction.

    Specification(s): skewcorrected

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16239

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.72The system shall display first order convergence when using a skew-corrected average-based face-interpolation together with extrapolated BCs.

    Specification(s): skewcorrected

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #16239

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.24.73The system shall be able to solve a diffusion problem with the finite volume method and display second order convergence.

    Specification(s): diffusion

    Design: FVKernels System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.74The system shall be able to solve a advection-diffusion problem with the finite volume method and display second order convergence.

    Specification(s): advection-diffusion

    Design: FVKernels System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.75The system shall be able to solve a advection-diffusion problem with the finite volume method, using a velocity supplied by a material, and display second order convergence.

    Specification(s): mat-advection-diffusion

    Design: FVKernels System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.76The system shall be able to solve a advection-diffusion problem with the finite volume method and display first order convergence with an upwind scheme for the advection operator.

    Specification(s): upwind-advection-diffusion

    Design: FVKernels System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.77The system shall be able to solve diffusion on an orthogonal grid using a diffusion kernel which accounts only for orthogonal diffusion.

    Specification(s): orthogonal-diffusion

    Design: FVOrthogonalDiffusionFVOrthogonalBoundaryDiffusion

    Issue(s): #16758

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.24.78The system shall be able to identify and show when a matrix is ill conditioned.

    Specification(s): bad

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.24.79The system shall be able to condition a system automatically through variable scaling factors.

    Specification(s): good

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.78

  • 2.24.80The system shall be able to condition a system manually through variable scaling factors.

    Specification(s): good_manual

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.79

  • 2.24.81The system shall be able to sequentially apply manual and automatic scaling and in the case of poor manual scaling, restore the condition number automatically.

    Specification(s): combined_manual_automatic

    Design: NonlinearSystemBase

    Issue(s): #15732

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.24.80

  • 2.24.82The system shall be able to run a flux boundary condition and a flux kernel for different variables on the same boundary and calculate correct function and Jacobian values.

    Specification(s): jac

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.24.83The system shall be able to perform limiting schemes on Euclidean vector functors. These limiting schemes include
    1. first-order upwind
    2. central differencing
    3. vanLeer

    Specification(s): limiting_schemes/upwind, limiting_schemes/central_difference, limiting_schemes/vanLeer

    Design: Finite Volume Design Decisions in MOOSE

    Issue(s): #20493

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • framework: Geomsearch
  • 2.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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.25.54

  • 2.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): 2.25.52

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

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

  • 2.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): 2.25.12.25.22.25.282.25.462.25.492.25.502.25.58

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

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

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

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

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

  • framework: Globalparams
  • 2.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

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

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

  • framework: Ics
  • 2.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

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

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

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

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

  • 2.28.6Generates a rectangular IC

    Specification(s): test

    Design: BoundingBoxIC

    Issue(s): #11034

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.28.7BoundingBoxIC shall have a diffuse interface option.

    Specification(s): diffuse

    Design: BoundingBoxIC

    Issue(s): #13331

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.28.20

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

  • 2.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): 2.28.22

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

  • 2.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): 2.28.24

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

  • 2.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): 2.28.26

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

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

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

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

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

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

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

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

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

  • 2.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): 2.28.52.28.62.28.122.28.132.28.152.28.182.28.302.28.312.28.352.28.362.28.48

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

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

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

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

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

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

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

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

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

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

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

  • framework: Indicators
  • 2.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

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

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

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

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

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

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

  • framework: Interfacekernels
  • 2.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

  • 2.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): 2.30.1

  • 2.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): 2.30.1

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

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

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

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

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

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

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

  • 2.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): 2.30.10

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

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

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

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

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

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

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

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

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

  • 2.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): 2.30.182.30.36

  • 2.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): 2.30.182.30.36

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.30.37

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

  • 2.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): 2.30.39

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

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

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

  • framework: Kernels
  • 2.32.1The system shall provide an ability to solve a 2D diffusion problem with Dirichlet boundary conditions.

    Specification(s): testdirichlet

    Design: DirichletBC

    Issue(s): #6397

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.2The system shall provide an ability to solve a 2D diffusion problem with Neumann boundary conditions.

    Specification(s): testneumann

    Design: NeumannBC

    Issue(s): #1410

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.3The system shall provide a diffusion kernel that obtains the diffusion coefficient from a material property

    Specification(s): testmatdiffusion

    Design: MatDiffusion

    Issue(s): #12074

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.4The system shall provide an ability to solve a 2D diffusion problem including a volumetric source term.

    Specification(s): testbodyforce

    Design: BodyForce

    Issue(s): #6136

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.5The system shall provide a tester that checks hand-coded Jacobian against finite difference Jacobian using -snes_type=test option.

    Specification(s): test_jacobian

    Design: Framework Software Test Plan

    Issue(s): #2337

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.6The system shall force the solver to take at least one iteration regardless of the initial residual norm when the snes_force_iteration option is specified.

    Specification(s): test_force_iteration

    Design: Transient

    Issue(s): #10594

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.12.32.69

  • 2.32.7The system shall not compute an extra residual if the linear solver is used.

    Specification(s): actual_linear_solver

    Design: FEProblem

    Issue(s): #11760

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.32.8The system shall provide an ability to solve a 2D diffusion problem with Dirichlet boundary conditions using
    1. automatic differentiation and
    2. compute the correct Jacobian matrix.

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

    Design: ADDirichletBC

    Issue(s): #13260

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.9The system shall provide an ability to solve a 2D diffusion problem Neumann boundary conditions using
    1. automatic differentiation and
    2. compute the correct Jacobian matrix.

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

    Design: ADNeumannBC

    Issue(s): #12903

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.10The system shall provide an ability to solve a 2D diffusion problem including a volumetric source term using
    1. automatic differentiation and
    2. compute the correct Jacobian matrix.

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

    Design: ADBodyForce

    Issue(s): #13260

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.11Coupled variable gradient Jacobian entries generated with AD shall be accurate

    Specification(s): test

    Design: Coupleable

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.12The system shall provide a source term proportional to the value of
    1. an aux variable and shall be able to produce the exact Jacobian
    2. an finite element primary variable and shall be able to produce the exact Jacobian

    Specification(s): jacobians/aux, jacobians/fe

    Design: CoupledForce / ADCoupledForce

    Issue(s): #18214

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.13Coupled variable value Jacobian entries generated with AD shall be accurate

    Specification(s): test

    Design: Coupleable

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.14We shall be able to get aux variable values through adCoupledValue with the knowledge that the derivatives will always be zero

    Specification(s): test_coupled_aux

    Design: Coupleable

    Issue(s): #12852

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.15Getting a constant aux variable through adCoupledValue shall not destroy our Jacobian

    Specification(s): test_coupled_aux_jac

    Design: Coupleable

    Issue(s): #12852

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.16We shall be able to get dot aux variable values through adCoupledValue with the knowledge that the time derivatives will always be zero

    Specification(s): test_coupled_dot_aux

    Design: Coupleable

    Issue(s): #12996

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.17The system shall automatically generate a full coupling matrix when doing global AD indexing such that there are no new matrix memory allocations.

    Specification(s): no_mallocs_pjfnk

    Design: Coupleable

    Issue(s): #16396

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.112.32.132.32.372.32.402.32.502.32.672.32.792.32.1012.32.1082.32.1232.32.1242.32.1252.32.1342.32.140

  • 2.32.18The system shall automatically generate a full coupling matrix when doing global AD indexing, resulting in a perfect Jacobian even when the user has not requested full coupling.

    Specification(s): perfect_jac_pjfnk_global_ad

    Design: Coupleable

    Issue(s): #16396

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

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

    Specification(s): trust_user_and_then_error

    Design: Coupleable

    Issue(s): #16396

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.20Jacobians calculated by ADTimeDerivative and ADBodyForce shall be perfect.

    Specification(s): testbodyforce-jac

    Design: ADTimeDerivative

    Issue(s): #13260

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.21The Jacobian of ADBodyForce with a force function shall be perfect.

    Specification(s): testbodyforce-adfunction-jac

    Design: BodyForce

    Issue(s): #13260

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.22The system shall provide a source term proportional to the value of a coupled variable with a material property prefactor.

    Specification(s): fe_result

    Design: ADMatCoupledForce

    Issue(s): #13744

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.23The system shall provide a source term proportional to the value of
    1. an aux variable with a material property prefactor and shall be able to produce the exact Jacobian.
    2. an finite element primary variable with a material property prefactor and shall be able to produce the exact Jacobian.

    Specification(s): jacobians/aux, jacobians/fe

    Design: ADMatCoupledForce

    Issue(s): #13744

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.24The system shall solve a one-dimensional Diffusion problem with a material property diffusivity and match a known solution.
    1. without and
    2. with automatic differentiation including
    3. the correct Jacobian matrix.

    Specification(s): 1D/1D_transient, 1D/ad_1D_transient, 1D/ad_1D_transient_jacobian

    Design: ADMatDiffusion

    Issue(s): #2582#5658#12633#13632

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.25The system shall solve a two-dimenional Diffusion problem with a material property diffusivity and match a known solution.
    1. without and
    2. with automatic differentiation including
    3. the correct Jacobian matrix.

    Specification(s): 2D/2D_steady_state, 2D/ad_2D_steady_state, 2D/ad_2D_steady_state_jacobian

    Design: ADMatDiffusion

    Issue(s): #2582#5658#12633#13632

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.26The system shall provide an ability to solve a steady-state diffusion-reaction problem, where the reaction term has a material property reaction rate.

    Specification(s): ad_mat_reaction

    Design: ADMatReaction

    Issue(s): #13484#13744

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.27The system shall calculate the correct Jacobian of ADMatReaction using automatic differentiation.

    Specification(s): ad_mat_reaction_jac

    Design: ADMatReaction

    Issue(s): #13484#13744

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.28The system shall contain a consuming reaction term object whose Jacobian is calculated via forward automatic differentiation.

    Specification(s): ad_reaction

    Design: Reaction / ADReaction

    Issue(s): #21009

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.29The system shall produce a perfect Jacobian for a consuming reaction term object using forward automatic differentiation.

    Specification(s): ad_reaction_jac

    Design: Reaction / ADReaction

    Issue(s): #21009

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.30The system shall contain a consuming reaction term object with a scalar coefficient whose Jacobian is calculated via forward automatic differentiation.

    Specification(s): ad_coef_reaction

    Design: CoefReaction / ADCoefReaction

    Issue(s): #21009

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.31The system shall produce a perfect Jacobian for a consuming reaction term object with a scalar coefficient using forward automatic differentiation.

    Specification(s): ad_coef_reaction_jac

    Design: CoefReaction / ADCoefReaction

    Issue(s): #21009

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.32The system will produce a harmonic function with a prescribed average value,
    1. showing the correct results with separate computation of residual and Jacobian
    2. verifying the separated Jacobian
    3. showing the correct results with computation of residual and Jacobian together
    4. verifying the Jacobian together

    Specification(s): kernel_dirichlet/physics_separate, kernel_dirichlet/jacobian_separate, kernel_dirichlet/physics_together, kernel_dirichlet/jacobian_together

    Design: ADScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.33The system shall solve the constrained Neumann problem using the AD Lagrange multiplier approach with LU solver,
    1. showing the correct results with separate computation of residual and Jacobian for Neumann
    2. verifying the separated Jacobian for Neumann
    3. showing the correct results with computation of residual and Jacobian together for Neumann
    4. verifying the Jacobian together for Neumann

    Specification(s): kernel_neumann/physics_separate, kernel_neumann/jacobian_separate, kernel_neumann/physics_together, kernel_neumann/jacobian_together

    Design: ADScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterCSVDiff

  • 2.32.34The system shall solve the constrained Neumann problem using the AD Lagrange multiplier approach with LU solver, computing the residual and Jacobian simultaneously.

    Specification(s): kernel_together

    Design: ADScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.32.35The system shall support the ability to include the AD scalar wrapper but not actually using a scalar variable.

    Specification(s): bipass

    Design: ADScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): override

    Design: ADScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.37Jacobian entries generated with AD for a simple diffusion problem shall be accurate

    Specification(s): test

    Design: ADDiffusion

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.38The system shall be able to solve a transient diffusion problem with
    1. automatic differentiation and
    2. compute the correct Jacobian matrix.

    Specification(s): transient_diffusion/ad, transient_diffusion/jac_ad_transient_diffusion

    Design: ADTimeDerivative

    Issue(s): #5658#12633

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.39The system shall be able to solve a transient diffusion problem with vector variables
    1. automatic differentiation and
    2. compute the correct Jacobian matrix.

    Specification(s): transient_vector_diffusion/ad, transient_vector_diffusion/jac_ad

    Design: ADVectorTimeDerivative

    Issue(s): #13017

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.32.40Jacobian entries generated with AD shall match hand-coded Jacobian entries as measured through save-in values

    Specification(s): test

    Design: Kernels System

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.41The system shall provide a generic kernel object that allows for easy switching between hand-coded and automatic computation of the Jacobian, and encourages maximum kernel code-reuse.

    Specification(s): generic_test

    Design: Kernels System

    Issue(s): #15552

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.42The system shall support coupling of variables with automatic differentiation and vector values.

    Specification(s): ad_vector_couple

    Design: Coupleable

    Issue(s): #12836

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.43The system shall support coupling to the gradient of variables with automatic differentiation and vector values.

    Specification(s): ad_grad_vector_couple

    Design: Coupleable

    Issue(s): #12836

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.44The system shall support coupling of default values for variables with automatic differentiation and vector values.

    Specification(s): ad_vector_couple_default

    Design: Coupleable

    Issue(s): #12836

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.45The system shall run a coupled diffusion-advection problem with higher-order variables on a non-regular mesh domain:
    1. in a steady-state calculation, and
    2. in a transient calculation.

    Specification(s): adv_diff_reaction/steady, adv_diff_reaction/transient

    Design: Kernels System

    Issue(s): #1410

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.46The system shall support direct tensor-vector products and vector dot products to maintain dimension agnostic formulations where possible.

    Specification(s): test_aniso

    Design: AnisotropicDiffusion

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.47The system shall be able to reproduce the exact Jacobian for a 1d grid for a coupled array time derivative kernel.

    Specification(s): jac_1d

    Design: ArrayCoupledTimeDerivative

    Issue(s): #25833

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.48The system shall be able to reproduce the exact Jacobian for a 2d grid for a coupled array time derivative kernel.

    Specification(s): jac_2d

    Design: ArrayCoupledTimeDerivative

    Issue(s): #25833

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.49The system shall be able to reproduce the exact Jacobian for a 3d grid for a coupled array time derivative kernel.

    Specification(s): jac_3d

    Design: ArrayCoupledTimeDerivative

    Issue(s): #25833

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.50The system shall provide array diffusion kernels on an array variable.

    Specification(s): test

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.51The system shall provide array reaction kernels on an array variable.

    Specification(s): test_diffusion_reaction

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.52The system shall provide array DG diffusion kernels on an elemental array variable.

    Specification(s): test_diffusion_reaction_dg

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.53The system shall provide coupling of standard variables in array kernels.

    Specification(s): test_diffusion_reaction_coupling

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.54The system shall provide coupling of array variables in standard kernels.

    Specification(s): test_diffusion_reaction_other_coupling

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.55The system shall provide residual save-in and Jacobian diagonal save-in for
    1. array and
    2. standard variables.

    Specification(s): save_in/array, save_in/test_standard_save_in

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.56The system shall provide array time derivative kernels on an array variable.

    Specification(s): test_diffusion_reaction_transient

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.57The system shall provide array body-force kernels on an array variable.

    Specification(s): test_body_force

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.58The system shall assemble the Jacobian properly with array variables.

    Specification(s): test_array_custom_coupling

    Design: ArrayMooseVariable

    Issue(s): #6881#14057#23123

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.32.59We shall be able to show that without automatic scaling, this system is singular

    Specification(s): poorly-conditioned-field-scalar-system

    Design: ExecutionerFEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.32.60We shall be able to show that with automatic scaling, this system is non-singular

    Specification(s): auto-scaled-field-scalar-system

    Design: ExecutionerFEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.61We shall be able to show that with automatic scaling we can run this problem successfully in parallel

    Specification(s): auto-scaled-field-scalar-system-parallel

    Design: ExecutionerFEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.60

  • 2.32.62The system shall support the ability to apply a kernel to a subset of the domain
    1. through a subdomain restriction on the kernel, and
    2. through a subdomain restriction on the variable.

    Specification(s): block_restriction/kernel, block_restriction/variable

    Design: BlockRestrictable Interface

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.63The system shall support applying a function of space-time as a forcing function to the mesh domain.

    Specification(s): forcing_function_test

    Design: BodyForce

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.64The system shall support applying a material property of space-time as a forcing function to the mesh domain.

    Specification(s): mat_forcing_function_test

    Design: BodyForce

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.65The system shall support applying a material property of space-time as a forcing function to the mesh domain using AD.

    Specification(s): ad_mat_forcing_function_test

    Design: BodyForce

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): parsed_func_error_check

    Design: BodyForce

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.32.63

  • 2.32.67The system shall support scaling the computed time derivative by a scalar coefficient.

    Specification(s): test

    Design: CoefTimeDerivative

    Issue(s): #11047

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.68The system shall include the ability to compute the residual contribution from the conservative form of the advection operator
    1. without upwinding in 3D,
    2. with upwinding in 3D,
    3. without upwinding in 1D,
    4. with upwinding in 1D,
    5. without upwinding in 2D,
    6. with upwinding in 2D,
    7. with upwinding and an outflow boundary condition, and
    8. without any outflow boundary conditions.

    Specification(s): upwinding/no_upwinding_jacobian, upwinding/full_upwinding_jacobian, upwinding/no_upwinding_1D, upwinding/full_upwinding_1D, upwinding/no_upwinding_2D, upwinding/full_upwinding_2D, upwinding/none_in_all_out, upwinding/none_in_none_out

    Design: ConservativeAdvection

    Issue(s): #11852

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiffCSVDiff

  • 2.32.69A coupled time derivative kernel shall be provided

    Specification(s): testdirichlet

    Design: CoupledTimeDerivative

    Issue(s): #9786

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.70A coupled time derivative kernel with forward mode automatic differentiation shall be provided

    Specification(s): adtestdirichlet

    Design: ADCoupledTimeDerivative

    Issue(s): #13138

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.12.32.69

  • 2.32.71A coupled time derivative kernel compatible with vector variables with hand-coded jacobians shall be provided

    Specification(s): vectortestdirichlet

    Design: VectorCoupledTimeDerivative

    Issue(s): #13913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.72The Jacobian from VectorCoupledTimeDerivative shall be perfect

    Specification(s): jac_vectortestdirichlet

    Design: VectorCoupledTimeDerivative

    Issue(s): #13913

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.73The SMP Jacobian for a problem with a hanging-node shall be non-singular

    Specification(s): test_smp

    Design: Diffusion

    Issue(s): libmesh#1985

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.74The colored finite difference Jacobian for a problem with a hanging-node shall be non-singular

    Specification(s): test_fd_coloring

    Design: Diffusion

    Issue(s): libmesh#1985

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.73

  • 2.32.75The standard finite difference Jacobian for a problem with a hanging-node shall be non-singular

    Specification(s): test_fd_standard

    Design: Diffusion

    Issue(s): libmesh#1985

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.74

  • 2.32.76A matrix-free operator shall be able to solve the hanging-node problem, indicating it is non-singular

    Specification(s): test_mf

    Design: Diffusion

    Issue(s): libmesh#1985

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.75

  • 2.32.77The SMP Jacobian shall be perfect for the hanging-node problem

    Specification(s): test_smp_jacobian

    Design: Diffusion

    Issue(s): libmesh#1985

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.78The system shall compute a perfect Jacobian via automatic differentiation for a hanging-node problem and simultaneously handle automatic differentiation objects that do not actually have nonlinear variable dependence.

    Specification(s): test_ad_smp_jacobian

    Design: Diffusion

    Issue(s): libmesh#1985#15732

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.79The system shall run a simple 2D linear diffusion problem with Dirichlet boundary conditions on a regular mesh, where the laplace operator uses a function coefficient.

    Specification(s): test

    Design: FunctionDiffusion

    Issue(s): #13744

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.80The system shall support hybrid finite element method (HFEM) calculations with Dirichlet boundary conditions using standard variables.

    Specification(s): dirichlet

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.81The system shall support hybrid finite element method (HFEM) calculations with Dirichlet boundary conditions using array variables.

    Specification(s): array_dirichlet

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.82The system shall support hybrid finite element method (HFEM) calculations with preconditioner only using the block diagonal Jacobian.

    Specification(s): array_dirichlet_pjfnk

    Design: DGKernels System

    Issue(s): #20029

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.83The system shall support hybrid finite element method (HFEM) calculations with coupling of components of array variables on internal sides.

    Specification(s): array_dirichlet_transform

    Design: DGKernels System

    Issue(s): #20029

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.84The system shall support hybrid finite element method (HFEM) calculations with coupling of components of array variables on boundary sides.

    Specification(s): array_dirichlet_transform_bc

    Design: DGKernels System

    Issue(s): #20029

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.85The system shall support hybrid finite element method (HFEM) calculations with Neumann boundary conditions using standard variables.

    Specification(s): neumann

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.86The system shall support hybrid finite element method (HFEM) calculations with Neumann boundary conditions using array variables.

    Specification(s): array_neumann

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.87The system shall support hybrid finite element method (HFEM) calculations with Robin boundary conditions using standard variables.

    Specification(s): robin

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.88The system shall support hybrid finite element method (HFEM) calculations with Robin boundary conditions using array variables.

    Specification(s): array_robin

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.89The system shall support hybrid finite element method (HFEM) calculations with high order shape functions.

    Specification(s): high_order

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.90The system shall support hybrid finite element method (HFEM) calculations with Robin boundary conditions through Lagrange multipliers.

    Specification(s): variable_robin

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.91The system shall support hybrid finite element method (HFEM) calculations with displaced meshes.

    Specification(s): robin_displaced

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): robin_adpatation

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.93The system shall support hybrid finite element method (HFEM) calculations with Dirichlet boundary conditions with boundary values specified by variables.

    Specification(s): variable_dirichlet

    Design: DGKernels System

    Issue(s): #17447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.94The system shall be able to compute lower dimensional element volumes using element Jacobian information computed earlier during finite element object reinitialization and when the highest dimension of the mesh is
    1. two
    2. three

    Specification(s): accurate_lower_d_volumes/2d, accurate_lower_d_volumes/3d

    Design: DGKernels System

    Issue(s): #17938

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.95We shall automatically capture the dependence of things like JxW and grad_test on (second order) displacements

    Specification(s): jxw_jacobian

    Design: DisplacedProblem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.96We shall automatically capture the dependence of things like JxW and grad_test on (first order) displacements

    Specification(s): jxw_jacobian_2

    Design: DisplacedProblem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 2.32.95

  • 2.32.97We shall automatically capture the dependence of things like JxW and grad_test on (second order) displacements for a cylindrical geometry

    Specification(s): jxw_jacobian_cylindrical

    Design: DisplacedProblem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.98We shall automatically capture the dependence of things like JxW and grad_test on (first order) displacements for a cylindrical geometry

    Specification(s): jxw_jacobian_2_cylindrical

    Design: DisplacedProblem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 2.32.97

  • 2.32.99We shall automatically capture the dependence of things like JxW and grad_test on (second order) displacements for a spherical geometry

    Specification(s): jxw_jacobian_spherical

    Design: DisplacedProblem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.100We shall automatically capture the dependence of things like JxW and grad_test on (first order) displacements for a spherical geometry

    Specification(s): jxw_jacobian_2_spherical

    Design: DisplacedProblem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 2.32.99

  • 2.32.101The system shall provide optimized kernels for residuals with the test function or its gradient factored out.

    Specification(s): test

    Design: Kernel

    Issue(s): #3492#12658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.102The system shall provide optimized kernels for residuals with the test function or its gradient factored out in the automatic differentiation system.

    Specification(s): adtest

    Design: Kernel

    Issue(s): #3492#12658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.112.32.132.32.372.32.402.32.502.32.672.32.792.32.1012.32.1082.32.1232.32.1242.32.1252.32.1342.32.140

  • 2.32.103The system shall calculate perfect Jacobians for the automatic differentiation precompute problem.

    Specification(s): adtest-jac

    Design: Kernel

    Issue(s): #3492#12658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

    Prerequisite(s): 2.32.102

  • 2.32.104The system shall support the ability to use mass lumping for time derivative terms.

    Specification(s): mass_lumping

    Design: MassLumpedTimeDerivative

    Issue(s): #2689

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.105The system shall verify that the Jacobian terms when using mass lumping for time derivative terms are computed correctly.

    Specification(s): mass_lumping_jacobian

    Design: MassLumpedTimeDerivative

    Issue(s): #2689

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.106The system shall support a kernel for coupling the sum of several products of material properties with variables and constant coefficients

    Specification(s): material_coupled_force

    Design: MatCoupledForce

    Issue(s): #14665

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.107The system shall have the ability to declare the derivatives of material properties.

    Specification(s): test_jacobian

    Design: Kernels System

    Issue(s): #8377

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.108The system shall have the ability to verify individual Jacobian contributions before they are scaled by other finite element factors in the system.

    Specification(s): test

    Design: MaterialPropertyValue

    Issue(s): #14823

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.109The system shall support solving Ordinary Differential Equations in explicit form.

    Specification(s): test_expl

    Design: ScalarKernels System

    Issue(s): #726

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.110The system shall support solving Ordinary Differential Equations in implicit form.

    Specification(s): test_sys_impl

    Design: ScalarKernels System

    Issue(s): #726

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.111The system shall support solving ODEs specified within the input file through parsed expression syntax.

    Specification(s): test_parsed_sys_impl

    Design: ParsedODEKernel

    Issue(s): #726

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.110

  • 2.32.112The system support coupling of postprocessor values in the parsed expression ODE kernel.

    Specification(s): test_parsed_pp

    Design: ParsedODEKernel

    Issue(s): #14034

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.32.113The system shall support solving Coupled Ordinary Differential Equations.

    Specification(s): test_coupled_ode_td

    Design: ScalarKernels System

    Issue(s): #726

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.32.114The system shall allow scalar variable initial condition to be loaded from a file mesh

    Specification(s): test_coupled_ode_td_var_ic_from_mesh

    Design: SystemBase

    Issue(s): #13040

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.32.113

  • 2.32.115The system shall allow auxscalar variable initial condition to be loaded from a file mesh

    Specification(s): test_coupled_ode_td_auxvar_ic_from_mesh

    Design: SystemBase

    Issue(s): #13040

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.32.113

  • 2.32.116The system shall be able to compute the residual and the Jacobian of each Kernel together.

    Specification(s): resid_jac_together

    Design: NonlinearSystem

    Issue(s): #23487

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.117The system shall solve the constrained Neumann problem using the Lagrange multiplier approach.

    Specification(s): kernel

    Design: ScalarKernels System

    Issue(s): cbf6d2235379f6ad75908b0f9d4be792dbce6c3d

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.118The system shall solve the constrained Neumann problem using the Lagrange multiplier approach when displacements are active.

    Specification(s): kernel_disp

    Design: ScalarKernels System

    Issue(s): #7699

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.119The system shall support the ability to set Dirichlet boundary conditions using the Lagrange multiplier approach.

    Specification(s): bc

    Design: ScalarKernels System

    Issue(s): #1800

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.120The system shall solve a constrained Neumann problem and volume averaging using the Lagrange multiplier approach derived from a scalar augmentation class.

    Specification(s): kernel

    Design: ScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.121The system shall support the ability to include the scalar wrapper but not actually use a scalar variable.

    Specification(s): bipass

    Design: ScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): override

    Design: ScalarLMKernel

    Issue(s): #22174

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.123The system shall support retrieving a vector of values in a kernel object for the purpose of computing a residual statement.

    Specification(s): test

    Design: Kernels System

    Issue(s): #7425

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.124The system shall run a simple 2D linear diffusion problem with Dirichlet boundary conditions on a regular mesh.

    Specification(s): test

    Design: Diffusion

    Issue(s): #1493

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.125The system shall be able to run a transient diffusion problem

    Specification(s): test

    Design: TimeDerivative

    Issue(s): #000

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.126The system shall not do any mallocs in MatSetValues for simple kernels

    Specification(s): test_mallocs

    Design: TimeDerivative

    Issue(s): #13736

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.32.112.32.132.32.372.32.402.32.502.32.672.32.792.32.1012.32.1082.32.1232.32.1242.32.1252.32.1342.32.140

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

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

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.128We shall be able to solve an initially poorly scaled problem by using MOOSE's automatic scaling feature

    Specification(s): automatic-scaling-done-once

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.129We shall be able to solve an initially poorly scaled problem by using MOOSE's automatic scaling feature in parallel

    Specification(s): automatic-scaling-done-once-parallel-preconditioner

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.128

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

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

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.131We shall be able to solve a problem where the physics has large changes over time if we scale on every time step

    Specification(s): automatic-scaling-done-per-time-step

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.132We shall be able to solve a problem where the physics has large changes over time if we scale on every time step in parallel

    Specification(s): automatic-scaling-done-per-time-step-parallel-preconditioner

    Design: FEProblemSolve

    Issue(s): #12601

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.131

  • 2.32.133The system shall be able to do on the fly time derivative and gradient evaluations of variable functors.

    Specification(s): dot_grad_test

    Design: MooseVariableBase

    Issue(s): #16809

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): test

    Design: Kernels System

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.135Time kernel requires a transient executioner

    Specification(s): bad_transient

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bad_vector_tag

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bad_matrix_tag

    Design: TaggingInterface

    Issue(s): #9669

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.138The system shall be able to reproduce the simple_transient_diffusion test with VectorTimeDerivative (hand-coded Jacobian).

    Specification(s): transient_vector_diffusion

    Design: VectorTimeDerivative

    Issue(s): #13913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.139The Jacobian from VectorTimeDerivative shall be perfect

    Specification(s): jac_transient_vector_diffusion

    Design: VectorTimeDerivative

    Issue(s): #13913

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.140The system shall compute second-order time derivatives for vector variables

    Specification(s): test

    Design: Coupleable

    Issue(s): #13913

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.141The system shall be able to solve a curl-curl problem using Nedelec elements of the first kind.

    Specification(s): vector_fe

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.142The system shall be able to estimate the L2 and H(curl) errors for a curl-curl problem solved using Nedelec elements of the first kind.

    Specification(s): vector_fe_errors

    Design: ElementVectorL2ErrorElementHCurlSemiErrorElementHCurlError

    Issue(s): #26394

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.32.143The system shall be able to couple a vector variable into a standard kernel.

    Specification(s): coupled_scalar_vector

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.144The system shall be able to assign a default value for a vector variable from the source file.

    Specification(s): coupled_scalar_default_vector_source

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.145The system shall warn when assigning a default value with number of components less than LIBMESH_DIM, and it shall be able to assign the default value from the input file.

    Specification(s): coupled_scalar_default_vector_input_and_warn

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.146The system shall be able to assign a default value for a vector variable from the input file and still have the correct jacobian.

    Specification(s): coupled_scalar_default_vector_jacobian

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.147The system shall be able to solve multi-dimensional problems with vector Lagrange variables.

    Specification(s): lagrange_vec

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.148The system shall be able to solve one-dimensional problems with vector Lagrange variables.

    Specification(s): lagrange_vec_1d

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.149The system shall be able to solve one-dimensional problems with vector Lagrange variables and produce the correct Jacobian.

    Specification(s): lagrange_vec_1d_jac

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.150The system shall be able to solve multi-d vector Lagrange problems with automatic differentiation and reproduce the hand-coded result.

    Specification(s): ad_lagrange_vec

    Design: ADVectorFunctionDirichletBC

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.32.147

  • 2.32.151The system shall be able to solve multi-d vector Lagrange problems with automatic differentiation and have a perfect Jacobian.

    Specification(s): ad_lagrange_vec_jacobian

    Design: ADVectorFunctionDirichletBC

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.152The system shall be able to couple a vector variable into a standard kernel and produce the correct Jacobian.

    Specification(s): jacobian

    Design: Variables System

    Issue(s): #10049

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.153The system shall be able to couple a standard variable into a vector kernel. Additionally, the system shall be able to calculate time derivatives of variable gradients.

    Specification(s): coupled_gradient_dot_em_gauge

    Design: Variables SystemVectorBodyForce

    Issue(s): #10861

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.154The system shall be able to compute the correct Jacobian when coupling a standard variable into a vector kernel and taking time derivatives of variable gradients.

    Specification(s): coupled_gradient_dot_jacobian

    Design: Variables SystemVectorBodyForce

    Issue(s): #10861

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.32.155The system shall be able to assign Dirichlet boundary conditions for vector Lagrange variables; obtain coupled vector variable gradients; and correctly initialize both volume and face curl shape functions when the curl of a variable is requested.

    Specification(s): coupled_vector_gradient

    Design: Variables SystemVectorDiffusionVectorDirichletBCVectorFunctionDirichletBC

    Issue(s): #11150

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): comp_error

    Design: VectorBodyForce

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): ad_comp_error

    Design: ADVectorFunctionDirichletBC

    Issue(s): #13309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.32.158The system shall be capable of modeling a div-grad problem in H(div) using the following Raviart-Thomas elements:
    1. HEX27,
    2. TET14,
    3. TRI6,
    4. TRI7,
    5. QUAD8,
    6. and QUAD9.

    Specification(s): coupled_electrostatics/hex27, coupled_electrostatics/tet14, coupled_electrostatics/tri6, coupled_electrostatics/tri7, coupled_electrostatics/quad8, coupled_electrostatics/quad9

    Design: DivFieldGradFieldVectorDivPenaltyDirichletBC

    Issue(s): #26105

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.32.159The system shall be capable of estimating the L2 and H(div) errors for a div-grad problem in H(div) solved using the following Raviart-Thomas elements:
    1. HEX27,
    2. TET14,
    3. TRI6,
    4. TRI7,
    5. QUAD8,
    6. and QUAD9.

    Specification(s): coupled_electrostatics_errors/hex27, coupled_electrostatics_errors/tet14, coupled_electrostatics_errors/tri6, coupled_electrostatics_errors/tri7, coupled_electrostatics_errors/quad8, coupled_electrostatics_errors/quad9

    Design: ElementVectorL2ErrorElementHDivSemiErrorElementHDivError

    Issue(s): #26394

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • framework: Linearfvkernels
  • 2.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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Mesh
  • 2.37.1The system shall support importing mesh information from Abaqus that includes
    1. element identifiers,
    2. element sets, and
    3. element sets with extra space in file.

    Specification(s): abaqus/testcube_elem_id, abaqus/testcube_elset_name, abaqus/testcube_elset_name_ws

    Design: FileMesh

    Issue(s): #14302

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.2The system shall perform identical adaptivity patterns on both the reference mesh and the displaced mesh when it exists.

    Specification(s): displaced_test

    Design: Adaptivity System

    Issue(s): #443

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.3The system shall support toggling adaptivity on/off during a simulation.

    Specification(s): test_time

    Design: Adaptivity System

    Issue(s): #1755#447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.4The system shall perform one or more adaptivity steps on the mesh before the simulation begins.

    Specification(s): initial_adaptivity_test

    Design: Adaptivity System

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.5The system shall support patch-based error estimation among a stencil of elements.

    Specification(s): patch_test

    Design: Adaptivity System

    Issue(s): #833

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.6The system shall support multiple adaptive steps per solve.

    Specification(s): adapt_cycles_test

    Design: Adaptivity System

    Issue(s): #830

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.7The system shall perform adaptivity on systems containing multiple independent field variables.

    Specification(s): test

    Design: Adaptivity System

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.8The system shall support running adaptivity on an interval basis (every several time steps).

    Specification(s): interval

    Design: Adaptivity System

    Issue(s): #6888

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.9The system shall support weighted error estimation when considering multiple field variables for adaptivity.

    Specification(s): test

    Design: Adaptivity System

    Issue(s): #447

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.10The system shall allow specifying valid sideset IDs that do not exist on the initial mesh.

    Specification(s): add_sideset_ids

    Design: MooseMesh

    Issue(s): #23557

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.11The system shall allow specifying valid sideset IDs and names that do not exist on the initial mesh.

    Specification(s): add_sideset_ids_and_names

    Design: MooseMesh

    Issue(s): #23557

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.37.10

  • 2.37.12The system shall allow specifying valid sideset names that do not exist on the initial mesh, and assign IDs automatically.

    Specification(s): add_sideset_names

    Design: MooseMesh

    Issue(s): #23557

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.13The system shall allow specifying valid subdomain IDs that do not exist on the initial mesh.

    Specification(s): add_subdomain_ids

    Design: MooseMesh

    Issue(s): #23557

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.14The system shall allow specifying valid subdomain IDs and names that do not exist on the initial mesh.

    Specification(s): add_subdomain_ids_and_names

    Design: MooseMesh

    Issue(s): #27474

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.15The system shall allow specifying valid subdomain names that do not exist on the initial mesh.

    Specification(s): add_subdomain_names

    Design: MooseMesh

    Issue(s): #27474

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.16The system shall get the correct mesh dimension for a list of subdomains.

    Specification(s): test

    Design: Mesh System

    Issue(s): #23794

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.17The system shall output all boundary and subdomain connections.

    Specification(s): boundary_subdomain_connections

    Design: MooseMesh

    Issue(s): #14971#15019

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.18The system shall support the use of a centroid-based parallel partitioning scheme.

    Specification(s): centroid_partitioner_test

    Design: Mesh System

    Issue(s): #2270#2289

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.19The system shall generate pre-split mesh files using a standard input file combined with command line arguments.

    Specification(s): test_2_generate_split

    Design: Mesh Splitting

    Issue(s): #8472#7752#11004

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.20The system shall use pre-split mesh files using a standard input file combined with command line arguments.

    Specification(s): test_2

    Design: Mesh Splitting

    Issue(s): #8472#7752#11004

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.37.19

  • 2.37.21The system shall generate pre-split binary mesh files using a standard input file combined with command line arguments.

    Specification(s): test_2a_generate_split

    Design: Mesh Splitting

    Issue(s): #8472#7752#11004

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.22The system shall use pre-split binary mesh files using a standard input file combined with command line arguments.

    Specification(s): test_2a

    Design: Mesh Splitting

    Issue(s): #8472#7752#11004

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.37.21

  • 2.37.23The system shall generate a quadrilateral mesh consisting of concentric circles.

    Specification(s): test

    Design: ConcentricCircleMesh

    Issue(s): #11656

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.24The system shall support the ability to create custom objects for performing mesh partitioning, for example
    1. a linear partitioner that
    2. operates with a displaced configuration and
    3. is capable of restarting.

    Specification(s): group/custom_linear_partitioner, group/custom_linear_partitioner_displacement, group/custom_linear_partitioner_restart

    Design: Partitioner System

    Issue(s): #5543

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.25The system shall compute and store internal finite volume related element data on request for
    1. quadrilateral elements,
    2. quadrilateral elements in a cylindrical coordinate system, and
    3. triangular elements.

    Specification(s): elem_info/quad, elem_info/rz-quad, elem_info/tri

    Design: Mesh System

    Issue(s): #25824

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.26The system shall compute and store internal face data on request for
    1. quadrilateral elements,
    2. triangular elements, and
    3. quadrilateral elements in multiple regions.

    Specification(s): face_info/quad, face_info/tri, face_info/two_region_quads

    Design: Mesh System

    Issue(s): #14549

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.27The system shall read GMesh (.msh) format file meshes.

    Specification(s): gmsh_test

    Design: FileMesh

    Issue(s): #2105

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.28The system shall read GMesh (.msh) format file meshes containing multiple boundaries.

    Specification(s): gmsh_bc_test

    Design: FileMesh

    Issue(s): #1402

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.29The system shall support refinement of QUAD4 mesh elements.

    Specification(s): test_quad4_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.30The system shall support refinement of QUAD8 mesh elements.

    Specification(s): test_quad8_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.31The system shall support refinement of QUAD9 mesh elements.

    Specification(s): test_quad9_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.32The system shall support refinement of TRI3 mesh elements.

    Specification(s): test_tri3_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.33The system shall support refinement of TRI6 mesh elements.

    Specification(s): test_tri6_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.34The system shall support refinement of TRI7 mesh elements.

    Specification(s): test_tri7_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.35The system shall support refinement of HEX8 mesh elements.

    Specification(s): test_hex8_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.36The system shall support refinement of HEX20 mesh elements.

    Specification(s): test_hex20_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.37The system shall support refinement of HEX27 mesh elements.

    Specification(s): test_hex27_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.38The system shall support refinement of TET4 mesh elements.

    Specification(s): test_tet4_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.39The system shall support refinement of TET10 mesh elements.

    Specification(s): test_tet10_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.40The system shall support refinement of TET14 mesh elements.

    Specification(s): test_tet14_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.41The system shall support refinement of PRISM6 mesh elements.

    Specification(s): test_prism6_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.42The system shall support refinement of PRISM15 mesh elements.

    Specification(s): test_prism15_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.43The system shall support refinement of PRISM18 mesh elements.

    Specification(s): test_prism18_refine

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.44The system shall support refinement of PYRAMID5 mesh elements.

    Specification(s): test_pyramid5

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.45The system shall support refinement of PYRAMID13 mesh elements.

    Specification(s): test_pyramid13

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.46The system shall support refinement of PYRAMID14 mesh elements.

    Specification(s): test_pyramid14

    Design: Mesh System

    Issue(s): #4989#5021

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.47The system shall be able to process boundary and subdomain names that start with digits but which have non-digits later in the name.

    Specification(s): test

    Design: MooseMesh

    Issue(s): #23776

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.48The system shall generate a structured mesh on a Cartesian domain.

    Specification(s): test

    Design: GeneratedMesh

    Issue(s): #760

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.49The system shall generate first-order, structured meshes with biasing in the x, y, and z directions.

    Specification(s): mesh_bias

    Design: GeneratedMesh

    Issue(s): #6129

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.50The system shall generate second-order, structured meshes with biasing in the x, y, and z directions.

    Specification(s): mesh_bias_quadratic

    Design: GeneratedMesh

    Issue(s): #6129

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.51The system shall include the ability to generate an annular mesh that errors when
    1. the min radius is larger than the max radius;
    2. the min angle is greater than or equal to the max angle;
    3. the angle separation is larger than 360 degrees;
    4. the number of elements in the angular direction is too small due to the number of elements; and
    5. the number of elements in the angular direction is too small due to the maximum angle.
    6. shall throw an error if the quadrilateral and triangular subdomain ids are the same.
    7. shall throw an error if both radial positions and the number of radial elements are prescribed.
    8. shall throw an error if both radial positions and the radius growth parameter are prescribed.
    9. shall throw an error if any of the radial positions fall out of the bounds between rmin and rmax.

    Specification(s): annular_errors/annular_except1, annular_errors/annular_except2, annular_errors/annular_except3, annular_errors/annular_except4, annular_errors/annular_except5, annular_errors/annular_except6, annular_errors/annular_except7, annular_errors/annular_except8, annular_errors/annular_except9

    Design: AnnularMeshGenerator

    Issue(s): #8432#18486

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.52The system shall include the ability to create
    1. an annulus using quad elements;
    2. an annulus sector using quad elements;
    3. a circular disk using quad elements; and
    4. circular disk sector using quad elements.

    Specification(s): annular/annulus, annular/annulus_sector, annular/disc, annular/disc_sector

    Design: AnnularMeshGenerator

    Issue(s): #8432

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.53The system shall have an algorithm for meshing an annular region with triangular elements.

    Specification(s): spiral_annular_mesh

    Design: SpiralAnnularMesh

    Issue(s): #12205

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.54The system shall have an algorithm for generating triangular and quadrilateral meshes for the Ringleb problem.

    Specification(s): ringleb_mesh

    Design: RinglebMesh

    Issue(s): #12246

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.61The system shall allow writing out the mesh without running a simulation.

    Specification(s): mesh_only_test

    Design: Mesh System

    Issue(s): #1568

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.62The system shall print out information about the mesh when writing out the mesh and avoid emitting petsc warnings in mesh-only mode.

    Specification(s): mesh_info

    Design: Mesh System

    Issue(s): #11917#11921#26002

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.63The system shall warn when using –mesh-only and there is no clear filename to use

    Specification(s): mesh_only_warning

    Design: Mesh System

    Issue(s): #1568

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.64The system shall support overriding output dimension when necessary to store coordinates in higher planes

    Specification(s): output_dimension_override

    Design: Mesh System

    Issue(s): #12757

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.65The system shall support writing parallel checkpoint files with –mesh-only

    Specification(s): mesh_only_checkpoint

    Design: Mesh System

    Issue(s): #14312

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.37.66The system shall allow writing out the mesh with extra element ids without running a simulation.

    Specification(s): mesh_only_with_extra_elem_ids

    Design: Mesh System

    Issue(s): #23386

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.67The system shall allow writing out the mesh with extra element ids without running a simulation and user-provided id names.

    Specification(s): mesh_only_with_restricted_elem_ids

    Design: Mesh System

    Issue(s): #23386

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.68The system shall throw a warning if user-provided extra element id names do not exist on mesh.

    Specification(s): mesh_only_with_unrecognized_elem_ids

    Design: Mesh System

    Issue(s): #23386

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.69The system shall support simulations on meshes containing both 1D and 2D element types.

    Specification(s): oned_twod_test

    Design: Mesh System

    Issue(s): #1710#2130#2105

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.70The system shall support proper material evaluations on meshes containing both 1D and 2D element types.

    Specification(s): oned_twod_w_matl_test

    Design: Mesh System

    Issue(s): #1710#2130#2105

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.71The system shall support simulations on meshes containing both 1D and 3D element types.

    Specification(s): oned_threed_test

    Design: Mesh System

    Issue(s): #1710#2130#2105

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.72The system shall generate meshes with different sets of element integers and properly stitch them.

    Specification(s): mesh_integer

    Design: Mesh System

    Issue(s): #13764

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.73The system shall support interchangeable use of integer and string identifiers for mesh entities.

    Specification(s): test_names

    Design: Mesh System

    Issue(s): #979

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.74The system shall support interchangeable use of integer and string identifiers for mesh entities read from the XDA format.

    Specification(s): test_names_xda

    Design: Mesh System

    Issue(s): #1055

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.75The system shall support interchangeable use of integer and string identifiers within the BCs/Periodic block.

    Specification(s): test_periodic_names

    Design: Mesh System

    Issue(s): #979

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.76The system shall support the ability to assign and use string names to mesh entities during the simulation startup.

    Specification(s): on_the_fly_test

    Design: Mesh System

    Issue(s): #979

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.77The system shall support writing solution data in the Nemesis parallel file format.

    Specification(s): nemesis_test

    Design: Mesh SystemNemesis

    Issue(s): #2520#23006

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.78The system shall support the re-partitioning of mesh files input using the Nemesis format.

    Specification(s): nemesis_repartitioning_test

    Design: Mesh SystemNemesis

    Issue(s): #2520#23006

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.37.79The system shall issue an error if no Mesh block is provided.

    Specification(s): no_mesh_block_err

    Design: Mesh System

    Issue(s): #2408

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.80The system shall issue a diagnostic when a referenced node set does not exist in the mesh

    Specification(s): test

    Design: MooseMesh

    Issue(s): #13509#6985#6987

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.81The system shall generate a mesh using one or more meshes stitched into a pattern controlled by a 2D array.

    Specification(s): patterned_generation

    Design: PatternedMesh

    Issue(s): #6950

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.82The system shall read in a previously generated "patterned mesh" and run a simulation using that mesh.

    Specification(s): patterned_run

    Design: PatternedMesh

    Issue(s): #6950

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.37.81

  • 2.37.83The system shall produce a valid periodic node map with only one periodic constraint direction.

    Specification(s): 1D

    Design: Mesh System

    Issue(s): #11891

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.84The system shall produce a valid periodic node map with two periodic constraint directions.

    Specification(s): 2D

    Design: Mesh System

    Issue(s): #11891

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.85The system shall produce a valid periodic node map with three periodic constraint directions.

    Specification(s): 3D

    Design: Mesh System

    Issue(s): #11891

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.86The system shall ensure that the mesh is prepared at the time users execute their simulation.

    Specification(s): test

    Design: Mesh System

    Issue(s): #14329

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.87The system shall make available additional meshes as requested by the user
    1. and be able to save only one of the mesh generator meshes

    Specification(s): save_in_meshes_output/REPLICATED

    Design: MeshGenerator

    Issue(s): #23618

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.88The system shall report a useful error when saving additional meshes when
    1. the requested names are not unique,
    2. the requested name uses a reserved name,
    3. trying to use the mesh-saving capability with the final mesh,
    4. the requested saved mesh does not exist, and when
    5. the requested saved mesh has already been retrieved.

    Specification(s): save_in_name_error/repeat_save_in_name, save_in_name_error/save_in_name_as_main, save_in_name_error/save_in_name_for_final_mesh_generator, save_in_name_error/save_in_meshes_not_find, save_in_name_error/save_in_meshes_retrieved_twice

    Design: MeshGenerator

    Issue(s): #23618

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.89The system shall issue a diagnostic when a referenced side set does not exist in the mesh.

    Specification(s): missing_side_set

    Design: MooseMesh

    Issue(s): #13509

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.90The system shall have the ability to construct a side set from a set of nodes.

    Specification(s): construct_side_sets

    Design: MooseMesh

    Issue(s): #13509

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.91The system shall support optionally allowing uniform refinements when using a pre-split mesh

    Specification(s): square

    Design: Mesh SystemMesh Splitting

    Issue(s): #18575#27240

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.92A mesh can be split into a specified number of files using command line options.

    Specification(s): make_split

    Design: Mesh Splitting

    Issue(s): #10623#27240

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.37.93A mesh can be pre-split properly and used to generate equivalent results to running a simulation with the unsplit mesh when
    1. set by command line, no split extension specified
    2. set by command line, with a specified split extension
    3. set by an input parameter

    Specification(s): use_split/from_cli, use_split/from_cli_ext, use_split/from_input

    Design: Mesh Splitting

    Issue(s): #10623#17318

    Collection(s): FUNCTIONAL

    Type(s): ExodiffRunApp

    Prerequisite(s): 2.37.92

  • 2.37.94Console output should include an indicator that a pre-split mesh is being used when using –split-mesh in distributed = auto mode
    1. without and
    2. with the forced option.

    Specification(s): check/pre_split, check/forced_pre_split

    Design: Mesh Splitting

    Issue(s): #11825

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.37.92

  • 2.37.95The mesh splitter will throw an error when an attempt is made to split a "DistributedMesh".

    Specification(s): split_with_distributed_error

    Design: Mesh Splitting

    Issue(s): #11434

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.96The mesh splitter capability will honor geometric RelationshipManager objects.

    Specification(s): split_with_RM_part1

    Design: Mesh Splitting

    Issue(s): #11434#27240

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.37.97Meshes that are pre-split with active RelationshipManager objects work the same as if using an online DistributedMesh.

    Specification(s): split_with_RM_part2

    Design: Mesh Splitting

    Issue(s): #11434

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.37.96

  • 2.37.98Splitting meshes from file should work with custom partitioners.

    Specification(s): grid_from_file

    Design: Mesh Splitting

    Issue(s): #11944

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.37.99Splitting meshes from a generated mesh should work with custom partitioners.

    Specification(s): grid_from_generated

    Design: Mesh Splitting

    Issue(s): #11944

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.37.100The system should be able to load a pre-split mesh and perform additional mesh generation on it.

    Specification(s): meshgenerators_acting_on_split

    Design: Mesh SplittingFileMeshGenerator

    Issue(s): #18635#27240

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.37.93

  • 2.37.101The system shall support the creating a single mesh from multiple meshes stitched together.

    Specification(s): test

    Design: StitchedMesh

    Issue(s): #8308

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.102The system shall report an error if at least one mesh file is not supplied when creating a mesh from multiple meshes stitched together.

    Specification(s): files_error

    Design: StitchedMesh

    Issue(s): #8308

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.103The system shall provide a parallel partition based on mesh subdomains

    Specification(s): test

    Design: Partitioner System

    Issue(s): #8672#8747#8950#8956

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.104The parallel partitioning capability by subdomain shall report a reasonable error when a given subdomain does not exist

    Specification(s): missing_block

    Design: Partitioner System

    Issue(s): #8672#8747#8950#8956

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.37.105The system shall read TetGen file meshes.

    Specification(s): mesh_only_warning

    Design: FileMeshGenerator

    Issue(s): #20694

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.106The system shall construct a mesh by "tiling" another mesh repeatedly.

    Specification(s): tiled_mesh_test

    Design: TiledMesh

    Issue(s): #1729

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.107The system shall support avoiding repartitioning the mesh and deleting remote elements after uniform refinements

    Specification(s): square

    Design: Mesh System

    Issue(s): #18571

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.37.108The system shall support having a truly unique_id (never recycled) for all mesh elements and nodes when using replicated mesh.

    Specification(s): replicated_mesh

    Design: Mesh System

    Issue(s): #2142

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.37.109The system shall support having a truly unique_id (never recycled) for all mesh elements and nodes when using distributed mes.

    Specification(s): distributed_mesh

    Design: Mesh System

    Issue(s): #2142

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.37.108

  • framework: Minimal App
  • 2.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

  • framework: Misc
  • 2.42.1The system shall compute a curvature close to unity for a unit sphere.

    Specification(s): sphere_hex27

    Design: SphereMeshGeneratorFileMeshGenerator

    Issue(s): #12839

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.2The system shall compute a curvature close to minus unity for a unit circle.

    Specification(s): circle_tri6

    Design: SphereMeshGeneratorFileMeshGenerator

    Issue(s): #12839

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.3We shall be able to call AD variable methods on an auxiliary variable in a transient simulation and not hit assertions for both regular and neighbor calculations

    Specification(s): guard_time_deriv_for_ad_aux

    Design: MooseVariableFE

    Issue(s): #13171

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.4Coupling an auxiliary variable into a DGKernel shall not destroy the Jacobian

    Specification(s): neighbor_ad_with_aux_jac

    Design: MooseVariableFE

    Issue(s): #13171

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.42.5We shall be able to do NL variable coupling into a DGKernel

    Specification(s): neighbor_ad_with_nl

    Design: MooseVariableFE

    Issue(s): #13171

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.6We shall be able to do NL variable coupling into a DGKernel and have a good Jacobian

    Specification(s): neighbor_ad_with_nl_jac

    Design: MooseVariableFE

    Issue(s): #13171

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.42.7The compiled application shall be capable of returning the name used for registering objects.

    Specification(s): test

    Design: MooseApp

    Issue(s): #11337

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.8The system shall be able to run a specific application by passing a command line option.

    Specification(s): specified_app

    Design: MooseApp

    Issue(s): #20062

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.9The system shall be able to run a kernel on the displaced mesh with blocks that are a superset of the displacement variable blocks.

    Specification(s): run

    Design: DisplacedProblem

    Issue(s): #25804

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.10The system shall report an error when a material property is not defined on a boundary.

    Specification(s): bc_check

    Design: Problem system overview

    Issue(s): #9835#5309#9482

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.11The system shall report an error when a material property requested by a UserObject is not defined on a boundary.

    Specification(s): side_uo_check

    Design: Problem system overview

    Issue(s): #9835#5309#9482

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.12The system shall report an error when a material property requested by a DGKernel is not defined on a boundary.

    Specification(s): dgkernel_check_boundary

    Design: Problem system overview

    Issue(s): #9835#5309#9482

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.13The system shall report an error when a material property requested by a DGKernel is not defined on a subdomain.

    Specification(s): dgkernel_check_block

    Design: Problem system overview

    Issue(s): #9835#5309#9482

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.14The system shall verify that objects that use subdomain restricted variables are defined on a subset of the restricted domain area.

    Specification(s): variable_interface_run

    Design: Problem system overview

    Issue(s): #9889

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.15The system shall produce an error when an object's discretization area is explicitly set to a value greater than the area of the underlying variable used by the object.

    Specification(s): variable_interface_error_block_set

    Design: Problem system overview

    Issue(s): #9889

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.16The system shall produce an error when an object's discretization area is greater than the area of the underlying variable used by the object.

    Specification(s): variable_interface_error_block_any

    Design: Problem system overview

    Issue(s): #9889

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.17The system shall produce an error when an object's discretization area is explicitly set to a different area than the area of a coupled variable used by the object.

    Specification(s): coupleable_error_block_set

    Design: Problem system overview

    Issue(s): #9889

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.18The system shall produce an error when an object's discretization area is different than an explicitly set variable on only defined on a different portion of the mesh.

    Specification(s): coupleable_error_block_set2

    Design: Problem system overview

    Issue(s): #9889

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.19The system shall produce an error when an object's discretization area is covers the whole mesh but a coupled variable only exists on a portion of the mesh.

    Specification(s): coupleable_error_block_any

    Design: Problem system overview

    Issue(s): #9889

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.20The system shall report an error if a boundary restricted object depends on a variable that is not defined on any portion of the boundary. These boundary restricted objects include
    1. nodal auxiliary kernels
    2. nodal user objects
    3. nodal boundary conditions
    4. integrated boundary conditions
    5. side user objects
    6. elemental auxiliary kernels

    Specification(s): error/nodal_aux, error/nodal_uo, error/nodal_bc, error/integrated_bc, error/side_uo, error/elemental_aux

    Design: AuxKernels SystemUserObject System

    Issue(s): #9734

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.21The system shall report an error if a variable is coupled into a boundary restricted object, along whose boundary the variable is only partially defined.

    Specification(s): partial_coverage

    Design: AuxKernels SystemUserObject System

    Issue(s): #9734

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.22The system shall report an error if an object restricted on an internal boundarydepends on a variable that is not defined on any portion of the boundary.

    Specification(s): error

    Design: AuxKernels SystemUserObject System

    Issue(s): #9734

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.25The system shall report an error when a null pointer-checked parameter is retrieved from the InputParameters object.

    Specification(s): checked_pointer_param_test

    Design: Problem system overview

    Issue(s): #10356

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.26The system shall report an error when multiple AuxVariables are added to the system with conflicting types.

    Specification(s): add_aux_variable_multiple_test

    Design: Problem system overview

    Issue(s): #1222

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.27The system shall report an error when multiple Scalar AuxVariables are added to the system with conflicting types.

    Specification(s): add_aux_scalar_variable_multiple_test

    Design: Problem system overview

    Issue(s): #9313

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.28The system shall report an error when multiple AuxVariables are added to the system with conflicting block-restriction.

    Specification(s): add_aux_variable_multiple_subdomain_test

    Design: Problem system overview

    Issue(s): #28568

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.29The system shall report an error when an attempt is made to instantiate a non-existent BoundaryCondition object.

    Specification(s): bad_bc_test

    Design: Problem system overview

    Issue(s): #10486

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.30The system shall report an error when a non-existent nonlinear variable name is used by a MooseObject.

    Specification(s): bad_bc_var_test

    Design: Problem system overview

    Issue(s): #11227

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.31The system shall report an error message when an invalid enumeration is supplied in any MooseEnum type.

    Specification(s): bad_enum_test

    Design: Problem system overview

    Issue(s): #489

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.32The system shall report an error message when an invalid Executioner is specified.

    Specification(s): bad_executioner_test

    Design: Problem system overview

    Issue(s): #12106

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.33The system shall report an error message when an invalid Kernel is specified.

    Specification(s): bad_kernel_test

    Design: Problem system overview

    Issue(s): #12106

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.34The system shall report an error message when a Kernel object attempts to access a non-existent variable.

    Specification(s): bad_kernel_var_test

    Design: Problem system overview

    Issue(s): #11227

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.35The system shall report an error when an invalid Material is specified.

    Specification(s): bad_material_test

    Design: Problem system overview

    Issue(s): #12106

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.36The system shall report an error when a previously undeclared variable is used in a parsed function expression.

    Specification(s): bad_parsed_function_vars_test

    Design: Problem system overview

    Issue(s): #4683

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.37The system shall report an error when a first order element is used with a second order discretization.

    Specification(s): bad_second_order_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.38The system shall report an error message when a deprecated input file block is used.

    Specification(s): deprecated_block_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.39The system shall report a warning when a deprecated parameter with a default value is explicitly set by the user.

    Specification(s): deprecated_param_default

    Design: Problem system overview

    Issue(s): #1951

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.40The system shall report a warning when an optional deprecated parameter is explicitly set by the user.

    Specification(s): deprecated_param_no_default

    Design: Problem system overview

    Issue(s): #1951

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.41The system shall report an error when conflicting domain restrictions are applied to a single object.

    Specification(s): double_restrict_uo_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.42The system shall report an error when the number of ids and corresponding block names are mismatched.

    Specification(s): dynamic_check_name_block_mismatch_test

    Design: Problem system overview

    Issue(s): #8596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.43The system shall report an error when a duplicate name is provided for a set of unique block ids.

    Specification(s): dynamic_check_name_block_test

    Design: Problem system overview

    Issue(s): #8596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.44The system shall report an error when the number of ids and corresponding boundary names are mismatched.

    Specification(s): dynamic_check_name_boundary_mismatch_test

    Design: Problem system overview

    Issue(s): #8596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.45The system shall report an error when a duplicate name is provided for a set of unique boundary ids.

    Specification(s): dynamic_check_name_boundary_test

    Design: Problem system overview

    Issue(s): #8596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.46The system shall report an error when the linear interpolation utility is supplied with bad domain values.

    Specification(s): linear_interp_material_check

    Design: Problem system overview

    Issue(s): #5886

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.47The system shall report an error when the Piecewise utility encounters an unexpected column data format.

    Specification(s): function_file_test1

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.48The system shall report an error when the Piecewise utility encounters an unexpected row data format.

    Specification(s): function_file_test2

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.49The system shall report an error when the Piecewise utility encounters inconsistent domain and range data.

    Specification(s): function_file_test3

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.50The system shall report an error when an invalid enumeration is supplied in the Piecewise utility.

    Specification(s): function_file_test4

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.51The system shall report an error when the Piecewise data is over-specified with the data file option.

    Specification(s): function_file_test5

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.52The system shall report an error when the Piecewise data is over-specified with row/column data.

    Specification(s): function_file_test6

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.53The system shall report an error when either the domain or range is missing when using the domain/range option in the Piecewise utility.

    Specification(s): function_file_test7

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.54The system shall report and error if the supplied domain/range pairs are not even in the Piecewise utility.

    Specification(s): function_file_test8

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.55The system shall report an error if no function is supplied in the Piecewise utility.

    Specification(s): function_file_test9

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.56The system shall report an error if the xy_data is supplied but the function is missing in the Piecewise utility.

    Specification(s): function_file_test10

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.57The system shall report an error when the number of columns appears incorrect in the Piecewise utility.

    Specification(s): function_file_test11

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.58The system shall report an error when an out of range y-column index is supplied in the Piecewise utility.

    Specification(s): function_file_test12

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.59The system shall report an error when an out of range x-column index is supplied in the Piecewise utility.

    Specification(s): function_file_test13

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.60The system shall report an error if too many rows are supplied when the data is expected to contain row information.

    Specification(s): function_file_test14

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.61The system shall report an error when an out of range x-row index is supplied in the Piecewise utility.

    Specification(s): function_file_test15

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.62The system shall report an error when an out of range y-row index is supplied in the Piecewise utility.

    Specification(s): function_file_test16

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.63The system shall report an error when the x and y index in file are equal in the Piecewise utility.

    Specification(s): function_file_test17

    Design: Problem system overview

    Issue(s): #2421

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.64The system shall report an error if one or more domain blocks do not have any active Kernels objects assigned.

    Specification(s): incomplete_kernel_block_coverage_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.65The system shall report an error if one or more variables do not have any active Kernel objects assigned.

    Specification(s): incomplete_kernel_variable_coverage_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.66The system shall report an error if one or more domain blocks do not have any active FVKernels objects assigned.

    Specification(s): incomplete_fvkernel_block_coverage_test

    Design: Problem system overview

    Issue(s): #1405#15196

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.67The system shall report an error if one or more variables do not have any active FVKernel objects assigned.

    Specification(s): incomplete_fvkernel_variable_coverage_test

    Design: Problem system overview

    Issue(s): #1405#15196

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.68The system shall report an error when an elemental variable (no C0C_0 continuity) is coupled to a variable with C0C_0 continuity.

    Specification(s): invalid_elemental_to_nodal_couple_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.69The system shall report an error when an active input block section is specified but missing.

    Specification(s): missing_active_section_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.70The system shall report an error when a material property is requested but not supplied on a mesh block.

    Specification(s): missing_coupled_mat_prop_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.71The system shall report an error when a coupled variable is supplied that was not added as a valid parameter.

    Specification(s): coupled_grad_without_declare

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.72The system shall report an error when the data file is non-existent or not-readable in the Piecewise utility.

    Specification(s): missing_function_file_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.73The system shall report an error when the coupled function does not exist or can not be parsed by a piecewise utility.

    Specification(s): missing_function_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.74The system shall report an error when one or more material properties are missing from any mesh block.

    Specification(s): missing_material_prop_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.75The system shall report an error when a material property is supplied on some blocks but missing on other blocks where it is requested.

    Specification(s): missing_material_prop_test2

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.76The system shall report an error when only "old" properties are supplied but current properties are requested.

    Specification(s): bad_stateful_material_only_old

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.77The system shall report an error when only "older" properties are supplied but current properties are requested.

    Specification(s): bad_stateful_material_only_older

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.78The system shall report an error when the mesh file cannot be found.

    Specification(s): missing_mesh_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.79The system shall report an error when a required parameter is not supplied in an Action.

    Specification(s): missing_req_par_action_obj_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.80The system shall report an error when a specific mesh required parameter is not supplied.

    Specification(s): missing_req_par_mesh_block_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.81The system shall report an error when the special "type" parameter is not supplied for a MooseObject.

    Specification(s): missing_req_par_moose_obj_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): missing_required_param_in_kernel_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.83The system shall report an error when the variable parameter is missing from a residual object

    Specification(s): missing_var_parameter_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.84The system shall report an error when a required coupling parameter is missing.

    Specification(s): missing_required_coupled_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.85The system shall report an error when more than one preconditioner block is supplied.

    Specification(s): multi_precond_test

    Design: Problem system overview

    Issue(s): #1904

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.86The system shall abort the solve and report a floating point error when a NaN is produced during user computation with the Steady executioner.

    Specification(s): nan_no_trap_fpe_test

    Design: Problem system overview

    Issue(s): #374#3614

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.87The system shall abort the solve and report a floating point error when a NaN is produced during user computation with the Transient executioner.

    Specification(s): nan_no_trap_fpe_test_trans

    Design: Problem system overview

    Issue(s): #374#3614

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.88The system shall report an error when a nodal AuxKernel attempts to access a material property.

    Specification(s): nodal_material_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.89The system shall report an error when the same named parameter appears multiple times in the same input file.

    Specification(s): override_name_variable_test

    Design: Problem system overview

    Issue(s): #9617

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.90The system shall report an error when the coordinate transformation conflicts with the underlying element types.

    Specification(s): rz_3d_error_check_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.91The system shall report an error when solver and auxiliary variables are declared with the same name.

    Specification(s): same_name_variable_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.92The system shall report an error when an AuxKernel is applied outside of the domain where a restricted variable exists.

    Specification(s): subdomain_restricted_auxkernel_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.93The system shall report an error when a Kernel is applied outside of the domain where a restricted variable exists.

    Specification(s): subdomain_restricted_kernel_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.94The system shall report an error when an unused parameter is provided through the input file or an Action.

    Specification(s): unused_param_test

    Design: Problem system overview

    Issue(s): #709#759#4101

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.95The system shall report an error when an unused parameter is supplied on the command line.

    Specification(s): unused_param_test_cli

    Design: Problem system overview

    Issue(s): #709#759#4101

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.96The system shall include the option to report a warning instead of an error for an unused parameter set in input.

    Specification(s): unused_param_test_warn

    Design: Problem system overview

    Issue(s): #709#759#4101

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.97The system shall include the option to report a warning instead of an error for an unused parameter set in command line arguments

    Specification(s): unused_param_test_warn_cli

    Design: Problem system overview

    Issue(s): #709#759#4101

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.98The system shall report an error when a UserObject and a Postprocessor are added with the same names.

    Specification(s): uo_pps_name_collision_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.99The system shall report and error when a UserObject and a VectorPostprocessor are added with the same names.

    Specification(s): uo_vector_pps_name_collision_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.100The system shall report an error when an input file block associated with a pluggable system is asked to build an object from a different system.

    Specification(s): wrong_object_test

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.101The system shall report an error when an input file block associated with a pluggable system is misspelled.

    Specification(s): wrong_action_spelling

    Design: Problem system overview

    Issue(s): #20062

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.102The system shall report a standard Unix usage statement when an invalid command line switch is used.

    Specification(s): wrong_input_switch

    Design: Problem system overview

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.103The system shall report an error when a required variable is missing from the ICs input file block.

    Specification(s): ics_missing_variable

    Design: Problem system overview

    Issue(s): #534

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.104The system shall report an error when a boundary restriction is applied to a non-nodal variable discretization.

    Specification(s): ic_bnd_for_non_nodal

    Design: Problem system overview

    Issue(s): #534

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.105The system shall report an error when coupling to old temporal solution vectors in a Steady (no time) Executioner.

    Specification(s): old_integrity_check

    Design: Problem system overview

    Issue(s): #380

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.106The system shall report an error when coupling to a time derivative solution vector in a Steady (no time) Executioner.

    Specification(s): dot_integrity_check

    Design: Problem system overview

    Issue(s): #10810

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.107The system shall report an error when an older scalar solution variable is accessed in a Steady (no time) Executioner.

    Specification(s): scalar_old_integrity_check

    Design: Problem system overview

    Issue(s): #10810

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.108The system shall report an error when an older time derivative scalar solution variable is accessed in a Steady (no time) Executioner.

    Specification(s): scalar_dot_integrity_check

    Design: Problem system overview

    Issue(s): #10810

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.109The system shall report an error when a coupled variable is not defined in the same region as the variable performing the coupling.

    Specification(s): node_value_off_block

    Design: Problem system overview

    Issue(s): #2849

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.110The system shall report the successful parsing and interpretation of input file syntax when using the "–check-input" command line flag.

    Specification(s): check_syntax_ok

    Design: Problem system overview

    Issue(s): #4437

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.111The system shall report an error when performing nodal constraints when there is a mismatch in the number of constrained nodes.

    Specification(s): check_syntax_error

    Design: Problem system overview

    Issue(s): #4437

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.112The system shall report an error when requested to check the syntax in an input file but no input file is supplied.

    Specification(s): check_syntax_no_input

    Design: Problem system overview

    Issue(s): #4437

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.113The system shall report an error when multiple time schemes are specified in the same input file.

    Specification(s): multiple_time_int_check

    Design: Problem system overview

    Issue(s): #5463

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.114The system shall report an error when there is a mismatch between the parameter for an object and the type of object are mismatched.

    Specification(s): calling_wrong_feproblem_method

    Design: Problem system overview

    Issue(s): #6383

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.115The system shall report an error when the variables representing displacement are of a lower order than the mesh.

    Specification(s): wrong_displacement_order

    Design: Problem system overview

    Issue(s): #6561

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.116The system shall report an error when the name of a function could be misinterpreted because it could also be evaluated (e.g. a function name of "x").

    Specification(s): function_conflict

    Design: Problem system overview

    Issue(s): #8412

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.117The system shall report an error when floating point input parameter types fail to parse as floating point numbers.

    Specification(s): bad_number

    Design: Problem system overview

    Issue(s): #10310

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.118The system shall report an error when a scalar variable is used where a spatial variable is expected.

    Specification(s): coupling_field_into_scalar

    Design: Problem system overview

    Issue(s): #10398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.119The system shall report an error when a field variable is used where a scalar variable is expected.

    Specification(s): coupling_scalar_into_field

    Design: Problem system overview

    Issue(s): #10398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.120The system shall report an error when an invalid coupled spatial variable is requested.

    Specification(s): coupling_nonexistent_field

    Design: Problem system overview

    Issue(s): #10398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.121The system shall report an error when an invalid coupled scalar variable is requested.

    Specification(s): coupling_nonexistent_scalar

    Design: Problem system overview

    Issue(s): #10398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.122The system shall report an error when an attempt is made to couple a variable with itself.

    Specification(s): coupling_itself

    Design: Problem system overview

    Issue(s): #10398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.123The system shall report an error when an attempt is made to couple a variable with itself in coupled force term using automated differentiation.

    Specification(s): coupling_itself_ad

    Design: Problem system overview

    Issue(s): #18214

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.124The system shall report an error when an input file cannot be opened and read.

    Specification(s): missing_input

    Design: Problem system overview

    Issue(s): #10909

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.125The system shall report an error when a Kernel attempts to use an auxiliary variable.

    Specification(s): kernel_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.126The system shall report an error when a boundary condition object attempts to use an auxiliary variable.

    Specification(s): bc_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.127The system shall report an error when an AuxKernel specifies a non-existent variable.

    Specification(s): aux_kernel_with_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.128The system shall report an error when a scalar Kernel specifies a non-existent variable.

    Specification(s): scalar_kernel_with_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.129The system shall report an error when a nodal Kernel attempts to use an auxiliary variable.

    Specification(s): nodal_kernel_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.130The system shall report an error when a constraint attempts to use an auxiliary variable.

    Specification(s): constraint_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.131The system shall report an error when a scalar auxiliary Kernel attempts to use a solution variable.

    Specification(s): scalar_aux_kernel_with_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.132The system shall report an error when a DiracKernel attempts to use an auxiliary variable.

    Specification(s): dirac_kernel_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.133The system shall report an error when a discontinuous Galerkin Kernel attempts to use an auxiliary variable.

    Specification(s): dg_kernel_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.134The system shall report an error when an interface Kernel attempts to use an auxiliary variable.

    Specification(s): interface_kernel_with_aux_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.135The system shall report an error when a Kernel attempts to retrieve an empty string variable.

    Specification(s): kernel_with_empty_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.136The system shall report an error when a vector Kernel attempts to use a scalar solution variable.

    Specification(s): vector_kernel_with_standard_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.137The system shall report an error when a Kernel attempts to use a vector solution variable.

    Specification(s): kernel_with_vector_var

    Design: Problem system overview

    Issue(s): #11039

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.138The system shall report an error if users try to get nodal values of non-nodal variables.

    Specification(s): coupled_nodal_for_non_nodal_variable

    Design: Coupleable

    Issue(s): #11623

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.139The system shall report an error if users try to get old nodal values of non-nodal variables.

    Specification(s): coupled_nodal_for_non_nodal_variable_old

    Design: Coupleable

    Issue(s): #11623

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.140The system shall report an error if users try to get older nodal values of non-nodal variables.

    Specification(s): coupled_nodal_for_non_nodal_variable_older

    Design: Coupleable

    Issue(s): #11623

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.141The system shall report an error if an object tries to get the name of a coupled constant.

    Specification(s): coupled_constant_yet_needs_name

    Design: Coupleable

    Issue(s): #22597

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.142The system shall have an integrity check that ensures an Executioner object exists in the system.

    Specification(s): missing_executioner

    Design: Executioner System

    Issue(s): #11586

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.143The system shall report an error when nodal boundary condition is applied on a non-nodal variable.

    Specification(s): nodal_bc_on_elemental_var

    Design: NonlinearSystem

    Issue(s): #14019

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.144The system shall report an error when a git-lfs file pointer is encountered for the mesh file.

    Specification(s): check_git_lfs_pointer

    Design: MooseUtils Namespace

    Issue(s): #17407

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.145The system shall report an error when a git-lfs file pointer is encountered for the mesh for a mesh generator.

    Specification(s): check_git_lfs_pointer_fmg

    Design: MooseUtils Namespace

    Issue(s): #17407

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.146The system shall report a helpful error when the dump parameter does not match any valid parameters

    Specification(s): dump_error_with_unrecogized_param

    Design: Problem system overview

    Issue(s): #26714

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.147The system shall support the ability for actions to query the existence of a mesh attribute (meta data).

    Specification(s): check_mesh_meta_data

    Design: MeshMetaDataInterface

    Issue(s): #15987

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.148The system shall be to find data files in designated directories, regardless of the source repository or install location.

    Specification(s): exists

    Design: MooseObject

    Issue(s): #20839

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.149The system shall throw an exception if a data file cannot be found in any of the designated directories.

    Specification(s): error

    Design: MooseObject

    Issue(s): #20839

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.150The system shall support the output a processor id field for the purposes of debugging

    Specification(s): test

    Design: SetupDebugActionProcessorIDAux

    Issue(s): #16154

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.151The system shall produce a warning when non-expired deprecated code is executed.

    Specification(s): deprecated

    Design: MooseApp

    Issue(s): #10745

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.152The system shall produce a warning when expired deprecated code is executed.

    Specification(s): expired

    Design: MooseApp

    Issue(s): #10745

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.153The system shall produce an error when the –no-deprecated-flag is passed and deprecated code is executed.

    Specification(s): expired_error

    Design: MooseApp

    Issue(s): #10745

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.154The system shall produce a warning indicating a possible replacement when deprecated code is superseded.

    Specification(s): renamed

    Design: MooseApp

    Issue(s): #10745

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.155The system shall be able to deprecate parameter names, while enabling user code to only use the new, blessed name

    Specification(s): deprecate_param

    Design: InputParameters

    Issue(s): #15497

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.156The system shall be able to deprecate coupled variable names, while enabling user code to only use the new, blessed name

    Specification(s): deprecated_coupled_var

    Design: InputParameters

    Issue(s): #15497

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.157The system shall not give a deprecation warning if the user uses the blessed coupled variable name instead of the deprecated coupled variable name.

    Specification(s): blessed_coupled_var

    Design: InputParameters

    Issue(s): #15497

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.158The system shall output one warning per deprecated parameter, regardless of how many deprecated parameters are in the system.

    Specification(s): deprec_param_duplicate_print

    Design: MooseApp

    Issue(s): #6780

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.159The system shall produce a warning only once indicating a possible replacement of an object when deprecated code is superseded.

    Specification(s): deprec_obj_two_obj

    Design: MooseApp

    Issue(s): #6780

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.160The system allow coupling between variables on or off displaced meshes
    1. not using automatic differentiation methods
    2. using automatic differentiation methods

    Specification(s): g/nonad, g/ad

    Design: MooseApp

    Issue(s): #9659

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.161The system shall add ghost entries to residual vectors when needed

    Specification(s): ghosted

    Design: NonlinearSystemBase

    Issue(s): #20654

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.162The system shall not add ghost entries to residual vectors when not needed

    Specification(s): not_ghosted

    Design: NonlinearSystemBase

    Issue(s): #20654

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.163The system shall support throwing an exception during the residual calculation, which will cut back the time step.

    Specification(s): parallel_exception_residual_transient

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.164The system shall support throwing an exception during the residual calculation on a non-zero rank, which will cut back the time step.

    Specification(s): parallel_exception_residual_transient_non_zero_rank

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.42.163

  • 2.42.165The system shall support throwing an exception during the Jacboain calculation, which will cut back the time step.

    Specification(s): parallel_exception_jacobian_transient

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.166The system shall support throwing an exception during the Jacobian calculation on a non-zero rank, which will cut back the time step.

    Specification(s): parallel_exception_jacobian_transient_non_zero_rank

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.42.165

  • 2.42.167The system shall support throwing an exception during the initial condition calculation, which will terminate the solve.

    Specification(s): parallel_exception_initial_condition

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.168The system shall support throwing an error during a residual calculation, which will terminate the solve.

    Specification(s): parallel_error_residual_transient_non_zero_rank

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.169The system shall support throwing an error during a Jacobian calculation, which will terminate the solve.

    Specification(s): parallel_error_jacobian_transient_non_zero_rank

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.170The system shall allow users to skip exception checks to avoid global communication.

    Specification(s): skip_exception_check

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.171The system shall interrupt a solve immediately as soon as an exception is thrown.

    Specification(s): exception_transient

    Design: MooseException

    Issue(s): #3777#9181

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.172The system shall maintain a flag available for inspection indicating the current "execution stage" enumeration.

    Specification(s): test

    Design: SetupInterface

    Issue(s): #8610

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.42.173The hit find command shall be able to find
    1. files with specific parameters,
    2. files not containing a specified parameter,
    3. parameters set to an exact specified value,
    4. parameters not set to an exact specified value,
    5. parameters with additional pattern constraints,
    6. parameters with additional inverted pattern constraints.

    Specification(s): find/parameter_exists, find/parameter_does_not_exist, find/positive_pattern, find/negative_pattern, find/additional_pattern, find/additional_pattern_negative

    Design: The hit command

    Issue(s): #19001

    Collection(s): FUNCTIONAL

    Type(s): RunCommand

  • 2.42.174The hit merge command shall be able to combine input files.

    Specification(s): merge

    Design: The hit command

    Issue(s): #19001

    Collection(s): FUNCTIONAL

    Type(s): RunCommand

  • 2.42.175The hit diff command shall be able to
    1. show differences between input files,
    2. show differences between input files marked up using terminal colors,
    3. show differences between input files with verbose explanations,
    4. show differences between input files with verbose explanations marked up using terminal colors,
    5. show common parameters/value pairs between input files,

    Specification(s): diff/vanilla, diff/color, diff/verbose, diff/verbose_color, diff/common

    Design: The hit command

    Issue(s): #19001

    Collection(s): FUNCTIONAL

    Type(s): RunCommand

  • 2.42.176The system shall verify equality among the current, old, and older solution vectors prior to running the simulation.

    Specification(s): equal_solutions

    Design: ICs System

    Issue(s): #1396

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.177The system shall support a testing mechanism that fails intermittently.

    Specification(s): intermittent_failure

    Design: Framework Software Test Plan

    Issue(s): #13334

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.178We shall be able the scrape the DOFMapOutput and determine when the Jacobian is slightly off

    Specification(s): simple

    Design: Assembly

    Issue(s): #4182

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 2.42.179We shall be able the scrape the DOFMapOutput and determine when the Jacobian is questionable

    Specification(s): med

    Design: Assembly

    Issue(s): #4182

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 2.42.180We shall throw no errors if the off-diagonal Jacobian is wrong if we are only testing the on-diagonal Jacobian

    Specification(s): offdiag

    Design: Assembly

    Issue(s): #6624

    Collection(s): FUNCTIONAL

    Type(s): AnalyzeJacobian

  • 2.42.181If use_displaced_mesh = false then MOOSE will not throw an exception if elements are inverted to produce a negative element Jacobian, in 3D simulations

    Specification(s): no_negative_jacobian

    Design: Assembly

    Issue(s): #9740

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.182A 3D simulation shall throw an exception if there is a zero element Jacobian, when use_displaced_mesh = true

    Specification(s): jacobian_zero

    Design: Assembly

    Issue(s): #9740

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.42.181

  • 2.42.183A 3D simulation shall throw an exception if there is a negative element Jacobian, when use_displaced_mesh = true

    Specification(s): jacobian_negative

    Design: Assembly

    Issue(s): #9740

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.42.181

  • 2.42.184If use_displaced_mesh = false then MOOSE will not throw an exception if elements are inverted to produce a negative element Jacobian, in 2D simulations

    Specification(s): no_negative_jacobian_2D

    Design: Assembly

    Issue(s): #9740#10229

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.185If use_displaced_mesh = false then MOOSE will not throw an exception if elements are distored to produce a zero element Jacobian, in 2D simulations

    Specification(s): zero_jacobian_2D_ok

    Design: Assembly

    Issue(s): #9740#10229

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.42.184

  • 2.42.186A 2D simulation shall throw an exception if there is a zero element Jacobian, when use_displaced_mesh = true

    Specification(s): jacobian_zero_2D

    Design: Assembly

    Issue(s): #9740#10229

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.42.185

  • 2.42.187The PETSc Jacobian test shall reveal nans if there are nans in the matrix

    Specification(s): inf_nan

    Design: Assembly

    Issue(s): #10788

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.42.188The system shall support embedding a 1D block inside of a 3D block.

    Specification(s): test

    Design: Mesh System

    Issue(s): #3990

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.189The maximum number of degrees of freedom for a single variable on a 1D EDGE2 elem shall be 2

    Specification(s): 1d

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.190The maximum number of degrees of freedom for a single variable on a 2D QUAD4 elem shall be 4

    Specification(s): 2d

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.191The maximum number of degrees of freedom for a single variable on a 2D QUAD9 elem shall be 9

    Specification(s): 2d_high_order

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.192The maximum number of degrees of freedom for a single variable on a 2D TRI3 elem shall be 3

    Specification(s): triangles

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.193The maximum number of degrees of freedom for a single variable on a 2D TRI6 elem shall be 6

    Specification(s): triangles_second_order

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.194The maximum number of degrees of freedom for a single variable on a 2D TRI7 elem shall be 7

    Specification(s): triangles_third_order

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.195The maximum number of degrees of freedom for a single variable on a 3D HEX8 elem shall be 8

    Specification(s): 3d

    Design: MaxVarNDofsPerElem

    Issue(s): #5658

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.196The system shall report an error if the user provides inconsistent parameter values to the mesh and problem for the parameters related to
    1. subdomain blocks
    2. coordinate system types

    Specification(s): bad_params/block, bad_params/coord_type

    Design: Mesh System

    Issue(s): #21975

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.197The software shall be able to solve a system of equations in which one variable depends on another by
    1. segregating the solves; first the independent variable is solved for, and second the dependent variable is solved for using the solution of the first
    2. segregating the solves using finite volume discretization; first the independent variable is solved for, and second the dependent variable is solved for using the solution of the first
    3. solving the equations monolothically; both the independent and dependent variable equations are solved in a single large system

    Specification(s): coupled_system/segregated, coupled_system/segregated-fv, coupled_system/monolithic

    Design: Problem system overview

    Issue(s): #8780

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • The system shall be able to perform a segregated solve using AD objects and
    1. match the results of a segregated solve using hand-coded Jacobian objects
    2. show a perfect Jacobian for both solves

    Specification(s): AD/residuals, AD/jacobian

    Design: Problem system overview

    Issue(s): #8780

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTesterExodiff

  • 2.42.199The system shall be able to perform a segregated solve using objects with hand-coded Jacobians and show perfect Jacobians for those objects.

    Specification(s): hand-jac

    Design: Problem system overview

    Issue(s): #8780

    Collection(s): FUNCTIONAL

    Type(s): PetscJacobianTester

  • 2.42.200The software shall allow having a different number of variables in nonlinear systems within the same problem when the action of the Jacobian is provided by
    1. an assembled matrix, or
    2. a matrix-free approximation.

    Specification(s): different_num_vars_per_system/newton, different_num_vars_per_system/pjfnk

    Design: Problem system overview

    Issue(s): #8780

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.201The system shall be able to output postprocessor data after solving multiple solver systems.

    Specification(s): postprocessors

    Design: Problem system overview

    Issue(s): #28331

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.202The system shall be able to restart multiple nonlinear variables from different nonlinear systems from an exodus file
    1. using problem_out.e as a starting point, slightly modify the BCs and rerun

    Specification(s): restart/restart_problem

    Design: Problem system overview

    Issue(s): #26580

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.203The testing system shall support the ability to disable geometrical mapping of mesh elements for comparison purposes.

    Specification(s): test

    Design: Framework Software Test Plan

    Issue(s): #6011

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.204The system shall use the default PETSc option database in the parent app to handle system-level PETSc parameters

    Specification(s): test_options_not_left

    Design: FEProblem

    Issue(s): #15129

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.205The system shall warn the user of unused options if and only if they are not valid moose options.

    Specification(s): test_non_petsc_options_not_left

    Design: FEProblem

    Issue(s): #25577

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.206The system shall print an understandable message when a user-specified path/file does not exist.

    Specification(s): except01

    Design: Parser

    Issue(s): #15718

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.207The system shall allow application developers, in derived classes, to rename
    1. parameters
    2. coupled field variables
    3. coupled scalar variables
    4. functors
    5. material properties
    6. postprocessors

    Specification(s): renamed/param, renamed/coupled-field, renamed/coupled-scalar, renamed/coupled-functor, renamed/coupled-mat-prop, renamed/coupled-postprocessor

    Design: InputParameters

    Issue(s): #23259

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.208The system shall set vector and matrix types from the PETSc command line option parameters within an input file.

    Specification(s): take_vec_mat_types

    Design: Executioner

    Issue(s): #28380#28354

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.42.209The system shall be capable of storing residual contributions as an auxiliary field variable for
    1. continuous Galerkin and
    2. discontinuous Galerkin methods.

    Specification(s): save_in/cg, save_in/dg

    Design: Kernels System

    Issue(s): 4cb5e2a9f87973dba738584db39f7db935b65ce5

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.210The system shall report an error if the residual calculation contribution is assigned to the incorrect variable for
    1. on-diagonal and
    2. off-diagonal terms.

    Specification(s): error/test_soln_var_err, error/test_diag_sol_var_err

    Design: Kernels System

    Issue(s): 4cb5e2a9f87973dba738584db39f7db935b65ce5

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.211The system shall be able to compute the same value for a block-restricted save-in variable regardless of the number of processes used to run a simulation.

    Specification(s): block-restricted-save-in

    Design: Kernels System

    Issue(s): #12239

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.212The system shall only reinitialize variables values that are consumed by other active objects in the system.

    Specification(s): test

    Design: FEProblemBase

    Issue(s): #1386#18777

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.213The system shall make a serialized solution vector available when requested by objects in the system.

    Specification(s): test

    Design: SystemBase

    Issue(s): #4490

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.214The system shall make a serialized solution vector available when requested by objects in the system when uniform refinement is active.

    Specification(s): uniform_refine

    Design: SystemBase

    Issue(s): #4490

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.215The system shall make a serialized solution vector available when requested by objects in the system when adaptivity is active.

    Specification(s): adapt

    Design: SystemBase

    Issue(s): #4490

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.216The test system shall have the ability to execute a specific input file.

    Specification(s): execute

    Design: Framework Software Test Plan

    Issue(s): #7215

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.217The test system shall have the ability to run a test that neither clears expected outputs or runs the expected executeable for multiple output testing.

    Specification(s): dont

    Design: Framework Software Test Plan

    Issue(s): #7215

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.42.216

  • 2.42.218The app should write out a checkpoint file at any time by sending a signal to it.

    Specification(s): test_signal

    Design: Restart and RecoverCheckpoint

    Issue(s): #12722

    Collection(s): FUNCTIONAL

    Type(s): SignalTester

  • 2.42.219The app should be able to recover from the autosaved checkpoint created by a signal.

    Specification(s): test_signal_recover

    Design: Restart and RecoverCheckpoint

    Issue(s): #12722

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.42.218

  • 2.42.220The app, recovered from a signal-created checkpoint, should produce an accurate solution.

    Specification(s): test_signal_recover_exodiff

    Design: Restart and RecoverCheckpoint

    Issue(s): #25755

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.42.219

  • 2.42.221The app should write out a parallel checkpoint file at any time by sending a signal to it.

    Specification(s): test_signal_parallel

    Design: Restart and RecoverCheckpoint

    Issue(s): #12722

    Collection(s): FUNCTIONAL

    Type(s): SignalTester

  • 2.42.222The app should be able to recover from a parallel autosaved checkpoint created by a signal.

    Specification(s): test_signal_parallel_recover

    Design: Restart and RecoverCheckpoint

    Issue(s): #12722

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.42.221

  • 2.42.223The app, recovered from a parallel signal-created checkpoint, should produce an accurate solution.

    Specification(s): test_signal_parallel_recover_exodiff

    Design: Restart and RecoverCheckpoint

    Issue(s): #25755

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.42.222

  • 2.42.224The app should write out a checkpoint file at any time by sending a signal to it, in a debug build.

    Specification(s): test_signal_debug

    Design: Restart and RecoverCheckpoint

    Issue(s): #12722

    Collection(s): FUNCTIONAL

    Type(s): SignalTester

  • 2.42.225The app should be able to recover from the autosaved checkpoint created by a signal, in a debug build.

    Specification(s): test_signal_recover_debug

    Design: Restart and RecoverCheckpoint

    Issue(s): #12722

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.42.224

  • 2.42.226The app, recovered from a signal-created checkpoint, should produce an accurate solution in a debug build.

    Specification(s): test_signal_recover_exodiff_debug

    Design: Restart and RecoverCheckpoint

    Issue(s): #25755

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.42.225

  • 2.42.227The system shall not accept a converged solution if the solution has been tagged as invalid.

    Specification(s): solution_invalid

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.42.228The system shall allow overriding the solution validity checks.

    Specification(s): allow_solution_invalid

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.229The system shall be able to count warnings through the solution invalidity interface and report them,
    1. unless the user specifies to silence them,
    2. and otherwise both in the console window and a json file.

    Specification(s): solution_invalid_warning/no_console_output, solution_invalid_warning/console_output

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionRunApp

  • 2.42.230The system shall be able to output to screen immediately a detailed reason as to why a solution is invalid

    Specification(s): immediately_print_invalid_solution

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.231The system shall be able to output detailed reasons and occurrences as to why a solution is invalid to file

    Specification(s): solution_invalid_json

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.42.232The system shall be able to output detailed information about why a solution is invalid to a file in transient simulations

    Specification(s): solution_invalid_transient

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.42.233The system shall be able to handle a solution invalidity happening on just one processor in a parallel run

    Specification(s): solution_invalid_parallel

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.42.234The system shall be able to handle a solution invalidity occurs in the previous time step and recover in the next time step

    Specification(s): solution_valid_again_by_cutting_step

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.235The system shall be able to support
    1. outputting of checkpoint files
    2. restarting from the output data

    Specification(s): test/solution_valid_checkpoint, test/solution_valid_recover

    Design: SolutionInvalidity

    Issue(s): #22814

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.42.236The system shall support pausing execution for the purpose of attaching a debugger after launch.

    Specification(s): test

    Design: MooseApp

    Issue(s): #11166

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.237The system shall support running a user-defined subroutine each time a subdomain change occurs when iterating over the mesh.

    Specification(s): test

    Design: SetupInterface

    Issue(s): #9474

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.42.238The application executable shall report the version with the –version command line argument.

    Specification(s): print_version_long

    Design: MooseApp

    Issue(s): #10163

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.42.239The application executable shall report the version with the -v command line argument.

    Specification(s): print_version_short

    Design: MooseApp

    Issue(s): #10163

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • framework: Mortar
  • 2.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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.43.16

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.43.63

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Multiapps
  • 2.44.1The system shall support running a multiapp simulation
    1. without using the Application system input block
    2. with explicitly specifying application type in the Application system input block.

    Specification(s): Run_multiapp/no_application_block, Run_multiapp/application_block

    Design: Application SystemCreateApplicationBlockAction

    Issue(s): #26474

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.44.2The system shall return an error
    1. when the input application type is not registered in main app
    2. when the input application type is not registered in sub app
    3. when a command line option is used to set the application type for a child application.

    Specification(s): errors/wrong_main_application_type, errors/wrong_sub_application_type, errors/application_type_set_for_subapp

    Design: Application SystemCreateApplicationBlockAction

    Issue(s): #26474

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.3The system shall allow use of automatic differentiation and automatic scaling in sub-applications.

    Specification(s): test

    Design: NonlinearSystemBase

    Issue(s): #17078

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.4The system shall support running a transient simulation with sub-applications that can fail and re-execute with smaller timesteps until the execution times for the parent and sub-applications are equivalent.

    Specification(s): test

    Design: TransientMultiApp

    Issue(s): #10609

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.5The system shall include the ability to execute a sub-application at the centroid of every element within the finite element mesh.

    Specification(s): test

    Design: CentroidMultiApp

    Issue(s): #10483#24264

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.6The system shall optionally allow the first sub-app to fully initialize before initializing all the remaining child apps in parallel.

    Specification(s): test_quiet

    Design: CentroidMultiApp

    Issue(s): #10483#24264

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): input_file

    Design: MultiApp System

    Issue(s): #4101#4113

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): unused_subapp_param

    Design: MultiApp System

    Issue(s): #4101#4113

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): positions

    Design: MultiApp System

    Issue(s): #1845#3556#5784

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): not_enough_positions

    Design: MultiApp System

    Issue(s): #1845#3556#5784

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): not_enough_position_files

    Design: MultiApp System

    Issue(s): #1845#3556#5784

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): both_positions

    Design: MultiApp System

    Issue(s): #1845#3556#5784

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): bad_positions

    Design: MultiApp System

    Issue(s): #1845#3556#5784

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.14The system shall report an error when the Multiapp parameter sub_cycling and catch_up are both set to true.

    Specification(s): sub_cycling_and_catch_up

    Design: MultiApp System

    Issue(s): #6127

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.15The system shall support reading command-line arguments from a file with multiple lines

    Specification(s): multiline_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.16The system shall support reading command-line arguments from a file with a single line

    Specification(s): one_line_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.15

  • 2.44.17The system shall support reading command-line arguments from multiple files

    Specification(s): two_files

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.16

  • 2.44.18The system shall support reading command-line arguments from a file with multiple parameters separated semicolon

    Specification(s): multiple_parameters

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.17

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

    Specification(s): input_and_from_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): input_and_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): no_cliarg_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.22The system shall not use an empty commandLine argument file

    Specification(s): empty_cliarg_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): inconsistent_cliargs_from_file

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): positions_and_cliargs

    Design: MultiApp System

    Issue(s): #18596

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.25The system shall be able to clone the mesh created in parent application into its sub-application(s) for geometries in
    1. XY-cartesian coordinates,
    2. RZ-cylindrical coordinates, and
    3. R-spherical coordinates.

    Specification(s): clone/XY, clone/RZ, clone/RSpherical

    Design: MultiApp System

    Issue(s): #24345

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.44.26The MultiApp system shall include the ability to set command line parameters for each sub application from the input file.

    Specification(s): parent

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.27The MultiApp system shall include the ability to set common command line parameters for all sub applications from the input file.

    Specification(s): parent_common

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.28The MultiApp system shall include the ability to set common command line vector parameters, using double quotes, for all sub applications from the input file.

    Specification(s): common_vector

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.29The MultiApp system shall include the ability to set common command line vector parameters, using single quotes, for all sub applications from the input file.

    Specification(s): common_vector_single

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.28

  • 2.44.30The MultiApp system shall include the ability to set command line vector parameters, using double quotes, distributed among all sub applications from the input file.

    Specification(s): split_with_vector_single

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.29

  • 2.44.31The MultiApp system shall include the ability to set command line vector parameters, using single quotes, distributed among all sub applications from the input file.

    Specification(s): split_with_vector_double

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.30

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

    Specification(s): wrong_size

    Design: MultiApp System

    Issue(s): #12576

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.33The system shall include the ability to halt the execution of sub-applications when steady-state is detected.

    Specification(s): test

    Design: MultiApp System

    Issue(s): #1893

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.34The system shall be capable of executing a sub-application from a Steady executioner on
    1. initial and
    2. final.

    Specification(s): steady/exec_initial, steady/exec_final

    Design: FullSolveMultiApp

    Issue(s): #1940

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.35The system shall be capable of executing a sub-application from a Eigenvalue executioner on
    1. initial and
    2. final.

    Specification(s): nl_eigen/exec_initial, nl_eigen/exec_final

    Design: FullSolveMultiApp

    Issue(s): #1940

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

    Design: FullSolveMultiApp

    Issue(s): #1940

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunExceptionExodiff

  • 2.44.37The system shall be able to use the solution of a coarse mesh as the initial guess for a fine mesh solution for a
    1. diffusion problem and a
    2. variational inequality problem resulting in a significantly reduced number of nonlinear iterations to solve the fine mesh problem

    Specification(s): sequencing/diffusion, sequencing/vi

    Design: MultiAppShapeEvaluationTransfer

    Issue(s): #14166

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.38The system shall be able to solve a fine mesh variational inequality problem without grid sequencing but with a lot more nonlinear iterations

    Specification(s): no_sequencing

    Design: MultiAppShapeEvaluationTransfer

    Issue(s): #14166

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.39The system shall report an error if the execution of a sub-application fails during the initial execution.

    Specification(s): initial_multiapp_failure

    Design: MultiApp System

    Issue(s): #7213

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.40The system shall support creating a Multiapp that is not initially enabled

    Specification(s): initial_inactive

    Design: TransientMultiApp

    Issue(s): #12642

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.41The system shall allow forcibly evaluating general user objects on the initial timestep before applying initial conditions.

    Specification(s): test

    Design: UserObject

    Issue(s): #14676

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.42The system shall be able to keep the auxiliary solution during fixed point iterations.

    Specification(s): aux

    Design: MultiApp System

    Issue(s): #19078

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.43The system shall support the ability for a sub-application to adaptive modify the time step of the parent application when the sub-application operates at the
    1. beginning and
    2. end of a timestep.

    Specification(s): group/begin, group/end

    Design: MultiApp System

    Issue(s): #7842

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.44The system shall support limiting the number of processors for sub-applications.

    Specification(s): test

    Design: MultiApp System

    Issue(s): #1873

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.45The system shall support the ability to re-position sub-applications at a specified time
    1. for single and
    2. multi-level sub-applications.

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

    Design: MultiApp System

    Issue(s): #1971

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.46The system shall support the ability to re-position and reset sub-applications at a specified time
    1. for single and
    2. multi-level sub-applications.

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

    Design: MultiApp System

    Issue(s): #1971

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.47The system shall support evaluating multi-level sub-applications:
    1. where the parent application controls the time step for all sub-applications;
    2. where the parent application controls the time step via a function for all sub-applications; and
    3. where the sub-application controls the time step for the parent application,

    Specification(s): group/dt_from_parent, group/time_dt_from_parent, group/dt_from_sub

    Design: MultiApp System

    Issue(s): #1832

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.48The system shall support writing screen output from multi-level sub-applications to a file.

    Specification(s): console_to_file

    Design: MultiApp System

    Issue(s): #1832

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 2.44.47

  • 2.44.49The system shall be capable of running multiple sub-applications that are defined by input and position file pairs.

    Specification(s): test

    Design: MultiApp System

    Issue(s): #5784

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.50The system shall support outputting sub-application data in a specified position
    1. for single and
    2. multi-level sub-applications.

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

    Design: MultiApp System

    Issue(s): #1888

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.51The MultiApp system shall allow overriding the cliArgs function to provide parameters to the subapp programmatically.

    Specification(s): override_cli_args

    Design: MultiApp System

    Issue(s): #20443

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.52The system shall support the the ability to set solver options within sub-applications.

    Specification(s): test

    Design: MultiApp System

    Issue(s): #1872

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.53The system shall allow transient multiapps to use Picard iterations to rerun the time step

    Specification(s): test

    Design: TransientMultiApp

    Issue(s): #2116

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.54The system shall support adaptive time stepping for transient multiapps with Picard iterations controlled by tolerances

    Specification(s): iteration_adaptive

    Design: IterationAdaptiveDT

    Issue(s): #2116#10311

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.55The system shall reject the solve if the maximum number of Picard iterations is reached without converging

    Specification(s): iteration_adaptive_picard_max_its

    Design: IterationAdaptiveDT

    Issue(s): #12618

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.56The system shall allow transient multiapps with Picard iterations controlled by relative tolerances

    Specification(s): rel_tol

    Design: TransientMultiApp

    Issue(s): #2116

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.57The system shall allow transient multiapps with Picard iterations controlled by absolute tolerances

    Specification(s): abs_tol

    Design: TransientMultiApp

    Issue(s): #2116

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.58The system shall allow function-defined time stepping for transient multiapps

    Specification(s): function_dt

    Design: FunctionDT

    Issue(s): #5800

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.59The system shall allow steady-state Picard iteration with multiapps

    Specification(s): steady

    Design: FullSolveMultiApp

    Issue(s): #9038

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.60The system shall allow fixed number of Picard iterations

    Specification(s): steady_fixed_picard_its

    Design: FullSolveMultiApp

    Issue(s): #9038

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.44.59

  • 2.44.61The system shall allow steady-state Picard iteration with pseudo-transient multiapps

    Specification(s): steady_with_pseudo_transient_sub

    Design: FullSolveMultiApp

    Issue(s): #9038

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.62The system shall allow convergence check with user defined postprocessor directly.

    Specification(s): steady_with_postprocessor_convergence

    Design: FullSolveMultiApp

    Issue(s): #14642

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.63The system shall allow convergence check with the convergence of a user defined postprocessor.

    Specification(s): steady_with_postprocessor_diff_convergence

    Design: FullSolveMultiApp

    Issue(s): #14642

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.64The system shall show the Multiapp coupling convergence history of a user defined postprocessor that is used for convergence check.

    Specification(s): postprocessor_convergence_history

    Design: FullSolveMultiApp

    Issue(s): #16940

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.44.65The system shall support performing iterative solves of sub-applications that perform additional time steps to maintain time step consistency with the parent application
    1. resetting the initial condition for every coupling
    2. or re-using the previous solution as the initial condition for subsequent iterations.

    Specification(s): catch_up/test, catch_up/keep_solution

    Design: MultiApp System

    Issue(s): #10337

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.66Multiapps shall be able to be restored when a subapp encounters a solve failure.

    Specification(s): test

    Design: MultiApp System

    Issue(s): #5126

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.67CSV file writing should remain unaffected when a subapp encounters a solve failure.

    Specification(s): test_csv

    Design: MultiApp System

    Issue(s): #11178

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.68Multiapps shall be able to cut the parent app time step when any subapp encounters a solve failure.

    Specification(s): test_2subapps

    Design: MultiApp System

    Issue(s): #12477

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.69The system should be able to restart from the latest solution

    Specification(s): restart_from_latest_solution

    Design: TransientMultiApp

    Issue(s): #14056

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): parameter_error

    Design: TransientMultiApp

    Issue(s): #14056

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.44.69

  • 2.44.71The system shall support Picard iteration with a FullSolveMultiApp at the root with multiple multiapp levels.

    Specification(s): test

    Design: FullSolveMultiApp

    Issue(s): #13310

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.72The system shall be able to run multiple timesteps of a multi-level multi-app simulation, handling the case when Picard coupling between two levels fails to converge.

    Specification(s): run

    Design: TransientMultiApp

    Issue(s): #15166

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.44.73The system shall be able to uniformly cut the time-step across levels of a multi-app solve, even when there is no Picard coupling between two levels.

    Specification(s): python

    Design: TransientMultiApp

    Issue(s): #15166

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

    Prerequisite(s): 2.44.72

  • 2.44.74The system shall support Picard iteration with multiple levels of Multiapps.

    Specification(s): test

    Design: TransientMultiApp

    Issue(s): #5126#15837

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.75The system shall support the evaluation of TIMESTEP_BEGIN and TIMESTEP_END norms even when there are not active Multiapps on both of those execute_on times.

    Specification(s): test_force_norms

    Design: TransientMultiApp

    Issue(s): #12709#15837

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.44.32.44.42.44.52.44.332.44.412.44.442.44.492.44.522.44.532.44.662.44.712.44.742.44.782.44.80

  • 2.44.76The system shall allow multiapp steady-state simulations coupled by a postprocessor transfer using Picard iterations
    1. with a steady-state sub-application,
    2. and with pseudo-transient sub-applications.

    Specification(s): pp_steady/steady, pp_steady/steady_with_pseudo_transient_sub

    Design: FullSolveMultiApp

    Issue(s): #9038#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.77The system shall allow transient multiapp simulations coupled by a postprocessor transfer using Picard iterations
    1. with a failed timestep,
    2. with adaptive timestepping,
    3. with a subapp using a smaller timestep,
    4. with the sub-app and the postprocessor transfers executed at the beginning of each time step,
    5. with the sub-app executed at the beginning of each time step and postprocessor transfers executed at the end of each timestep,
    6. with the sub-app executed at the end of each time step and postprocessor transfers executed at the beginning of each timestep,
    7. with the sub-app and the postprocessor transfers executed at the end of each time step.
    8. for updating the subapp postprocessor with the sub-app and the variable transfers executed at the beginning of each time step,
    9. for updating the subapp postprocessor with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    10. for updating the subapp postprocessor with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    11. and for updating the subapp postprocessor with the sub-app and the variable transfers executed at the end of each time step.

    Specification(s): pp_transient/test_rerun, pp_transient/iteration_adaptive, pp_transient/sub_cycling, pp_transient/app_begin_transfers_begin, pp_transient/app_begin_transfers_end, pp_transient/app_end_transfers_begin, pp_transient/app_end_transfers_end, pp_transient/app_begin_transfers_begin_picard_sub, pp_transient/app_begin_transfers_end_picard_sub, pp_transient/app_end_transfers_begin_picard_sub, pp_transient/app_end_transfers_end_picard_sub

    Design: TransientMultiApp

    Issue(s): #2116#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.78The system shall support performing iterative solves of sub-applications that used smaller time steps than parent application.

    Specification(s): test

    Design: MultiApp System

    Issue(s): #5126

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.79The system shall support evaluating sub-applications at spatial positions specified in a file.

    Specification(s): dt_from_multi

    Design: MultiApp System

    Issue(s): #1845

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.80The system shall include the ability to execute a sub-application at the quadrature points on every element within the finite element mesh.

    Specification(s): test

    Design: QuadraturePointMultiApp

    Issue(s): #22490

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.81The system shall provide an ability to perform iterative solves with sub-applications.

    Specification(s): standard

    Design: Executioner System

    Issue(s): #9115

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.82The system shall provide an ability to relax solutions with iterative solves with sub-applications.

    Specification(s): parent_relaxed

    Design: Executioner System

    Issue(s): #9115

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.83The system shall provide an ability to relax sub-applications solutions along with the parent solution for during iterative solves.

    Specification(s): sub_relaxed

    Design: Executioner System

    Issue(s): #9115

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.84The system shall provide an ability to relax solutions of array variables with iterative solves with sub-applications.

    Specification(s): array_relaxed

    Design: Executioner System

    Issue(s): #9115

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): bad_relax_factor

    Design: Executioner System

    Issue(s): #9115

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.86The system shall support the ability to reset a sub-application at a specified time during the simultation
    1. for single and
    2. multi-level sub-applications.

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

    Design: MultiApp System

    Issue(s): #1970

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.87The system shall support the ability to reset a sub-application at multiple specified times during the simultation

    Specification(s): multiple_times

    Design: MultiApp System

    Issue(s): #1970

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): not_sorted_times

    Design: MultiApp System

    Issue(s): #1970

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.89The system shall support simulations that
    1. that execute sub-applications, which
    2. are capable of being restarted from a previous simulation.

    Specification(s): group/first, group/second

    Design: MultiApp System

    Issue(s): #5695

    Collection(s): FUNCTIONAL

    Type(s): RunAppExodiff

    Prerequisite(s): 2.44.902.44.91

  • 2.44.90The system shall support simulations that
    1. that execute with multi-level sub-applications, which
    2. are capable of being restarted from a previous simulation.

    Specification(s): group/first, group/second

    Design: MultiApp System

    Issue(s): #5695

    Collection(s): FUNCTIONAL

    Type(s): RunAppExodiff

    Prerequisite(s): 2.44.892.44.91

  • 2.44.91The system shall support simulations that
    1. that executes sub-applications, which
    2. can restart from a previous simulation and project the initial condition from the previous solution to the current, restarted simulation.

    Specification(s): group/first, group/second

    Design: MultiApp System

    Issue(s): #6087

    Collection(s): FUNCTIONAL

    Type(s): RunAppExodiff

    Prerequisite(s): 2.44.892.44.90

  • 2.44.92The system shall support executing sub-applications in a specified position and/or with the specified frame of reference transformation
    1. with a scaled, rotated, translated child application
    2. with a scaled, rotated, translated parent application exchanging information with a translated child application

    Specification(s): group/multi-app, group/transform-main-multi-app

    Design: MultiApp System

    Issue(s): #19121

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

    Design: MultiApp System

    Issue(s): #19121

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.94The system shall allow multiapp simulations coupled by a variable transfer transformed using the Secant method for transient problems
    1. with a failed timestep,
    2. with adaptive timestepping,
    3. coupled with a subapp using a smaller timestep,
    4. with the sub-app and the variable transfers executed at the beginning of each time step,
    5. with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    6. with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    7. with the sub-app and the variable transfers executed at the end of each time step.
    8. and when updating the subapp variables with the sub-app and the variable transfers executed at the beginning of each time step,
    9. for when updating the subapp variables with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    10. for updating the subapp variables with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    11. and for updating the subapp variables with the sub-app and the variable transfers executed at the end of each time step.

    Specification(s): variables_transient/test_rerun, variables_transient/iteration_adaptive, variables_transient/sub_cycling, variables_transient/app_begin_transfers_begin, variables_transient/app_begin_transfers_end, variables_transient/app_end_transfers_begin, variables_transient/app_end_transfers_end, variables_transient/app_begin_transfers_begin_secant_sub, variables_transient/app_begin_transfers_end_secant_sub, variables_transient/app_end_transfers_begin_secant_sub, variables_transient/app_end_transfers_end_secant_sub

    Design: TransientMultiApp

    Issue(s): #2116#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.95The system shall allow multiapp steady-state simulations coupled by a postprocessor transfer using the secant method
    1. with a steady-state sub-application,
    2. and with pseudo-transient sub-applications.

    Specification(s): pp_steady/steady, pp_steady/steady_with_pseudo_transient_sub

    Design: FullSolveMultiApp

    Issue(s): #9038#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.96The system shall allow transient multiapp simulations coupled by a postprocessor transfer using the secant method
    1. with a failed timestep,
    2. with adaptive timestepping,
    3. with a subapp using a smaller timestep,
    4. with the sub-app and the postprocessor transfers executed at the beginning of each time step,
    5. with the sub-app executed at the beginning of each time step and postprocessor transfers executed at the end of each timestep,
    6. with the sub-app executed at the end of each time step and postprocessor transfers executed at the beginning of each timestep,
    7. with the sub-app and the postprocessor transfers executed at the end of each time step.
    8. for updating the subapp postprocessor with the sub-app and the variable transfers executed at the beginning of each time step,
    9. for updating the subapp postprocessor with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    10. for updating the subapp postprocessor with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    11. and for updating the subapp postprocessor with the sub-app and the variable transfers executed at the end of each time step.

    Specification(s): pp_transient/test_rerun, pp_transient/iteration_adaptive, pp_transient/sub_cycling, pp_transient/app_begin_transfers_begin, pp_transient/app_begin_transfers_end, pp_transient/app_end_transfers_begin, pp_transient/app_end_transfers_end, pp_transient/app_begin_transfers_begin_secant_sub, pp_transient/app_begin_transfers_end_secant_sub, pp_transient/app_end_transfers_begin_secant_sub, pp_transient/app_end_transfers_end_secant_sub

    Design: TransientMultiApp

    Issue(s): #2116#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.97MultiApps shall be properly identified in the PerfGraph

    Specification(s): slow_sub

    Design: PerfGraph

    Issue(s): #19662

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.44.98The system shall support executing sub-applications that operate with smaller time steps then the parent application that include material properties that are based on previous time steps.

    Specification(s): test_stateful_subcycle

    Design: MultiApp System

    Issue(s): #8286

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.99The system shall allow multiapp simulations coupled by a variable transfer transformed using Steffensen's method for transient problems
    1. with a failed timestep,
    2. with adaptive timestepping,
    3. coupled with a subapp using a smaller timestep,
    4. with the sub-app and the variable transfers executed at the beginning of each time step,
    5. with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    6. with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    7. with the sub-app and the variable transfers executed at the end of each time step.
    8. and when updating the subapp variables with the sub-app and the variable transfers executed at the beginning of each time step,
    9. for when updating the subapp variables with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    10. for updating the subapp variables with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    11. and for updating the subapp variables with the sub-app and the variable transfers executed at the end of each time step.

    Specification(s): variables_transient/test_rerun, variables_transient/iteration_adaptive, variables_transient/sub_cycling, variables_transient/app_begin_transfers_begin, variables_transient/app_begin_transfers_end, variables_transient/app_end_transfers_begin, variables_transient/app_end_transfers_end, variables_transient/app_begin_transfers_begin_steffensen_sub, variables_transient/app_begin_transfers_end_steffensen_sub, variables_transient/app_end_transfers_begin_steffensen_sub, variables_transient/app_end_transfers_end_steffensen_sub

    Design: TransientMultiApp

    Issue(s): #2116#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.100The system shall allow multiapp steady-state simulations coupled by a postprocessor transfer using Steffensen's method
    1. with a steady-state sub-application,
    2. and with pseudo-transient sub-applications.

    Specification(s): pp_steady/steady, pp_steady/steady_with_pseudo_transient_sub

    Design: FullSolveMultiApp

    Issue(s): #9038#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.101The system shall allow transient multiapp simulations coupled by a postprocessor transfer using Steffensen's method
    1. with a failed timestep,
    2. with adaptive timestepping,
    3. with a subapp using a smaller timestep,
    4. with the sub-app and the postprocessor transfers executed at the beginning of each time step,
    5. with the sub-app executed at the beginning of each time step and postprocessor transfers executed at the end of each timestep,
    6. with the sub-app executed at the end of each time step and postprocessor transfers executed at the beginning of each timestep,
    7. with the sub-app and the postprocessor transfers executed at the end of each time step.
    8. for updating the subapp postprocessor with the sub-app and the variable transfers executed at the beginning of each time step,
    9. for updating the subapp postprocessor with the sub-app executed at the beginning of each time step and variable transfers executed at the end of each timestep,
    10. for updating the subapp postprocessor with the sub-app executed at the end of each time step and variable transfers executed at the beginning of each timestep,
    11. and for updating the subapp postprocessor with the sub-app and the variable transfers executed at the end of each time step.

    Specification(s): pp_transient/test_rerun, pp_transient/iteration_adaptive, pp_transient/sub_cycling, pp_transient/app_begin_transfers_begin, pp_transient/app_begin_transfers_end, pp_transient/app_end_transfers_begin, pp_transient/app_end_transfers_end, pp_transient/app_begin_transfers_begin_steffensen_sub, pp_transient/app_begin_transfers_end_steffensen_sub, pp_transient/app_end_transfers_begin_steffensen_sub, pp_transient/app_end_transfers_end_steffensen_sub

    Design: TransientMultiApp

    Issue(s): #2116#17479

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.44.102The system shall support the execution of sub-applications that operate with smaller time steps then the parent application:
    1. with a sub-application that continues to the end time of the parent application and
    2. with a sub-application that specifies and completion time prior to the parent application.

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

    Design: MultiApp System

    Issue(s): #1880

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.103The system shall support the output of sub-application data that operate with smaller time steps then the parent application.

    Specification(s): test_sub_cycle_output

    Design: MultiApp System

    Issue(s): #1880

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.104The system shall support the execution of sub-application that operate with adaptive time steps that differ from the parent application.

    Specification(s): test_it_adapt

    Design: MultiApp System

    Issue(s): #1880

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.105The system shall support sub-cycling with negative times by particularly ensuring that the sub-app does not advance further than the main app.

    Specification(s): test_negative_time

    Design: MultiApp System

    Issue(s): #15766

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.106The system shall support the failure of sub-application that operates with differing time steps than the parent application.
    1. The simulation shall continue by reducing the time step and
    2. support the failure and the ability to limit the number of processors for the sub-application.

    Specification(s): group/test_failure, group/test_failure_max_procs

    Design: MultiApp System

    Issue(s): #1880

    Collection(s): FUNCTIONAL

    Type(s): ExodiffRunApp

  • 2.44.107The system shall support a time offset between the parent and a subapp when using the Multiapp system.

    Specification(s): start_time

    Design: TransientMultiApp

    Issue(s): #12755

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): warning

    Design: TransientMultiApp

    Issue(s): #22338

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.44.109The system shall support the execution of sub-applications:
    1. with a time step governed by the sub-application and
    2. with a time step governed by the parent application.

    Specification(s): group/dt_from_multi, group/dt_from_parent

    Design: TransientMultiApp

    Issue(s): #1736

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.44.110The system shall support negative times by particularly ensuring that the sub-app properly updates its time without sub-cycling.

    Specification(s): test_negative_time

    Design: TransientMultiApp

    Issue(s): #15802

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • framework: Nodalkernels
  • 2.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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Outputs
  • 2.46.1The system shall support the ability to append the date to output filenames.

    Specification(s): test

    Design: FileOutput

    Issue(s): #6001

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.2The system shall support outputting of checkpoint files:
    1. at a specific interval while only maintaining a specified number of recent files and
    2. be capable of restarting a simulation from previously exported data at this interval.

    Specification(s): interval/test_files, interval/test_recover

    Design: Checkpoint

    Issue(s): #1927#2395#27240

    Collection(s): FUNCTIONAL

    Type(s): CheckFilesExodiff

  • 2.46.3The system shall support outputting of checkpoint files, using a simplified input format:
    1. at every timestep while maintaining the most recent two files and
    2. be capable of restarting a simulation from the output data.
    3. at specified wall time intervals and
    4. be capable of restarting a simulation from the wall time checkpoint.
    5. with an option to disable wall time checkpoints and
    6. not recover.
    7. catching invalid values of output-wall-time-interval.
    8. at specified wall time intervals smaller than the time required to output a checkpoint
    9. ensuring that wall time checkpoints are not written at the subapp level if not explicitly requested.

    Specification(s): default/recover_half_transient, default/recover, default/wall_time_interval, default/wall_time_interval_recover, default/wall_time_interval_disabled, default/wall_time_interval_disabled_recover, default/output_wall_time_interval_error, default/wall_time_interval_tiny, default/wall_time_interval_multiapp

    Design: Checkpoint

    Issue(s): #1927#13562#27240

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): CheckFilesRunExceptionRunAppExodiff

  • 2.46.4The system shall support outputting of checkpoint files, using a complete input block:
    1. at every timestep while maintaining the most recent two files and
    2. be capable of restarting a simulation from the output data.
    3. at specified wall time intervals
    4. be capable of restarting a simulation from the wall time checkpoint.
    5. with an option to disable wall time checkpoints and
    6. not recover.
    7. catching invalid values of execute_on

    Specification(s): block/recover_with_checkpoint_block_half_transient, block/recover_with_checkpoint_block, block/wall_time_interval, block/wall_time_interval_recover, block/wall_time_interval_disabled, block/wall_time_interval_disabled_recover, block/execute_on_param_error

    Design: Checkpoint

    Issue(s): #1927#13562#25755#27240

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): CheckFilesRunExceptionRunAppExodiff

  • 2.46.5The system shall be capable of throwing an error when multiple checkpoints are defined

    Specification(s): multiple_checkpoints_error

    Design: Checkpoint

    Issue(s): #13562

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.6The system shall be capable of throwing an error when multiple checkpoints are defined, including the shortcut syntax

    Specification(s): multiple_checkpoints_error_shortcut

    Design: Checkpoint

    Issue(s): #13562

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.7The system shall support outputting checkpoint files at the subapp level with checkpoints disabled in the main app:
    1. for transient simulations
    2. for steady-state simulations

    Specification(s): subapp/subapp_only_cp_transient, subapp/subapp_only_cp_steady_state

    Design: Checkpoint

    Issue(s): #24777#20998

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.8The system shall support outputting of simulation data using the ExodusII format using simplified input file syntax.

    Specification(s): exodus

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.9The system shall by default display data on the console from:
    1. the Postprocessor system and
    2. the scalar variable system.

    Specification(s): console/postprocessors, console/scalar_variables

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.10The system shall output a running list of coupling iteration residual norms during multiapp coupling iterations.

    Specification(s): picard_norm_output

    Design: TransientMultiApp

    Issue(s): #12708

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.11The system shall only output the coupling iteration residual TIMESTEP_BEGIN norms when there are no TIMESTEP_END Multiapps.

    Specification(s): ts_begin_multi_output

    Design: TransientMultiApp

    Issue(s): #12708

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.12The system shall only output the coupling iteration TIMESTEP_END norms when there are no TIMESTEP_BEGIN Multiapps.

    Specification(s): ts_end_multi_output

    Design: TransientMultiApp

    Issue(s): #12708

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.13The system shall output the coupling iteration residual norm for TIMESTEP_BEGIN and TIMESTEP_END Multiapps when both exist in the simulation.

    Specification(s): ts_both_multi_output

    Design: TransientMultiApp

    Issue(s): #12708

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.14The system shall run a simulation without producing any file-based output.

    Specification(s): no_outputs_block

    Design: Console

    Issue(s): #3320

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.15The system shall support outputting table based Postprocessor data.

    Specification(s): postprocessors

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.16The system shall output Scalar Variables on the console in a table to the screen.

    Specification(s): scalar_variables

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.17The system shall warning when multiple console outputs attempt to write to the screen simultaneously.

    Specification(s): warning

    Design: Console

    Issue(s): #3286

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.18The system shall support outputting console information to a file.

    Specification(s): file_system_information

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.19The system shall support outputting head processor console information to a file when run in parallel.

    Specification(s): file_system_information_2procs_head

    Design: Console

    Issue(s): #26174

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.20The system shall support outputting all processors' console information to separate files when run in parallel with the –keep-cout command line option.

    Specification(s): file_system_information_2procs_all

    Design: Console

    Issue(s): #26174

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.21The system shall output Scalar Variables on the console in a table to a file.

    Specification(s): file_postprocessor

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.22The system shall support outputting Scalar Variables to a file.

    Specification(s): file_scalar_aux

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.23The system shall support writing the console solve log to an output file.

    Specification(s): file_solve_log

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.24The system shall support writing norms to the console for each nonlinear variable in the simulation.

    Specification(s): norms

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.25The system shall output a Performance log based on a command line flag.

    Specification(s): timing

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.26The system shall support writing negative time information in the console.

    Specification(s): transient

    Design: Console

    Issue(s): #1927#2728

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.27The system shall support outputting the Performance Log at user specified intervals.

    Specification(s): transient_perf_int

    Design: Console

    Issue(s): #1927#2728

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.28The system shall support writing time information in DTIME format in the console.

    Specification(s): console_dtime_format

    Design: Console

    Issue(s): #24813

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.29The system shall support writing time information in minutes in the console.

    Specification(s): console_minute_format

    Design: Console

    Issue(s): #24944

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.30The system shall support writing time information in hours in the console.

    Specification(s): console_hour_format

    Design: Console

    Issue(s): #24944

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.31The system shall support writing time information in days in the console.

    Specification(s): console_day_format

    Design: Console

    Issue(s): #24944

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.32The system shall support writing to a buffered console object from every MooseObject-derived object.

    Specification(s): _console

    Design: Console

    Issue(s): #3286

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.33The system shall support writing to a buffered console object from const methods in MooseObject-derived objects.

    Specification(s): _console_const

    Design: Console

    Issue(s): #3286

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.34The system shall support outputting a transformed input file to the screen.

    Specification(s): input_output

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.35The system shall support disabling the linear residual output.

    Specification(s): print_linear_residuals_disable

    Design: Console

    Issue(s): #4497

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.36The system shall output a Performance Log based on a single input file parameter.

    Specification(s): perf_graph

    Design: Console

    Issue(s): #4497

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.37The system shall override Performance Log output when conflicting values appear on the command line and input file.

    Specification(s): perf_graph_disable

    Design: Console

    Issue(s): #4497

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.38The system shall support adding an additional output time option without clobbering existing default options.

    Specification(s): additional_output_on

    Design: Console

    Issue(s): #4497

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.39The system shall output a "final" label at the end of the simulation before additional screen output occurs.

    Specification(s): console_final

    Design: Console

    Issue(s): #5756

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.40The system shall report an error when specifying an invalid table fit width option.

    Specification(s): console_fit_width_error

    Design: Console

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.41The system shall support the output of postprocessors and scalars to CSV files for steady state problems.

    Specification(s): steady

    Design: Output SystemCSV

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.42The system shall support the output of postprocessors and scalars to CSV files for transient propblems.

    Specification(s): transient

    Design: Output SystemCSV

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.43The system shall support the output of postprocessors and scalars to CSV files for transient problems without a time column.

    Specification(s): no_time

    Design: Output SystemCSV

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.44The system shall support the output of postprocessors and scalars to Exodus files for transient problems.

    Specification(s): transient_exodus

    Design: Output SystemCSV

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.46.262.46.42

  • 2.46.45The system shall support the output of CSV data:
    1. with checkpoint enabled and
    2. when restarted creates a new output file or
    3. optionally appends the existing file from the first part.

    Specification(s): restart/restart_part1, restart/restart_part2, restart/restart_part2_append

    Design: Output SystemCSV

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.46The system shall support CSV output aligned columns and a custom delimiter.

    Specification(s): align

    Design: Output SystemCSV

    Issue(s): #3229

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.47The system shall support CSV output to the console that is sorted by the variable name.

    Specification(s): sort

    Design: Output SystemCSV

    Issue(s): #8974

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.48The system shall support CSV output to files on linear iterations, generating unique filenames containing the time step, current nonlinear and linear iteration numbers.

    Specification(s): csv_transient_vpp_linear

    Design: Output SystemCSV

    Issue(s): #24705

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.49The system shall support CSV output to files on nonlinear iterations, generating unique filenames containing the time step and current nonlinear iteration number.

    Specification(s): csv_transient_vpp_nonlinear

    Design: Output SystemCSV

    Issue(s): #24705

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.50The system shall report an error if post-processors and scalar variables have different CSV output frequency.

    Specification(s): pp_scalar_execute_on_mismatch

    Design: Output SystemCSV

    Issue(s): #25211

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.51The system shall report an error if post-processors and reporters have different CSV output frequency.

    Specification(s): pp_reporter_execute_on_mismatch

    Design: Output SystemCSV

    Issue(s): #25211

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.52The CSV output object shall create a symlink to the final output with a '_FINAL' suffix for VectorPostprocessor data when there are execute flags in addition to FINAL.

    Specification(s): final

    Design: VectorPostprocessors SystemCSV

    Issue(s): #11087

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.53The CSV output object shall create a symlink to the final output with a '_FINAL' suffix for VectorPostprocessor data when the execute flag is set to FINAL.

    Specification(s): final_only

    Design: VectorPostprocessors SystemCSV

    Issue(s): #11087

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 2.46.52

  • 2.46.54The CSV output object 'create_final_symlink' parameter shall be able to disable the creation of the final symlink.

    Specification(s): no_link

    Design: VectorPostprocessors SystemCSV

    Issue(s): #11087

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 2.46.53

  • 2.46.55The CSV output object shall create a symlink to the most recent output with a '_LATEST' suffix for VectorPostprocessor data.

    Specification(s): latest

    Design: VectorPostprocessors SystemCSV

    Issue(s): #11087

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.56The CSV output object 'create_latest_symlink' parameter shall be able to disable the creation of the latest symlink.

    Specification(s): no_latest

    Design: VectorPostprocessors SystemCSV

    Issue(s): #11087

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 2.46.55

  • 2.46.57The system shall include the ability to display variable residual norms.

    Specification(s): show_var_residual_norms

    Design: VariableResidualNormsDebugOutput

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.58The system shall include debug syntax that includes the ability to enable variable residual norm output.

    Specification(s): show_var_residual_norms_debug

    Design: VariableResidualNormsDebugOutputDebug System

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.59The system shall include the ability to display material property information.

    Specification(s): show_material_props

    Design: MaterialPropertyDebugOutput

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.60The system shall include debug syntax that includes the ability to enable material property information output.

    Specification(s): show_material_props_block

    Design: MaterialPropertyDebugOutputDebug System

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.61The system shall include the ability to display residual information for variables.

    Specification(s): show_top_residuals

    Design: TopResidualDebugOutput

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.62The system shall include debug syntax that includes the ability to enable variable residual information.

    Specification(s): show_top_residuals_debug

    Design: TopResidualDebugOutputDebug System

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.63The system shall include the ability to display residual information for variables that is limited to non-linear iterations.

    Specification(s): show_top_residuals_nonlinear_only

    Design: TopResidualDebugOutput

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.64The system shall include the ability to display residual information for scalar variables.

    Specification(s): show_top_residuals_scalar

    Design: TopResidualDebugOutput

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.65The system shall include debug syntax that includes material property consumption information.

    Specification(s): show_material_properties_consumed

    Design: MaterialPropertyDebugOutputDebug System

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.66The system shall be able to output debug information for functors and objects requesting functors

    Specification(s): show_functors

    Design: Debug System

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.67The system shall include the ability to output the execution order of
    1. objects contributing to the residual and Jacobian, notably regular kernels,
    2. objects contributing to the residual and Jacobian, notably boundary conditions,
    3. elemental dampers,
    4. interface kernels,
    5. Dirac kernels,
    6. discontinuous Galerkin kernels,
    7. finite volume flux objects contributing to the residual and Jacobian, notably finite volume flux kernels and flux boundary conditions,
    8. finite volume elemental kernels,
    9. finite volume interface kernels,
    10. finite volume elemental kernels when combining both jacobian and residual computations,
    11. linear finite volume elemental kernels,
    12. linear finite volume flux kernels,
    13. nodal objects contributing to the residual, notably nodal kernels and boundary conditions,
    14. nodal dampers,
    15. user objects, including postprocessors, executed at the beginning of the simulation,
    16. user objects, including postprocessors, executed at the beginning and end of each time step,
    17. nodal user objects,
    18. domain user objects,
    19. general user objects,
    20. threaded general user objects,
    21. user objects, including postprocessors, executed on transfers between applications,
    22. each step of the adaptive refinement process, including side-based indicators,
    23. each step of the adaptive refinement process, including element-based indicators,
    24. initial conditions of variables,
    25. auxiliary kernels intermingled with initial conditions and user objects, and
    26. boundary restricted auxiliary kernels.

    Specification(s): show_execution_order/regular_kernels, show_execution_order/regular_bcs, show_execution_order/elem_dampers, show_execution_order/interface_kernels, show_execution_order/dirac, show_execution_order/dgkernels, show_execution_order/fv_flux_kernels_bcs, show_execution_order/fv_elem_kernels, show_execution_order/fv_interface_kernels, show_execution_order/fv_elem_kernels_res_and_jac_combined, show_execution_order/linear_fv_elem_kernels, show_execution_order/linear_fv_flux_kernels, show_execution_order/nodal_kernel_bcs, show_execution_order/nodal_dampers, show_execution_order/user_objects_initial, show_execution_order/user_objects_timestep_begin_end, show_execution_order/nodal_user_objects, show_execution_order/domain_user_objects, show_execution_order/general_user_objects, show_execution_order/threaded_general_user_objects, show_execution_order/user_objects_transfers, show_execution_order/adaptivity_side_indicator, show_execution_order/adaptivity_elem_indicator, show_execution_order/initial_conditions, show_execution_order/auxkernels, show_execution_order/boundary_auxkernels

    Design: Debug System

    Issue(s): #1927#19423

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.68The system shall include the ability to output block-restriction of objects
    1. when requested via debug parameter.
    2. when requested as output-block.

    Specification(s): show_block_restriction/debug_parameter, show_block_restriction/block

    Design: Debug System

    Issue(s): #28290

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.69The system shall be able to output the displaced mesh for a model with adaptive mesh refinement.

    Specification(s): use_displaced

    Design: Output SystemAdaptivity System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): non_displaced_fallback

    Design: Output System

    Issue(s): #11309

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): mesh_use_displaced_mesh_false

    Design: Mesh System

    Issue(s): #12580

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.46.70

  • 2.46.72The Output system shall be capable of applying displacements directly to the outputted mesh for steady problems.

    Specification(s): test

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.73The Output system shall be capable of applying displacements directly to the outputted mesh for transient problems with Kernels using the displaced configuration.

    Specification(s): displaced_eq_test

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.74The Output system shall be capable of applying displacements directly to the outputted mesh for transient problems.

    Specification(s): displacement_transient_test

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.75The system shall support the ability to output the degree-of-freedom information:
    1. to a json file,
    2. to the screen,
    3. with uniform refinement, and
    4. with transient adaptivity.

    Specification(s): group/simple, group/simple_screen, group/uniform_refine, group/transient

    Design: DOFMap

    Issue(s): #3847

    Collection(s): FUNCTIONAL

    Type(s): CheckFilesRunApp

  • 2.46.76The system shall report an error when two outputs with the same name are created.

    Specification(s): duplicate_objects

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.77The system shall report an error when two outputs produce a file with the same name.

    Specification(s): duplicate_output_files

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.79The system shall support ExodusII output.

    Specification(s): basic

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.80The system ExodusII output shall not use HDF5 unless requested.

    Specification(s): hdf5

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): RunCommand

    Prerequisite(s): 2.46.792.46.1442.46.1462.46.192

  • 2.46.81The system shall support including the executed input file within the ExodusII output.

    Specification(s): input

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.82The system shall support inclusion of initial condition data within the ExodusII output.

    Specification(s): enable_initial

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.83The system shall support writing non-linear, auxililary, scalar, and postprocessor variables to ExodusII format.

    Specification(s): output_all

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.84The system shall support the exclusion of non-linear, scalar, and postprocessor variables from ExodusII output.

    Specification(s): hide_output

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.85The system shall support outputting elemental and scalar variables as nodal variables within ExodusII output.

    Specification(s): nodal_output

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.86The system shall support outputting discontinuous finite element types with the ExodusII format.

    Specification(s): discontinuous

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.87The system shall support outputting side-discontinuous edge element data with the ExodusII format.

    Specification(s): side_discontinuous_edge2

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.88The system shall support outputting side-discontinuous quad element data with the ExodusII format.

    Specification(s): side_discontinuous

    Design: Exodus

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.89The system shall support outputting extra element id data defined on the input mesh with the ExodusII format.

    Specification(s): output_elem_id

    Design: Exodus

    Issue(s): #23386

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.90The system shall support restricting which extra element id data defined on the input mesh are outputted with the ExodusII format.

    Specification(s): output_elem_id_restrict

    Design: Exodus

    Issue(s): #23386

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.91The system shall report an error if
    1. the supplied names for including or excluding variables is invalid.
    2. a file base is supplied for a child app when there are multiple instances.

    Specification(s): errors/invalid_hide, errors/file_base_in_child_apps

    Design: Exodus

    Issue(s): #23743

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.92The system shall support Nemesis output.

    Specification(s): nemesis_out_test

    Design: Nemesis

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.93The system shall support GMV output.

    Specification(s): gmv_out_test

    Design: GMV

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.94The system shall be able to dump YAML data.

    Specification(s): yaml_dump_test

    Design: YAMLFormatter

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.95The system shall only give Executioner output once.

    Specification(s): no_double_executioner_output

    Design: YAMLFormatter

    Issue(s): #2855

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.96The system shall support Tecplot output.

    Specification(s): tecplot_out_test

    Design: Tecplot

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.97The system shall support Tecplot output given in Tecplot binary format if the Tecplot API is available.

    Specification(s): tecplot_bin_test

    Design: Tecplot

    Issue(s): #3403

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.98The system shall support Tecplot output given in ASCII format if the Tecplot API is not available.

    Specification(s): tecplot_bin_test_override

    Design: Tecplot

    Issue(s): #3403

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.99The system shall be able to generate gnuplot PostScript output.

    Specification(s): gnuplot_ps_out_test

    Design: Gnuplot

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.100The system shall be able to generate gnuplot PNG output.

    Specification(s): gnuplot_png_out_test

    Design: Gnuplot

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.101The system shall be able to generate gnuplot GIF output.

    Specification(s): gnuplot_gif_out_test

    Design: Gnuplot

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.102The system shall warn the user if a postprocessor utilizes the "outputs" parameter but postprocessor output is disabled for the console object.

    Specification(s): pps_screen_out_warn_test

    Design: Output System

    Issue(s): #1426

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.103The system shall print parameters when the --show-input flag is used on the command line.

    Specification(s): show_input_test

    Design: MooseApp

    Issue(s): #1404#1131

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.46.93

  • 2.46.104The system shall support solution history output.

    Specification(s): sln_out_test

    Design: SolutionHistory

    Issue(s): #920

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.105The system shall support XDR output.

    Specification(s): xdr_output

    Design: XDA/XDR

    Issue(s): #2243

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.106The system shall be able to dump input file syntax in JSON format.

    Specification(s): json_full

    Design: JsonInputFileFormatterMooseApp

    Issue(s): #7855#7661#2881#10839#12455

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.46.107The system shall be able to dump input file syntax in JSON format and exclude test object syntax.

    Specification(s): json_no_test_objects

    Design: JsonInputFileFormatterMooseApp

    Issue(s): #7855#7661#2881#10839#12455

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

    Prerequisite(s): 2.46.106

  • 2.46.108The system shall be able to dump a subset of JSON formatted syntax.

    Specification(s): json_search

    Design: JsonInputFileFormatterMooseApp

    Issue(s): #7855#7661#2881#10839#12455

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

    Prerequisite(s): 2.46.107

  • 2.46.109The system shall dump line information along with JSON formatted syntax.

    Specification(s): json_line_info

    Design: JsonInputFileFormatterMooseApp

    Issue(s): #7855#7661#2881#10839#12455

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

    Prerequisite(s): 2.46.108

  • 2.46.110The system shall not include RESIDUAL and JACOBIAN template arguments in the JSON syntax format.

    Specification(s): json_no_template

    Design: JsonInputFileFormatter

    Issue(s): #12960

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

    Prerequisite(s): 2.46.109

  • 2.46.111The system shall be able to dump input file (HIT) syntax.

    Specification(s): hit

    Design: JsonInputFileFormatterMooseApp

    Issue(s): #7855#7661#2881#10839#12455

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.46.112The system shall be able to dump a subset of input file (HIT) syntax.

    Specification(s): hit_search

    Design: JsonInputFileFormatterMooseApp

    Issue(s): #7855#7661#2881#10839#12455

    Collection(s): FUNCTIONAL

    Type(s): PythonUnitTest

  • 2.46.113The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check InputChoices

    Specification(s): definition_input_choices_test

    Design: SONDefinitionFormatter

    Issue(s): #16165

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.114The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check ChildAtLeastOne

    Specification(s): definition_childatleastone_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.115The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check ValEnums

    Specification(s): definition_valenum_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.116The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check active parameter

    Specification(s): definition_active_parameter_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.117The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check normal_sub

    Specification(s): definition_normal_sub_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.118The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check type_sub

    Specification(s): definition_type_sub_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.119The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check default type

    Specification(s): definition_default_type_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.120The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check MinValInc

    Specification(s): definition_minvalinc_inputdefault_test

    Design: SONDefinitionFormatter

    Issue(s): #9651

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.121The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check default types child parameter promotion

    Specification(s): definition_default_types_child_parameter_promotion_test

    Design: SONDefinitionFormatter

    Issue(s): #18639

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.122The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check default subblock_types child parameter promotion

    Specification(s): definition_default_subblock_types_child_parameter_promotion_test

    Design: SONDefinitionFormatter

    Issue(s): #18639

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.123The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check Mesh file parameter requirement removal

    Specification(s): definition_mesh_file_parameter_requirement_removal_test

    Design: SONDefinitionFormatter

    Issue(s): #18639

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.124The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check Boolean type ValEnums choices

    Specification(s): definition_boolean_type_valenum_choices_test

    Design: SONDefinitionFormatter

    Issue(s): #18639

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.125The system shall be able to convert a JsonSyntaxTree into Standard Object Notation (SON) for use by the NEAMS workbench. Check beginning and ending markers

    Specification(s): definition_scraping_markers

    Design: SONDefinitionFormatter

    Issue(s): #17324

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.126The system shall support outputting data to the general mesh viewer format.

    Specification(s): test

    Design: GMV

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.127The system shall support limiting vector postrocessor data to a specific CSV output object.

    Specification(s): test

    Design: OutputInterface

    Issue(s): #1927#7511

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.128The system shall support the ability to control the output of an aggregate calculation via a parameter of the object itself.

    Specification(s): test

    Design: Reporter System

    Issue(s): #16666

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.46.129The system shall support specifying an output interval for an output input file block.

    Specification(s): time_step

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.130The system shall support specifying an output interval for all outputs.

    Specification(s): common_time_step

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.46.129

  • 2.46.131The system shall support limiting output to the final timestep of a simulation.

    Specification(s): output_final

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.132The system shall support output at specific simulation times.

    Specification(s): sync_times

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.133The system shall support output at times defined by the function.

    Specification(s): output_limiting_function

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.134The system shall support multiple output objects that have different simulation synchronization times specified.

    Specification(s): multiple_sync_times

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.135The system shall support specifying an minimum time difference between successive outputs.

    Specification(s): minimum_time_interval

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): no_output

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.137The system shall support the ability to limit output objects only at the beginning and end of a simulation.

    Specification(s): no_intermediate

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.138The system shall not output the same information multiple times when an output object is defined to operate on the end of each timestep and the final timestep.

    Specification(s): no_final_repeat

    Design: Output System

    Issue(s): #1927#23212

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.139The system shall support output during linear and non-linear iterations during transient simulations using the ExodusII format.

    Specification(s): exodus

    Design: Output System

    Issue(s): #2617

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.140The system shall support output during linear and non-linear iterations during steady simulations using the ExodusII format:
    1. in a single file or
    2. in a sequence of files.

    Specification(s): iterative/exodus_steady, iterative/exodus_steady_sequence

    Design: Output System

    Issue(s): #2617

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.141The system shall support output during linear and non-linear iterations during transient simulations using the VTK format.

    Specification(s): vtk

    Design: Output System

    Issue(s): #2617

    Collection(s): FUNCTIONAL

    Type(s): XMLDiff

  • 2.46.142The system shall support output during linear and non-linear iterations during transient simulations using the CSV format.

    Specification(s): csv

    Design: Output System

    Issue(s): #2617

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.143The system shall support output during linear and non-linear iterations during transient simulations:
    1. with both the start and end times defined,
    2. with only the start time defined,
    3. with the start and end timestep provided,
    4. with the start timestep given, and
    5. with the end timestep provided.

    Specification(s): start_stop/exodus_inline, start_stop/exodus_start_time, start_stop/output_step_window, start_stop/output_start_step, start_stop/output_end_step

    Design: Output System

    Issue(s): #2617

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.144The system shall support JSON output for data.

    Specification(s): basic

    Design: JSON

    Issue(s): #11323

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.145The system shall include the ability to output simulation data in JSON format:
    1. that produces multiple files for parallel distributed data and
    2. for parallel replicated data in a single file.

    Specification(s): info/default, info/limit

    Design: JSON

    Issue(s): #11323

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.146The system shall support creating unique JSON output files per timestep.

    Specification(s): basic

    Design: JSON

    Issue(s): #18133

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

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

    Specification(s): getOutput

    Design: OutputWarehouse

    Issue(s): #2885

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): getOutputs

    Design: OutputWarehouse

    Issue(s): #2885

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): getOutputs_with_names

    Design: OutputWarehouse

    Issue(s): #2885

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

    Specification(s): getOutputNames

    Design: OutputWarehouse

    Issue(s): #2885

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.151The system shall support the naming of output files based on the input file block name.

    Specification(s): default_names

    Design: OutputWarehouse

    Issue(s): #2885

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.152The Nemesis Output object shall output separate files per process for visualization purposes.

    Specification(s): test

    Design: Output System

    Issue(s): #2122

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.153The Nemesis Output object shall support writing elemental variables.

    Specification(s): nemesis_elemental_replicated

    Design: Output System

    Issue(s): #2122

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.154The Nemesis Output object shall support writing elemental variables with the same numbering on DistributedMesh.

    Specification(s): nemesis_elemental_distributed

    Design: Output System

    Issue(s): #2122

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.155The Nemesis Ouput object shall support writing scalar variables.

    Specification(s): nemesis_scalar_replicated

    Design: Output System

    Issue(s): #2122

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.156The Nemesis Ouput object shall support writing scalar variables when using DistributedMesh.

    Specification(s): nemesis_scalar_distributed

    Design: Output System

    Issue(s): #2122

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.157The system shall support the ability to specify the output dimension when outputting in ExodusII format.

    Specification(s): test

    Design: Exodus

    Issue(s): #9205

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.158The system shall support the ability to limit output to certain sub-applications based on name.

    Specification(s): dt_from_parent

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.159The system shall include the ability to limit automatic output of adaptivity objects, including
    1. indicators and
    2. markers.

    Specification(s): group/indicators, group/markers

    Design: OutputInterface

    Issue(s): #3702

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.160The system shall allow the user to select different console output intervals.

    Specification(s): postprocessor

    Design: Console

    Issue(s): #4454

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.161The system shall display active output information with corresponding execute flags.

    Specification(s): show_outputs

    Design: Console

    Issue(s): #4454

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.162The system shall provide a system for outputting solution variables with a uniformly refined mesh:
    1. with a shift in output position,
    2. with a custom filename,
    3. with mesh adaptivity,
    4. with a generated mesh,
    5. with a file mesh, and
    6. with second order elements from a file mesh.

    Specification(s): group/oversample, group/oversample_filemesh, group/adapt, group/test_gen, group/test_file, group/test_first_order

    Design: Output System

    Issue(s): #1927#2646

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.163The system shall include an example demonstrating the use of oversampling.
    1. without and
    2. with mesh adaptivity.

    Specification(s): example/ex02, example/ex02_adapt

    Design: Output System

    Issue(s): #1927#2646

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.164The system shall include the ability to overwrite existing timesteps when writing ExodusII format.

    Specification(s): test

    Design: Exodus

    Issue(s): #5857

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.165The system shall output a performance log information for sub-applications
    1. that are transient,
    2. use differing time steps from the main, and
    3. execute an entire simulation.

    Specification(s): perf/with_multi, perf/with_sub_cycle, perf/with_full

    Design: PerfGraphOutput

    Issue(s): #11551#11453#12186

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.166The system shall have the ability to output a detailed performance log

    Specification(s): test

    Design: PerfGraphOutput

    Issue(s): #11551

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.167The system shall be able to produce png images:
    1. for 2D square images,
    2. arbitrary shapped domains,
    3. and complex shapes with periodic boudary conditions.

    Specification(s): image_tests/square_domain, image_tests/adv_diff_reaction, image_tests/wedge

    Design: PNGOutput (Outputs)

    Issue(s): #12846

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.168The system shall support offseting the spatial position of a domain during output.

    Specification(s): test

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.169The system shall support the ability to specify the output object for postprocessor data from within the input file block defining the postprocessor.

    Specification(s): limit

    Design: Output SystemOutputInterface

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

    Specification(s): invalid_outputs

    Design: Output SystemOutputInterface

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.171The system shall support limiting postprocessor output to the screen.

    Specification(s): console

    Design: Output SystemOutputInterface

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.172The system shall support limiting postprocessor output to from within the input file syntax of an output object.

    Specification(s): show_hide

    Design: Output SystemOutputInterface

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

    Specification(s): test_hidden_shown

    Design: Output SystemOutputInterface

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.174The system shall support limiting the output of comma seperated value data to the final timestep:
    1. for all scalar data and
    2. for postprocessor data only.

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

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.175The system shall support the ability to output single value aggregate calculations to JSON format.

    Specification(s): test

    Design: JSON

    Issue(s): #16543

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.46.176The system shall support printing a progress bar that indicates the fraction of total simulation time passed.

    Specification(s): full

    Design: Progress

    Issue(s): #22906

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.177The system shall support using a shortcut to set up a progress bar output.

    Specification(s): common

    Design: Progress

    Issue(s): #22906

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.178Correctly set up initial recover files for the part2 test.

    Specification(s): part1

    Design: RestartableDataIO

    Issue(s): #2661#27240

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.179A simulation executed using the "–recover" flag successfully runs a simulation using the specified recover file argument.

    Specification(s): part2

    Design: RestartableDataIO

    Issue(s): #2661

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.46.178

  • 2.46.180Correctly set up initial recover files for the part2_latest test.

    Specification(s): part1_latest

    Design: RestartableDataIO

    Issue(s): #10494#12403#27240

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

    Prerequisite(s): 2.46.179

  • 2.46.181A simulation executed using the "–recover" flag with a file argument using the placeholder "LATEST" successfully runs a simulation using most recent checkpoint/recover file from the specified directory.

    Specification(s): part2_latest

    Design: RestartableDataIO

    Issue(s): #10494#12403

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.46.180

  • 2.46.182Correctly set up initial recover files for the nemesis part2 test.

    Specification(s): nemesis_part1

    Design: RestartableDataIO

    Issue(s): #2661#13396#27240#28547

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.183A simulation executed using the "–recover" flag successfully runs a simulation using most recent checkpoint/recover file from the specified directory and correctly appends to the nemesis output.

    Specification(s): nemesis_part2

    Design: RestartableDataIO

    Issue(s): #2661#13396#27240#28547

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.46.182

  • 2.46.184The system shall automatically output values to a comma separated (CSV) file in
    1. root/replicated mode
    2. and distributed mode.

    Specification(s): csv/root, csv/distributed

    Design: Reporter System

    Issue(s): #11323

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.185The system shall support the ability to output the residual norms of individual nodal variables.

    Specification(s): test

    Design: Debug System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.186The system shall support the ability to output the residual norms of individual elemental variables.

    Specification(s): elem

    Design: Debug System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.187The system shall not output linear residuals when requested.

    Specification(s): no_linear_residuals

    Design: Output System

    Issue(s): #22056

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.188The system shall not output non-linear residuals when requested.

    Specification(s): no_nonlinear_residuals

    Design: Output System

    Issue(s): #22056

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.189The system shall support writing file to sub-directories.

    Specification(s): test

    Design: Output System

    Issue(s): #3249

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.190The system shall allow output to occur at times provided by a times object.

    Specification(s): sync_times_object

    Design: Output System

    Issue(s): #25368

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.46.191The system shall report an error if output is specified to use a times object with changing times.

    Specification(s): sync_times_object_changing_times

    Design: Output System

    Issue(s): #25368

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.192The system shall print the various components of the simulation information header to the screen

    Specification(s): basic

    Design: Output SystemConsole

    Issue(s): #2173

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.193The system shall print the mesh information to the screen when the mesh changes

    Specification(s): mesh

    Design: Output SystemConsole

    Issue(s): #2173

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.194The system shall print the auxiliary system information to the screen when the mesh changes

    Specification(s): aux

    Design: Output SystemConsole

    Issue(s): #2173

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.195The system shall print the nonlinear system information to the screen when the mesh changes

    Specification(s): nonlinear

    Design: Output SystemConsole

    Issue(s): #2173

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.46.196The system shall support writing ASCII Tecplot output.

    Specification(s): test

    Design: Tecplot

    Issue(s): #440#1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.197The system shall support appending Tecplot output files.

    Specification(s): test_append

    Design: Tecplot

    Issue(s): #440#1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.198The system shall optionally support writing binary Tecplot files.

    Specification(s): test_binary

    Design: Tecplot

    Issue(s): #440#1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.199The system shall guarantee that scalar variables are in the proper state for output when outputting:
    1. ExodusII format and
    2. CSV format.

    Specification(s): group/exodus, group/csv

    Design: OutputWarehouse

    Issue(s): #4474

    Collection(s): FUNCTIONAL

    Type(s): ExodiffCSVDiff

  • 2.46.200The system shall support outputting field and scalar data to the ExodusII format.

    Specification(s): test

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.201The system shall report an error if a variable is marked for output and output suppression.

    Specification(s): test_hidden_shown

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.202The system shall report an error if a variable is perscribed for output but does not exist.

    Specification(s): test_nonexistent

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.46.203The system shall test that output of an auxiliary field can be disabled within the input block defining the variable.

    Specification(s): block_hide

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.204The system shall support a system for including or suppressing output variables the operates when only a single variable for each type exists.

    Specification(s): show_single_vars

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.205The system shall support a system for including or suppressing output variables.

    Specification(s): show_hide

    Design: Output System

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.206The variables specified in an Output object's 'hide = ' list shall not appear in the output file.

    Specification(s): nemesis_hide

    Design: Output System

    Issue(s): #1895

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.46.207The system shall support the ability to output vector aggregate calculations to JSON format.

    Specification(s): test

    Design: JSON

    Issue(s): #16543

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.46.208The system shall optionally support output of files using the VTK format:
    1. in serial and
    2. in parallel.

    Specification(s): files/serial, files/parallel

    Design: VTK

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.209The system shall support the output of data using native libMesh formats:
    1. in XDA (ASCII) format and
    2. in XDR (binary) format.

    Specification(s): group/xda, group/xdr

    Design: XDA/XDR

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.210The system shall support simultaneous output of the ASCII and binary forms of the libMesh native format.

    Specification(s): both_xda_and_xdr

    Design: XDA/XDR

    Issue(s): #1927

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

  • 2.46.211The system shall support XML output for vector data that is
    1. replicated or
    2. distributed in parallel.

    Specification(s): parallel/replicated, parallel/distributed

    Design: XMLOutput

    Issue(s): #14634

    Collection(s): FUNCTIONAL

    Type(s): XMLDiff

  • 2.46.212The system shall support XML output for vector data during nonlinear solve.

    Specification(s): iterations

    Design: XMLOutput

    Issue(s): #14634

    Collection(s): FUNCTIONAL

    Type(s): CheckFiles

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

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

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

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

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

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

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

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

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

  • 2.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): 2.47.9

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.47.21

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Phi Zero
  • 2.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

  • 2.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): 2.50.1

  • framework: Physics
  • 2.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

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

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

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

  • framework: Positions
  • 2.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

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

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

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

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

  • framework: Preconditioners
  • 2.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

  • 2.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): 2.54.1

  • 2.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): 2.54.2

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

  • 2.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): 2.54.4

  • 2.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): 2.54.5

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

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

  • 2.54.9The system shall support nested field splits.

    Specification(s): nested

    Design: FSP

    Issue(s): #1851#22359

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Predictors
  • 2.55.1The system shall include a means for predicting future solution based on previous solutions.

    Specification(s): test

    Design: SimplePredictor

    Issue(s): #2282#6506#16796

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.55.2The system shall include a means for predicting future solution based on previous solutions and print the scale factor to the output stream.

    Specification(s): output

    Design: SimplePredictor

    Issue(s): #2282#6506#16796

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.55.3The system shall support the ability to skip performing solution predictions
    1. using solution times or
    2. previous solution times.

    Specification(s): skip/test_skip, skip/test_skip_old

    Design: SimplePredictor

    Issue(s): #2282#6506#16796

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.55.4The system shall support the ability to skip a prediction after a failed time step

    Specification(s): skip_after_failed_timestep

    Design: SimplePredictor

    Issue(s): #2282#6506#16796

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.55.5The system shall support the ability to output pre-SMO residual

    Specification(s): pre_smo

    Design: SimplePredictor

    Issue(s): #2282#6506#16796

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.55.6The system shall support the ability to use the Execitioner timestep tolerance to determine if a prediction should be peformed.

    Specification(s): timestep_tolerance

    Design: SimplePredictor

    Issue(s): #2282#6506#16796

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.55.3

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

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

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

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

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

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

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

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

  • 2.56.9Eigenvalue system should support standard eigenvalue problems

    Specification(s): test

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.56.10Eigenvalue system should support generalized eigenvalue problems

    Specification(s): gipm_test

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.56.11Eigenvalue system should support IntegratedBC

    Specification(s): gipm_ibc

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

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

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

  • 2.56.14Eigenvalue system requires SLEPc installed

    Specification(s): no_slepc

    Design: Eigenvalue

    Issue(s): #7398

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

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

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

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

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

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

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

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

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

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

  • 2.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): 2.56.23

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

  • 2.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): 2.56.25

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

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

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

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

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

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

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

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

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

  • 2.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): 2.56.35

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

  • 2.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): 2.56.31

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

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

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

  • 2.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): 2.56.39

  • 2.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): 2.56.42

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

  • 2.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): 2.56.44

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

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

  • 2.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): 2.56.47

  • 2.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): 2.56.48

  • 2.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): 2.56.49

  • 2.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): 2.56.49

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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): 2.56.64

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • framework: Quadrature
  • 2.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

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

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

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

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

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

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

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

  • framework: Relationship Managers
  • 2.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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  • 2.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

  • 2.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

  • 2.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

  • 2.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): RunAppRunCommand

  • 2.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

  • 2.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): RunAppRunCommand

    Prerequisite(s): 2.59.17

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • framework: Restart
  • 2.60.1The system shall be able to generate a checkpoint of stateful material properties that supports the advanced restart of the properties

    Specification(s): checkpoint

    Design: Materials System

    Issue(s): #25840

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.60.2The system shall report a reasonable error when using advanced stateful restart when
    1. a stateful property for a single material object is removed
    2. a stateful property for a single material object is added
    3. a previously checkpointed stateful property is declared in a new material
    4. the type of a restored stateful property has changed
    5. the requested state of a restored stateful property has changed

    Specification(s): errors/remove_prop, errors/add_prop, errors/object_rename, errors/different_type, errors/different_state

    Design: Materials System

    Issue(s): #25840

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.60.12.60.13

  • 2.60.3The system shall support reading and writing solutions on meshes containing duplicate or overlapping mesh nodes.

    Specification(s): test

    Design: DataIORestartable

    Issue(s): #2306

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.4The system shall support the ability to
    1. perform residual calculations that accumulate state and
    2. restart the calculation using the accumulated state.

    Specification(s): kernel/test, kernel/test2

    Design: DataIORestartable

    Issue(s): #2306

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.5The system shall support the ability to
    1. to name problem objects in a simulation and
    2. restart the calculation using the defined name.

    Specification(s): custom/custom_name, custom/custom_name2

    Design: DataIORestartable

    Issue(s): #2306

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.6The system shall report an error when
    1. a simulation is started with multiple processors but
    2. restarted with a different number processors.

    Specification(s): parallel_error/error1, parallel_error/error2

    Design: DataIORestartable

    Issue(s): #2306

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): ExodiffRunException

    Prerequisite(s): 2.60.4

  • 2.60.7The system shall report an error when
    1. a simulation is started with multiple threads but
    2. restarted with a different number threads.

    Specification(s): thread_error/with_threads, thread_error/threads_error

    Design: DataIORestartable

    Issue(s): #2306

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): ExodiffRunException

    Prerequisite(s): 2.60.6

  • 2.60.8The system shall support running a transient test for the purposed of changing a restart time step size.

    Specification(s): test_part1

    Design: DataIORestartable

    Issue(s): #2304#27240

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.60.9The system shall support changing the time step size during a recover operation.

    Specification(s): test_restart

    Design: DataIORestartable

    Issue(s): #2304#27240

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.8

  • 2.60.10The system shall produce an error when an attempt is made to serialize a type without a serialization (dataStore) routine when that data is declared as restartable.

    Specification(s): pointer_store_error

    Design: DataIORestartable

    Issue(s): #1169

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.60.11The system shall store a custom type that contains a data serialization routine that is declared as restartable.

    Specification(s): pointer_load_error

    Design: DataIORestartable

    Issue(s): #1169

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.60.12The system shall produce an error when an attempt is made to deserialize a type without a deserialization (dataLoad) routine when that data is declared as restartable during a restart or recover operation.

    Specification(s): pointer_load_error2

    Design: DataIORestartable

    Issue(s): #1169

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.60.11

  • 2.60.13The system shall support the checkpointed output of postprocessors.

    Specification(s): checkpoint

    Design: RestartableReceiver

    Issue(s): #25414#27240

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.60.14The system shall support loading a postprocessor into another postprocessor during restart.

    Specification(s): restart

    Design: RestartableReceiver

    Issue(s): #25414#27240

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.60.12.60.13

  • 2.60.15The systen shall support running and saving off a transient solution with stateful material properties for a restart test.

    Specification(s): transient_with_stateful

    Design: RestartableDataIO

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.16The systen shall support restart with a solution containing only a subset of the variables in the restart simulation.

    Specification(s): add_variable_restart

    Design: RestartableDataIO

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.15

  • 2.60.17The system shall support outputting a mesh from a simulation
    1. with uniform refinement to ExodusII format,
    2. start a new simulation that adds additional refinement,
    3. which can be used in an third simulation.

    Specification(s): uniform_refine/test_1, uniform_refine/test_2, uniform_refine/test_3

    Design: RestartableDataIO

    Issue(s): #563

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.18The system shall support outputting a mesh to checkpoint format for restart testing.

    Specification(s): steady_1

    Design: RestartableDataIO

    Issue(s): #563

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.19The system shall support starting a transient simulation from a steady simulation result.

    Specification(s): trans_from_steady

    Design: RestartableDataIO

    Issue(s): #563

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.18

  • 2.60.20The system shall support renaming a variable read from a solution file upon restart.

    Specification(s): restart_with_variable_rename

    Design: RestartableDataIO

    Issue(s): #4965

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.18

  • 2.60.21The system shall support writing out several timesteps to a solution file to test reading from a specific point.

    Specification(s): restart_use_end_part1

    Design: RestartableDataIO

    Issue(s): #5748

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.60.22The system shall support restarting from the last timestep using the keyword "LATEST".

    Specification(s): restart_use_end_part2

    Design: RestartableDataIO

    Issue(s): #5748

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.21

  • 2.60.23The system shall issue a useful error message stating the valid options when a user requests an invalid time step number or keyword.

    Specification(s): restart_use_end_error_check

    Design: RestartableDataIO

    Issue(s): #5748

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

    Prerequisite(s): 2.60.22

  • 2.60.24The system shall issue a useful error message stating that initial conditions should not be used when restarting.

    Specification(s): restart_error_with_ics

    Design: RestartableDataIO

    Issue(s): #21423

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.60.25The system shall support running and saving off a transient solution for using in a steady state restart.

    Specification(s): transient_solve

    Design: RestartableDataIO

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.26The system shall support restarting a steady state solve from a transient simulation solution.

    Specification(s): steady_from_transient_restart

    Design: RestartableDataIO

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.25

  • 2.60.27The system shall support solving a transient problem as a reference solution for a two part multiapp solve.

    Specification(s): complete_solve_no_subapp

    Design: DataIORestartable

    Issue(s): #6297#27240

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.28The system shall support writing out checkpoint directly from a subapp, a subtree of the multiapp tree of the parent solve.

    Specification(s): two_step_solve_parent

    Design: DataIORestartable

    Issue(s): #6297#27240

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.29The system shall support restarting a subapp, a subtree of the multiapp tree of a parent solve without restarting the parent application.

    Specification(s): two_step_solve_parent_restart

    Design: DataIORestartable

    Issue(s): #6297#27240

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.28

  • 2.60.30The system shall support storing the solution of an eigenvalue solve such that it can be restarted later into a non-eigenvalue solve.

    Specification(s): eigen_store_solution

    Design: Restartable

    Issue(s): #21011

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.31The system shall support loading the restarted solution from an eigenvalue solve into a transient solve.

    Specification(s): transient_from_eigen_solution

    Design: Restartable

    Issue(s): #21011

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.30

  • 2.60.32The system shall support executing a
    1. a steady-state problem
    2. and restarting a transient simulation from the previous solution.

    Specification(s): tests/steady, tests/restart_trans_from_steady

    Design: RestartableDataIO

    Issue(s): #563#13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.33The system shall support generating checkpoint files for restart testing with sub apps.

    Specification(s): steady_with_sub

    Design: RestartableDataIO

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.34The system shall support restarting a transient simulation from a steady solution file with sub apps.

    Specification(s): restart_trans_from_steady_with_sub

    Design: RestartableDataIO

    Issue(s): #13438

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.33

  • 2.60.35The system shall support generating checkpoint files for restart testing with multiple sub apps.

    Specification(s): steady_with_2subs

    Design: RestartableDataIO

    Issue(s): #15287

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.36The system shall support restarting a transient simulation from a steady solution file with multiple sub apps.

    Specification(s): restart_trans_from_steady_with_2subs

    Design: RestartableDataIO

    Issue(s): #15287

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.35

  • 2.60.37The system shall support generating checkpoint files for transient to transient restart testing with multiple sub apps.

    Specification(s): pseudo_trans_with_2subs

    Design: RestartableDataIO

    Issue(s): #15287

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.38The system shall support restarting a transient simulation from a pseudo-transient solution file with multiple sub apps.

    Specification(s): restart_trans_from_pseudo_trans_with_2subs

    Design: RestartableDataIO

    Issue(s): #15287

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.60.37

  • 2.60.39The system shall be capable, on a single process, of
    1. writing data to a restart file
    2. and restarting the simulation from the restart file.

    Specification(s): serial/first, serial/second

    Design: Restartable

    Issue(s): #1169#2218

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.60.40The system shall be capable, in parallel, of
    1. writing data to a restart file
    2. and restarting the simulation from the restart file.

    Specification(s): parallel/first, parallel/second

    Design: Restartable

    Issue(s): #1169#2218

    Collection(s): FUNCTIONAL

    Type(s): RunApp

    Prerequisite(s): 2.60.39

  • 2.60.41The system shall be able to restart a scalar variable in the presence of other variables with the standard sequence of:
    1. run initial input
    2. run restart input

    Specification(s): restarting/part1, restarting/part2

    Design: MooseVariableBase

    Issue(s): #17471

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.60.42The system shall support outputting a mesh to checkpoint format for restart testing with "start_time".

    Specification(s): steady

    Design: RestartableDataIO

    Issue(s): #563

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.60.43The system shall use the the final time as the "start_time" from the restart file.

    Specification(s): default_start_timestart

    Design: RestartableDataIO

    Issue(s): #13182

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.60.42

  • 2.60.44The system shall support resetting "start_time" when restarting from a checkpoint mesh format.

    Specification(s): start_time_override_zero

    Design: RestartableDataIO

    Issue(s): #13182

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.60.42

  • 2.60.45The system shall support overriding "start_time" when restarting from a checkpoint mesh format to an arbitrary time.

    Specification(s): start_time_override_non_zero

    Design: RestartableDataIO

    Issue(s): #13182

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

    Prerequisite(s): 2.60.42

  • framework: Restrictable
  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • framework: Scalar Kernels
  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • framework: Scaling
  • 2.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

  • 2.64.2The system shall ignore particular variable automatic scaling factors

    Specification(s): ignore

    Design: NonlinearSystem

    Issue(s): #19573

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • 2.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): PetscJacobianTesterExodiff

  • 2.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

  • 2.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

  • 2.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

  • 2.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

  • framework: Utils
  • 2.73.1The system shall support a piecewise bilinear interpolation object to be constructed from x, y data read from an external file.

    Specification(s): test

    Design: BilinearInterpolation

    Issue(s): #1405

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.73.2The system shall support a piecewise bilinear interpolation object to be constructed from x, y data.

    Specification(s): test_internal

    Design: BilinearInterpolation

    Issue(s): #5991

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

    Prerequisite(s): 2.73.12.73.62.73.7

  • 2.73.3The system shall report an error when a file and data are supplied simultaneously in the PiecewiseBilinear object.

    Specification(s): data_file_and_xyz_error

    Design: BilinearInterpolation

    Issue(s): #5991

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.4The system shall report an error when there is a mismatch in vector lengths in the PiecewiseBilinear object.

    Specification(s): size_xyz_error

    Design: BilinearInterpolation

    Issue(s): #5991

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.5The system shall report an error when there are insufficient parameters supplied for the PiecewiseBilinear object.

    Specification(s): xyz_error

    Design: BilinearInterpolation

    Issue(s): #5991

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.6The system shall provide a method for transferring common parameters from one object to another.

    Specification(s): test

    Design: InputParameters

    Issue(s): #3352

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.73.7The system shall prevent the user from copying InputParameters objects inside of MooseObject-derived objects.

    Specification(s): test

    Design: InputParameters

    Issue(s): #5439

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.8The system shall throw an error while creating a LibtorchArtificialNeuralNet when encountering
    1. an unsupported activation function;
    2. the wrong number of activation functions;
    3. a non-supported optimizer.

    Specification(s): libtorch-nn-errors/wrong-activation, libtorch-nn-errors/wrong-activation-number, libtorch-nn-errors/wrong-optimizer

    Design: LibtorchArtificialNeuralNet

    Issue(s): #19571

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.9The system shall be able to create and evaluate a neural network with an activation function type of
    1. rectified linear unit (ReLU);
    2. sigmoid;
    3. Gaussian Error Linear Unit (GELU);
    4. Exponential Linear Unit (ELU);
    5. linear;

    Specification(s): libtorch-nn-activation/relu, libtorch-nn-activation/sigmoid, libtorch-nn-activation/gelu, libtorch-nn-activation/elu, libtorch-nn-activation/linear

    Design: LibtorchArtificialNeuralNet

    Issue(s): #19571

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.73.10The system shall be able to train a neural network with an optimizer type of
    1. Adaptive Gradient (AdaGrad);
    2. Adam;
    3. Root Mean Squared Propagation (RMSProp);
    4. Stochastic Gradient Descent (CGD);

    Specification(s): libtorch-nn-optimizer/adagrad, libtorch-nn-optimizer/adam, libtorch-nn-optimizer/rmsprop, libtorch-nn-optimizer/sgd

    Design: LibtorchArtificialNeuralNet

    Issue(s): #19571

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.73.11The system shall be able to evaluate a neural net with the same values as the python code which created the neural net.

    Specification(s): libtorch-torch-script

    Design: LibtorchTorchScriptNeuralNet

    Issue(s): #19571

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.73.12The system shall have a function that evaluates the polynomial and derivative of polyonimal of varying degree and arbitrary coefficients

    Specification(s): poly

    Design: MathUtils Namespace

    Issue(s): #13184

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.73.13The system shall have a clamp function that returns a value limited to upper and lower bounds

    Specification(s): clamp

    Design: MathUtils Namespace

    Issue(s): #13231

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.73.14The system shall have a smootherstep function that returns a smooth transition value between an upper and lower bound

    Specification(s): smootherstep

    Design: MathUtils Namespace

    Issue(s): #13231

    Collection(s): FUNCTIONAL

    Type(s): CSVDiff

  • 2.73.15The system shall support the use of the Dennis-Schnabel method for computing the finite difference parameter for matrix free finite difference solver.

    Specification(s): mffd_test

    Design: Executioner System

    Issue(s): #584

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.16The system shall automatically report input errors when a required parameter is not specified.

    Specification(s): error

    Design: InputParameters

    Issue(s): #16410

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.17The PerfGraph shall report a reasonable error when
    1. registering a section without a name
    2. registering a section without a live message
    3. requesting the ID of a section that does not exist
    4. requesting the section info for a section that does not exist

    Specification(s): errors/register_no_section, errors/register_no_live_message, errors/section_id_missing, errors/section_info_missing

    Design: PerfGraph

    Issue(s): #15444

    Collection(s): FUNCTIONALFAILURE_ANALYSIS

    Type(s): RunException

  • 2.73.18The system shall allow for timing sections of code and having automated print-outs when they take too long.

    Specification(s): time_test

    Design: PerfGraph

    Issue(s): #15444

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.19The system shall allow for nested code timing sections and having automated print-outs of the code section names when they are taking a long time.

    Specification(s): nested_sections

    Design: PerfGraphLivePrint

    Issue(s): #15444

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.20The system shall be able to display the automatic print-out of a timed section even when an external print happened before the threshold for the automatic print-out was met.

    Specification(s): section_interrupted_by_regular_print

    Design: PerfGraphLivePrint

    Issue(s): #23746

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.21The system shall allow for automatic print-outs of timing sections within multiapps.

    Specification(s): multiapps

    Design: PerfGraphLivePrint

    Issue(s): #19114

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.22The system shall allow for automatic print-outs of nested timing sections within multiapps.

    Specification(s): multiapps_and_nested

    Design: PerfGraphLivePrint

    Issue(s): #19114

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.23The system shall allow for automatic print-outs of timing sections within nested multiapps.

    Specification(s): nested_multiapps

    Design: PerfGraphLivePrint

    Issue(s): #19114

    Collection(s): FUNCTIONAL

    Type(s): RunApp

  • 2.73.24The system shall include a utility for swapping values within a vector of data.

    Specification(s): swap

    Design: Samplers System

    Issue(s): #14830

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.73.25The system shall include a utility for shuffling values within a vector of data.

    Specification(s): serial

    Design: Samplers System

    Issue(s): #14830

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.73.26The system shall include a utility for resampling values within a vector of data.

    Specification(s): resample

    Design: Samplers System

    Issue(s): #14830

    Collection(s): FUNCTIONAL

    Type(s): JSONDiff

  • 2.73.27The system shall include a utility for computing spline functions.

    Specification(s): regular_spline

    Design: SplineFunction

    Issue(s): #10918

    Collection(s): FUNCTIONAL

    Type(s): Exodiff

  • 2.73.28The system shall include a utility for computing bicubic spline functions
    1. using the x-component, and
    2. using the y-component.
    3. using the z-component,

    Specification(s): bicubic/spline_x, bicubic/spline_y, bicubic/spline_z

    Design: SplineFunction

    Issue(s): #10918

    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]