Contact Failure Analysis Report
Introduction
The 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.
Failure Analysis Requirements
The following is a complete list for all the requirements related to failure analysis for Contact.
- contact: Bouncing-Block-Contact
- 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
Specification(s): ranfs-ping-pong
Design: Constraints System
Issue(s): #10950
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 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
Specification(s): kinematic-ping-pong
Design: Constraints System
Issue(s): #10950
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- contact: Check Error
- 4.5.1
Specification(s): contact_displacements
Design: Contact Module
Issue(s): #2816
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- contact: Mortar Aux Kernels
- 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.
Specification(s): frictional-mortar-3d-status-error
Design: ComputeDynamicFrictionalForceLMMechanicalContactComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- contact: Mortar Dynamics
- 4.15.3The 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): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- 4.15.4The 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): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
- contact: Verification
- 4.31.30The Contact 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): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 4.31.29