ReverseLoad Custom Task

A custom task to alter calculations based on crack propagation results.

Introduction

A ReverseLoad custom task can either monitor crack lengths or monitor any current global archive quantity and respond as follows:

1. Crack length monitoring: Once any crack or a specified crack reaches a specified crack length or debonded crack length, all crack propagation stops and the task's action is triggered
2. Global quantity monitoring: Once the specified global quantity passes a critical value, the task's action is triggered.
3. 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).

Task Scheduling

In scripted files, a ReverseLoad custom tasks based on crack lengths or on a global archive quantity are scheduled with one of the two following blocks:

CustomTask ReverseLoad
Parameter maxLength,(length)
Parameter debondedLength,(useDebonded)
Parameter crackNumber,(number)
Parameter style,(style)
Parameter hold,(holdTIme)

CustomTask ReverseLoad
Parameter quantity,(quant)
Parameter material,(matOrBCID)
Parameter maxValue,(value)
Parameter style,(style)
Parameter hold,(holdTIme)
Parameter maxValue,(minValue)

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

<Schedule name='ReverseLoad'>
   <Parameter name='maxLength'>(length)</Parameter>
   <Parameter name='debondedLength'>(useDebonded)</Parameter>
   <Parameter name='crackNumber'>(number)</Parameter>
   <Parameter name='style'>(styleNumber)</Parameter>
   <Parameter name='hold'>(holdTime)</Parameter>
</Schedule>

<Schedule name='ReverseLoad'>
   <Parameter name='global (quant)'/>
   <Parameter name='mat'>(matOrBCNum)</Parameter>
   <Parameter name='maxValue'>(value)</Parameter>
   <Parameter name='style'>(styleNumber)</Parameter>
   <Parameter name='hold'>(holdTime)</Parameter>
   <Parameter name='minValue'>(minValue)</Parameter>
</Schedule>

When the task triggers on crack length, these two parameters determine its trigger point:

• (length) - specifies the maximum crack length (in length units). Once this length is reached, all crack propagation will stop.
• (useDebonded) - 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).
• (number) - gives the crack number to watch. When that crack reaches the specified maximum length, the task will take effect. Alternatively, (number) 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.

When the task triggers on a global archive quantity, these parameters determine its trigger point

• (quant) - gives the name of the global archive quantity to use a trigger. In XML files, the quantiy name must be embedded in the parameter name, such as 'global sxx'.
• (matOrBCID) - if the desired global archive quantity is defined for a specific material or for a specific boundary condition, you must enter that material ID or boundary condition ID in this parameter (otherwise the entered quantity will not match the global archive quantity).
• (matOrBCNum) - in XML files, the specific material or boundary condition ID must be specified by number (it cannot use a material ID).
• (value) - specifies the critical value for the 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 minValue is provided the tasks converts to be triggered on passing a peak value as follows:

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

Task Action

Once the specified crack length is reached (and all crack propagation stops) or the critical global archive quantity is reached, the task performs various actions specified by the (style) and (hold) parameters. Scripted files can enter text for the style, but XML files must use the (styleNumber):

• reverse (or 0): Reverses all linearly increasing loads or tractions (see "linear" style in particle loads) and reverses direction of all boundary-condition rigid particles moving at constant velocity (i.e., they have set direction 1 to 7 and do not use any 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 maximum time is reached before loading returns to zero).
• hold (or 1): Stops all linearly increasing loads or tractions (see "linear" style in particle loads) at the current values and sets all boundary-condition rigid particles moving at constant velocity (i.e., they have set direction 1 to 7 and do not use any setting functions) to zero velocity. The analysis continues until maximum time is reached.
• continue (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 global archive quantity, and is therefore not allowed for such tasks.
• abort (or 3): The analysis terminates.

The default (style) is to reverse loads, tractions, and particles to unload the specimen (as implied by the task name). Notice that reverse and hold affects only selected types of boundary conditions. The task has no affect on other types of boundary conditions.

If (holdTime) is set to a positive number, it gives a time (in alt time units) to hold at current conditions before applying the task's action. The (hold) parameter only applies when (style) is reverse or abort. The hold phase will only hold boundary conditions that can be reversed (see reverse optoins above). After the hold phase is done, the reverse style will unload to zero as described above and the abort style will stop the analysis. The default (holdTime) is zero (or no hold phase).