Contact System Requirements Specification

This template follows INL template TEM-135, "IT System Requirements Specification".

note

This document serves as an addendum to Framework System Requirements Specification and captures information for SRS specific to the Contact module.

Framework System Requirements Specification
sqa/tensor_mechanics_srs.md

Introduction

System Purpose

The purpose of the MOOSE Contact module is to enforce mechanical contact constraints between opposing interacting surfaces of models of deforming bodies.

System Scope

The MOOSE Contact module provides capabilities for enforcing a variety of types of mechanical contact constraints between surfaces on deforming bodies. These constraints typically enforce the condition that the two surfaces do not penetrate each other. They can also optionally enforce that the two surfaces do not separate or slide relative to each other, or allow for slip only when the frictional capacity has been reached. Multiple methods are provided for enforcing these constraints, including node-on-face and mortar-based formulations. In addition to providing the capabilities for enforcing contact constraints, the Contact module also provides various supporting tools to facilitate setting up these models and outputting the results related to contact.

System Overview

System Context

The Contact module is command-line driven. Like MOOSE, this is typical for a high-performance software that is designed to run across several nodes of a cluster system. As such, all usage of the software is through any standard terminal program generally available on all supported operating systems. Similarly, for the purpose of interacting through the software, there is only a single user, "the user", which interacts with the software through the command-line. The Contact module does not maintain any back-end database or interact with any system daemons. It is an executable, which may be launched from the command line and writes out various result files as it runs.

Figure 1: Usage of the Contact module and other MOOSE-based applications.

System Functions

Since the Contact module is a command-line driven application, all functionality provided in the software is operated through the use of standard UNIX command line flags and the extendable MOOSE input file. The Contact module is completely extendable so individual design pages should be consulted for specific behaviors of each user-defined object.

User Characteristics

Like MOOSE, there are three kinds of users working on the Contact module:

Contact module Developers: These are the core developers of the Contact module. They are responsible for following and enforcing the software development standards of the module, as well as designing, implementing, and maintaining the software.
Developers: A scientist or engineer that uses the Contact module alongside MOOSE to build their own application. This user will typically have a background in modeling or simulation techniques (and perhaps numerical analysis) but may only have a limited skillset when it comes to code development using the C++ language. This is the primary focus group of the module. In many cases, these developers will be encouraged to contribute module-appropriate code back to the Contact module, or to MOOSE itself.
Analysts: These are users that will run the code and perform analysis on the simulations they perform. These users may interact with developers of the system requesting new features and reporting bugs found and will typically make heavy use of the input file format.

Assumptions and Dependencies

The Contact module is developed using MOOSE and can itself be based on various MOOSE modules, as such the SRS for the Contact module is dependent upon the files listed at the beginning of this document. Any further assumptions or dependencies are outlined in the remainder of this section.

The Contact module has no constraints on hardware and software beyond those of the MOOSE framework and the Solid Mechanics module. The Contact module provides access to a number of code objects that perform computations. These objects each make their own physics-based assumptions, such as the units of the inputs and outputs. Those assumptions are described in the documentation for those individual objects.

References

ISO/IEC/IEEE 24765:2010(E). Systems and software engineering—Vocabulary. first edition, December 15 2010.

@manual{ISO-systems-software,
    author = "24765:2010(E), ISO/IEC/IEEE",
    title = "Systems and software engineering---Vocabulary",
    edition = "First",
    year = "2010",
    month = "December 15"
}

ASME NQA-1. ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications. first edition, August 31 2009.

@manual{ASME-NQA-1-2008,
    author = "NQA-1, ASME",
    title = "ASME NQA-1-2008 with the NQA-1a-2009 addenda: Quality Assurance Requirements for Nuclear Facility Applications",
    orginization = "American Socieity of Mechanical Engineers",
    year = "2009",
    month = "August 31",
    edition = "First"
}

Definitions and Acronyms

This section defines, or provides the definition of, all terms and acronyms required to properly understand this specification.

Definitions

Verification: (1) The process of: evaluating a system or component to determine whether the products of a given development phase satisfy the conditions imposed at the start of that phase. (2) Formal proof of program correctness (e.g., requirements, design, implementation reviews, system tests) (24765:2010(E), 2010).

Acronyms

Acronym	Description
INL	Idaho National Laboratory
LGPL	GNU Lesser General Public License
MOOSE	Multiphysics Object Oriented Simulation Environment
NQA-1	Nuclear Quality Assurance Level 1
POSIX	Portable Operating System Interface
SRS	Software Requirement Specification

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.

Hardware	Information
CPU Architecture	x86_64, ARM (Apple Silicon)
Memory	8 GB (16 GBs for debug compilation)
Disk Space	30GB

Libraries	Version / Information
GCC	8.5.0 - 12.2.1
LLVM/Clang	10.0.1 - 16.0.6
Intel (ICC/ICX)	Not supported at this time
Python	3.7 - 3.11
Python Packages	packaging pyaml jinja2

Functional Requirements

