Setting Velocity and Transport Values - Revision history

Nairnj: /* Other Transport Conditions */

2023-11-18T00:46:51Z

Other Transport Conditions

← Older revision		Revision as of 00:46, 18 November 2023
Line 139:		Line 139:
	Concentration (style),(value),(time),(phaseStyle)		Concentration (style),(value),(time),(phaseStyle)

	In <tt>XML</tt> files, the <tt><ConcBC</tt> adds a <tt>phase</tt> attribute:		In <tt>XML</tt> files, the <tt><ConcBC></tt> adds a <tt>phase</tt> attribute (which must be numeric):

	<ConcBC style='(style)' value='(value)' time='(time)' function='(function)' phase='(phaseStyle)'/>		<ConcBC style='(style)' value='(value)' time='(time)' function='(function)' phase='(phaseStyle)'/>
Line 145:		Line 145:
	where <tt>(phaseStyle)</tt> can be the following options:		where <tt>(phaseStyle)</tt> can be the following options:

	* <tt>fracture</tt> (phaseStyle=3): set to dimensionless value 0 to 1		* <tt>fracture</tt> (or phaseStyle=3): set to dimensionless value 0 to 1
	* <tt>battery</tt> (phaseStyle=4): set to dimensionless value 0 to 1		* <tt>battery</tt> (or phaseStyle=4): set to dimensionless value 0 to 1
	* <tt>conduction</tt> (phaseStyle=5): set to value in volts.		* <tt>conduction</tt> (or phaseStyle=5): set to value in volts.

	All other parameters are defined [[#Concentration or Poroelasticity Conditions\|above]]. To specify <tt>(phaseStyle)</tt> in scripted files, the <tt>(time)</tt> parameters is required. It can be set to default zero if not needed.		All other parameters are defined [[#Concentration or Poroelasticity Conditions\|above]]. To specify <tt>(phaseStyle)</tt> in scripted files, the <tt>(time)</tt> parameters is required. It can be set to default zero if not needed.

Nairnj: /* Other Transport Conditions */

2023-11-15T16:49:03Z

Other Transport Conditions

← Older revision		Revision as of 16:49, 15 November 2023
Line 145:		Line 145:
	where <tt>(phaseStyle)</tt> can be the following options:		where <tt>(phaseStyle)</tt> can be the following options:

	* <tt>fracture</tt> (~~or <tt>phase</tt> or~~ phaseStyle=3): set to dimensionless value 0 to 1		* <tt>fracture</tt> (phaseStyle=3): set to dimensionless value 0 to 1
	* <tt>battery</tt> (phaseStyle=4): set to dimensionless value 0 to 1		* <tt>battery</tt> (phaseStyle=4): set to dimensionless value 0 to 1
	* <tt>conduction</tt> (phaseStyle=5): set to value in volts.		* <tt>conduction</tt> (phaseStyle=5): set to value in volts.

Nairnj: /* Other Transport Conditions */

2023-11-15T16:48:35Z

Other Transport Conditions

← Older revision		Revision as of 16:48, 15 November 2023
Line 145:		Line 145:
	where <tt>(phaseStyle)</tt> can be the following options:		where <tt>(phaseStyle)</tt> can be the following options:

	* <tt>fracture</tt> (phaseStyle=3): set to dimensionless value 0 to 1		* <tt>fracture</tt> (or <tt>phase</tt> or phaseStyle=3): set to dimensionless value 0 to 1
	* <tt>battery</tt> (phaseStyle=4): set to dimensionless value 0 to 1		* <tt>battery</tt> (phaseStyle=4): set to dimensionless value 0 to 1
	* <tt>conduction</tt> (phaseStyle=5): set to value in volts.		* <tt>conduction</tt> (phaseStyle=5): set to value in volts.

Nairnj: /* Boundary Condition ID */

2023-08-12T16:31:34Z

Boundary Condition ID

← Older revision		Revision as of 16:31, 12 August 2023
Line 159:		Line 159:
	BoundaryID <(negnum)>		BoundaryID <(negnum)>

	where <tt>(negnum)</tt> is an integer value (less than zero) for the boundary condition ID. All supported boundary conditions will use this ID until it is changed by another <tt>BoundaryID</tt> command. If <tt>(negnum)</tt> is omitted the ID reverts to zero and boundary conditions will stop getting IDs. The number should be less than zero to avoid conflict with IDs for boundary conditions created by [[Rigid Material\|rigid material particles]]. The only boundary conditions that currently make use of an ID are [[#Velocity Conditions\|velocity boundary conditions]], [[#Moving Wall Velocity Conditions\|wall velocity boundary conditions]] and . In <tt>XML</tt> files, ~~velocity~~ boundary condition IDs are set with an attribute on the ~~[[#Velocity Command\|<tt><DisBC></tt>~~ command]].		where <tt>(negnum)</tt> is an integer value (less than zero) for the boundary condition ID. All supported boundary conditions will use this ID until it is changed by another <tt>BoundaryID</tt> command. If <tt>(negnum)</tt> is omitted the ID reverts to zero and boundary conditions will stop getting IDs. The number should be less than zero to avoid conflict with IDs for boundary conditions created by [[Rigid Material\|rigid material particles]]. The only boundary conditions that currently make use of an ID are [[#Velocity Conditions\|velocity boundary conditions]], [[#Moving Wall Velocity Conditions\|wall velocity boundary conditions]] and [[#Temperature Conditions\|temperature boundary conditions]]. In <tt>XML</tt> files, boundary condition IDs are set with an attribute on the appropriate boundary condition command.

	~~Boundary~~ conditions created by [[MPM Grid Generation#Symmetry Planes\|symmetry planes]] will automatically have IDs of -10, -11, -20, -21, -30, or -31, depending on the plane edge. Other boundary conditions should not use these IDs unless either there are no symmetry planes or you want the other boundary conditions lumped in with the symmetry plane boundary conditions.		Velocity boundary conditions created by [[MPM Grid Generation#Symmetry Planes\|symmetry planes]] will automatically have IDs of -10, -11, -20, -21, -30, or -31, depending on the plane edge. Other boundary conditions should not use these IDs unless either there are no symmetry planes or you want the other boundary conditions lumped in with the symmetry plane boundary conditions. Note that [[#Temperature Conditions\|temperature boundary conditions]] on symmetry plane will not get these boundary IDs; you have to assign them IDs using this command.

	~~Boundary~~ conditions created when [[ExtrapolateRigid Command\|extrapolating rigid material particles]] before setting the boundary ~~condition~~ will all automatically have ID of -40. When using the [[ExtrapolateRigid Command\|ExtrapolateRigid mode]], all boundary conditions created by [[Rigid Material\|rigid materials]] will have the same -40 boundary ID and the [[MPM Global Archiving Options\|archived reaction force]] will be the total force on all those particles. In this mode, it is not possible to archive reaction forces from individual [[Rigid Material\|rigid material]] types.		Velocity boundary conditions created when [[ExtrapolateRigid Command\|extrapolating rigid material particles]] before setting the boundary conditions will all automatically have ID of -40. When using the [[ExtrapolateRigid Command\|ExtrapolateRigid mode]], all boundary conditions created by [[Rigid Material\|rigid materials]] will have the same -40 boundary ID and the [[MPM Global Archiving Options\|archived reaction force]] will be the total force on all those particles. In this mode, it is not possible to archive reaction forces from individual [[Rigid Material\|rigid material]] types.

Nairnj: /* Temperature Conditions */

2023-08-12T16:24:05Z

Temperature Conditions

← Older revision		Revision as of 16:24, 12 August 2023
Line 107:		Line 107:
	* <tt>(style)</tt> specifies the [[Boundary Condition Styles\|style of the applied temperature]]. Each temperature depends on two parameters specified by arguments <tt>(value)</tt> and <tt>(time)</tt>. If either argument is not supplied, they are set to zero. The standard units are degrees K for <tt>(value)</tt> and [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]] for <tt>(time)</tt> (but the units may change depending on the [[Boundary Condition Styles\|<tt>(style)</tt> setting]]).		* <tt>(style)</tt> specifies the [[Boundary Condition Styles\|style of the applied temperature]]. Each temperature depends on two parameters specified by arguments <tt>(value)</tt> and <tt>(time)</tt>. If either argument is not supplied, they are set to zero. The standard units are degrees K for <tt>(value)</tt> and [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]] for <tt>(time)</tt> (but the units may change depending on the [[Boundary Condition Styles\|<tt>(style)</tt> setting]]).
	* <tt>(function)</tt> - if the <tt>(style)</tt> is <tt>function</tt> (or 6), this attribute in <tt>XML</tt> files specifies a [[User Defined Functions\|user defined function]]. In scripted files, the [[User Defined Functions\|user defined function]] should replace the <tt>(value)</tt> argument and must be entered as quoted text. The function should evaluate to the desired temperature in degrees K.		* <tt>(function)</tt> - if the <tt>(style)</tt> is <tt>function</tt> (or 6), this attribute in <tt>XML</tt> files specifies a [[User Defined Functions\|user defined function]]. In scripted files, the [[User Defined Functions\|user defined function]] should replace the <tt>(value)</tt> argument and must be entered as quoted text. The function should evaluate to the desired temperature in degrees K.
			*<tt>(id)</tt> - this attribute in <tt>XML</tt> files specifies an ID for the boundary condition. In scripted files, IDs are set using the [[#Boundary Condition ID\|BoundaryID command]].

	Thermal stresses are caused by temperature difference relative to the [[Thermal Calculations#Stress Free Temperature\|stress free temperature]]. If the stress free temperature has not been set, its default value is zero and thus temperature boundary conditions set the temperature difference. If the stress free temperature is set to a non-zero value, the temperature boundary conditions use the absolute temperature and the temperature difference is calculated by subtracting the stress free temperature.		Thermal stresses are caused by temperature difference relative to the [[Thermal Calculations#Stress Free Temperature\|stress free temperature]]. If the stress free temperature has not been set, its default value is zero and thus temperature boundary conditions set the temperature difference. If the stress free temperature is set to a non-zero value, the temperature boundary conditions use the absolute temperature and the temperature difference is calculated by subtracting the stress free temperature.

Nairnj: /* Temperature Conditions */

2023-08-12T16:23:01Z

Temperature Conditions

← Older revision		Revision as of 16:23, 12 August 2023
Line 101:		Line 101:
	In <tt>XML</tt> files, the command is:		In <tt>XML</tt> files, the command is:

	<TempBC style='(style)' value='(value)' time='(time)' function='(function)'/>		<TempBC style='(style)' value='(value)' time='(time)' function='(function)' id='(ID)'/>

	where		where

Nairnj: /* Boundary Condition ID */

2023-08-12T16:22:26Z

Boundary Condition ID

← Older revision		Revision as of 16:22, 12 August 2023
Line 158:		Line 158:
	BoundaryID <(negnum)>		BoundaryID <(negnum)>

	where <tt>(negnum)</tt> is an integer value (less than zero) for the boundary condition ID. All supported boundary conditions will use this ID until it is changed by another <tt>BoundaryID</tt> command. If <tt>(negnum)</tt> is omitted the ID reverts to zero. The number should be less than zero to avoid conflict with IDs for boundary conditions created by [[Rigid Material\|rigid material particles]]. The only boundary conditions that currently make use of an ID are [[#Velocity Conditions\|velocity boundary conditions]] ~~and~~ [[#Moving Wall Velocity Conditions\|wall velocity boundary conditions]]. In <tt>XML</tt> files, velocity boundary condition IDs are set with an attribute on the [[#Velocity Command\|<tt><DisBC></tt> command]].		where <tt>(negnum)</tt> is an integer value (less than zero) for the boundary condition ID. All supported boundary conditions will use this ID until it is changed by another <tt>BoundaryID</tt> command. If <tt>(negnum)</tt> is omitted the ID reverts to zero and boundary conditions will stop getting IDs. The number should be less than zero to avoid conflict with IDs for boundary conditions created by [[Rigid Material\|rigid material particles]]. The only boundary conditions that currently make use of an ID are [[#Velocity Conditions\|velocity boundary conditions]], [[#Moving Wall Velocity Conditions\|wall velocity boundary conditions]] and . In <tt>XML</tt> files, velocity boundary condition IDs are set with an attribute on the [[#Velocity Command\|<tt><DisBC></tt> command]].

	Boundary conditions created by [[MPM Grid Generation#Symmetry Planes\|symmetry planes]] will automatically have IDs of -10, -11, -20, -21, -30, or -31, depending on the plane edge. Other boundary conditions should not use these IDs unless either there are no symmetry planes or you want the other boundary conditions lumped in with the symmetry plane boundary conditions.		Boundary conditions created by [[MPM Grid Generation#Symmetry Planes\|symmetry planes]] will automatically have IDs of -10, -11, -20, -21, -30, or -31, depending on the plane edge. Other boundary conditions should not use these IDs unless either there are no symmetry planes or you want the other boundary conditions lumped in with the symmetry plane boundary conditions.

	Boundary conditions created when [[ExtrapolateRigid Command\|extrapolating rigid material particles]] before setting the boundary condition will all automatically have ID of -40. When using the [[ExtrapolateRigid Command\|ExtrapolateRigid mode]], all boundary conditions created by [[Rigid Material\|rigid materials]] will have the same -40 boundary ID and the [[MPM Global Archiving Options\|archived reaction force]] will be the total force on all those particles. In this mode, it is not possible to archive reaction forces from individual [[Rigid Material\|rigid material]] types.		Boundary conditions created when [[ExtrapolateRigid Command\|extrapolating rigid material particles]] before setting the boundary condition will all automatically have ID of -40. When using the [[ExtrapolateRigid Command\|ExtrapolateRigid mode]], all boundary conditions created by [[Rigid Material\|rigid materials]] will have the same -40 boundary ID and the [[MPM Global Archiving Options\|archived reaction force]] will be the total force on all those particles. In this mode, it is not possible to archive reaction forces from individual [[Rigid Material\|rigid material]] types.

Nairnj: /* Boundary Condition ID */

2023-08-12T16:21:17Z

Boundary Condition ID

← Older revision		Revision as of 16:21, 12 August 2023
Line 154:		Line 154:
	== Boundary Condition ID ==		== Boundary Condition ID ==

	The <tt>BoundaryID</tt> command (in scripted files only) sets an ID to assign to subsequent boundary conditions (velocity conditions only). The main reason to assign IDs to boundary conditions is to control the calculation of [[MPM Global Archiving Options\|reaction forces]]. The command is:		The <tt>BoundaryID</tt> command (in scripted files only) sets an ID to assign to subsequent boundary conditions (velocity and temperature conditions only). The main reason to assign IDs to boundary conditions is to control the calculation of [[MPM Global Archiving Options\|reaction forces or heating power]]. The command is:

	BoundaryID <(negnum)>		BoundaryID <(negnum)>

Nairnj: /* Boundary Condition ID */

2023-08-11T01:17:29Z

Boundary Condition ID

← Older revision		Revision as of 01:17, 11 August 2023
Line 154:		Line 154:
	== Boundary Condition ID ==		== Boundary Condition ID ==

	The <tt>BoundaryID</tt> command (in scripted files only) sets an ID to assign to subsequent boundary conditions. The main reason to assign IDs to boundary conditions is to control the calculation of [[MPM Global Archiving Options\|reaction forces]]. The command is:		The <tt>BoundaryID</tt> command (in scripted files only) sets an ID to assign to subsequent boundary conditions (velocity conditions only). The main reason to assign IDs to boundary conditions is to control the calculation of [[MPM Global Archiving Options\|reaction forces]]. The command is:

	BoundaryID <(negnum)>		BoundaryID <(negnum)>

Nairnj: /* Other Transport Conditions */

2023-08-04T22:53:08Z

Other Transport Conditions

← Older revision		Revision as of 22:53, 4 August 2023
Line 144:		Line 144:
	where <tt>(phaseStyle)</tt> can be the following options:		where <tt>(phaseStyle)</tt> can be the following options:

	* <tt>fracture</tt> (phaseStyle=3)		* <tt>fracture</tt> (phaseStyle=3): set to dimensionless value 0 to 1
	* <tt>battery</tt> (phaseStyle=4)		* <tt>battery</tt> (phaseStyle=4): set to dimensionless value 0 to 1
	* <tt>conduction</tt> (phaseStyle=5): set value in ~~Coulombs/[[ConsistentUnits Command\|(time units)]])~~		* <tt>conduction</tt> (phaseStyle=5): set to value in volts.

	All other parameters are defined [[#Concentration or Poroelasticity Conditions\|above]]. To specify <tt>(phaseStyle)</tt> in scripted files, the <tt>(time)</tt> parameters is required. It can be set to default zero if not needed.		All other parameters are defined [[#Concentration or Poroelasticity Conditions\|above]]. To specify <tt>(phaseStyle)</tt> in scripted files, the <tt>(time)</tt> parameters is required. It can be set to default zero if not needed.

← Older revision		Revision as of 16:24, 12 August 2023
Line 107:		Line 107:
	* <tt>(style)</tt> specifies the [[Boundary Condition Styles\|style of the applied temperature]]. Each temperature depends on two parameters specified by arguments <tt>(value)</tt> and <tt>(time)</tt>. If either argument is not supplied, they are set to zero. The standard units are degrees K for <tt>(value)</tt> and [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]] for <tt>(time)</tt> (but the units may change depending on the [[Boundary Condition Styles\|<tt>(style)</tt> setting]]).		* <tt>(style)</tt> specifies the [[Boundary Condition Styles\|style of the applied temperature]]. Each temperature depends on two parameters specified by arguments <tt>(value)</tt> and <tt>(time)</tt>. If either argument is not supplied, they are set to zero. The standard units are degrees K for <tt>(value)</tt> and [[ConsistentUnits Command#Legacy and Consistent Units\|alt time units]] for <tt>(time)</tt> (but the units may change depending on the [[Boundary Condition Styles\|<tt>(style)</tt> setting]]).
	* <tt>(function)</tt> - if the <tt>(style)</tt> is <tt>function</tt> (or 6), this attribute in <tt>XML</tt> files specifies a [[User Defined Functions\|user defined function]]. In scripted files, the [[User Defined Functions\|user defined function]] should replace the <tt>(value)</tt> argument and must be entered as quoted text. The function should evaluate to the desired temperature in degrees K.		* <tt>(function)</tt> - if the <tt>(style)</tt> is <tt>function</tt> (or 6), this attribute in <tt>XML</tt> files specifies a [[User Defined Functions\|user defined function]]. In scripted files, the [[User Defined Functions\|user defined function]] should replace the <tt>(value)</tt> argument and must be entered as quoted text. The function should evaluate to the desired temperature in degrees K.
			*<tt>(id)</tt> - this attribute in <tt>XML</tt> files specifies an ID for the boundary condition. In scripted files, IDs are set using the [[#Boundary Condition ID\|BoundaryID command]].

	Thermal stresses are caused by temperature difference relative to the [[Thermal Calculations#Stress Free Temperature\|stress free temperature]]. If the stress free temperature has not been set, its default value is zero and thus temperature boundary conditions set the temperature difference. If the stress free temperature is set to a non-zero value, the temperature boundary conditions use the absolute temperature and the temperature difference is calculated by subtracting the stress free temperature.		Thermal stresses are caused by temperature difference relative to the [[Thermal Calculations#Stress Free Temperature\|stress free temperature]]. If the stress free temperature has not been set, its default value is zero and thus temperature boundary conditions set the temperature difference. If the stress free temperature is set to a non-zero value, the temperature boundary conditions use the absolute temperature and the temperature difference is calculated by subtracting the stress free temperature.