Defining Cracks

This section explains how to add explicit cracks to an MPM simulation.

Introduction

The extension of MPM to model explicit cracks is called CRAMP for CRAcks in the Material Point Method. The commands is this section are used to define the explicit cracks (and there can be any number of them). In addition, whenever a simulation has cracks you can use various crack settings commands to customize the features of the crack physics and set various material fracture properties.

The development of CRAMP is described first in a paper by Nairn (2003) (and its development was done using NairnMPM). Some other papers discuss calculation of J integral and stress intensity factor,, propose energy balance propagation, handle cracks in 3D (although not currently available in NairnMPM), use cracks to model imperfect interfaces,, and use traction laws with cracks. Some applications of using cracks in MPM include wood fracture, use of cracks to model glue bods in oriented strand board, simulation of dynamic fracture, and simulation of crack growth with fiber bridging.

Crack Definition Commmands

In CRAMP, a crack is defined as series of massless particles connected by crack segments. The first particle is the "start" tip and the last particle is the "end" tip. When CRAMP is active, nodes around the crack will be divided into two velocity fields to separately model motion of particle "above" the crack and "below" the crack. You define a crack by providing the points along the crack - (x₁,y₁) to (x_n,y_n). In addition, CRAMP fully accounts for crack contact, can model cracks with frictional contact, can use cracks to model imperfect interfaces, and can insert traction laws to model cohesive zones. When defining cracks, some additional commands are used to set crack contact mechanics, set crack tip materials, and insert traction laws.

In scripted files, a single crack is started with a NewCrack command, which is followed by one or more of the other commands to complete the crack definition:

NewCrack (x1),(y1),<(mat)>,<(frict)>,<(tract)>
GrowCrack (x2),(y2),<(mat)>
GrowCrackLine (x2),(y2),(segs),<(mat)>,<(tract)>
GrowCrackArc (x1),(y1),(x2),(y2),(segs),(ang1),(ang2)<(mat)>,<(tract)>
CrackInterface
CrackThickness (thick)

In XML files, each crack is defined in a CrackList element:

<CrackList friction='(frict)'>
  <pt units='mm' x='(x1)' y='(x2)' tip='(mat)'/>
  <pt x='53' y='0'/>
     . . .
  <pt x='(x2)' y='(y2)'/>
  <Line xmin="(x1)" ymin="(y1)" xmax="(x2)" ymax="(y2)" resolution="(segs)"
           start_tip="(mat)" end_tip="(mat)"/>
  <Circle xmin="(x1)" ymin="(y1)" xmax="(x2)" ymax="(y2)" resolution="(segs)"
           start_tip="(mat)" end_tip="(mat)" start_angle="(ang1)" end_angle="(ang2)"/>
  <Thickness>(thick)</Thickness>
</CrackList>

The commands and their functions are:

• NewCrack command - this command starts a new crack (in XML files, the <CrackList> element starts the crack.
• GrowCrack, GrowCrackLine, and GrowCrackArc commands - this commands extend the crack (the corresponding XML commands are <pt>, <Line>, and <Circle>).
• CrackInterface commands - this commands set the crack to be an imperfect interface.
• CrackThickness command - this commands sets the crack thickness (the corresponding XML command is <Thickness>).

Starting the Crack

In scripted files, crack is started with the NewCrack command:

NewCrack (x1),(y1),<(mat)>,<(frict)>,<(tract)>

In XML files, a crack is started with

<CrackList friction='(frict)'>
  <pt units='mm' x='(x1)' y='(x2)' tip='(mat)'/>

where

• (x1),(y1) - defines the start of the crack with crack tip (the coordinates are (R,Z) if axisymmetric).
• (mat) - this optional parameter can be one of three things:
  1. A Material ID - It can define the material at the start of the crack. Crack propagation is only possible when one or both of its crack tips have a material ID. If the material ID is omitted, the MPM calculations will correctly model that crack, but no propagation or fracture parameter calculations will occur.
  2. "exterior" - this text indicates a crack tip at the edge of the body. In XML files, use -2 instead of of the word "exterior".
  3. "fixed" - this text indicates a fixed crack (scripted files only). A fixed crack will not translate with the object and will not track surfaces. It can calculate J Integral but not Stress Intensity factor. It is useful when using cracks to create surfaces in an object. The surface can change by propagating the crack at constant crack speed initiated by critical J or by initiation time (see steady state propagation).
• (frict) - this optional parameter can specify custom frictional contact for this crack. The frictional properties are setting use the same options available in the Friction and FrictionMM commands. This option lets each crack have a different contact law such as different coefficients of friction. If you want to set a contact law on a non-fixed crack, but do not want to define a tip material in (mat), you can enter (mat)="free", and then enter the desired (frict).
• (frict) and (tract) - alternatively, these optional parameters can assign a traction law to the initial crack tip. To use this option, set (frict)="traction" and then set (tract) to a material ID for a traction law material. The traction law will be applied only to the first crack particle.

Some differences in XML files are:

1. To set a "fixed" crack, add an attribute type='fixed' to the <CrackList element.
2. The (mat) option must set the material by number.
3. To assign a traction law use a mat='n' or matnam='name' attribute on the <pt> command.

Growing the Crack

Once a crack is started, it is extended by using one or more growing commands. In scripted files, the commands are:

GrowCrack (x2),(y2),<(mat)>
GrowCrackLine (x2),(y2),(segs),<(mat)>,<(tract)>
GrowCrackArc (x1),(y1),(x2),(y2),(segs),(ang1),(ang2)<(mat)>,<(tract)>

In XML files, the growing commands are:

  <pt x='(x2)' y='(y2)'/>
  <Line xmin="(x1)" ymin="(y1)" xmax="(x2)" ymax="(y2)" resolution="(segs)"
           start_tip="(mat)" end_tip="(mat)"/>
  <Circle xmin="(x1)" ymin="(y1)" xmax="(x2)" ymax="(y2)" resolution="(segs)"
           start_tip="(mat)" end_tip="(mat)" start_angle="(ang1)" end_angle="(ang2)"/>

• (x1,y1) and (x2,y2) - defines two points that are used in the growing action that results from the command (the coordinates are (R,Z) if axisymmetric). Some commands give only (x2,y2); for these commands (x1,y1) is the given by the last point of the previous crack definition command.
• (segs) - the number of segments to create in the command's growing action.
• (ang1) and (ang2) - for the arc commands, these parameters define the start and end angles for the arc growing action.
• (mat) - this optional parameter can be one of two things:
  1. A Material ID - it can define the material at the end of the growing action. Crack propagation is only possible when one or both of its crack tips have a material ID. If the material ID is omitted, the MPM calculations will correctly model that crack, but no propagation or fracture parameter calculations will occur. A crack tip material is only needed if the growing command is the last crack definition command for the current crack.
  2. "exterior" - this text indicates a crack tip at the edge of the body. In XML files, use -2 instead of of the word "exterior". A setting of "exterior" only has an effect if the growing command is the last crack definition command for the current crack.
• (tract) - this optional parameter can assign a traction law to all new crack particles created by the growing action by setting it to the material ID for a traction law material. To set a traction law material but no crack tip material in (mat), you can set(mat) to "0" (or actually to any invalid material ID).

The growing actions for the various crack definition commands are:

• GrowCrack and <pt> - create a single crack particle at (x2,y2) and a crack segment from (x1,y1) to (x2,y2).
• GrowCrackLine and <Line> - create (seg) crack particles and segments evenly spaced along the line (x1,y1) to (x2,y2).
• GrowCrackArc and <Circle> - the points (x1,y1) define (x2,y2) are used to define the corners of a rectangle and an arc is followed between the two (ang1) and (ang2) angles (in degrees as counter-clockwise angle from the positive x axis). The arc is divided into (segs) evenly spaced particles and segments. In addition, the last point of the previous crack definition command will be connected with one segment to the start of the arc. Because the control points for the arc are the boundaries of the oval's rectangle and not the starting and ending points of the resulting arc, linking arcs with points and lines may cause jumps in the crack geometry. One solution is to choose the previou crack definition command to add at the starting of the arc.

Crack as Imperfect Interface

The global ImperfectInterface command sets cracks by default to be an imperfect interface and selects interface parameters. By using the CrackInterface command, you can customize any crack to use different interface parameters. This command can also convert one crack to be an imperfect interface when the default crack setting is for frictional sliding. In scripted files, you can customize the current crack with:

CrackInterface #1,#2,<#3>

where #1, #2, and #3 are all interfacial stiffness parameters and should be entered with units of MPa/mm. See the ImperfectInterface command for a discussion of these three parameters.

In brief, you use the ImperfectInterface command to select interface parameters for all cracks in a simulation. If you want some cracks to have different interface parameters, uses a CrackInterface command sometime after starting the crack with a NewCrack command.

Notes

When an analysis has imperfect interface, you can track total interface energy using the global archiving methods. In an elastic analysis, the total strain energy is the sum of the strain energy and the interface energy. The numerical modeling of imperfect interfaces with linear traction-displacement discontinuity relations is described in a reference by the developer of NairnFEAMPM. Also see beginning of help on interface elements for brief discussion of interface stiffnesses or parameters. The CrackInterface command is only allowed for MPM analyses.

Crack Thickness

The CrackThickness command sets the thickness for an explicit crack. It is only needed if the crack has any particles with a traction law or when crack tips release their energy into heat. In the scripted file, the command is

CrackThickness (thick)

and it applies to the current crack started with the most recent NewCrack command. In XML files, the command, which must by within a <CrackList> element, is:

<Thickness>(thick)</Thickness>

where (thick) is the crack thickness (in mm).

Notes

1. Once a CrackThickness command has been used, all subsequent cracks will use the same thickness unless a new CrackThickness command changes it.
2. If the grid was created using a GridThickness command, (or a thickness attribute) the crack thickness will inherit that thickness. You only need a CrackThickness command to have a different thickness (although having a different thickness is very uncommon and may alter the physics of the cracks.)

Exterior Crack Tip

For cracks that extend outside the object, the recommended approach is to stop the cracking slightly before the edge (e.g., 1/4 to 1/2 a cell from the edge) and define that tip as an "exterior" crack tip by setting its tip property to -2. Such tips are virtually extended beyond the object during calculations to model a crack through the surface. An alternative is simply run the crack beyond the edge ((e.g., 1/2 to 1 beyond the edge). Such crack tips, however, can suffer inaccuracies due to lack of imformation about local velocity fields. The result is such crack tips may not move correctly if the object is moving.

Interacting Cracks

Two cracks handled with rigor. Three or more are beyond the resolution for MPM or any numerical method. Details to follow

Notes

1. Although a straight crack can be mathematically defined with a single segment, the crack surfaces and plane of such cracks would not update well under arbitrary deformation states. Instead cracks should be defined with at least one segment per cell of the background grid. If the crack has [[Traction Laws|traction laws, experience suggest the crack should have at least two segments per cell.