contact: 3D-Mortar-Contact
3.1.1The system shall solve a 3D frictionless bouncing block problem with mortar constraint
3.1.2The system shall solve a 3D frictionless bouncing block problem with mortar constraint using Petrov-Galerkin approach.
3.1.3The system shall solve a 3D frictionless bouncing block problem with mortar constraints where the primary suface is composed of a single element and the secondary side is composed of first order faces with a required derivative container size of less than 50.
3.1.4The system shall solve a 3D frictionless bouncing block problem with mortar constraint using the contact action.
3.1.5The system shall solve a 3D frictionless bouncing block problem with mortar constraint using Petrov-Galerkin approach in contact action.
3.1.6The system shall solve a 3D frictionless bouncing block problem with mortar constraint using the contact action and selecting the temporary flag correct edge dropping.
3.1.7The system shall solve a 3D frictionless bouncing block problem with mortar constraint and output the mortar segment mesh for debugging purposes.
3.1.8The system shall solve a 3D frictional bouncing block problem with mortar constraint using nodal-attached geometry.
3.1.9The system shall solve a 3D frictional bouncing block problem with mortar constraint using the Petrov-Galerkin approach.
3.1.10The system shall solve a 3D frictional block problem with mortar constraint using a simple frictional model dependent on relative velocity and contact pressure.
3.1.11The system shall solve a 3D frictional bouncing block problem with mortar constraints using nodal-attached geometry and a frictional pressure vector generated by an auxiliary kernel through a user-friendly action. Results are diffed against non-action output.
3.1.12The system shall solve a 3D frictional bouncing block problem with mortar constraint using the Petrov-Galerkin approach in contact action.
3.1.13The system shall generate consistent mortar nodal geometry (normal and tangent vectors) on a spherical surface.
3.1.14The system shall solve a 3D frictional problem with mortar constraint using a penalty approach
3.1.15The system shall solve a 3D frictionless problem with mortar constraint using a penalty approach
3.1.16The system shall be able to solve a 3D frictional problem with mortar constraint using a augmented Lagrange approach and converging to prescribed tolerance.

contact: Adaptivity
3.2.1Contact shall be enforced on new nodes created due to mesh refinement

contact: Bouncing-Block-Contact
3.3.1The system shall use grid sequencing in order to improve the performance of the nonlinear solve in a frictional contact problem
3.3.2The node-face discretization with a RANFS formulation for frictionless mechanical contact shall be susceptible to ping-ponging, specifically in this case to a secondary node oscillating back and forth between different primary faces
3.3.3The node-face discretization with a kinematic formulation for frictionless mechanical contact shall be susceptible to ping-ponging, specifically in this case to a secondary node oscillating back and forth between different primary faces
3.3.4A variational consistent mortar formulation with dual bases for frictionless mechanical contact shall not show any ping-ponging behavior
3.3.5
The system shall be able to solve frictionless mechanical contact using a reduced active nonlinear function set scheme (RANFS) in conjunction with a node-face geometric discretization. The RANFS scheme shall be
1. nonsingular both with bounds projection and
2. without bounds projection and be
3. solvable with amg both with bounds projection
4. and without bounds projection.
5. The system's RANFS scheme shall have a perfect Jacobian for mechanical contact that only has one non-zero normal component
6. The system shall be able to detect when a secondary node is ping-ponging back and forth between different primary faces and consequently tie the locations of the secondary and corresponding primary node using Lagrange Multipliers corresponding to equality constraints, e.g. more RANFS
7. The system shall be able to solve a smaller model of the full ping-ponging problem
3.3.6
Using a RANFS scheme with Lagrange multipliers corresponding to equality constraints the system shall be able to
1. tie nodes together and
2. have a perfect Jacobian
3.3.7
The system shall support a variationally consistent weighted gap implementation of the zero-penetration contact constraint
1. using equal, first order bases for displacements and the lagrange multiplier
2. using a second order basis for displacements and a first order basis for the lagrange multiplier
3. using equal, first order bases for displacements and the lagrange multiplier with correct edge dropping
4. using a first order basis for displacements and penalty multiplication times the negative gap distance to form the contact force.
5. using a first order basis for displacements and penalty multiplication times the negative gap distance to form the contact force via the contact action.
3.3.8The system shall be able to communicate semilocal weighted gaps back to any process that contributed to computing said weighted gaps.
3.3.9The system shall be able to communicate semilocal weighted gaps and velocities back to any process that contributed to computing said weighted quantities. We check against the serial numerical results.
3.3.10
The system shall support a variationally consistent mortar frictional constraints with dual bases
1. using verbose input file
2. using the contact action
3.3.11The system shall be able to solve a frictional, variationally consistent, mortar mechanical contact problem in which the secondary side of the contact interface is split between processes when run in parallel.
3.3.12The system shall be able to solve a frictional, variationally consistent, mortar mechanical contact problem in which the secondary side of the contact interface is split between processes when run in parallel while using the contact action to build the set of constraints, user objects, and application of generalized forces.
3.3.13The system shall not attempt to zero Lagrange multipliers that do not exist on inactive nodes.

contact: Catch Release
3.4.1The contact system shall enforce three-dimensional block to block interaction using a penalty approach.

contact: Check Error
3.5.1

contact: Cohesive Zone Model
3.6.1The system shall be able to apply cohesive zone modeling with bilinear mixed mode traction to a simple model.
3.6.2The system shall be able to apply cohesive zone modeling with bilinear mixed mode traction and mechanical contact to a simple model.
3.6.3The system shall be able to apply reproduce the setup of the interface cohesive zone modeling with a mortar formulation.
3.6.4The system shall be able to apply reproduce the setup of the interface cohesive zone modeling with a mortar formulation and output analysis information to the Exodus mesh.
3.6.5The system shall be able to apply a cohesive zone model based on interface objects.
3.6.6The system shall be able to apply a mortar cohesive zone model and yield results similar to those of interface objects.

contact: Dual Mortar
3.7.1The system shall converge and match the solution produced by standard mortar contact.
3.7.2The system shall converge and match the solution produced by dual mortar contact.
3.7.3The system shall converge and match the solution with the standard methods using variable condenstation with AMG.
3.7.4The system shall converge and match the solution with the standard methods using variable condenstation with AMG, by always condensing out the LMs.
3.7.5The system shall converge and match the solution with the standard methods using variable condenstation with AMG, by using LU to solve for the LM variable (not assuming diagonal coupling with the primal variable).

