DeleteDamaged Custom Task - Revision history

Nairnj: /* Notes */

2021-07-22T20:10:34Z

Notes

← Older revision		Revision as of 20:10, 22 July 2021
Line 53:		Line 53:
	== Notes ==		== Notes ==

			* Deleted particles are moved into the [[Material Point Reservoir]].
	* A single <tt>DeleteDamage</tt> task applies to one material type. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle deletions for more than one material type.		* A single <tt>DeleteDamage</tt> task applies to one material type. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle deletions for more than one material type.
	* Deleting after decohesion only works for [[Material_Models#Softening_Materials\|softening materials]]. Deleting after a specified time can be used for any material type.		* Deleting after decohesion only works for [[Material_Models#Softening_Materials\|softening materials]]. Deleting after a specified time can be used for any material type.
	* If <tt>(minCOD)</tt> is less the the material COD at failure, the particle will be deleted right after failure (and not before). To delay failure until after some post-decohesion deformation, set <tt>(minCOD)</tt> to be larger than the material's COD at failure.		* If <tt>(minCOD)</tt> is less the the material COD at failure, the particle will be deleted right after failure (and not before). To delay failure until after some post-decohesion deformation, set <tt>(minCOD)</tt> to be larger than the material's COD at failure.

Nairnj: /* Notes */

2021-01-02T01:50:41Z

Notes

← Older revision		Revision as of 01:50, 2 January 2021
Line 53:		Line 53:
	== Notes ==		== Notes ==

	* A single <tt>DeleteDamage</tt> task applies to one material type. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle ~~deleting~~ for more than one material type.		* A single <tt>DeleteDamage</tt> task applies to one material type. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle deletions for more than one material type.
	* Deleting after decohesion only ~~applies to~~ for [[Material_Models#Softening_Materials\|softening materials]]. ~~Deleteing~~ after a specified time can be used for any material ~~types~~.		* Deleting after decohesion only works for [[Material_Models#Softening_Materials\|softening materials]]. Deleting after a specified time can be used for any material type.
	* If <tt>(minCOD)</tt> 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 <tt>(minCOD)</tt> to be ~~large~~ than the material's COD at failure.		* If <tt>(minCOD)</tt> is less the the material COD at failure, the particle will be deleted right after failure (and not before). To delay failure until after some post-decohesion deformation, set <tt>(minCOD)</tt> to be larger than the material's COD at failure.

Nairnj: /* Notes */

2021-01-02T01:49:30Z

Notes

← Older revision		Revision as of 01:49, 2 January 2021
Line 53:		Line 53:
	== Notes ==		== Notes ==

	* A single <tt>DeleteDamage</tt> task applies to one material ~~types~~. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle deleting for more than one material type.		* A single <tt>DeleteDamage</tt> task applies to one material type. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle deleting for more than one material type.
	* Deleting after decohesion only applies to for [[Material_Models#Softening_Materials\|softening materials]]. Deleteing after a specified time can be used for any material types.		* Deleting after decohesion only applies to for [[Material_Models#Softening_Materials\|softening materials]]. Deleteing after a specified time can be used for any material types.
	* If <tt>(minCOD)</tt> 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 <tt>(minCOD)</tt> to be large than the material's COD at failure.		* If <tt>(minCOD)</tt> 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 <tt>(minCOD)</tt> to be large than the material's COD at failure.

Nairnj: /* Task Action */

2021-01-02T01:48:59Z

Task Action

← Older revision		Revision as of 01:48, 2 January 2021
Line 49:		Line 49:
	=== Task Action ===		=== Task Action ===

	Each time step loops over all particles of the material type specified for the ~~tasks~~. If <tt>(time)</tt> 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 <tt>(minCOD)</tt> (and optionally <tt>(dir)</tt>) where entered, the particle is deleted only if the crack opening displacement has passed the entered minimum.		Each time step loops over all particles of the material type specified for the task. If <tt>(time)</tt> 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 <tt>(minCOD)</tt> (and optionally <tt>(dir)</tt>) where entered, the particle is deleted only if the crack opening displacement has passed the entered minimum.

	== Notes ==		== Notes ==

Nairnj: /* Task Scheduling */

2021-01-02T01:47:52Z

Task Scheduling

← Older revision		Revision as of 01:47, 2 January 2021
Line 39:		Line 39:
	* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].		* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].
	* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])		* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])
	* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the COD. Alternatively, the minimum can apply to one component of the COD:		* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the COD. Alternatively, the minimum can apply to one component of the COD selected by entered integer
	** 1 - use magnitude of the COD (the default and option used if you enter an invalid <tt>dir</tt>)		*# = use magnitude of the COD (the default and option used if you enter an invalid <tt>dir</tt>)
	** 2 - use component of COD normal to the crack plane		*# = use component of COD normal to the crack plane
	** 3 - use component of COD tangential to the crack plane		*# = use component of COD tangential to the crack plane
	** 4 - use xy shear slippage (same as 3 in 2D simulations)		*# = use xy shear slippage (same as 3 in 2D simulations)
	** 5 - use xz shear slippage (only nonzero in 3D simulations)		*# = use xz shear slippage (only nonzero in 3D simulations)
	* <tt>(time)</tt> - if this parameter is set, particles of the specified material type will all be deleted when time reaches the entered <tt>(time)</tt> in [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]].		* <tt>(time)</tt> - if this parameter is set, particles of the specified material type will all be deleted when time reaches the entered <tt>(time)</tt> in [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]].

