LoadControl Custom Task - Revision history

Nairnj: /* Start Up and Smoothing Settings */

2025-04-18T17:39:59Z

Start Up and Smoothing Settings

← Older revision		Revision as of 17:39, 18 April 2025
Line 120:		Line 120:
	(smoothA) = 1		(smoothA) = 1

	The <tt>(inittime)</tt> is negative to tell the load control to use the provided <math>A_t</math> value once it starts. The entered value defines the start up time as the time to reach about 3% strain. The <tt>(smoothA)=1</tt> is to use a fixed <math>A_t</math> value throughout the simulations. Using a fixed <math>A_t</math> is often a good way to choose PID gain factors. Once those ~~value of~~ found, however, the <tt>(smoothA)</tt> should be reduced to allow non-linear PID load control that tracks changes in stiffness expected for the non-linear [[Mooney Material]].		The <tt>(inittime)</tt> is negative to tell the load control to use the provided <math>A_t</math> value once it starts. The entered value defines the start up time as the time to reach about 3% strain. The <tt>(smoothA)=1</tt> is to use a fixed <math>A_t</math> value throughout the simulations. Using a fixed <math>A_t</math> is often a good way to choose PID gain factors. Once those values are found, however, the <tt>(smoothA)</tt> should be reduced to allow non-linear PID load control that tracks changes in stiffness expected for the non-linear [[Mooney Material]].

	==== Choose <math>K_p</math> ====		==== Choose <math>K_p</math> ====

Nairnj: /* Start Up and Smoothing Settings */

2025-04-18T17:39:12Z

Start Up and Smoothing Settings

← Older revision		Revision as of 17:39, 18 April 2025
Line 115:		Line 115:
	to pull in the negative x direction. The load rate was estimated assuming a linear elastic material. For the nonlinear [[Mooney Material]], which softens in tension, the final strain based on this loading rate and time will exceed the 30% strain used for start up calculations. Other startup parameters used were		to pull in the negative x direction. The load rate was estimated assuming a linear elastic material. For the nonlinear [[Mooney Material]], which softens in tension, the final strain based on this loading rate and time will exceed the 30% strain used for start up calculations. Other startup parameters used were

	[[MPM Global Archiving Options\|Global archiving time]] set to have 500 samples over the ~~estimate~~ loading time		[[MPM Global Archiving Options\|Global archiving time]] set to have 500 samples over the estimated loading time
	(minVelocity) = 20% of (initvelocity)		(minVelocity) = 20% of (initvelocity)
	(inittime) = -(10% of estimated loading time)		(inittime) = -(10% of estimated loading time)

Nairnj: /* Choosing Smoothing Parameters */

2025-04-18T17:35:50Z

Choosing Smoothing Parameters

← Older revision		Revision as of 17:35, 18 April 2025
Line 83:		Line 83:

	# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).		# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).
	# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task into a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.		# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task into a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes due to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.
	# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).		# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).

Nairnj: /* Choosing Smoothing Parameters */

2025-04-18T17:35:16Z

Choosing Smoothing Parameters

← Older revision		Revision as of 17:35, 18 April 2025
Line 83:		Line 83:

	# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).		# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).
	# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task in a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.		# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task into a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.
	# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).		# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).

Nairnj: /* Choosing Start Up Conditions */

2025-04-18T17:32:11Z

Choosing Start Up Conditions