contact: Explicit Dynamics
3.8.1The system shall be able to solve a simple few-element normal contact problem using explicit dynamics.
3.8.2The system shall be able to solve a simple few-element normal contact problem using explicit dynamics solving uncoupled, local equations of momentum balance.
3.8.3The system shall be able to solve a simple few-element normal contact problem using explicit dynamics solving uncoupled, local equations of momentum balance and overwrite boundary variables after applying the time stepper scheme.
3.8.4The system shall be able to solve a simple few-element normal contact problem using explicit dynamics solving uncoupled, local equations of momentum balance in debug mode.
3.8.5The system shall be able to solve a simple few-element normal contact problem using explicit dynamics solving uncoupled, local equations of momentum balance and overwrite boundary variables after applying the time stepper scheme in debug mode.
3.8.6The system shall be able to solve a simple few-element normal contact problem using explicit dynamics solving uncoupled, local equations of momentum balance during an impact-settling under gravity acceleration.
3.8.7The system shall be able to solve a simple few-element normal contact problem with contact at an elevated velocity using explicit dynamics solving uncoupled, local equations of momentum balance during an impact-settling under increased gravity acceleration.

contact: Fieldsplit
3.9.1The system shall allow for split preconditioning based on contact surfaces.
3.9.2The system shall allow split preconditioning of frictionless mortar contact.
3.9.3The system shall allow split preconditioning of frictional mortar contact.

contact: Frictional
3.10.1The contact system shall enforce 2D single-point contact with significant accumulated slip.
3.10.2The contact system shall enforce 2D single-point contact with significant accumulated slip. With predictor solver options.
3.10.3The contact system shall enforce 2D single-point contact with significant accumulated slip when formulation selected is tangential_penalty contact.
3.10.4The contact system shall enforce 2D line contact between quads with significant accumulated slip.
3.10.5The contact system shall enforce 2D line contact between quads with significant accumulated slip, when formulation selected is tangential_penalty.

contact: Glued
3.11.1The contact system shall enforce a glued contact constraint that ties together two blocks that are separated by an initial gap when the come in contact with each other so that the blocks move together.

contact: Hertz Spherical
3.12.1The Contact system shall simulate Hertz contact between sphere and plane as a 2D axisymmetric problem with Quad4 elements.
3.12.2The Contact system shall simulate Hertz contact between sphere and plane as a 2D axisymmetric problem with Quad8 elements.
3.12.3The Contact system shall simulate Hertz contact between sphere and plane as a 3D problem with Hex8 elements.
3.12.4The Contact system shall simulate Hertz contact between sphere and plane as a 3D problem with Hex27 elements.

contact: Incremental Slip
3.13.1

contact: Kinematic-And-Scaling
3.14.1The system shall be able to apply automatic scaling in conjunection with kinematic contact constraint enforcement and show no penetration and exhibit good nonlinear convergence
3.14.2The system shall yield the same physical results when solving a kinematic contact problem with and without automatic scaling

contact: Mechanical Constraint
3.15.1The contact system shall enforce a frictionless mechanical contact condition between two blocks with a combination of normal and tangential motion using a kinematic enforcement with the Constraint system.
3.15.2The contact system shall enforce a frictionless mechanical contact condition between two blocks with gap offsets on both primary and secondary blocks using a kinematic enforcement with the DiracKernel system.
3.15.3The contact system shall enforce a frictionless mechanical contact condition between two blocks with a combination of normal and tangential motion using a penalty enforcement with the Constraint system.
3.15.4The contact system shall enforce a glued mechanical contact condition between two blocks with a combination of normal and tangential motion using a kinematic enforcement with the Constraint system.
3.15.5The contact system shall enforce a glued mechanical contact condition between two blocks with a combination of normal and tangential motion using a penalty enforcement with the Constraint system.

contact: Mortar Augmented Lagrange
3.16.1
The aux kernel shall throw an error if the supplied user object dies not support computing the property
1. normal_pressure
2. accumulated_slip_one
3. tangential_pressure_one
4. tangential_velocity_one
5. accumulated_slip_two
6. tangential_pressure_two
7. tangential_velocity_two
8. normal_gap
9. normal_lm
10. delta_tangential_lm_one
11. delta_tangential_lm_two
12. active_set

