ReverseLoad Custom Task - Revision history

Nairnj: /* Task Action */

2023-01-31T01:09:26Z

Task Action

← Older revision		Revision as of 01:09, 31 January 2023
Line 72:		Line 72:

	* <tt>reverse</tt> (or 0): Reverses all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) and reverses direction of all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]). This style will unload until the load or traction (on loaded particles) or displacement (on moving rigid particles) returns to zero at which point the analysis will stop (the analysis, however, may stop sooner if the [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached before loading returns to zero).		* <tt>reverse</tt> (or 0): Reverses all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) and reverses direction of all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]). This style will unload until the load or traction (on loaded particles) or displacement (on moving rigid particles) returns to zero at which point the analysis will stop (the analysis, however, may stop sooner if the [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached before loading returns to zero).
	* <tt>hold</tt> (or 1): Stops all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) at the current values, sets all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]) to zero velocity, and sets all grid-based velocity conditions to zero velocity. The analysis continues until [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached.		* <tt>hold</tt> (or 1): Stops all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) at the current values, sets all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]) to zero velocity, and sets all [[Grid-Based Boundary Conditions\|grid-based velocity conditions]] to zero velocity. The analysis continues until [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached.
	* <tt>continue</tt> (or 2): All loads, tractions, and rigid particles continue unchanged. Only the crack propagation stops. Because this action only stops crack propagation, it is meaningless when the task is triggered on a [[MPM Global Archiving Options\|global archive quantity]], and is therefore not allowed for such tasks.		* <tt>continue</tt> (or 2): All loads, tractions, and rigid particles continue unchanged. Only the crack propagation stops. Because this action only stops crack propagation, it is meaningless when the task is triggered on a [[MPM Global Archiving Options\|global archive quantity]], and is therefore not allowed for such tasks.
	* <tt>abort</tt> (or 3): The analysis terminates.		* <tt>abort</tt> (or 3): The analysis terminates.

Nairnj: /* Task Action */

2023-01-31T01:08:37Z

Task Action

← Older revision		Revision as of 01:08, 31 January 2023
Line 72:		Line 72:

	* <tt>reverse</tt> (or 0): Reverses all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) and reverses direction of all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]). This style will unload until the load or traction (on loaded particles) or displacement (on moving rigid particles) returns to zero at which point the analysis will stop (the analysis, however, may stop sooner if the [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached before loading returns to zero).		* <tt>reverse</tt> (or 0): Reverses all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) and reverses direction of all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]). This style will unload until the load or traction (on loaded particles) or displacement (on moving rigid particles) returns to zero at which point the analysis will stop (the analysis, however, may stop sooner if the [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached before loading returns to zero).
	* <tt>hold</tt> (or 1): Stops all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) at the current values ~~and~~ sets all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]) to zero velocity. The analysis continues until [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached.		* <tt>hold</tt> (or 1): Stops all linearly increasing [[Setting Forces and Fluxes\|loads or tractions]] (see [[Boundary Condition Styles\|"linear" style]] in particle loads) at the current values, sets all [[Rigid Material\|boundary-condition rigid particles]] moving at constant velocity (''i.e''., they have [[Rigid Material#Material Properties\|set direction 1 to 7]] and do not use any [[Rigid Material#Material Properties\|setting functions]]) to zero velocity, and sets all grid-based velocity conditions to zero velocity. The analysis continues until [[MPM Methods and Simulation Timing#Input Commands\|maximum time]] is reached.
	* <tt>continue</tt> (or 2): All loads, tractions, and rigid particles continue unchanged. Only the crack propagation stops. Because this action only stops crack propagation, it is meaningless when the task is triggered on a [[MPM Global Archiving Options\|global archive quantity]], and is therefore not allowed for such tasks.		* <tt>continue</tt> (or 2): All loads, tractions, and rigid particles continue unchanged. Only the crack propagation stops. Because this action only stops crack propagation, it is meaningless when the task is triggered on a [[MPM Global Archiving Options\|global archive quantity]], and is therefore not allowed for such tasks.
	* <tt>abort</tt> (or 3): The analysis terminates.		* <tt>abort</tt> (or 3): The analysis terminates.

Nairnj: /* Task Scheduling */

2023-01-31T01:07:29Z

Task Scheduling

← Older revision		Revision as of 01:07, 31 January 2023
Line 28:		Line 28:
	Parameter style,(style)		Parameter style,(style)
	Parameter hold,(holdTIme)		Parameter hold,(holdTIme)
	Parameter ~~maxValue~~,(minValue)		Parameter minValue,(minValue)

	In <tt>XML</tt> files, these two task options are scheduled using <tt><Schedule></tt> elements, which must be within the single <tt><CustomTasks></tt> block:		In <tt>XML</tt> files, these two task options are scheduled using <tt><Schedule></tt> elements, which must be within the single <tt><CustomTasks></tt> block:

Nairnj: /* Task Scheduling */

2023-01-31T01:07:07Z

Task Scheduling

← Older revision		Revision as of 01:07, 31 January 2023
Line 64:		Line 64:
	But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:		But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:

	# If <tt>minValue:>0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt> (pick a value to avoid any intial noise). It then tracks maximum value reached and this task is triggered when the global quantity ever drops to a fraction <tt>(value)</tt> of the simulation peak value (<tt>(value)</tt> must a number between 0 to 1).		# If <tt>minValue>0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt> (pick a value to avoid any intial noise). It then tracks maximum value reached and this task is triggered when the global quantity ever drops to a fraction <tt>(value)</tt> of the simulation peak value (<tt>(value)</tt> must a number between 0 to 1).
	# If <tt>minValue:<0</tt> the simulation runs until the selected global quantity is more negative than <tt>minValue</tt> (pick a value to avoid any initial noise). It then tracks maximum negative value reached and this task is triggered when the global quantity ever increases to a fraction <tt>(value)</tt> of the simulation negative peak value (<tt>(value)</tt> must a number between 0 to 1).		# If <tt>minValue<0</tt> the simulation runs until the selected global quantity is more negative than <tt>minValue</tt> (pick a value to avoid any initial noise). It then tracks maximum negative value reached and this task is triggered when the global quantity ever increases to a fraction <tt>(value)</tt> of the simulation negative peak value (<tt>(value)</tt> must a number between 0 to 1).

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

Nairnj: /* Task Scheduling */

2023-01-31T01:06:47Z

Task Scheduling

← Older revision		Revision as of 01:06, 31 January 2023
Line 64:		Line 64:
	But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:		But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:

	# If <tt>minValue:>0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt>. In then tracks maximum value reached and the ~~tasks~~ is ~~trigger if~~ the global quantity ever ~~drops~~ to a fraction <tt>(value)</tt> of the simulation peak value (a number ~~from~~ 0 to 1).		# If <tt>minValue:>0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt> (pick a value to avoid any intial noise). It then tracks maximum value reached and this task is triggered when the global quantity ever drops to a fraction <tt>(value)</tt> of the simulation peak value (<tt>(value)</tt> must a number between 0 to 1).
			# If <tt>minValue:<0</tt> the simulation runs until the selected global quantity is more negative than <tt>minValue</tt> (pick a value to avoid any initial noise). It then tracks maximum negative value reached and this task is triggered when the global quantity ever increases to a fraction <tt>(value)</tt> of the simulation negative peak value (<tt>(value)</tt> must a number between 0 to 1).

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

Nairnj: /* Task Scheduling */

2023-01-31T01:01:10Z

Task Scheduling

← Older revision		Revision as of 01:01, 31 January 2023
Line 64:		Line 64:
	But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:		But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:

	# If <tt>minValue:gt;0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt>. In then tracks maximum value reached and the tasks is trigger if the global quantity ever drops to a fraction <tt>(value)</tt> of the simulation peak value (a number from 0 to 1).		# If <tt>minValue:>0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt>. In then tracks maximum value reached and the tasks is trigger if the global quantity ever drops to a fraction <tt>(value)</tt> of the simulation peak value (a number from 0 to 1).

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

Nairnj: /* Task Scheduling */

2023-01-31T01:00:46Z

Task Scheduling

← Older revision		Revision as of 01:00, 31 January 2023
Line 28:		Line 28:
	Parameter style,(style)		Parameter style,(style)
	Parameter hold,(holdTIme)		Parameter hold,(holdTIme)
			Parameter maxValue,(minValue)

	In <tt>XML</tt> files, these two task options are scheduled using <tt><Schedule></tt> elements, which must be within the single <tt><CustomTasks></tt> block:		In <tt>XML</tt> files, these two task options are scheduled using <tt><Schedule></tt> elements, which must be within the single <tt><CustomTasks></tt> block:
Line 45:		Line 46:
	<Parameter name='style'>(styleNumber)</Parameter>		<Parameter name='style'>(styleNumber)</Parameter>
	<Parameter name='hold'>(holdTime)</Parameter>		<Parameter name='hold'>(holdTime)</Parameter>
			<Parameter name='minValue'>(minValue)</Parameter>
	</Schedule>		</Schedule>

Line 59:		Line 61:
	* <tt>(matOrBCNum)</tt> - in <tt>XML</tt> files, the specific material or boundary condition ID must be specified by number (it cannot use a [[Material Command Block\|material ID]]).		* <tt>(matOrBCNum)</tt> - in <tt>XML</tt> files, the specific material or boundary condition ID must be specified by number (it cannot use a [[Material Command Block\|material ID]]).
	* <tt>(value)</tt> - specifies the critical value for the [[MPM Global Archiving Options\|global archive quantity]] to trigger the task action. If the number is positive, the action is triggered when the quantity reaches the value; if it is negative, the action is triggered when the quantity becomes more negative than the value.		* <tt>(value)</tt> - specifies the critical value for the [[MPM Global Archiving Options\|global archive quantity]] to trigger the task action. If the number is positive, the action is triggered when the quantity reaches the value; if it is negative, the action is triggered when the quantity becomes more negative than the value.

			But, if the option <tt>minValue</tt> is provided the tasks converts to be triggered on passing a peak value as follows:

			# If <tt>minValue:gt;0</tt> the simulation runs until the selected global quantity exceeds <tt>minValue</tt>. In then tracks maximum value reached and the tasks is trigger if the global quantity ever drops to a fraction <tt>(value)</tt> of the simulation peak value (a number from 0 to 1).

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

Nairnj: /* Introduction */

2023-01-31T00:53:20Z

Introduction

← Older revision		Revision as of 00:53, 31 January 2023
Line 7:		Line 7:
	# Crack length monitoring: Once any crack or a specified crack reaches a specified crack length or debonded crack length, all [[Crack Propagation Commands\|crack propagation]] stops and the task's action is triggered		# Crack length monitoring: Once any crack or a specified crack reaches a specified crack length or debonded crack length, all [[Crack Propagation Commands\|crack propagation]] stops and the task's action is triggered
	# Global quantity monitoring: Once the specified global quantity passes a critical value, the task's action is triggered.		# Global quantity monitoring: Once the specified global quantity passes a critical value, the task's action is triggered.
			# Global quantity peak monitoring: Once the specified global quantity passes a critical value and then decreases to an input fraction of the peak, the task's action is triggered.

	The possible task actions are to reverse various boundary conditions, hold at current boundary conditions, stop the analysis, or continue (with no change except crack propagation stops).		The possible task actions are to reverse various boundary conditions, hold at current boundary conditions, stop the analysis, or continue (with no change except crack propagation stops).

Nairnj: /* Task Scheduling */

2021-01-25T19:00:05Z

Task Scheduling

← Older revision		Revision as of 19:00, 25 January 2021
Line 57:		Line 57:
	* <tt>(matOrBCID)</tt> - if the desired [[MPM Global Archiving Options\|global archive quantity]] is defined for a specific material or for a specific boundary condition, you must enter that [[Material Command Block\|material ID]] or [[Setting Velocity and Transport Values#Boundary Condition ID\|boundary condition ID]] in this parameter (otherwise the entered quantity will not match the [[MPM Global Archiving Options\|global archive quantity]]).		* <tt>(matOrBCID)</tt> - if the desired [[MPM Global Archiving Options\|global archive quantity]] is defined for a specific material or for a specific boundary condition, you must enter that [[Material Command Block\|material ID]] or [[Setting Velocity and Transport Values#Boundary Condition ID\|boundary condition ID]] in this parameter (otherwise the entered quantity will not match the [[MPM Global Archiving Options\|global archive quantity]]).
	* <tt>(matOrBCNum)</tt> - in <tt>XML</tt> files, the specific material or boundary condition ID must be specified by number (it cannot use a [[Material Command Block\|material ID]]).		* <tt>(matOrBCNum)</tt> - in <tt>XML</tt> files, the specific material or boundary condition ID must be specified by number (it cannot use a [[Material Command Block\|material ID]]).
	* <tt>(value)</tt> - specifies the critical value for the [[MPM Global Archiving Options\|global archive quantity]] to trigger the task action. If the number is positive, the action is triggered when the quantity reaches the value; if it is negative, the action is triggered when the quantity ~~become~~ more negative than the value.		* <tt>(value)</tt> - specifies the critical value for the [[MPM Global Archiving Options\|global archive quantity]] to trigger the task action. If the number is positive, the action is triggered when the quantity reaches the value; if it is negative, the action is triggered when the quantity becomes more negative than the value.

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

Nairnj: /* Task Scheduling */

2021-01-03T19:51:59Z

Task Scheduling

← Older revision		Revision as of 19:51, 3 January 2021
Line 49:		Line 49:

	* <tt>(length)</tt> - specifies the maximum crack length (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). Once this length is reached, all crack propagation will stop.		* <tt>(length)</tt> - specifies the maximum crack length (in [[ConsistentUnits Command#Legacy and Consistent Units\|length units]]). Once this length is reached, all crack propagation will stop.
	* <tt>(useDebonded)</tt> - if zero (which is the default), this task is triggered by total crack length. If set to one (~~and~~ any non-zero value), this task is triggered by debonded crack length, which is total length minus that part of the crack with remaining cohesive zones (''i.e.'', non-debonded [[Traction Laws]]).		* <tt>(useDebonded)</tt> - if zero (which is the default), this task is triggered by total crack length. If set to one (or any non-zero value), this task is triggered by debonded crack length, which is total length minus that part of the crack with remaining cohesive zones (''i.e.'', non-debonded [[Traction Laws]]).
	* <tt>(number)</tt> - gives the crack number to watch. When that crack reaches the specified maximum length, the task will take effect. Alternatively, <tt>(number)</tt> can be zero which causes the task to take effect when any crack reaches the specified maximum length. The default value is 0 or to watch all cracks.		* <tt>(number)</tt> - gives the crack number to watch. When that crack reaches the specified maximum length, the task will take effect. Alternatively, <tt>(number)</tt> can be zero which causes the task to take effect when any crack reaches the specified maximum length. The default value is 0 or to watch all cracks.