Difference between revisions of "DeleteDamaged Custom Task"
Line 3: | Line 3: | ||
== Introduction == | == Introduction == | ||
The main use of a <tt>DeleteDamage</tt> 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. | The main use of a <tt>DeleteDamage</tt> custom task is to delete particles from a simulation after then undergo decohesion. This function is only useful for [[Material_Models#Softening_Materials|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 | A second use of this task is to delete particles after a certain time. This function work best for [[Material_Models#Rigid_Materials|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 == | == Task Scheduling == |
Revision as of 16:33, 1 January 2021
A custom task to delete failed particles or to remove 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 for particles to be deleted by number or name.
- (xloc),(yloc),(zloc) - storage.
- (minCOD) -
- (dir) -
- (time) -