Contact Failure Analysis Report
Introduction
The FAR for the Contact module describes the system functional and non-functional requirements that describe the expected interactions that the software shall provide.
Dependencies
The Contact module is developed using MOOSE and can itself be based on various MOOSE modules, as such the FAR for the Contact module is dependent upon the following documents.
- Framework Failure Analysis Report
- sqa/tensor_mechanics_far.md
Failure Analysis Requirements
The following is a complete list for all the requirements related to failure analysis for the Contact module.
- contact: Bouncing-Block-Contact
- 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
Specification(s): ranfs-ping-pong
Design: Constraints System
Issue(s): #10950
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 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
Specification(s): kinematic-ping-pong
Design: Constraints System
Issue(s): #10950
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Check Error
- 3.5.1
Specification(s): contact_displacements
Design: Contact Module
Issue(s): #2816
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Mortar Augmented Lagrange
- 3.16.1The aux kernel shall throw an error if the supplied user object dies not support computing the property
- normal_pressure
- accumulated_slip_one
- tangential_pressure_one
- tangential_velocity_one
- accumulated_slip_two
- tangential_pressure_two
- tangential_velocity_two
- normal_gap
- normal_lm
- delta_tangential_lm_one
- delta_tangential_lm_two
- active_set
Specification(s): aux_errors/normal_pressure, aux_errors/accumulated_slip_one, aux_errors/tangential_pressure_one, aux_errors/tangential_velocity_one, aux_errors/accumulated_slip_two, aux_errors/tangential_pressure_two, aux_errors/tangential_velocity_two, aux_errors/normal_gap, aux_errors/normal_lm, aux_errors/delta_tangential_lm_one, aux_errors/delta_tangential_lm_two, aux_errors/active_set
Design: PenaltyMortarUserObjectAux
Issue(s): #24349
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Mortar Aux Kernels
- 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.
Specification(s): frictional-mortar-3d-status-error
Design: ComputeDynamicFrictionalForceLMMechanicalContactMortarPressureComponentAux
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Mortar Dynamics
- 3.19.4The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter beta is provided.
Specification(s): block-dynamics-action-beta-error
Design: ComputeDynamicFrictionalForceLMMechanicalContactComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- 3.19.5The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter gamma is provided.
Specification(s): block-dynamics-action-gamma-error
Design: ComputeDynamicFrictionalForceLMMechanicalContactComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Multiple Contact Pairs
- 3.22.11The system shall generate an error if insufficient information to automatically define contact surface pairs is provided.
Specification(s): three_hexagons_coarse_automatic_pair_error
Design: ContactMechanicalContactConstraintContactPressureAux
Issue(s): #24122
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Pdass Problems
- 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.
Specification(s): action_error
Design: ComputeFrictionalForceLMMechanicalContact
Issue(s): #17495
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
- contact: Verification
- 3.34.31The system shall enforce that the nearest neighbor node is inside the ghosted set of elements.
Specification(s): error_test
Design: ContactMechanicalContactConstraint
Issue(s): #716
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
Prerequisite(s): 3.34.30