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: 3D-Mortar-Contact
3.1.6
The system shall support the contact action Lagrange multiplier space option for 3D mortar contact
1. by accepting it for a 3D mortar formulation
2. and by rejecting it for non-mortar contact formulations
3. and by rejecting it for mortar penalty contact.
Specification(s): frictionless-mortar-3d-action-lm-space/linear, frictionless-mortar-3d-action-lm-space/non-mortar-error, frictionless-mortar-3d-action-lm-space/mortar-penalty-error
Design: Constraints System
Issue(s): #33284
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunAppRunException

contact: Bouncing-Block-Contact
3.4.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.4.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
3.4.12
The contact action shall support Coulomb friction regularization options for mortar Lagrange multiplier contact
1. by accepting Lagrange multiplier mortar friction regularization options
2. and by requiring a positive reference slip when the friction coefficient is regularized
3. and by rejecting a nonpositive friction enforcement epsilon
4. and by rejecting nonpositive reference slip for regularized friction
5. and by rejecting negative reference slip even without coefficient regularization
6. and by solving a short regularized mortar Lagrange multiplier contact problem.
Specification(s): coulomb_friction_regularization_lm_mortar/accept, coulomb_friction_regularization_lm_mortar/missing_reference_slip_error, coulomb_friction_regularization_lm_mortar/bad_epsilon_error, coulomb_friction_regularization_lm_mortar/nonpositive_reference_slip_error, coulomb_friction_regularization_lm_mortar/negative_reference_slip_error, coulomb_friction_regularization_lm_mortar/run
Design: Contact Action ComputeFrictionalForceLMMechanicalContact
Issue(s): #33356
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunAppRunException
3.4.13
The contact action shall reject friction regularization options for unsupported contact models and formulations
1. by rejecting friction regularization for non-Coulomb contact
2. and by rejecting friction regularization for RANFS contact
3. and by rejecting friction regularization for node-face penalty contact
4. and by rejecting friction regularization for mortar-penalty contact.
Specification(s): coulomb_friction_regularization_action_errors/non_coulomb_regularization_error, coulomb_friction_regularization_action_errors/ranfs_regularization_error, coulomb_friction_regularization_action_errors/node_face_penalty_regularization_error, coulomb_friction_regularization_action_errors/mortar_penalty_regularization_error
Design: Contact Action
Issue(s): #33356
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException

contact: Check Error
3.6.1The system shall generate an error if contact is used without updated coordinates
Specification(s): contact_displacements
Design: Contact Module
Issue(s): #2816
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException

contact: Mortar Augmented Lagrange
3.17.1
The aux kernel shall throw an error if the supplied user object dies not support computing the property
1. accumulated_slip_one
2. tangential_pressure_one
3. tangential_velocity_one
4. accumulated_slip_two
5. tangential_pressure_two
6. tangential_velocity_two
7. normal_gap
8. normal_lm
9. delta_tangential_lm_one
10. delta_tangential_lm_two
11. active_set
Specification(s): 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: MortarUserObjectAux
Issue(s): #24349
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException

contact: Mortar Aux Kernels
3.18.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): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException

contact: Mortar Dynamics
3.20.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: Contact Action ComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671 #33356
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
3.20.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: Contact Action ComputeDynamicFrictionalForceLMMechanicalContact
Issue(s): #19671 #33356
Collection(s): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException

contact: Multiple Contact Pairs
3.23.15The 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): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException

contact: Pdass Problems
3.27.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.35.31The 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): FUNCTIONALFAILURE_ANALYSIS
Type(s): RunException
Prerequisite(s): 3.35.30


[non-mortar-error]
  type = 'RunException'
  input = 'frictionless-mortar-3d-action.i'
  cli_args = 'Contact/mortar/formulation=kinematic Contact/mortar/lm_space=LINEAR'
  expect_err = "The 'lm_space' option can only be used with the 'mortar' formulation"
  detail = 'and by rejecting it for non-mortar contact formulations'
[]


[mortar-penalty-error]
  type = 'RunException'
  input = 'frictionless-mortar-3d-action.i'
  cli_args = 'Contact/mortar/formulation=mortar_penalty Contact/mortar/lm_space=LINEAR'
  expect_err = "The 'lm_space' option can only be used with the 'mortar' formulation"
  detail = 'and by rejecting it for mortar penalty contact.'
[]


