Difference between revisions of "Grid-Based Boundary Conditions"

From OSUPDOCS
Jump to navigation Jump to search
 
(3 intermediate revisions by the same user not shown)
Line 6: Line 6:
== Grid-Based Boundary Condition Commands ==
== Grid-Based Boundary Condition Commands ==


In scripted files, all grid-based boundary conditions are created by a series of <tt>GridBC</tt> command blocks that select nodes on the grids:
In scripted files, all grid-based boundary conditions are created by a series of <tt>GridBC</tt> command blocks that select nodes on the grid:


  GridBC
  GridBC
Line 26: Line 26:
The nodes that will get boundary conditions are selected by defining one [[2D MPM Shape Commands|2D shape]] (for 2D simulations) or one [[3D MPM Shape Commands|3D shape]] (for 3D simulations). The shape be a [[Nested Shapes|nested shape]].
The nodes that will get boundary conditions are selected by defining one [[2D MPM Shape Commands|2D shape]] (for 2D simulations) or one [[3D MPM Shape Commands|3D shape]] (for 3D simulations). The shape be a [[Nested Shapes|nested shape]].


All nodes within the one shape will be set to all provided [[Setting Velocity, Temperature, and Concentration|velocity, temperature and/or concentration conditions]].
All nodes within the one shape will be set to all provided [[Setting Velocity and Transport Values|velocity and/or transport value conditions]].


=== Deprecated Commands ===
=== Deprecated Commands ===
Line 51: Line 51:
  </GridBCs>
  </GridBCs>


The <tt>&lt;BCShape&gt;</tt> blocks set boundary conditions as explained [[#Grid-Based Boundary Condition Commands|above]]. The <tt>&lt;DisplacementBCs&gt;</tt> blocks lets you [[Explicit Grid Boundary Conditions|explicitly list each grid point]]. The explicit method is limited to velocity conditions, and is usually generated with other software. You can use both [[#Grid-Based Boundary Condition Commands|<tt>&lt;BCShape&gt;</tt> commands]] and a <tt>&lt;DisplacementBCs&gt;</tt> block in the same input file.
The <tt>&lt;BCShape&gt;</tt> blocks set boundary conditions as explained [[#Grid-Based Boundary Condition Commands|above]]. The <tt>&lt;DisplacementBCs&gt;</tt> block lets you [[Explicit Grid Boundary Conditions|explicitly list each grid point]]. The explicit method is limited to velocity conditions, and is usually generated with other software. You can use both [[#Grid-Based Boundary Condition Commands|<tt>&lt;BCShape&gt;</tt> commands]] and a <tt>&lt;DisplacementBCs&gt;</tt> block in the same input file.


== Layers of Boundary Conditions ==
== Layers of Boundary Conditions ==

Latest revision as of 10:39, 20 September 2017

Introduction

Grid-based boundary conditions are used to create fixed edges, to create moving edges that displace the object, and for setting boundary temperature or concentration. Fixed edges are created be setting velocity to zero. If the edge is a symmetry plane in the object, however, it is better to create the symmetry plane boundary conditions automatically rather then to set them manually with boundary condition commands. The use of a moving edge to apply displacements is limited to small displacements because in large-displacement problems, the particles may move away from the boundary conditions and the conditions will no longer have the correct influence. The alternative method for creating a moving edge is to use rigid material particles set to use the moving boundary condition mode. These particles create grid-based boundary conditions that move with the particle position. They can set velocity or moving temperature and concentration values. Besides grid-based conditions, simulations can set Particle-Based Boundary Conditions.

Grid-Based Boundary Condition Commands

In scripted files, all grid-based boundary conditions are created by a series of GridBC command blocks that select nodes on the grid:

GridBC
  (one 2D or 3D shape command, which can be nested)
  (one or more velocity, temperature, or concentration condition)
    ...
EndGridBC

In XML files, grid-based boundary conditions are created with a <BCShape> block

<BCShape>
  (one 2D or 3D shape command, which can be nested)
  (one or more velocity, temperature, or concentration condition)
    ...
</BCShape>

which must be within the main <GridBC> block.

The nodes that will get boundary conditions are selected by defining one 2D shape (for 2D simulations) or one 3D shape (for 3D simulations). The shape be a nested shape.

All nodes within the one shape will be set to all provided velocity and/or transport value conditions.

Deprecated Commands

Prior to the grid-based boundary condition commands in the previous section, the boundary conditions used to be set with boundary condition shape commands. The deprecated commands are:

  • MoveLine and <BCLine>
  • MoveArc and <BCArc>
  • <LdRect>
  • MoveBox and <BCBox>

See documentation for conversion of old commands to the new method.

Explicit Grid-Based Boundary Condition in XML Files

An option in XML files is to explicitly set boundary conditions on nodes without using shape functions. The format is

<GridBCs>
   (one or more <BCShape> blocks)
   ...
   <DisplacementBCs>
      (one or more explicit boundary conditions)
   </DisplacementBCs>
</GridBCs>

The <BCShape> blocks set boundary conditions as explained above. The <DisplacementBCs> block lets you explicitly list each grid point. The explicit method is limited to velocity conditions, and is usually generated with other software. You can use both <BCShape> commands and a <DisplacementBCs> block in the same input file.

Layers of Boundary Conditions

Grid boundary conditions are typcially placed on a layer of nodes that is outside the body defined by the material points and that layer defines the boundary. When using GIMP methods, however, a particle near the boundary will interact with that boundary layer, but may also interact with nodes beyond a single row of boundary conditions. To prevent non-physical results from the extra nodes that are physcially outside the body, it may be necessary to set up two rows (or columns) of boundary conditions. For example, to have a rigid wall, set the velocity of two rows (or columns) or nodes to be zero. An alternative solution is to fill a boundary area with rigid particles. Rigid particle automatically create the required boundary conditions on two rows (or columns) of nodes.

Sometimes even two rows of boundary conditions will lead to artifacts in particles near the edges. These artifacts can be reduced by using symmetry planes or rigid particles with the mirrored property.