Contact System Requirement Specification
Introduction
The Software Requirement Specification (SRS) for Contact describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.
Dependencies
The Contact application is developed using MOOSE and is based on various modules, as such the SRS for Contact is dependent upon the following documents.
Requirements
The following is a complete list for all the functional requirements for Contact.
- contact: Bouncing-Block-Contact
- F4.1.1The system shall use grid sequencing in order to improve the performance of the nonlinear solve in a frictional contact problem
- F4.1.2The system shall be able to produce the same result when not using grid sequencing
- F4.1.3We will solve the frictionless bouncing block problem with nodal constraint enforcement, mortar application of forces, and min NCP function
- F4.1.4We will solve the frictionless bouncing block problem with nodal constraint enforcement, mortar application of forces, and fb NCP function
- F4.1.5We will solve the frictionless bouncing block problem with nodal constraint enforcement, nodal application of forces, and min NCP function
- F4.1.6We will solve the frictionless bouncing block problem with nodal constraint enforcement, nodal application of forces, and fb NCP function
- F4.1.7We will solve the frictionless bouncing block problem with mortar constraint enforcement, mortar application of forces, and min NCP function
- F4.1.8We will solve the frictionless bouncing block problem with mortar constraint enforcement, mortar application of forces, and fb NCP function
- F4.1.9We will solve the frictional bouncing block problem with mortar constraint enforcement, mortar application of forces, and min NCP function
- F4.1.10We will solve the frictional bouncing block problem with mortar constraint enforcement, mortar application of forces, and fb NCP function
- F4.1.11We will solve the frictional bouncing block problem with nodal constraint enforcement, mortar application of forces, and min NCP function
- F4.1.12We 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
- F4.1.13We 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 using the ContactAction. The result shall be identical to that obtained by directly specifying individual objects.
- F4.1.14The 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
- nonsingular both with bounds projection and
- without bounds projection and be
- solvable with amg both with bounds projection
- and without bounds projection.
- The system's RANFS scheme shall have a perfect Jacobian for mechanical contact that only has one non-zero normal component
- The system shall be able to detect when a slave node is ping-ponging back and forth between different master faces and consequently tie the locations of the slave and corresponding master node using Lagrange Multipliers corresponding to equality constraints, e.g. more RANFS
- The system shall be able to solve a smaller model of the full ping-ponging problem
- F4.1.15Using a RANFS scheme with Lagrange multipliers corresponding to equality constraints the system shall be able to
- tie nodes together and
- have a perfect Jacobian
- contact: Mechanical-Small-Problem
- F4.2.1We shall be able to do mechanical contact with the new mortar system. It's beautiful.
- F4.2.2We shall be able to do mechanical contact with mortar for the displacements and node enforcement of the constraints.
- F4.2.3We shall be able to do mechanical contact with mortar for the displacements and node enforcement of the constraints while using the Contact action block. The results should be identical to those gained by specifying individual mortar constraints, variables, and mesh objects.