contact: Mortar Aux Kernels
3.17.1The contact module shall be able to compute nodal weighted gap distance velocity values via a mortar auxiliary kernel.
3.17.2The contact module shall be able to compute nodal wear depth values in accordance with Archard equation via a mortar auxiliary kernel.
3.17.3The contact module shall be able to compute nodal wear depth values in accordance with Archard equation and the mortar gap velocity via mortar auxiliary kernels in the same input file.
3.17.4Contact module shall compute nodal frictional status of mortar surfaces for a simple problem in which nodes are in stick and slip states.
3.17.5The contact module shall be able to generate an informative error if the nodal frictional status auxiliary kernel is not provided a second frictional Lagrange multiplier for a three-dimensional problem.
3.17.6The contact module shall be able to compute nodal wear depth values in accordance with Archard equation and the mortar gap velocity via mortar auxiliary kernels while including these computations in the definition of mortar normal contact constraints in an asymmetric problem for a short simulation.
3.17.7The contact module shall be able to compute nodal wear depth values in accordance with Archard equation and the mortar gap velocity via mortar auxiliary kernels while including these computations in the definition of mortar normal contact constraints in an asymmetric problem for a short simulation where secondary elements/nodes may project in an oblique manner and where sidesets only span the possible contact patch area.
3.17.8The contact module shall be able to compute nodal wear depth values in accordance with Archard equation and the mortar gap velocity via mortar auxiliary kernels while including these computations in the definition of mortar normal contact constraints in an asymmetric problem for a short simulation where secondary elements/nodes may project in an oblique manner due to wrap-around lower-dimensional domains and sidesets. This test checks for the ability to discard oblique segments with a default minimum projection angle and the fact that wrapping around the lowerd mesh modifies contact geometry (normals, e.g.) and this has an impact on the contact force direction at the geometry discontinuity.
3.17.9The contact module shall be able to compute nodal wear depth values in accordance with Archard equation and the mortar gap velocity via mortar auxiliary kernels while including these computations in the definition of mortar normal contact constraints in an asymmetric problem for a short simulation using the contact action.
3.17.10The system shall allow for a user controllable input such that the mortar segment mesh does not contain segments built from oblique projections. Therefore, the system shall generate many segments from oblique projections if a very small minimum projection angle is chosen.
3.17.11The system shall produce the correct normal contact pressure value for frictionless mortar contact when using an auxiliary kernel.
3.17.12The system shall be able to produce the correct normal contact pressure value in 3D for frictionless mortar contact when using an auxiliary kernel.
3.17.13The system shall be able to produce the correct tangential contact pressure value for frictional mortar contact when using an auxiliary kernel.
3.17.14The system shall be able to produce the correct tangential contact pressure value in 3D for frictional mortar contact when using an auxiliary kernel.

contact: Mortar Cartesian Lms
3.18.1The contact module shall be able to solve a two-dimensional frictionless problem with Cartesian Lagrange multipliers.
3.18.2The contact module shall be able to solve a three-dimensional frictionless problem with Cartesian Lagrange multipliers.
3.18.3Contact module shall solve a three-dimensional frictional problem with Cartesian Lagrange multipliers.
3.18.4The contact module shall be able to solve a flat surface-flat surface frictional problem with Cartesian Lagrange multipliers.
3.18.5The contact module shall be able to solve a cylinder-on-plane plane strain frictional problem with Cartesian Lagrange multipliers.
3.18.6The contact module shall be able to solve a flat surface-flat surface frictional problem with Cartesian Lagrange multipliers using VCP.
3.18.7The contact module shall be able to solve a cylinder-on-plane plane strain frictional problem with Cartesian Lagrange multipliers using VCP.

contact: Mortar Dynamics
3.19.1The system shall solve mortar frictionless contact between two blocks with weighted gap time stabilization using mortar nodal geometry.
3.19.2The system shall solve dynamics mortar contact between two blocks with weighted gap time stabilization and match reference kinetic and elastic energy results.
3.19.3The system shall solve mortar frictionless contact between two blocks with weighted gap time stabilization using mortar nodal geometry via the contact mechanics action.
3.19.4The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter beta is provided.
3.19.5The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter gamma is provided.
3.19.6The system shall solve mortar frictional contact between two blocks with weighted gap time stabilization using mortar nodal geometry.
3.19.7The system shall solve mortar frictional contact between two blocks with weighted gap time stabilization using mortar nodal geometry via the contact action.
3.19.8The system shall simulate mortar frictional contact between two blocks with weighted gap time stabilization using mortar nodal geometry with a creep material model.
3.19.9The system shall solve a dynamic 3D frictional bouncing block problem with mortar constraint using nodal-attached geometry
3.19.10The system shall solve a dynamic 3D frictional one-element bouncing block problem with mortar constraint using nodal-attached geometry and the correct edge dropping setting
3.19.11The system shall solve a dynamic 3D frictional one-element bouncing block problem with mortar constraint using nodal-attached geometry and the incorrect edge dropping setting
3.19.12The system shall solve a dynamic 3D frictional one-element bouncing block problem with mortar constraints using nodal geometry and a friction coefficient that depends on the normal contact pressure and the relative tangential velocity

contact: Mortar Restart
3.20.1The system shall be able to run a two-dimensional frictional model using the contact action for mortar applications
3.20.2The system shall be able to restart a mortar mechanical contact simulation via the action without generating additional lower dimensional subdomains which may be unused