[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
[]


[accept]
  type = 'RunApp'
  input = frictional-nodal-min-normal-lm-mortar-pdass-tangential-lm-mortar-action.i
  check_input = true
  cli_args = 'Contact/frictional/friction_elastic_slip=1e-4 Contact/frictional/friction_coefficient_regularization=ARCTAN_SLIP Contact/frictional/friction_reference_slip=1e-3'
  detail = 'by accepting Lagrange multiplier mortar friction regularization options'
[]


[missing_reference_slip_error]
  type = 'RunException'
  input = frictional-nodal-min-normal-lm-mortar-pdass-tangential-lm-mortar-action.i
  cli_args = 'Contact/frictional/friction_coefficient_regularization=ARCTAN_SLIP'
  expect_err = 'A positive friction_reference_slip is required when friction_coefficient_regularization is not NONE'
  detail = 'and by requiring a positive reference slip when the friction coefficient is regularized'
[]


[bad_epsilon_error]
  type = 'RunException'
  input = frictional-nodal-min-normal-lm-mortar-pdass-tangential-lm-mortar-disp.i
  cli_args = 'Constraints/frictional_normal_lm/epsilon=0'
  expect_err = "Range check failed for parameter Constraints/frictional_normal_lm/epsilon; expression = 'epsilon > 0', value = 0"
  detail = 'and by rejecting a nonpositive friction enforcement epsilon'
[]


[nonpositive_reference_slip_error]
  type = 'RunException'
  input = frictional-nodal-min-normal-lm-mortar-pdass-tangential-lm-mortar-disp.i
  cli_args = 'Constraints/frictional_normal_lm/friction_coefficient_regularization=ARCTAN_SLIP Constraints/frictional_normal_lm/friction_reference_slip=0'
  expect_err = 'A positive friction_reference_slip is required when friction_coefficient_regularization is not NONE'
  detail = 'and by rejecting nonpositive reference slip for regularized friction'
[]


[negative_reference_slip_error]
  type = 'RunException'
  input = frictional-nodal-min-normal-lm-mortar-pdass-tangential-lm-mortar-action.i
  cli_args = 'Contact/frictional/friction_reference_slip=-1'
  expect_err = "Contact/frictional/friction_reference_slip: Range check failed; expression = 'friction_reference_slip >= 0', value = -1"
  detail = 'and by rejecting negative reference slip even without coefficient regularization'
[]


[run]
  type = 'RunApp'
  input = frictional-nodal-min-normal-lm-mortar-pdass-tangential-lm-mortar-action.i
  cli_args = "Postprocessors/active='' Executioner/end_time=60 Outputs/exodus=false Contact/frictional/friction_elastic_slip=1e-4 Contact/frictional/friction_coefficient_regularization=ARCTAN_SLIP Contact/frictional/friction_reference_slip=1e-3"
  detail = 'and by solving a short regularized mortar Lagrange multiplier contact problem.'
  # This short regression shares its input's default checkpoint base with an existing recover test.
  recover = false
  restep = false
[]


[non_coulomb_regularization_error]
  type = 'RunException'
  input = bouncing-block-ranfs.i
  cli_args = 'Contact/top_bottom/friction_elastic_slip=1e-4'
  expect_err = "The friction regularization options can only be used with the 'coulomb' model"
  detail = 'by rejecting friction regularization for non-Coulomb contact'
[]


[ranfs_regularization_error]
  type = 'RunException'
  input = bouncing-block-ranfs.i
  cli_args = 'Contact/top_bottom/model=coulomb Contact/top_bottom/friction_coefficient=0.1 Contact/top_bottom/friction_elastic_slip=1e-4'
  expect_err = "The friction regularization options are only supported with the 'mortar' formulation"
  detail = 'and by rejecting friction regularization for RANFS contact'
[]


[node_face_penalty_regularization_error]
  type = 'RunException'
  input = bouncing-block-ranfs.i
  cli_args = 'Contact/top_bottom/model=coulomb Contact/top_bottom/formulation=penalty Contact/top_bottom/friction_coefficient=0.1 Contact/top_bottom/friction_elastic_slip=1e-4'
  expect_err = "The friction regularization options are only supported with the 'mortar' formulation"
  detail = 'and by rejecting friction regularization for node-face penalty contact'
[]


[mortar_penalty_regularization_error]
  type = 'RunException'
  input = frictionless-penalty-weighted-gap-action.i
  cli_args = 'Contact/weighted_gap/model=coulomb Contact/weighted_gap/friction_coefficient=0.1 Contact/weighted_gap/friction_elastic_slip=1e-4'
  expect_err = "The friction regularization options are only supported with the 'mortar' formulation"
  detail = 'and by rejecting friction regularization for mortar-penalty contact.'
[]


[contact_displacements]
  type = 'RunException'
  input = 'contact_displacements.i'
  expect_err = "Contact requires updated coordinates.  Use the"
  requirement = "The system shall generate an error if contact is used without updated coordinates"
[]


[accumulated_slip_one]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=accumulated_slip_one'
  detail = 'accumulated_slip_one'
  expect_err = "The 'ACCUMULATED_SLIP_ONE' quantity is only provided by a 'PenaltyFrictionUserObject' or derived object\."
[]


[tangential_pressure_one]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=tangential_pressure_one'
  detail = 'tangential_pressure_one'
  expect_err = "The 'TANGENTIAL_PRESSURE_ONE' quantity is only provided by a 'PenaltyFrictionUserObject' or derived object\."
[]


[tangential_velocity_one]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=tangential_velocity_one'
  detail = 'tangential_velocity_one'
  expect_err = "The 'TANGENTIAL_VELOCITY_ONE' quantity is only provided by a 'WeightedVelocitiesUserObject' or derived object\."
[]


[accumulated_slip_two]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=accumulated_slip_two'
  detail = 'accumulated_slip_two'
  expect_err = "The 'ACCUMULATED_SLIP_TWO' quantity is only provided by a 'PenaltyFrictionUserObject' or derived object\."
[]


[tangential_pressure_two]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=tangential_pressure_two'
  detail = 'tangential_pressure_two'
  expect_err = "The 'TANGENTIAL_PRESSURE_TWO' quantity is only provided by a 'PenaltyFrictionUserObject' or derived object\."
[]


[tangential_velocity_two]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=tangential_velocity_two'
  detail = 'tangential_velocity_two'
  expect_err = "The 'TANGENTIAL_VELOCITY_TWO' quantity is only provided by a 'WeightedVelocitiesUserObject' or derived object\."
[]


[normal_gap]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=normal_gap'
  detail = 'normal_gap'
  expect_err = "The 'NORMAL_GAP' quantity is only provided by a 'WeightedGapUserObject' or derived object\."
[]


[normal_lm]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=normal_lm'
  detail = 'normal_lm'
  expect_err = "The 'NORMAL_LM' quantity is only provided by a 'PenaltyWeightedGapUserObject' or derived object\."
[]


[delta_tangential_lm_one]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=delta_tangential_lm_one'
  detail = 'delta_tangential_lm_one'
  expect_err = "The 'DELTA_TANGENTIAL_LM_ONE' quantity is only provided by a 'PenaltyFrictionUserObject' or derived object\."
[]


[delta_tangential_lm_two]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=delta_tangential_lm_two'
  detail = 'delta_tangential_lm_two'
  expect_err = "The 'DELTA_TANGENTIAL_LM_TWO' quantity is only provided by a 'PenaltyFrictionUserObject' or derived object\."
[]


[active_set]
  type = RunException
  input = aux_errors.i
  cli_args = 'AuxKernels/gap/contact_quantity=active_set'
  detail = 'active_set'
  expect_err = "The 'ACTIVE_SET' quantity is only provided by a 'PenaltyWeightedGapUserObject' or derived object\."
[]


[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'
  max_parallel = 2
  capabilities = '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'
  capabilities = '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'
  capabilities = '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
  # Automatic pairing method requires a serial mesh and the checkpoint is distributed
  mesh_mode = 'replicated'
[]


[action_error]
  type = 'RunException'
  input = 'cylinder_friction_penalty_frictional_al_action.i'
  expect_err = "Augmented Lagrange parameter was specified, but the selected problem type does not support Augmented Lagrange iterations."
  cli_args = 'Problem/type=FEProblem'
  requirement = "The contact action shall be alert the user if Augmented Lagrage parameters are supplied, but the selected Problem class does not support AL."
[]


[error_test]
  type = RunException
  input = 'sliding_update.i'
  cli_args = "Mesh/ghosting_patch_size=2 Mesh/patch_update_strategy='iteration' 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
  # max parallel set to avoid not running into error for more procs
  max_parallel = 2
  mesh_mode = REPLICATED
  requirement = "The system shall enforce that the nearest neighbor
                   node is inside the ghosted set of elements."
[]

Introduction
Dependencies
Failure Analysis Requirements