← Older revision		Revision as of 17:32, 18 April 2025
Line 64:		Line 64:
	=== Choosing Start Up Conditions ===		=== Choosing Start Up Conditions ===

	To get started, a load control task needs an initial velocity and an initial stiffness <math>A_t</math> (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a <tt>(inittime)</tt>, which is a time over which the rigid particles move at constant <tt>(initvelocity)</tt> without imposing any control. Once the start up time has passed, the load control begins using an initial <math>A_t</math> that can be determined one of two methods:		To get started, a load control task needs an initial velocity and an initial stiffness <math>A_t</math> (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a <tt>(inittime)</tt>, which is a time over which the rigid particles move at constant <tt>(initvelocity)</tt> without imposing any control. Once the start up time has passed, the load control begins using an initial <math>A_t</math> that can be determined by one of two methods:

	# If you do not want to (or not able to) calculate an initial <math>A_t</math>, specify a positive <tt>(inittime)</tt>. The initial <math>A_t</math> will be found by least squares slope for force <i>vs.</i> displacement up to <tt>(inittime)</tt>. Any provided <tt>(initAt)</tt> will be ignored. Note that this method cannot be used if <tt>(initvelocity)</tt> is zero.		# If you do not want to (or not able to) calculate an initial <math>A_t</math>, specify a positive <tt>(inittime)</tt>. The initial <math>A_t</math> will be found by least squares slope for force <i>vs.</i> displacement up to <tt>(inittime)</tt>. Any provided <tt>(initAt)</tt> will be ignored. Note that this method cannot be used if <tt>(initvelocity)</tt> is zero.

Nairnj: /* Choosing Smoothing Parameters */

2024-08-22T21:55:21Z

Choosing Smoothing Parameters

← Older revision		Revision as of 21:55, 22 August 2024
Line 83:		Line 83:

	# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).		# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).
	# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task in a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such ~~problem~~ require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.		# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task in a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.
	# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).		# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).

Nairnj: /* Choosing Start Up Conditions */

2024-08-22T21:47:46Z

Choosing Start Up Conditions

← Older revision		Revision as of 21:47, 22 August 2024
Line 66:		Line 66:
	To get started, a load control task needs an initial velocity and an initial stiffness <math>A_t</math> (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a <tt>(inittime)</tt>, which is a time over which the rigid particles move at constant <tt>(initvelocity)</tt> without imposing any control. Once the start up time has passed, the load control begins using an initial <math>A_t</math> that can be determined one of two methods:		To get started, a load control task needs an initial velocity and an initial stiffness <math>A_t</math> (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a <tt>(inittime)</tt>, which is a time over which the rigid particles move at constant <tt>(initvelocity)</tt> without imposing any control. Once the start up time has passed, the load control begins using an initial <math>A_t</math> that can be determined one of two methods:

	# If you do not want to (or not able to) calculate an initial <math>A_t</math>, specify a positive <tt>(inittime)</tt>. The initial <math>A_t</math> will be found by least squares slope for force <i>vs.</i> displacement up to <tt>(inittime)</tt>. Any provided <tt>(initAt)</tt> will be ignored. Note that this ~~methgod~~ cannot be used if <tt>(initvelocity)</tt> is zero.		# If you do not want to (or not able to) calculate an initial <math>A_t</math>, specify a positive <tt>(inittime)</tt>. The initial <math>A_t</math> will be found by least squares slope for force <i>vs.</i> displacement up to <tt>(inittime)</tt>. Any provided <tt>(initAt)</tt> will be ignored. Note that this method cannot be used if <tt>(initvelocity)</tt> is zero.
	# Specified <math>A_t</math>: If you can calculate initial stiffness for the simulation, you can enter it in <tt>(initAt)</tt> parameter and then set <tt>(inittime)</tt> to minus the desired start up time. Once the time is passed, control will start with the provided <math>A_t</math>.		# Specified <math>A_t</math>: If you can calculate initial stiffness for the simulation, you can enter it in <tt>(initAt)</tt> parameter and then set <tt>(inittime)</tt> to minus the desired start up time. Once the time is passed, control will start with the provided <math>A_t</math>.

Nairnj: /* Specifying the Force */

2024-08-22T21:30:32Z

Specifying the Force

← Older revision		Revision as of 21:30, 22 August 2024
Line 22:		Line 22:
	Parameter material,(matID)		Parameter material,(matID)
	Parameter matname,(matname)		Parameter matname,(matname)
	Parameter ~~load~~,(loadfunction)		Parameter Load,(loadfunction)

	where		where

Nairnj: /* Specifying the Force */

2023-10-02T16:24:11Z

Specifying the Force

← Older revision		Revision as of 16:24, 2 October 2023
Line 14:		Line 14:
	# When using [[Rigid Material\|RigidBC]] particles, include reaction force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>reactionx</tt>, <tt>reactiony</tt>, or <tt>reactionz</tt>]] for the chosen <tt>direction</tt>.		# When using [[Rigid Material\|RigidBC]] particles, include reaction force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>reactionx</tt>, <tt>reactiony</tt>, or <tt>reactionz</tt>]] for the chosen <tt>direction</tt>.
	# When using [[Rigid Material\|RigidContact]] particles, include contact force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>contactx</tt>, <tt>contacty</tt>, or <tt>contactz</tt>]] for the chosen <tt>direction</tt>.		# When using [[Rigid Material\|RigidContact]] particles, include contact force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>contactx</tt>, <tt>contacty</tt>, or <tt>contactz</tt>]] for the chosen <tt>direction</tt>.
	# Set the [[MPM Global Archiving Options\|global archiving time]] to sampling rate for load control (the ideal sample rate will depend on the target load function and other ~~simulations~~ parameters).		# Set the [[MPM Global Archiving Options\|global archiving time]] to sampling rate for load control (the ideal sample rate will depend on the target load function and other simulation parameters).

	Start the custom task and define the following force defining parameters (note: parameters in this documentation assume using a scripted file; see [[#Task Scheduling\|below]] for how to enter them in <tt>XML</tt> input files):		Start the custom task and define the following force defining parameters (note: parameters in this documentation assume using a scripted file; see [[#Task Scheduling\|below]] for how to enter them in <tt>XML</tt> input files):

Nairnj: /* Choosing Start Up Conditions */

2023-07-19T23:04:08Z

Choosing Start Up Conditions

← Older revision		Revision as of 23:04, 19 July 2023
Line 66:		Line 66:
	To get started, a load control task needs an initial velocity and an initial stiffness <math>A_t</math> (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a <tt>(inittime)</tt>, which is a time over which the rigid particles move at constant <tt>(initvelocity)</tt> without imposing any control. Once the start up time has passed, the load control begins using an initial <math>A_t</math> that can be determined one of two methods:		To get started, a load control task needs an initial velocity and an initial stiffness <math>A_t</math> (which is required to calculate control error). Furthermore, reaction and contact forces in dynamic calculations take a while to settle into reasonable values (such as when loading at constant velocity). A load control task thus normally needs a <tt>(inittime)</tt>, which is a time over which the rigid particles move at constant <tt>(initvelocity)</tt> without imposing any control. Once the start up time has passed, the load control begins using an initial <math>A_t</math> that can be determined one of two methods:

	# If you do not want to (~~are~~ not able to) calculate an initial <math>A_t</math>, specify a positive <tt>(inittime)</tt>. The initial <math>A_t</math> will be found by least squares slope for force <i>vs.</i> displacement up to <tt>(inittime)</tt>. Any provided <tt>(initAt)</tt> will be ignored. Note that this methgod cannot be used if <tt>(initvelocity)</tt> is zero.		# If you do not want to (or not able to) calculate an initial <math>A_t</math>, specify a positive <tt>(inittime)</tt>. The initial <math>A_t</math> will be found by least squares slope for force <i>vs.</i> displacement up to <tt>(inittime)</tt>. Any provided <tt>(initAt)</tt> will be ignored. Note that this methgod cannot be used if <tt>(initvelocity)</tt> is zero.
	# Specified <math>A_t</math>: If you can calculate initial stiffness for the simulation, you can enter it in <tt>(initAt)</tt> parameter and then set <tt>(inittime)</tt> to minus the desired start up time. Once the time is passed, control will start with the provided <math>A_t</math>.		# Specified <math>A_t</math>: If you can calculate initial stiffness for the simulation, you can enter it in <tt>(initAt)</tt> parameter and then set <tt>(inittime)</tt> to minus the desired start up time. Once the time is passed, control will start with the provided <math>A_t</math>.

← Older revision		Revision as of 17:35, 18 April 2025
Line 83:		Line 83:

	# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).		# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).
	# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task into a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.		# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task into a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes due to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.
	# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).		# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).

← Older revision		Revision as of 17:35, 18 April 2025
Line 83:		Line 83:

	# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).		# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).
	# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task in a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.		# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task into a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.
	# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).		# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).

← Older revision		Revision as of 21:55, 22 August 2024
Line 83:		Line 83:

	# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).		# <tt>smoothF</tt> - smooth recorded [[MPM Global Archiving Options\|reaction or contact force]]. This smoothing is probably always required. If no input value is provided, the default value is 0.9. This smoothing is limited to the interval [0,1) (<i>i.e.</i>, 1 is not allowed).
	# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task in a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such ~~problem~~ require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.		# <tt>smoothA</tt> - if [[#Choosing Start Up Conditions\|dyanamic updates to <math>A_t</math>]] are noisy, the updates can be smoothed. This parameter can use the entire iterval [0,1]. A value of 1 means <math>A_t</math> will remain fixed at its initial value. Note that a fixed <math>A_t</math> turns this task in a linear PID control algorithm. That approach, however, may not work well for problems where stiffness changes do to effects such as plasticity, damage, or non-linear elasticity. Such problems require non-linear PID with evolving <math>A_t</math> otherwise control parameters based on linear PID may become unstable.
	# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).		# <tt>smoothErr</tt> - smooths the [[#Non-Linear PID Control\|<tt>e(t)</tt> calculation]]. The default value is zero. This smoothing is limited to the interval [0,1).

← Older revision		Revision as of 16:24, 2 October 2023
Line 14:		Line 14:
	# When using [[Rigid Material\|RigidBC]] particles, include reaction force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>reactionx</tt>, <tt>reactiony</tt>, or <tt>reactionz</tt>]] for the chosen <tt>direction</tt>.		# When using [[Rigid Material\|RigidBC]] particles, include reaction force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>reactionx</tt>, <tt>reactiony</tt>, or <tt>reactionz</tt>]] for the chosen <tt>direction</tt>.
	# When using [[Rigid Material\|RigidContact]] particles, include contact force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>contactx</tt>, <tt>contacty</tt>, or <tt>contactz</tt>]] for the chosen <tt>direction</tt>.		# When using [[Rigid Material\|RigidContact]] particles, include contact force for the defined rigid material in the global archive using [[MPM Global Archiving Options\|<tt>contactx</tt>, <tt>contacty</tt>, or <tt>contactz</tt>]] for the chosen <tt>direction</tt>.
	# Set the [[MPM Global Archiving Options\|global archiving time]] to sampling rate for load control (the ideal sample rate will depend on the target load function and other ~~simulations~~ parameters).		# Set the [[MPM Global Archiving Options\|global archiving time]] to sampling rate for load control (the ideal sample rate will depend on the target load function and other simulation parameters).

	Start the custom task and define the following force defining parameters (note: parameters in this documentation assume using a scripted file; see [[#Task Scheduling\|below]] for how to enter them in <tt>XML</tt> input files):		Start the custom task and define the following force defining parameters (note: parameters in this documentation assume using a scripted file; see [[#Task Scheduling\|below]] for how to enter them in <tt>XML</tt> input files):