Difference between revisions of "Ignore Contact Law"

From OSUPDOCS
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
== Description ==
== Description ==


This [[Contact Laws#Frictional Contact Laws|frictional contact law]] is not actually a contact law. This law ignores contact on [[MPM Input Files#Using Explicit Cracks|explicit crack]] surfaces. For [[Multimaterial MPM|multimaterial]] contact, this law will revert to a single velocity field or revert to state as if there was no material interface.
This [[Contact Laws|contact law]] is not actually a contact law. This law ignores contact on [[MPM Input Files#Using Explicit Cracks|explicit crack]] surfaces. For [[Multimaterial MPM|multimaterial]] contact, this law will revert to a single velocity field or revert to state as if there was no material interface.


This law will give poor results for cracks that are in contact, unless those cracks never experience contact. For [[Multimaterial MPM|multimaterial mode]] simulations, this mode reverts to a single velocity field. For simulations with more than two materials where some contact by other contact laws and others should use single velocity fields, the better approach than using this law is to use the [[Common Material Properties#Contact Properties|shareMatField (matID)]] in materials that should share the same field.
This law will give poor results for crack problems, unless those cracks never experience contact. For [[Multimaterial MPM|multimaterial mode]] simulations, this mode reverts to a single velocity field. For simulations with more than two materials where some contact by other contact laws and others should use single velocity fields, the better approach than using this law is to use the [[Common Material Properties#Contact Properties|shareMatField (matID)]] in materials that should share the same field, and therefore always "stick" at the interfaces.


== Properties ==
== Properties ==


The law has no properties that need to be set.
This contact law has no properties that need to be set.

Latest revision as of 15:00, 23 January 2016

Description

This contact law is not actually a contact law. This law ignores contact on explicit crack surfaces. For multimaterial contact, this law will revert to a single velocity field or revert to state as if there was no material interface.

This law will give poor results for crack problems, unless those cracks never experience contact. For multimaterial mode simulations, this mode reverts to a single velocity field. For simulations with more than two materials where some contact by other contact laws and others should use single velocity fields, the better approach than using this law is to use the shareMatField (matID) in materials that should share the same field, and therefore always "stick" at the interfaces.

Properties

This contact law has no properties that need to be set.