Difference between revisions of "Detecting Contact"

From OSUPDOCS
Jump to navigation Jump to search
Line 100: Line 100:
=== Notes ===
=== Notes ===


# Note that the universal values of 0.8 and -0.58 apply only to calculations with [[MPM_Methods_and_Simulation_Timing#Input_Commands|two particle per cell]] in each direction and linear shape functions (e.g., [[MPM Methods and Simulation Timing|uGIMP and CPDI shape functions]]). The positive cutoff has to be changed for other particle sizes and spline shape functions. For one particle per cell and linear shape functions, a good value is 1.07. For three or more particles per cell, the value can be varied until you get good visual results in simple contact. The value should decrease as the number of particles per cell increases. A negative cutoff corresponds to a specific function that applies only when two particle per cell in each direction and linear shape functions. Use of any other number of particles on shape function should restrict the value to the best possible positive value and not use a negative value.
# Note that the universal values of 0.8 and -0.58 apply only to calculations with [[MPM_Methods_and_Simulation_Timing#Input_Commands|two particle per cell]] in each direction and linear shape functions (e.g., [[MPM Methods and Simulation Timing|uGIMP and CPDI shape functions]]). The positive cutoff has to be changed for other particle sizes and spline shape functions. For one particle per cell and linear shape functions, a good value is 1.07. For three or more particles per cell, the value can be varied until you get good visual results in simple contact. The value should decrease as the number of particles per cell increases. A negative cutoff corresponds to a specific function that applies only when two particle per cell in each direction and linear shape functions. Use of any other number of particles or shape function should restrict the value to the best possible positive value and not use a negative value.
# The <tt>ContactPosition</tt> command should always be present when all or some contacting material surfaces are initially separated. Note that the command is essential for handling initially-separated surfaces that later come into contact, and it causes no problems for surfaces that start out in contact. They are still modeled correctly.
# The <tt>ContactPosition</tt> command should always be present when all or some contacting material surfaces are initially separated. Note that the command is essential for handling initially-separated surfaces that later come into contact, and it causes no problems for surfaces that start out in contact. They are still modeled correctly.
# Similarly, the <tt>ContactPositionCracks</tt> command should always be present when all or some cracks surfaces are initially separated from materials.  
# Similarly, the <tt>ContactPositionCracks</tt> command should always be present when all or some cracks surfaces are initially separated from materials.  

Revision as of 12:53, 22 August 2019

Both multimaterial mode MPM and explicit cracks need to detect when two surfaces are in contact. This page describes the contact detection options.

Basic Contact Detection

NormalDef.jpg

The figure shows a surface between two materials (a and b) or between two sides of a crack (above and below). The arrow shows a vector normal to the surface oriented from side a to side b. For both multimaterial contact and crack contact, the first step is to decide if the two velocity fields at the node are actually in contact. NairnMPM uses two criteria to detect contact.

Approach velocity
The first step is to decide if the two surface are approaching each other in the normal direction. This criterion reduces to       [math]\displaystyle{ \Delta\vec v \cdot \hat n \lt 0 \qquad {\rm where} \qquad \Delta\vec v = \vec v_a - \vec v_b }[/math] When this criterion is not satisfied, the surfaces are separating and assumed to not be in contact. In early multimaterial MPM,[1] this criterion alone was assumed sufficient to be in contact. It is easy to visualize, however, that this assumption detects contact when surfaces are approaching each other but are still separated. For improved contact, a second criterion based on displacements is added.
Displacement check
If the approach velocity criterion is satisfied, NairnMPM next looks at displacements or positions of the two velocity fields. Basically, this criterion calculates the location of the two surfaces. If they overlap in the normal direction the surfaces are in contact. If they are separated, the surfaces are not in contact. Two ways to find contact surfaces by their surface location are to extrapolate particle displacements or particle positions. These methods are described in the section on the ContactPosition command.

Both multimaterial mode contact and crack contact use the above two criteria. Note that an accurate normal vector is crucial to contact detection and contact physics.

Separation Using Regression Methods

When using regression methods to find surface normals, the code builds list of point clouds around each multimaterial node. Once the normal is found, it examines distanced between the two material along that normal by checking each particle around the node. If the particle are deformed, the calculation accounts for that deformation. The two closest particle determine the interfacial separation.