Nairnj: /* Task Scheduling */

2021-01-02T01:46:34Z

Task Scheduling

← Older revision		Revision as of 01:46, 2 January 2021
Line 39:		Line 39:
	* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].		* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].
	* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])		* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])
	* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the ~~crack opening displacement (~~COD). Alternatively, the minimum can apply to one component of the COD:		* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the COD. 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 <tt>dir</tt>)		** 1 - use magnitude of the COD (the default and option used if you enter an invalid <tt>dir</tt>)
	** 2 - use component of COD normal to the crack plane		** 2 - use component of COD normal to the crack plane

Nairnj: /* Task Scheduling */

2021-01-02T01:46:04Z

Task Scheduling

← Older revision		Revision as of 01:46, 2 January 2021
Line 39:		Line 39:
	* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].		* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].
	* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])		* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])
	* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the crack opening displacement. Alternatively, the minimum can apply to one component of the COD:		* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the crack opening displacement (COD). 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 <tt>dir</tt>)		** 1 - use magnitude of the COD (the default and option used if you enter an invalid <tt>dir</tt>)
	** 2 - use component of COD normal to the crack plane		** 2 - use component of COD normal to the crack plane

Nairnj: /* Task Scheduling */

2021-01-02T01:45:21Z

Task Scheduling

← Older revision		Revision as of 01:45, 2 January 2021
Line 38:		Line 38:
	* <tt>(matID)</tt> or <tt>(matname)</tt> - specifies material type [[Material Command Block#Referencing Materials in XML Files\|by number or name]].		* <tt>(matID)</tt> or <tt>(matname)</tt> - specifies material type [[Material Command Block#Referencing Materials in XML Files\|by number or name]].
	* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].		* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].
	* <tt>(minCOD)</tt> - 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) ([[ConsistentUnits Command#Legacy and Consistent Units\|in length units]])		* <tt>(minCOD)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]])
	* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the crack opening displacement. Alternatively, the minimum can apply to one component of the COD:		* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> 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 <tt>dir</tt>)		** 1 - use magnitude of the COD (the default and option used if you enter an invalid <tt>dir</tt>)

Nairnj at 01:42, 2 January 2021

2021-01-02T01:42:08Z

← Older revision		Revision as of 01:42, 2 January 2021
Line 1:		Line 1:
	A [[MPM Input Files#Custom Tasks\|custom task]] ~~to delete~~ failed particles or ~~to remove~~ unneeded particles after a specified time.		This [[MPM Input Files#Custom Tasks\|custom task]] deletes failed particles and/or removes unneeded particles after a specified time.
	__TOC__		__TOC__
	== Introduction ==		== Introduction ==

Nairnj at 00:10, 2 January 2021

2021-01-02T00:10:32Z

← Older revision		Revision as of 00:10, 2 January 2021
Line 37:		Line 37:

	* <tt>(matID)</tt> or <tt>(matname)</tt> - specifies material type [[Material Command Block#Referencing Materials in XML Files\|by number or name]].		* <tt>(matID)</tt> or <tt>(matname)</tt> - specifies material type [[Material Command Block#Referencing Materials in XML Files\|by number or name]].
	* <tt>(xloc),(yloc),(zloc)</tt> - 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.		* <tt>(xloc),(yloc),(zloc)</tt> - 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 [[ConsistentUnits Command#Legacy and Consistent Units\|length units]].
	* <tt>(minCOD)</tt> - normally particles are deleted right after they fail. Alternatively, you can require the implied crack in the particle to open further before deletion by ~~enter that~~ crack opening displacement (~~cod~~) in		* <tt>(minCOD)</tt> - 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) ([[ConsistentUnits Command#Legacy and Consistent Units\|in length units]])
	* <tt>(dir)</tt> -		* <tt>(dir)</tt> - by default, the <tt>(minCOD)</tt> refers to magnitude of the crack opening displacement. Alternatively, the minimum can apply to one component of the COD:
	* <tt>(time)</tt> -		** 1 - use magnitude of the COD (the default and option used if you enter an invalid <tt>dir</tt>)
			** 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)
			* <tt>(time)</tt> - if this parameter is set, particles of the specified material type will all be deleted when time reaches the entered <tt>(time)</tt> in [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]].

	=== Task Action ===		=== Task Action ===

			Each time step loops over all particles of the material type specified for the tasks. If <tt>(time)</tt> 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 <tt>(minCOD)</tt> (and optionally <tt>(dir)</tt>) where entered, the particle is deleted only if the crack opening displacement has passed the entered minimum.

			== Notes ==

			* A single <tt>DeleteDamage</tt> task applies to one material types. A simulation can have multiple <tt>DeleteDamage</tt> tasks if you need particle deleting for more than one material type.
			* Deleting after decohesion only applies to for [[Material_Models#Softening_Materials\|softening materials]]. Deleteing after a specified time can be used for any material types.
			* If <tt>(minCOD)</tt> 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 <tt>(minCOD)</tt> to be large than the material's COD at failure.