contact: Mortar Tm
3.21.1
The system shall be able to compute a soft block bouncing on a soft plank problem on a first order 2D mesh using tensor mechanics and frictional mortar contact
1. using the finite strain formulation.
2. using the finite strain formulation for a limited time simulation.
3. using the finite strain formulation and reference residual.
4. using the finite strain formulation and reference residual with extra_vector_tags passed to the constraints.
3.21.2
The system shall be able to compute a block bouncing on a plank problem on a first order 2D mesh using tensor mechanics and frictional mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.3
The system shall be able to compute a soft block bouncing on a soft plank problem on a first order 2D mesh using tensor mechanics with second order elements and frictional mortar contact
1. using the finite strain formulation.
2. using the finite strain formulation and reference residual.
3.21.4
The system shall be able to compute a block bouncing on a plank problem on a first order 2D mesh using tensor mechanics with second order elements and frictional mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.5
The system shall be able to use automatic differentiation to compute a soft block bouncing on a soft plank problem on a first order 2D mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
5. using the small strain formulation and calculate a perfect Jacobian.
6. using the finite strain formulation and calculate a perfect Jacobian.
3.21.6
The system shall be able to use automatic differntiation to compute a block bouncing on a plank problem on a first order 2D mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.7
The system shall be able to use automatic differntiation to compute a soft block bouncing on a soft plank problem on a second order 2D mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
5. using the small strain formulation and calculate a perfect Jacobian.
6. using the finite strain formulation and calculate a perfect Jacobian.
3.21.8
The system shall be able to use automatic differntiation to compute a block bouncing on a plank problem on a second order 2D mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.9
The system shall be able to compute a soft block bouncing on a soft plank problem on a first order 2D mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation for a limited time simulation.
4. using the finite strain formulation with automatic scaling.
5. using the finite strain formulation and reference residual.
6. using the finite strain formulation and reference residual with extra_vector_tags passed to the constraints.
3.21.10
The system shall be able to compute a block bouncing on a plank problem on a first order 2D mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.11
The system shall be able to compute a soft block bouncing on a soft plank problem on a second order 2D mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
3.21.12
The system shall be able to compute a block bouncing on a plank problem on a second order 2D mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.13
The system shall be able to use automatic differntiation to compute a soft block bouncing on a soft plank problem on a first order 2DRz mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
5. using the small strain formulation and calculate a perfect Jacobian.
6. using the finite strain formulation and calculate a perfect Jacobian.
3.21.14
The system shall be able to use automatic differntiation to compute a block bouncing on a plank problem on a first order 2DRz mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.15
The system shall be able to use automatic differentiation to compute a soft block bouncing on a soft plank problem on a second order 2DRz mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
5. using the small strain formulation and calculate a perfect Jacobian.
6. using the finite strain formulation and calculate a perfect Jacobian.
3.21.16
The system shall be able to use automatic differntiation to compute a block bouncing on a plank problem on a second order 2DRz mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.17
The system shall be able to compute a soft block bouncing on a soft plank problem on a first order 2DRz mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
3.21.18
The system shall be able to compute a block bouncing on a plank problem on a first order 2DRz mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.19
The system shall be able to compute a soft block bouncing on a soft plank problem on a second order 2DRz mesh using tensor mechanics and mortar contact
1. using the small strain formulation.
2. using the finite strain formulation.
3. using the finite strain formulation with automatic scaling.
4. using the finite strain formulation and reference residual.
3.21.20
The system shall be able to compute a block bouncing on a plank problem on a second order 2DRz mesh using tensor mechanics and mortar contact and finite strain
1. using with a stiff block and a stiff plank.
2. using with a soft block and a stiff plank.
3.21.21

contact: Multiple Contact Pairs
3.22.1The system shall set up node-face interactions between multiple surface pairs using a contact action syntax.
3.22.2The system shall set up node-face interactions between multiple surface pairs using a contact action syntax and remove repeated contact pairs.
3.22.3The system shall set up mortar interactions between multiple surface pairs using a contact action syntax with distinct input blocks.
3.22.4The system shall set up frictional mortar interactions between multiple surface pairs using a contact action syntax with distinct input blocks.
3.22.5The system shall assign and accumulate a single contact pressure auxiliary variable for all contact pairs supplied to a single contact action object.
3.22.6The system shall assign and accumulate a single contact pressure auxiliary variable for all contact pairs supplied to a single contact action object with a different combination of primary-secondary pairs.
3.22.7The system shall be able to, if the user provides a reference distance, assign primary-secondary contact pairs automatically.
3.22.8The system shall be able to, if the user provides a reference distance, assign primary-secondary contact pairs automatically using proximity between nodes that belong to arbitrary boundaries.
3.22.9The system shall be able to, if the user provides a too-small reference distance, avoid assigning primary-secondary contact pairs using proximity between nodes.
3.22.10The system shall be able to, if the user provides a very large reference distance, assign primary-secondary contact pairs automatically using proximity between nodes that belong to arbitrary boundaries.
3.22.11The system shall generate an error if insufficient information to automatically define contact surface pairs is provided.
3.22.12The system shall assign and accumulate a single contact pressure auxiliary variable for all contact pairs supplied to a distinct contact action object.
3.22.13The system shall compute mechanical contact with multiple pairs, which are defined with separate contact sidesets.
3.22.14The system shall compute mechanical contact allowing a secondary surface to enforce constraints with multiple primary surfaces.

contact: Nodal Area
3.23.1The system shall compute the nodal area for use with contact calculations in 3D.
3.23.2The system shall compute the nodal area in parallel for use with contact calculations in 3D.
3.23.3The system shall compute the nodal area for use with contact calculations in 2D.
3.23.4The system shall compute the nodal area in parallel for use with contact calculations in 2D.
3.23.5The system shall compute the nodal area for Hex20 elements for use with contact calculations.
3.23.6The system shall compute the nodal area for Hex20 elements for use with frictionless contact calculations.
3.23.7The system shall compute the nodal area for Hex20 elements for use with penalty contact calculations.
3.23.8The system shall compute the nodal area in parallel for Hex20 elements for use with contact calculations.
3.23.9The system shall compute the nodal area for Hex27 elements for use with contact calculations.
3.23.10The system shall compute the nodal area in parallel for Hex27 elements for use with contact calculations.

contact: Non-Singular-Frictional-Mortar
3.24.1The system shall not generate singular Jacobians in frictional mortar contact.

contact: Normalized Penalty
3.25.1The contact system shall yield repeatable results for 2D contact with elements of various aspect ratios. Penalty contact.
3.25.2The contact system shall yield repeatable results for 2D contact with Q8 elements of various aspect ratios. Penalty contact.
3.25.3The contact system shall yield repeatable results for 2D contact with elements of various aspect ratios. Kinematic contact.
3.25.4The contact system shall yield repeatable results for 2D contact with Q8 elements of various aspect ratios. Kinematic contact.

