Contact System Requirements Specification

This template follows Idaho National Laboratory (INL) template TEM-135, "IT System Requirements Specification".

note

This document serves as an addendum to Framework System Requirements Specification and captures information for Software Requirement Specification (SRS) specific to the Contact application.

Introduction

System Purpose

The Multiphysics Object Oriented Simulation Environment (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.

System Overview

System Context

MOOSE is a command-line driven application. This is typical for a high-performance software that is designed to run across several nodes of a cluster system. As such, all of the 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. MOOSE does not maintain any back-end database or interact with any system daemons. It is a executable, which may be launched from the command line and writes out various result files as it runs.

Figure 1: Usage of MOOSE and MOOSE-based applications.

System Functions

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

User Characteristics

Framework Developers: These are the core developers of the framework. They will be responsible for following and enforcing the appropriate software development standards. They will be responsible for designing, implementing and maintaining the software.
Developers: A Scientist or Engineer that utilizes the framework to build his or her own application. This user will typically have a background in modeling and simulation techniques and/or numerical analysis but may only have a limited skill-set when it comes to object-oriented coding and the C++ language. This is our primary focus group. In many cases these developers will be encouraged to give their code back to the framework maintainers.
Analysts: These are users that will run the code and perform various 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 application is developed using MOOSE and is based on various modules, as such the SRS for Contact is dependent upon the files listed at the beginning of this document.

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
FEM	Finite Element Method
INL	Idaho National Laboratory
JFNK	Jacobian-Free Newton-Krylov
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

- A Portable Operating System Interface (POSIX) compliant Unix including the two most recent versions of MacOS and most current versions of Linux. - 4 GB of RAM for optimized compilation (8 GB for debug compilation), 2 GB per core execution - 100 GB disk space - C++17 compatible compiler (GCC, Clang) - Python 3.7+ - Git

Functional Requirements

contact: 3D-Mortar-Contact
4.1.1The system shall solve a 3D frictionless bouncing block problem with mortar constraint
4.1.2The 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
4.1.3The system shall solve a 3D frictionless bouncing block problem with mortar constraint using the contact action
4.1.4The system shall solve a 3D frictionless bouncing block problem with mortar constraint using the contact action and selecting the temporary flag correct edge dropping
4.1.5The system shall solve a 3D frictionless bouncing block problem with mortar constraint and output the mortar segment mesh for debugging purposes
4.1.6The system shall solve a 3D frictionless bouncing block problem with mortar constraint and output the normal and tangent vector fields for debugging purposes
4.1.7The system shall solve a 3D frictional bouncing block problem with mortar constraint using nodal-attached geometry
4.1.8The 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
4.1.9The system shall solve a 3D frictional bouncing block problem with mortar constraint using weakly interpolated mesh geometry, such as normal and tangent vectors

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

contact: Bouncing-Block-Contact
4.3.1The system shall use grid sequencing in order to improve the performance of the nonlinear solve in a frictional contact problem
4.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
4.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
4.3.4A variational consistent mortar formulation with dual bases for frictionless mechanical contact shall not show any ping-ponging behavior
4.3.5We will solve the frictionless bouncing block problem with nodal constraint enforcement, mortar application of forces, and min NCP function
4.3.6We will solve the frictionless bouncing block problem with nodal constraint enforcement, mortar application of forces, and fb NCP function
4.3.7We will solve the frictionless bouncing block problem with nodal constraint enforcement, nodal application of forces, and min NCP function
4.3.8We will solve the frictionless bouncing block problem with nodal constraint enforcement, nodal application of forces, and fb NCP function
4.3.9We will solve the frictionless bouncing block problem with mortar constraint enforcement, mortar application of forces, and min NCP function
4.3.10We will solve the frictionless bouncing block problem with mortar constraint enforcement, mortar application of forces, and fb NCP function
4.3.11We will solve the frictional bouncing block problem with mortar constraint enforcement, mortar application of forces, and min NCP function
4.3.12We will solve the frictional bouncing block problem with mortar constraint enforcement, mortar application of forces, and fb NCP function
4.3.13We will solve the frictional bouncing block problem with nodal constraint enforcement, mortar application of forces, and min NCP function
4.3.14We will solve the frictional bouncing block problem with nodal constraint enforcment for the normal LM using min NCP, mortar constraint enforcement of the tangential LM with fb, and mortar application of forces
4.3.15
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
4.3.16
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
4.3.17
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.3.18
The system shall support a variationally consistent mortar frictional constraints with dual bases
1. using verbose input file
2. using the contact action
4.3.19The 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.
4.3.20The system shall not attempt to zero Lagrange multipliers that do not exist on inactive nodes.

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

contact: Check Error
4.5.1

contact: Dual Mortar
4.6.1The system shall converge and match the solution produced by standard mortar contact.
4.6.2The system shall converge and match the solution produced by dual mortar contact.
4.6.3The system shall converge and match the solution with the standard methods using variable condenstation with AMG.
4.6.4The system shall converge and match the solution with the standard methods using variable condenstation with AMG, by always condensing out the LMs.
4.6.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: Fieldsplit
4.7.1The system shall allow for split preconditioning based on contact surfaces.

contact: Frictional
4.8.1The contact system shall enforce 2D single-point contact with significant accumulated slip.
4.8.2The contact system shall enforce 2D single-point contact with significant accumulated slip. With predictor solver options.
4.8.3The contact system shall enforce 2D single-point contact with significant accumulated slip when formulation selected is tangential_penalty contact.
4.8.4The contact system shall enforce 2D line contact between quads with significant accumulated slip.
4.8.5The contact system shall enforce 2D line contact between quads with significant accumulated slip, when formulation selected is tangential_penalty.

contact: Glued
4.9.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
4.10.1The Contact system shall simulate Hertz contact between sphere and plane as a 2D axisymmetric problem with Quad4 elements.
4.10.2The Contact system shall simulate Hertz contact between sphere and plane as a 2D axisymmetric problem with Quad8 elements.
4.10.3The Contact system shall simulate Hertz contact between sphere and plane as a 3D problem with Hex8 elements.
4.10.4The Contact system shall simulate Hertz contact between sphere and plane as a 3D problem with Hex27 elements.

contact: Incremental Slip
4.11.1

contact: Kinematic-And-Scaling
4.12.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
4.12.2The system shall yield the same physical results when solving a kinematic contact problem with and without automatic scaling

contact: Mechanical Constraint
4.13.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.
4.13.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.
4.13.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.
4.13.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.
4.13.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 Aux Kernels
4.14.1Contact module shall compute nodal weighted gap distance velocity values via a mortar auxiliary kernel.
4.14.2Contact module shall compute nodal wear depth values in accordance with Archard equation via a mortar auxiliary kernel.
4.14.3Contact module shall compute nodal wear depth values in accordance with Archard equation and the mortar gap velocity via mortar auxiliary kernels in the same input file.
4.14.4Contact module shall compute nodal frictional status of mortar surfaces for a simple problem in which nodes are in stick and slip states.
4.14.5Contact module shall generate an informative error if the nodal frictional status auxiliary kernel is not provided a second frictional Lagrange multiplier for a three-dimensional problem.
4.14.6Contact module shall 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.

contact: Mortar Dynamics
4.15.1The system shall solve mortar frictionless contact between two blocks with weighted gap time stabilization using mortar nodal geometry.
4.15.2The system shall solve mortar frictionless contact between two blocks with weighted gap time stabilization using mortar nodal geometry via the contact mechanics action.
4.15.3The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter beta is provided.
4.15.4The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter gamma is provided.
4.15.5The system shall solve mortar frictional contact between two blocks with weighted gap time stabilization using mortar nodal geometry.
4.15.6The system shall solve mortar frictional contact between two blocks with weighted gap time stabilization using mortar nodal geometry via the contact action.
4.15.7The system shall simulate mortar frictional contact between two blocks with weighted gap time stabilization using mortar nodal geometry with a creep material model.
4.15.8The system shall solve a dynamic 3D frictional bouncing block problem with mortar constraint using nodal-attached geometry
4.15.9The 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
4.15.10The 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
4.15.11The system shall solve a dynamic 3D frictional one-element bouncing block problem with mortar constraint using nodal-attached geometry and a friction coefficient that depends on the normal contact pressure and the relative tangential velocity

contact: Mortar Restart
4.16.1The system shall be able to run a two-dimensional frictional model using the contact action for mortar applications
4.16.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
4.17.1
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.
4.17.2
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.
4.17.3
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.
4.17.4
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.
4.17.5
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 with automatic scaling.
4. using the finite strain formulation and reference residual.
4.17.6
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.
4.17.7
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.
4.17.8
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.
4.17.9
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.
4.17.10
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.
4.17.11
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.
4.17.12
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.
4.17.13
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.
4.17.14
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.
4.17.15
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.
4.17.16
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.
4.17.17

contact: Multiple Contact Pairs
4.18.1Contact module action shall allow for multiple contact pairs when selecting node-face formulation.

contact: Nodal Area
4.19.1The system shall compute the nodal area for use with contact calculations in 3D.
4.19.2The system shall compute the nodal area in parallel for use with contact calculations in 3D.
4.19.3The system shall compute the nodal area for use with contact calculations in 2D.
4.19.4The system shall compute the nodal area in parallel for use with contact calculations in 2D.
4.19.5The system shall compute the nodal area for Hex20 elements for use with contact calculations.
4.19.6The system shall compute the nodal area for Hex20 elements for use with frictionless contact calculations.
4.19.7The system shall compute the nodal area for Hex20 elements for use with penalty contact calculations.
4.19.8The system shall compute the nodal area in parallel for Hex20 elements for use with contact calculations.
4.19.9The system shall compute the nodal area for Hex27 elements for use with contact calculations.
4.19.10The system shall compute the nodal area in parallel for Hex27 elements for use with contact calculations.

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

contact: Normal-Nodal-Lm-Tan-Tolerance
4.21.1The system shall provide an option for extending primary surfaces when doing mortar contact to ensure that secondary nodes which project near the edge of the primary surface are registered with the near-surface.

contact: Normalized Penalty
4.22.1The contact system shall yield repeatable results for 2D contact with elements of various aspect ratios. Penalty contact.
4.22.2The contact system shall yield repeatable results for 2D contact with Q8 elements of various aspect ratios. Penalty contact.
4.22.3The contact system shall yield repeatable results for 2D contact with elements of various aspect ratios. Kinematic contact.
4.22.4The contact system shall yield repeatable results for 2D contact with Q8 elements of various aspect ratios. Kinematic contact.

contact: Pdass Problems
4.23.1Contact module shall solve frictional contact between a cylinder and a plane.
4.23.2Contact module shall solve frictional contact between a semicircular tool and flexible base material.
4.23.3Contact module shall solve frictional contact between a bouncing block and flexible base material.
4.23.4Contact module shall solve frictional contact between a bouncing block and flexible base material verifying setup in the contact action.
4.23.5Contact module shall solve frictional contact between a bouncing block and a flexible substrate when correct edge dropping is enabled. Additional requirement is that the correct edge dropping treatment must yield same results as incorrect edge dropping treatment when there is not actual edge dropping, e.g.: All secondary surface projects to the primary surface.

contact: Pressure
4.24.1The contact system shall reproduce contact pressure results among various formulation types. Augmented Lagrangian formulation.
4.24.2The contact system shall reproduce contact pressure results among various formulation types. Penalty.
4.24.3The contact system shall reproduce contact pressure results among various formulation types. Mechanical constraint.

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

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

contact: Simple Contact
4.27.1
4.27.2
4.27.3
4.27.4
4.27.5The system shall simulate correct contact behavior in 2D when two blocks with the same height come into contact using the dual basis
4.27.6The system shall simulate correct contact behavior in 2D when two blocks with the same height come into contact using the standard (non-dual) basis
4.27.7The system shall simulate correct contact behavior in 3D when two blocks with the same height come into contact using the dual basis
4.27.8The 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
4.28.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
4.28.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
4.28.3The system shall simulate correct contact behavior in 3D when the node from a secondary mortar element does not project to the primary surface
4.28.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
4.28.5We shall be able to run our canonical frictional sliding block problem with lagrange multipliers and the mortar method
4.28.6We shall be able to solve the Coulomb friction sliding block problem using the penalty method and a friction coefficient of .2
4.28.7We shall be able to solve the Coulomb friction sliding block problem using the penalty method and a friction coefficient of .4
4.28.8We shall be able to solve the frictionless sliding block problem using a kinematic constraint formulation.
4.28.9Kinematic contact shall produce the same results regardless of whether variable scaling is used or not
4.28.10We shall be able to solve the frictionless sliding block problem using a penalty constraint formulation.
4.28.11We shall be able to solve the frictionless sliding block problem with a line serach customized for mechanical contact.
4.28.12The system shall support mechanics frictional contact problems
4.28.13The system shall support mechanics frictional contact problems
4.28.14The system shall support mechanics frictionless contact problems
4.28.15The system shall support mechanics frictionless contact problems
4.28.16The system shall support mechanics frictionless contact problems
4.28.17The system shall support mechanics frictional contact problems

contact: Tan-Pen-And-Scaling
4.29.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
4.29.2The system shall yield the same physical results when solving a tangential penalty contact problem with and without automatic scaling

contact: Tension Release
4.30.1The contact system shall enforce and release contact conditions. 4 elements.
4.30.2The contact system shall enforce and release contact conditions. 4 elements and mechanical constraints.
4.30.3The contact system shall enforce and release contact conditions. 4 elements and ensure no new Jacobian allocations.
4.30.4The contact system shall enforce and release contact conditions. 8 elements.

contact: Verification
4.31.1The Contact system shall enforce glued, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem.
4.31.2The Contact system shall enforce glued, penalty contact for 2D Hertz half-symmetry cylindrical contact problem.
4.31.3The Contact system shall enforce frictionless, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem.
4.31.4The Contact system shall enforce frictionless, penalty contact for 2D Hertz half-symmetry cylindrical contact problem.
4.31.5The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem.
4.31.6The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem with friction coefficient of 0.
4.31.7The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem with friction coefficient of 0.2.
4.31.8The Contact system shall enforce frictional, penalty contact for 2D Hertz half-symmetry cylindrical contact problem with friction coefficient of 1.0.
4.31.9The Contact system shall enforce frictional, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem.
4.31.10The Contact system shall enforce glued, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.11The Contact system shall enforce glued, penalty contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.12The Contact system shall enforce frictionless, kinematic contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.13The Contact system shall enforce frictionless, penalty contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.14The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.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.
4.31.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.
4.31.17The Contact system shall enforce frictional, Augmented Lagrange contact for 2D Hertz half-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.18The Contact system shall enforce glued, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem.
4.31.19The Contact system shall enforce glued, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem.
4.31.20The Contact system shall enforce frictionless, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem.
4.31.21The Contact system shall enforce frictionless, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem.
4.31.22The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz quarter-symmetry cylindrical contact problem.
4.31.23The Contact system shall enforce glued, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.24The Contact system shall enforce glued, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.25The Contact system shall enforce frictionless, kinematic contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.26The Contact system shall enforce frictionless, penalty contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.27The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D Hertz quarter-symmetry cylindrical contact problem using higher order QUAD8 elements.
4.31.28The Contact system shall enforce eliminating initial overclosure between the primary and secondary surfaces.
4.31.29The Contact system shall enforce the automatic patch update using the iteration option.
4.31.30The Contact system shall enforce that the nearest neighbor node is inside the ghosted set of elements.
4.31.31The Contact system shall enforce glued, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.32The Contact system shall enforce glued, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.33The Contact system shall enforce frictionless, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.34The Contact system shall enforce frictionless, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.35The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.36The Contact system shall enforce frictional, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.37The Contact system shall enforce frictional, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.38The Contact system shall enforce glued, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.39The Contact system shall enforce glued, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.40The Contact system shall enforce frictionless, kinematic contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.41The Contact system shall enforce frictionless, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.42The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.43The Contact system shall enforce frictional, Augmented Lagrange contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.44The Contact system shall enforce frictional, penalty contact for 3D brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.45The Contact system shall enforce frictionless, kinematic contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.46The Contact system shall enforce frictionless, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.47The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.48The Contact system shall enforce frictional, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.49The Contact system shall enforce frictional, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.50The Contact system shall enforce glued, kinematic contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.51The Contact system shall enforce glued, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.52The Contact system shall enforce frictionless, kinematic contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.53The Contact system shall enforce frictionless, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.54The Contact system shall enforce frictionless, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.55The Contact system shall enforce frictional, Augmented Lagrange contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.56The Contact system shall enforce frictional, penalty contact for 3D HEX20 brick geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.57The Contact system shall enforce glued, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.58The Contact system shall enforce glued, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.59The Contact system shall enforce frictionless, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.60The Contact system shall enforce frictionless, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.61The Contact system shall enforce frictionless, penalty Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.62The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.63The Contact system shall enforce frictional, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.64The Contact system shall enforce glued, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.65The Contact system shall enforce glued, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.66The Contact system shall enforce frictionless, kinematic contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.67The Contact system shall enforce frictionless, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.68The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.69The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.70The Contact system shall enforce frictional, penalty contact for 2D axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.71The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.72The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.73The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.74The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.75The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.76The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.77The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.78The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.79The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.80The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.81The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.82The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.83The Contact system shall enforce glued, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.84The Contact system shall enforce glued, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.85The Contact system shall enforce frictionless, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.86The Contact system shall enforce frictionless, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.87The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.88The Contact system shall enforce frictional, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.89The Contact system shall enforce frictional, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.90The Contact system shall enforce glued, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.91The Contact system shall enforce glued, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.92The Contact system shall enforce frictionless, kinematic contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.93The Contact system shall enforce frictionless, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.94The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.95The Contact system shall enforce frictional, Augmented Lagrange contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.96The Contact system shall enforce frictional, penalty contact for 2D plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.97The Contact system shall enforce glued, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.98The Contact system shall enforce glued, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.99The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.100The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.101The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.102The Contact system shall enforce frictional, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.103The Contact system shall enforce frictional, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.104The Contact system shall enforce glued, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.105The Contact system shall enforce glued, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.106The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.107The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.108The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.109The Contact system shall enforce frictional, Augmented Lagrange contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.110The Contact system shall enforce frictional, penalty contact for 2D QUAD8 plane geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.111The Contact system shall enforce glued, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.112The Contact system shall enforce glued, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.113The Contact system shall enforce frctionless, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.114The Contact system shall enforce frctionless, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.115The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.116The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.117The Contact system shall enforce frictional, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.118The Contact system shall enforce glued, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.119The Contact system shall enforce glued, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.120The Contact system shall enforce frictionless, kinematic contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.121The Contact system shall enforce frictionless, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.122The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.123The Contact system shall enforce frictional, Augmented Lagrange contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.124The Contact system shall enforce frictional, penalty contact for 2D axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.125The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.126The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.127The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.128The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.129The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.130The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with matched nodes).
4.31.131The Contact system shall enforce glued, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.132The Contact system shall enforce glued, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.133The Contact system shall enforce frictionless, kinematic contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.134The Contact system shall enforce frictionless, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.135The Contact system shall enforce frictionless, Augmented Lagrange contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.136The Contact system shall enforce frictional, Augmented Lagrange contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.137The Contact system shall enforce frictional, penalty contact for 2D QUAD8 axisymmetric ring geometry (NAFEMS CGS1 contact patch test with mismatched nodes).
4.31.138The Contact system shall enforce glued, kinematic contact for 2D plane strain single point contact model.
4.31.139The Contact system shall enforce glued, penalty contact for 2D plane strain single point contact model.
4.31.140The Contact system shall enforce frictionless, kinematic contact for 2D plane strain single point contact model.
4.31.141The Contact system shall enforce frictionless, penalty contact for 2D plane strain single point contact model.
4.31.142The Contact system shall enforce frictionless, penalty contact for 2D plane strain single point contact model using the contact line search solver options.
4.31.143The Contact system shall enforce frictional, kinematic contact for 2D plane strain single point contact model.
4.31.144The Contact system shall enforce frictional, penalty contact for 2D plane strain single point contact model.
4.31.145The Contact system shall enforce frictional, kinematic contact for 2D plane strain single point contact model with a non-zero friction coefficient.
4.31.146The Contact system shall enforce frictional, penalty contact for 2D plane strain single point contact model with a non-zero friction coefficient.

Usability Requirements

Performace Requirements

System Interfaces

System Operations

Human System Integration Requirements

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

Maintainablity

- 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 his or her 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 framework in its entirety will be made publicly available under the GNU Lesser General Public License (LGPL) version 2.0 license.

Reliability

The regression test suite will cover at least 80% of all lines of code at all times. Known regressions will be recorded and tracked (see Maintainablity) 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`	(inplies -i flag) Execute the 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.

Phyisical Characteristics

MOOSE is software only with no associated physical media. See System Requirements for a description of the minimum required hardware necessary for running a MOOSE-based application.

Environmental Conditions

Not Applicable

System Security

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

Information Management

The core framework in its entirety will be made publicly available on an appropriate repository hosting site. Backups and security services will be provided by the hosting service.

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. Some MOOSE-based development teams follow the Nuclear Quality Assurance Level 1 (NQA-1) standards.

Packaging, Handling, Shipping and Transportation

No special requirements are needed for packaging or shipping any media containing MOOSE source code. However, some MOOSE-based applications maybe 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