Difference between revisions of "Explicit Particle Boundary Conditions"

From OSUPDOCS
Jump to navigation Jump to search
Line 1: Line 1:
explicit loadBC
__TOC__
== Introduction ==


<!ELEMENT load (#PCDATA)>
If needed, particle load boundary conditions can be explicitly assigned to numbered particles by using <tt><load></tt> elements within the single <tt><LoadBCs></tt> element. This approach can only be used in <tt>XML</tt> input files and is rarely used, except perhaps in separate software or scripts that create an <tt>XML</tt> input file automatically. The more common way it to assign [[Particle-Based Boundary Conditions|boundary conditions to a block of particles]] suing shapes.
<!ATTLIST load
 
node CDATA #IMPLIED
== Explicit Load Conditions ==
pt CDATA #IMPLIED
 
dof CDATA #REQUIRED
An explicit load is assigned to one particle with a <tt><load></tt> element:
style (1|2|3|4|5|6) "1">
 
<fix pt='(num)' dof='(dir)' style='(style)'>(load)</fix>
 
where the text of the <tt><load></tt> tag (i.e., <tt>(load)</tt>) is the value of the fixed velocity in [[ConsistentUnits Command#Legacy and Consistent Units|velocity units]] and it can be a user-defined function of position. The attributes of the <tt><load></tt> element are:
 
* <tt>dof</tt> determines if the x direction ((dir)=1), the y direction ((dir)=2), the z direction ((dir)=3), the R direction when axisymetric ((dir)=1), or the Z direction when axisymmetric ((dir)=2) will have the specified velocity.
* <tt>(style)</tt> specifies the [[Setting Velocity, Temperature, and Concentration#Boundary Condition Styles|style of the applied velocity]]. Each velocity depends on two parameters specified by arguments (velocity) and (time). If either argument is not supplied, they are set to zero. The standard units are [[ConsistentUnits Command#Legacy and Consistent Units|velocity units]] for (velocity) and [[ConsistentUnits Command#Legacy and Consistent Units|alt time units]] for (time) (but the units may change depending on the [[Setting Velocity, Temperature, and Concentration#Boundary Condition Styles|<tt>(style)</tt> setting]]). When using an arbitrary function (see  [[Setting Velocity, Temperature, and Concentration#Boundary Condition Styles|<tt>(style)</tt>=6]]) the<tt>(velocity)</tt> text should be the a user-defined function of t (in [[ConsistentUnits Command#Legacy and Consistent Units|alt time units]]) that evaluates to velocity in [[ConsistentUnits Command#Legacy and Consistent Units|velocity units]]. If this attribute is omitted, it is assumed to be 1 (or a constant velocity).

Revision as of 11:36, 8 April 2017

Introduction

If needed, particle load boundary conditions can be explicitly assigned to numbered particles by using <load> elements within the single <LoadBCs> element. This approach can only be used in XML input files and is rarely used, except perhaps in separate software or scripts that create an XML input file automatically. The more common way it to assign boundary conditions to a block of particles suing shapes.

Explicit Load Conditions

An explicit load is assigned to one particle with a <load> element:

<fix pt='(num)' dof='(dir)' style='(style)'>(load)</fix>

where the text of the <load> tag (i.e., (load)) is the value of the fixed velocity in velocity units and it can be a user-defined function of position. The attributes of the <load> element are:

  • dof determines if the x direction ((dir)=1), the y direction ((dir)=2), the z direction ((dir)=3), the R direction when axisymetric ((dir)=1), or the Z direction when axisymmetric ((dir)=2) will have the specified velocity.
  • (style) specifies the style of the applied velocity. Each velocity depends on two parameters specified by arguments (velocity) and (time). If either argument is not supplied, they are set to zero. The standard units are velocity units for (velocity) and alt time units for (time) (but the units may change depending on the (style) setting). When using an arbitrary function (see (style)=6) the(velocity) text should be the a user-defined function of t (in alt time units) that evaluates to velocity in velocity units. If this attribute is omitted, it is assumed to be 1 (or a constant velocity).