contact: Pdass Problems
3.26.1The contact module shall be able to solve frictional contact between a cylinder and a plane.
3.26.2The contact module shall be able to approximate frictional contact solution between a cylinder and a plane using penalty mortar contact.
3.26.3The contact module shall be able to approximate frictional contact solution between a cylinder and a plane using penalty mortar contact after performing initial adaptivity around the contact area.
3.26.4The contact module shall be able to approximate normal contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement.
3.26.5The contact action shall be alert the user if Augmented Lagrage parameters are supplied, but the selected Problem class does not support AL.
3.26.6The contact module shall be able to approximate frictional contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement.
3.26.7The contact module shall be able to approximate frictional contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement with a tight slip distance tolerance.
3.26.8The contact module shall be able to approximate frictional contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement using the contact action.
3.26.9The contact module shall be able to approximate frictional contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement using the contact action and use the hypre algebraic multigrid preconditioner since the augmented Lagrange (Uzawa) constraint enfrocement approach allows for maintaining reasonable system condition numbers.
3.26.10The contact module shall be able to approximate frictional contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement using the contact action and use the hypre algebraic multigrid preconditioner since the augmented Lagrange (Uzawa) constraint enfrocement approach allows for maintaining reasonable system condition numbers and selecting the 'Bussetta' and 'Simple' adaptivity strategies for the normal and frictional penalty values, respectively.
3.26.11The contact module shall be able to approximate frictional contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement using the contact action and use the hypre algebraic multigrid preconditioner since the augmented Lagrange (Uzawa) constraint enfrocement approach allows for maintaining reasonable system condition numbers and selecting the 'Bussetta' and 'FrictionLimit' adaptivity strategies for the normal and frictional penalty values, respectively.
3.26.12The contact module shall be able to approximate normal contact in a two-dimensional cylinder via an augmented Lagrange approach to constraint enforcement and allow for separation.
3.26.13The contact module shall be able to solve frictional contact between a semicircular tool and flexible base material.
3.26.14The contact module shall be able to solve frictional contact between a semicircular tool and flexible base material using a penalty approach to mortar contact.
3.26.15The contact module shall be able to solve frictional contact between a semicircular tool and flexible base material using a penalty approach to mortar contact through the contact action.
3.26.16The contact module shall be able to solve frictional contact between a bouncing block and flexible base material.
3.26.17The contact module shall be able to solve frictional contact between a bouncing block and flexible base material verifying setup in the contact action.
3.26.18The contact module shall be able to solve frictional contact between a bouncing block and a flexible substrate when correct edge dropping is enabled. An additional requirement is that the correct edge dropping treatment must yield same results as an incorrect edge dropping treatment when there is not edge dropping, e.g. when the entire secondary surface projects to the primary surface.

contact: Pressure
3.27.1The contact system shall reproduce contact pressure results among various formulation types. Augmented Lagrangian formulation.
3.27.2The contact system shall reproduce contact pressure results among various formulation types. Penalty.
3.27.3The contact system shall reproduce contact pressure results among various formulation types. Mechanical constraint.

contact: Ranfs-And-Scaling
3.28.1The system shall be able to apply automatic scaling in conjunction with ranfs contact
3.28.2The system shall be able to solve ranfs contact with no scaling

contact: Ring Contact
3.29.1The contact system shall enforce contact between three-dimensional non-conformal surfaces with Hex20 elements.

contact: Simple Contact
3.30.1
3.30.2
3.30.3
3.30.4
3.30.5The system shall simulate correct contact behavior in 2D when two blocks with the same height come into contact using the dual basis
3.30.6The system shall simulate correct contact behavior in 2D when two blocks with the same height come into contact using the Petrov-Galerkin approach.
3.30.7The system shall simulate correct contact behavior in 2D when two blocks with the same height come into contact using the standard (non-dual) basis
3.30.8The system shall simulate correct contact behavior in 3D when two blocks with the same height come into contact using the dual basis
3.30.9The system shall simulate correct contact behavior in 3D when two blocks with the same height come into contact using the Petrov-Galerkin approach.
3.30.10The system shall simulate correct contact behavior in 3D when two blocks with the same height come into contact using the standard (non-dual) basis

contact: Sliding Block
3.31.1The system shall simulate correct contact behavior in 2D when the node from a secondary mortar element does not project to the primary surface using the dual basis
3.31.2The system shall simulate correct contact behavior in 2D when the node from a secondary mortar element does not project to the primary surface using the standard (non-dual) basis
3.31.3The system shall simulate correct contact behavior in 3D when the node from a secondary mortar element does not project to the primary surface
3.31.4The system shall simulate correct contact behavior in 3D when the node from a secondary mortar element does not project to the primary surface using the standard (non-dual) basis
3.31.5We shall be able to run our canonical frictional sliding block problem with lagrange multipliers and the mortar method
3.31.6We shall be able to solve the Coulomb friction sliding block problem using the penalty method and a friction coefficient of .2
3.31.7We shall be able to solve the Coulomb friction sliding block problem using the penalty method and a friction coefficient of .4
3.31.8We shall be able to solve the frictionless sliding block problem using a kinematic constraint formulation.
3.31.9Kinematic contact shall produce the same results regardless of whether variable scaling is used or not
3.31.10We shall be able to solve the frictionless sliding block problem using a penalty constraint formulation.
3.31.11We shall be able to solve the frictionless sliding block problem with a line serach customized for mechanical contact.
3.31.12The system shall support mechanics frictional contact problems
3.31.13The system shall support mechanics frictional contact problems
3.31.14The system shall support mechanics frictionless contact problems
3.31.15The system shall support mechanics frictionless contact problems
3.31.16The system shall support mechanics frictionless contact problems
3.31.17The system shall support mechanics frictional contact problems