These regression methods are preferred over all grid extrapolation methods because they provide a directly calculation of separation and can account for particle deformation. When not using regression methods, however, the separation calculation has to be based on extrapolated particle positions and displacement on the grid. See below for those methods. Note the crack modeling finds normals from crack surfaces and therefore never uses regression methods. When modeling cracks, therefore, you must select a grid extrapolation method for calculating separation.

ContactPosition Command

InitialContact.png

When evaluating material separation (for the displacement check) by grid methods, the code extrapolates particle positions within each velocity to the grid. The opening displacement normal to the surfaces is found from

      [math]\displaystyle{ \delta_n = (\vec x_b-\vec x_a)\cdot\hat n }[/math]

where xa and xb are the extrapolated positions for material above and below the surface and n is the surface normal. But, inherent imprecision of surfaces in MPM (or any particle method) causes a problem. Consider the two surfaces in the figure on the right. When calculations start, their nodal positions extrapolated to common nodes (the blue nodes) will show a positive separation. Calculations with linear MPM shape functions with two particles per cell in each direction show that the calculated separation based on positions of two surfaces precisely in contact is

      [math]\displaystyle{ \delta_n \approx 0.8\Delta x }[/math]

where Δx is the cell dimension along the contacting axis.[2] In other words, a contact criterion of δn<0 for contact would not detect contact correctly.

