DeleteDamaged Custom Task

This custom task deletes failed particles and/or removes unneeded particles after a specified time.

Introduction

The main use of a DeleteDamage custom task is to delete particles from a simulation after then undergo decohesion. This function is only useful for softening materials. Some simulations work better if failure particles are removed. This tasks works best when failure particles are confined to small regions of the object.

A second use of this task is to delete particles after a certain time. This function work best for rigid particles and provides one way to create transient boundary conditions in a problem (i.e., boundary conditions that disappear after a while).

Task Scheduling

In scripted files, a DeleteDamage is scheduled with the following block:

CustomTask DeleteDamaged
Parameter material,(matID)
Parameter matname,(matname)
Parameter store_x,(xloc)
Parameter store_y,(yloc)
Parameter store_z,(zloc)
Parameter minCOD,(cod)
Parameter direction,(dir)
Parameter deleteTime,(time)

In XML files, this task is created using a <Schedule> element, which must be within the single <CustomTasks> block:

<Schedule name='DeleteDamaged'>
   <Parameter name='material'>(matID)</Parameter>
   <Parameter name='matname'>(matname)</Parameter>
   <Parameter name='store_x'>(xloc)</Parameter>
   <Parameter name='store_y'>(yloc)</Parameter>
   <Parameter name='store_z'>(zloc)</Parameter>
   <Parameter name='minCOD'>(cod)</Parameter>
   <Parameter name='direction'>(dir)</Parameter>
   <Parameter name='deleteTime'>(time)</Parameter>
</Schedule>

The parameters are

• (matID) or (matname) - specifies material type by number or name.
• (xloc),(yloc),(zloc) - deleted particles are moved to this location on the background grid. This location must be empty such that particles will not interact with active particles. Enter in length units.
• (minCOD) - normally particles are deleted right after they fail. Alternatively, you can require the implied crack in the particle to open further before deletion by entering a minimum crack opening displacement (COD) (in length units)
• (dir) - by default, the (minCOD) refers to magnitude of the crack opening displacement. Alternatively, the minimum can apply to one component of the COD:
  • 1 - use magnitude of the COD (the default and option used if you enter an invalid dir)
  • 2 - use component of COD normal to the crack plane
  • 3 - use component of COD tangential to the crack plane
  • 4 - use xy shear slippage (same as 3 in 2D simulations)
  • 5 - use xz shear slippage (only nonzero in 3D simulations)
• (time) - if this parameter is set, particles of the specified material type will all be deleted when time reaches the entered (time) in alt time units.

Task Action

Each time step loops over all particles of the material type specified for the tasks. If (time) was entered and current time has reached that time, the particle is deleted. Otherwise, the particle is checked to see if it has failed by decohesion. If it has, it is deleted, but if (minCOD) (and optionally (dir)) where entered, the particle is deleted only if the crack opening displacement has passed the entered minimum.

Notes

• A single DeleteDamage task applies to one material types. A simulation can have multiple DeleteDamage tasks if you need particle deleting for more than one material type.
• Deleting after decohesion only applies to for softening materials. Deleteing after a specified time can be used for any material types.
• If (minCOD) is less the the material COD at failure, the particle will be deleted right after failure. To delay failure until after some post-decohesion deformation, set (minCOD) to be large than the material's COD at failure.