contact: Tan-Pen-And-Scaling
3.32.1The system shall be able to apply automatic scaling in conjunection with tangential penalty contact constraint enforcement and show no penetration and exhibit good nonlinear convergence
3.32.2The system shall yield the same physical results when solving a tangential penalty contact problem with and without automatic scaling

contact: Tension Release
3.33.1The contact system shall enforce and release contact conditions. 4 elements.
3.33.2The contact system shall enforce and release contact conditions. 4 elements and mechanical constraints.
3.33.3The contact system shall enforce and release contact conditions. 4 elements and ensure no new Jacobian allocations.
3.33.4The contact system shall enforce and release contact conditions. 8 elements.

contact: Verification
3.34.1The Contact system shall enforce glued, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem.
3.34.2The Contact system shall enforce glued, penalty contact for 2D Hertz half-symmetry cylindrical contact problem.
3.34.3The Contact system shall enforce frictionless, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem.
3.34.4The Contact system shall enforce frictionless, penalty contact for 2D Hertz half-symmetry cylindrical contact problem.
3.34.5The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem.
3.34.6The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem with friction coefficient of 0.
3.34.7The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem with friction coefficient of 0.2.
3.34.8The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem with friction coefficient of 1.0.
3.34.9The Contact system shall enforce frictional, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem.
3.34.10The Contact system shall enforce glued, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.11The Contact system shall enforce glued, penalty contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.12The Contact system shall enforce frictionless, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.13The Contact system shall enforce frictionless, penalty contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.14The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.15The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements and with a friction coefficient of 0.
3.34.16The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements and with a friction coefficient of 1.0.
3.34.17The Contact system shall enforce frictional, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.18The Contact system shall enforce glued, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem.
3.34.19The Contact system shall enforce glued, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem.
3.34.20The Contact system shall enforce frictionless, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem.
3.34.21The Contact system shall enforce frictionless, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem.
3.34.22The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz quarter-symmetry cylindrical contact problem.
3.34.23The Contact system shall enforce glued, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.24The Contact system shall enforce glued, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.25The Contact system shall enforce frictionless, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.26The Contact system shall enforce frictionless, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.27The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
3.34.28The Contact system shall enforce eliminating initial overclosure between the primary and secondary surfaces.
3.34.29The system shall enforce the automatic patch update using the 'always' option.
3.34.30The system shall enforce the automatic patch update using the iteration option and give results equal to the 'always' option.
3.34.31The system shall enforce that the nearest neighbor node is inside the ghosted set of elements.
3.34.32The system shall be able to couple iteration patch update strategies with initial adaptivity when using geometric searches with a replicated mesh.
3.34.33The system shall be able to couple iteration patch update strategies with initial adaptivity when using geometric searches using node face contact with a replicated or distributed mesh.
3.34.34The Contact system shall enforce glued, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.35The Contact system shall enforce glued, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.36The Contact system shall enforce frictionless, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.37The Contact system shall enforce frictionless, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.38The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.39The Contact system shall enforce frictional, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.40The Contact system shall enforce frictional, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.41The Contact system shall enforce glued, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.42The Contact system shall enforce glued, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.43The Contact system shall enforce frictionless, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.44The Contact system shall enforce frictionless, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.45The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.46The Contact system shall enforce frictional, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.47The Contact system shall enforce frictional, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.48The Contact system shall enforce frictionless, kinematic contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.49The Contact system shall enforce frictionless, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.50The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.51The Contact system shall enforce frictional, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.52The Contact system shall enforce frictional, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.53The Contact system shall enforce glued, kinematic contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.54The Contact system shall enforce glued, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.55The Contact system shall enforce frictionless, kinematic contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.56The Contact system shall enforce frictionless, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.57The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.58The Contact system shall enforce frictional, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.59The Contact system shall enforce frictional, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.60The Contact system shall enforce glued, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.61The Contact system shall enforce glued, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.62The Contact system shall enforce frictionless, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.63The Contact system shall enforce frictionless, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.64The Contact system shall enforce frictionless, penalty Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.65The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.66The Contact system shall enforce frictional, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.67The Contact system shall enforce glued, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.68The Contact system shall enforce glued, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.69The Contact system shall enforce frictionless, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.70The Contact system shall enforce frictionless, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.71The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.72The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.73The Contact system shall enforce frictional, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.74The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.75The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.76The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.77The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.78The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.79The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.80The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.81The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.82The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.83The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.84The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.85The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.86The system shall be able to run a two-dimensional simulation of a cylinder pressed onto a plane with a frictional interface.
3.34.87The Contact system shall enforce glued, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.88The Contact system shall enforce glued, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.89The Contact system shall enforce frictionless, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.90The Contact system shall enforce frictionless, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.91The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.92The Contact system shall enforce frictional, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.93The Contact system shall enforce frictional, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.94The Contact system shall enforce glued, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.95The Contact system shall enforce glued, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.96The Contact system shall enforce frictionless, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.97The Contact system shall enforce frictionless, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.98The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.99The Contact system shall enforce frictional, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.100The Contact system shall enforce frictional, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.101The Contact system shall enforce glued, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.102The Contact system shall enforce glued, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.103The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.104The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.105The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.106The Contact system shall enforce frictional, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.107The Contact system shall enforce frictional, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.108The Contact system shall enforce glued, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.109The Contact system shall enforce glued, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.110The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.111The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.112The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.113The Contact system shall enforce frictional, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.114The Contact system shall enforce frictional, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.115The Contact system shall enforce glued, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.116The Contact system shall enforce glued, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.117The Contact system shall enforce frctionless, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.118The Contact system shall enforce frctionless, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.119The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.120The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.121The Contact system shall enforce frictional, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.122The Contact system shall enforce glued, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.123The Contact system shall enforce glued, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.124The Contact system shall enforce frictionless, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.125The Contact system shall enforce frictionless, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.126The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.127The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.128The Contact system shall enforce frictional, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.129The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.130The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.131The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.132The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.133The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.134The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
3.34.135The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.136The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.137The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.138The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.139The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.140The Contact system shall enforce frictional, Augmented Lagrange contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.141The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
3.34.142The Contact system shall enforce glued, kinematic contact for 2D plane strain single point contact model.
3.34.143The Contact system shall enforce glued, penalty contact for 2D plane strain single point contact model.
3.34.144The Contact system shall enforce frictionless, kinematic contact for 2D plane strain single point contact model.
3.34.145The Contact system shall enforce frictionless, penalty contact for 2D plane strain single point contact model.
3.34.146The Contact system shall enforce frictionless, penalty contact for 2D plane strain single point contact model using the contact line search solver options.
3.34.147The Contact system shall enforce frictional, kinematic contact for 2D plane strain single point contact model.
3.34.148The Contact system shall enforce frictional, penalty contact for 2D plane strain single point contact model.
3.34.149The Contact system shall enforce frictional, kinematic contact for 2D plane strain single point contact model with a non-zero friction coefficient.
3.34.150The Contact system shall enforce frictional, penalty contact for 2D plane strain single point contact model with a non-zero friction coefficient.

