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): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
2
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): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
2

contact: Check Error
3.5.1
Specification(s): contact_displacements
Design: Contact Module
Issue(s): #2816
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
70

contact: Mortar Aux Kernels
3.14.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: ComputeDynamicFrictionalForceLMMechanicalContact MortarPressureComponentAux
Issue(s): #19671 #21461
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
10

contact: Mortar Dynamics
3.16.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: ComputeDynamicFrictionalForceLMMechanicalContact ComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
70
3.16.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: ComputeDynamicFrictionalForceLMMechanicalContact ComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
70

contact: Multiple Contact Pairs
3.19.8The 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: Contact MechanicalContactConstraint ContactPressureAux
Issue(s): #24122
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
70

contact: Verification
3.31.30The Contact system shall enforce that the nearest neighbor node is inside the ghosted set of elements.
Specification(s): error_test
Design: Contact MechanicalContactConstraint
Issue(s): #716
Collection(s): FAILURE_ANALYSISFUNCTIONAL
Type(s): RunException
Prerequisite(s): 3.31.29
62


[ranfs-ping-pong]
  type = RunException
  expect_err = 'Solve failed and timestep already at or below dtmin, cannot continue!'
  expect_out = 'Time Step 12'
  input = ranfs-ping-pong.i
  requirement = 'The 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'
  heavy = True
[]


[kinematic-ping-pong]
  type = RunException
  expect_err = 'Solve failed and timestep already at or below dtmin, cannot continue!'
  expect_out = 'Time Step 12'
  input = kinematic-ping-pong.i
  requirement = 'The 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'
  heavy = True
[]


[frictional-mortar-3d-status-error]
  type = RunException
  input = 'frictional-mortar-3d-status.i'
  expect_err = 'tangent_two: MortarFrictionalStateAux auxiliary kernel requires a second tangent Lagrange multiplier for three-dimensional problems'
  min_parallel = 1
  max_parallel = 2
  min_ad_size = '100'
  requirement = 'The 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.'
[]


[block-dynamics-action-beta-error]
  type = RunException
  input = 'block-dynamics-action.i'
  expect_err = 'newmark_beta can only be used with the mortar_dynamics option'
  cli_args = 'Contact/mechanical/mortar_dynamics=false Contact/mechanical/newmark_beta=0.25 Executioner/end_time=0.3'
  min_ad_size = '50'
  requirement = 'The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter beta is provided.'
[]


[block-dynamics-action-gamma-error]
  type = RunException
  input = 'block-dynamics-action.i'
  expect_err = 'newmark_gamma can only be used with the mortar_dynamics option'
  cli_args = 'Contact/mechanical/mortar_dynamics=false Contact/mechanical/newmark_gamma=0.5 Executioner/end_time=0.3'
  min_ad_size = '50'
  requirement = 'The system shall generate an error if dynamics is not specifically requested and Newmark-beta integration parameter gamma is provided.'

[]


[three_hexagons_coarse_automatic_pair_error]
  type = 'RunException'
  issues = '#24122'
  input = 'three_hexagons_coarse_automatic_pair.i'
  expect_err = "'primary' and 'secondary' surfaces or a list of boundaries"
  requirement = 'The system shall generate an error if insufficient information to automatically define contact surface pairs is provided.'
  allow_warnings = true
[]


[./error_test]
  type = RunException
  input = 'sliding_update.i'
  cli_args = 'Mesh/ghosting_patch_size=2
                Outputs/file_base=sliding_error_out'
  expect_err = "Error in NearestNodeLocator : The nearest neighbor lies outside the ghosted set of elements. Increase the ghosting_patch_size parameter in the mesh block and try again."
  prereq = sliding_blocks
  min_parallel = 2
  mesh_mode = REPLICATED
  requirement = "The Contact system shall enforce that the nearest neighbor
                   node is inside the ghosted set of elements."
[../]

Introduction
Dependencies
Failure Analysis Requirements