Four approaches can resolve this issue:

  1. Extrapolate particle displacements instead of particle positions to the velocity fields. Now the separation for two surfaces in contact when calculations start is zero and a subsequent finding of δn<0 will indicate contact.
  2. Define a contact-position offset, such as δcon= 0.8δx and detect contact when δncon.
  3. Undertake of more precise analysis of relation between extrapolated position of a material and actual distance to a node. First, we write the separation as:

          [math]\displaystyle{ \delta_n = d(d_{b,ext})-d(d_{a,ext}) \quad {\rm where} \quad d(d_{m,ext}) = (\vec x_m-\vec x_i)\cdot\hat n }[/math]

    where [math]\displaystyle{ d(d_{m,ext}) }[/math] is a function that finds actual distance to a nearby node as a function of the apparent or extrapolated distance. Calculations with linear MPM shape functions in 2D simulations with particles per cell in each direction led to the following function to convert extrapolation distance to actual distance:

          [math]\displaystyle{ {d(d_{ext})\over\Delta x} = \left\{\begin{array}{ll} 1-2\left({-d_{ext}\over 1.25}\right)^{0.58} & d_{ext}\lt 0 \\ 2\left({d_{ext}\over 1.25}\right)^{0.58}-1 & d_{ext}\gt 0 \end{array}\right. }[/math]

    Contact occurs when [math]\displaystyle{ \delta_n\le0 }[/math]
  4. Switch to regression methods to avoid grid data altogether and find separation by actual positions and deformation of particles near the node.

The first three optoins are available in NairnMPM and OSParticulas; the last is only available in OSParticulas. The first (or displacements) method requires all contact situations to exist in the initial state. This situation is common in crack or interface modeling. The second and third methods must be used when these requirements are not met, which is true for any problem where surfaces start out apart and then move into contact during the simulation.

The use of displacements or positions can be set independently for multimaterial contact and crack contact. For multimaterial calculations, pick the desired option using the ContactPosition command. For crack contact, pick the desired option using the ContactPositionCrack command. Multimaterial mode contact most commonly uses the corrected position method (with a ContactPosition command). For cracks, the most common approach is to use displacements instead of position (without a ContactPositionCracks command), but cracks that model dynamic interfacial contact might need to switch to a position method instead. One example of this use in cracks is found in a paper on using cracks to model glue bond lines in oriented strand board.[3]. For backward compatibility for simulations written when separate settings were not allowed (and only the ContactPosition was available), simulations run in single material mode with cracks will treat a ContactPosition command as a synonym for a ContactPositionCrack command.

Note that when using regression methods, neither extrapolated position nor displacement are ever used. Thus any setting made with a ContactPosition command will be ignored. Because cracks don't use regression method for normals, however, a ContactPositionCracks command can still be used to choose method for calculation of crack separation.

Note that imperfect interface modeling with cracks or in multimaterial mode, must use the displacements method for tangential separation whenever the interface law has non-zero tangential traction. Since introduction of the ContactPositionCracks command, the code automatically uses displacements for tangential separation regardless of settings made for multimaterial or crack contact. But, you should still use a ContactPosition are ContactPositionCracks if needed to control the method of finding separation in the normal direction. Simulations run in older versions that had tangential interfacial tractions and used a ContactPosition command may have been less accurate than current code.

Selecting ContactPosition Options

By default, NairnMPM extrapolates particle displacements to velocity fields and uses relative displacements of the two surfaces to detect contact when using grid methods for separation. To switch to extrapolating particle positions instead and pick a method for converting positions into surface separation, scripted files can add the commands:

ContactPosition (cutoff)
ContactPositionCracks (cutoff)

and XML files, the command to add is

<ContactPosition>(cutoff)</ContactPosition>

which should be in the multimaterial block to set for multimaterial contact or in the explicit cracks block to set for crack contact. In all commands, the value entered for (cutoff) determines the method used:

  • (cutoff)≥ 0: A non-negative value means to subtract (cutoff) from apparent separation to find actual separation (see method 2 in previous section). When using this method and two particles per cell, the (cutoff) should always be 0.8. If it is decreased, surfaces will visually come into contact before the particles reach each other. If it is larger than 0.8, objects will visually interpenetrate each other before contact is activated. See below for when 0.8 should be changed.
  • (cutoff)< 0: A negative values means to use a function to determine actual separation. The function that is used is given in method 3 in the previous section. The absolute value of the entered parameter is used as the exponent in that power-law expression. With two particle per cell, this number should always be -0.58 (i.e., exponent wiill be 0.58). See below for this approach can be used.

Note that setting (cutoff)=0 is not the same as omitting the command. It will use method 2 in previous section with zero subtraction and result in detecting contact before particles actually reach contact.

Notes

  1. Note that the universal values of 0.8 and -0.58 apply only to calculations with two particle per cell in each direction and linear shape functions (e.g., uGIMP and CPDI shape functions). The positive cutoff has to be changed for other particle sizes and spline shape functions. For one particle per cell and linear shape functions, a good value is 1.07. For three or more particles per cell, the value can be varied until you get good visual results in simple contact. The value should decrease as the number of particles per cell increases. A negative cutoff corresponds to a specific function that applies only when two particle per cell in each direction and linear shape functions. Use of any other number of particles or shape function should restrict the value to the best possible positive value and not use a negative value.
  2. The ContactPosition command should always be present when all or some contacting material surfaces are initially separated. Note that the command is essential for handling initially-separated surfaces that later come into contact, and it causes no problems for surfaces that start out in contact. They are still modeled correctly.
  3. Similarly, the ContactPositionCracks command should always be present when all or some cracks surfaces are initially separated from materials.
  4. Although ContactPosition and ContactPositionCracks methods can handle both initially-separated or initially-contacted interfaces, it is usually more accurate to omit this command when all surfaces are initially in contact. Some exceptions are when the problem has large relative displacements such as sliding of a block or rolling of a disk along a surface; these actually correspond to parts of the surfaces that were separated coming into contact as the simulation evolves.
  5. For irregular meshes, the absolute cutoff position will depend on the orientation of the crack. The code automatically corrects for this effect using a single input cutoff value by a method described in Nairn (2013).[4]

References

  1. S. G. Bardenhagen, J. E. Guilkey, K. M. Roessig, J. U. Brackbill, W. M. Witzel, and J. C. Foster, "An Improved Contact Algorithm for the Material Point Method and Application to Stress Propagation in Granular Material," Computer Modeling in Engineering & Sciences, 2, 509-522 (2001).
  2. V. Lemiale, A. Hurmane, and J. A. Nairn, "Material Point Method Simulation of Equal Channel Angular Pressing Involving Large Plastic Strain and Contact Through Sharp Corners," Computer Modeling in Eng. & Sci., 70(1), 41-66, (2010).
  3. J. A. Nairn and E. Le, "Numerical Modeling and Experiments on the Role of Strand-to-Strand Interface Quality on the Properties of Oriented Strand Board," Proc of 9th Int. Conf. on Wood Adhesives, Lake Tahoe, Neveda, USA, Sept. 28-30, 2009. (See PDF)
  4. J.A. Nairn, "Modeling Imperfect Interfaces in the Material Point Method using Multimaterial Methods," Computer Modeling in Eng. & Sci., 92, 271-299 (2013).