Usability Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

Performance Requirements

No requirements of this type exist for this application, beyond those of its dependencies.

System Interfaces

No requirements of this type exist for this application, beyond those of its dependencies.

System Operations

Human System Integration Requirements

The Contact module is command line driven and conforms to all standard terminal behaviors. Specific human system interaction accommodations shall be a function of the end-user's terminal. MOOSE (and therefore the Contact module) does support optional coloring within the terminal's ability to display color, which may be disabled.

Maintainability

The latest working version (defined as the version that passes all tests in the current regression test suite) shall be publicly available at all times through the repository host provider.
Flaws identified in the system shall be reported and tracked in a ticket or issue based system. The technical lead will determine the severity and priority of all reported issues and assign resources at their discretion to resolve identified issues.
The software maintainers will entertain all proposed changes to the system in a timely manner (within two business days).
The core software in its entirety will be made available under the terms of a designated software license. These license terms are outlined in the LICENSE file alongside the Contact module source code. As a MOOSE physics module, the license for the Contact module is identical to that of the framework - that is, the LGPL version 2.1 license.

Reliability

The regression test suite will cover at least 87% of all lines of code within the Contact module at all times. Known regressions will be recorded and tracked (see Maintainability) to an independent and satisfactory resolution.

System Modes and States

MOOSE applications normally run in normal execution mode when an input file is supplied. However, there are a few other modes that can be triggered with various command line flags as indicated here:

Command Line Flag	Description of mode
`-i <input_file>`	Normal execution mode
`--split-mesh <splits>`	Read the mesh block splitting the mesh into two or more pieces for use in a subsequent run
`--use-split`	(implies -i flag) Execute the simulation but use pre-split mesh files instead of the mesh from the input file
`--yaml`	Output all object descriptions and available parameters in YAML format
`--json`	Output all object descriptions and available parameters in JSON format
`--syntax`	Output all registered syntax
`--registry`	Output all known objects and actions
`--registry-hit`	Output all known objects and actions in HIT format
`--mesh-only` (implies -i flag)	Run only the mesh related tasks and output the final mesh that would be used for the simulation
`--start-in-debugger <debugger>`	Start the simulation attached to the supplied debugger

note

The list of system-modes may not be extensive as the system is designed to be extendable to end-user applications. The complete list of command line options for applications can be obtained by running the executable with zero arguments. See the command line usage.

Physical Characteristics

The Contact module is software only with no associated physical media. See System Requirements for a description of the minimum required hardware necessary for running the Contact module.

Environmental Conditions

Not Applicable

System Security

MOOSE-based applications such as the Contact module have no requirements or special needs related to system security. The software is designed to run completely in user-space with no elevated privileges required nor recommended.

Information Management

The core framework and all modules in their entirety will be made publicly available on an appropriate repository hosting site. Day-to-day backups and security services will be provided by the hosting service. More information about MOOSE backups of the public repository on INL-hosted services can be found on the following page: GitHub Backups

Polices and Regulations

MOOSE-based applications must comply with all export control restrictions.

System Life Cycle Sustainment

MOOSE-based development follows various agile methods. The system is continuously built and deployed in a piecemeal fashion since objects within the system are more or less independent. Every new object requires a test, which in turn requires an associated requirement and design description. The Contact module development team follows the NQA-1 standards.

Packaging, Handling, Shipping and Transportation

No special requirements are needed for packaging or shipping any media containing MOOSE and Contact module source code. However, some MOOSE-based applications that use the Contact module may be export-controlled, in which case all export control restrictions must be adhered to when packaging and shipping media.

Verification

The regression test suite will employ several verification tests using comparison against known analytical solutions, the method of manufactured solutions, and convergence rate analysis.

Introduction
System Overview
References
Definitions and Acronyms
System Requirements
Verification