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.

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: 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