Rigid Material

From OSUPDOCS
Revision as of 14:07, 8 October 2013 by Nairnj (talk | contribs) (Created page with "<p>This type of material is actually two materials in one, depending on the value for its <code>direction</code> property (which is defined below):</p> <ol> <li>If <code>dire...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This type of material is actually two materials in one, depending on the value for its direction property (which is defined below):

  1. If direction is 0 through 7, the material is not really a material and points that are this type of rigid material will not really be part of the MPM analysis. These rigid material points are used to set boundary conditions on the grid that move with the particles. The rigid material points should be initialized to a velocity, temperature, or concentration when they are created in <a href="region.html">Region commands</a>. As the rigid material points move through the grid, all nodes connected to those points will be assigned grid-based boundary conditions for the selected particle properties of velocity, temperature, and/or concentration. To have the boundary condition vary in time and position, use the settingFunction(2)(3) and valueFunction properties below to set the value rather than using the initial particle properties to pick a constant value.
  2. If direction is 8, the material will correspond to actual material points that moves through the analysis. Since they are rigid, they will move with their prescribed velocity. They will interact with other material points only through multimaterial contact or imperfect interface laws and thus this type of rigid material can only be used in <a href="multimaterialmode.html">multimaterial mode MPM</a> calculations. These particles will ignore grid-based velocity boundary conditions, including those set by rigid particles with direction equal to 1 through 7.
        The advantage of this type of rigid material (unlike the other type) is that you can set <a href="frictionmm.html">frictional properties</a> for contact between rigid materials and non-rigid materials or you can use material contact to model <a href="imperfectinterface.html">imperfect interfaces</a>. These rigid materials will move in the direction defined by the initial velocity, or, by using settingFunction(2)(3) properties below, they can moved by any prescribed velocity. If two different rigid materials of this type interact at the same node, however, there is a conflict and the calculation will stop. Finally, because this type of rigid material does not set boundary conditions, it cannot be used to set temperature or concentration.
        A direction=8 rigid material ignores cracks, but that actually makes it possible to use them for new crack problems. For example, these rigid particles can provide wedge opening of a crack. If the rigid particles run along an <a href="newcrack.html">explicit crack plane</a>, those particles may contact particles on both sides of the crack and then move the top and bottom surfaces of the crack apart. It may be only way to wedge open a crack (i.e., the only material that can act like it is within a crack rather than on either side of the crack). All crack calculations (e.g., crack contact, traction laws, imperfect interfaces, updating of crack position, and J integral) will ignore the rigid particles. The interactions with the rigid particles arise only by contact laws between the rigid particles and the various crack velocity fields.

The rigid material properties are set with the following commands:

  • direction to set various combinations of velocity directions. To create the alternate type of rigid particles that can implement frictional contact, set this value to 8. The options 1 through 7 set grid velocities to various components of the rigid particle velocity by bit-wise selection with first three bits being for x, y, and z directions (or R, Z, θ if axisymmetric). A value of 0 sets no direction:
    ValueBinarySet Directions
    00x000no direction
    10x001x only
    20x010y only
    30x011x and y
    40x100z only
    50x101x and z
    60x110y and z
    70x111x, y, and z
  • temperature should be 1 to set temperature boundary condition or 0 to not set it (usually it is either set to 1 or omitted from the material definition). This setting has no affect unless the analysis is doing thermal calculations. Can only be used if direction is 0 through 7. Use 0 to having moving heat source only; use 1 to 7 to combine moving heat source with velocity boundary conditions.
  • concentration should be 1 to set concentration boundary condition or 0 to not set it (usually it is either set to 1 or omitted from the material definition). This setting has no affect unless the analysis is doing diffusion calculations. Can only be used if direction is 0 through 7. Use 0 to having moving concentration source only; use 1 to 7 to combine moving concentration source with velocity boundary conditions.
  • settingFunction (or settingFunction1), settingFunction2, and settingFunction3 to enter a <a href="function.html">user-defined function</a> of time and position. The function should evaluate to the velocity in mm/s. The initial velocity assigned to the rigid particles when they are created in <a href="region.html">Region commands</a> will be ignored.
         The three setting functions can set up to three directions. For SetDirection 1 to 7 the functions must be given in order (settingFunction, settingFunction2, and settingFunction3) and apply to the set velocities in order (e.g., when controlling y and z with direction=6, the settingFunction is for y direction and settingFunction2 is for z direction).
         For direction of 8, the three functions are for setting x, y, and z directions and zero to three can be used. Any not controlled will use the initial particle velocity (you can use settingFunctionx (or y or z) as synonyms for settingFunction1 (or 2 or 3))
  • valueFunction to enter a <a href="function.html">user-defined function</a> of time and position. The function should evaluate to the temperature or concentration potential. The initial temperature or concentration assigned to the rigid particles when they are created in <a href="region.html">Region commands</a> will be ignored.
         Since there is only one value function, you cannot independently vary temperature and concentration with time and position. Thus rigid particles with value functions should only set one of these quantities.

Note that <a href="multimaterialmode.html">multimaterial mode MPM</a> calculations can combine moving boundary condition rigid particles (direction=0 to 7) with contact rigid particles (direction=8) to provide different functions, but single-material mode MPM can only use boundary condition rigid particles (direction=0 to 7).

Note that creating rigid particles but not setting any velocity direction (direction=0) can be used to create moving temperature or concentration boundary conditions that move over the particles; i.e., the rigid particles will move through the real particles. Such moving temperature or concentration boundary conditions can only move at a constant velocity defined by the initial particle velocity, because the direction=0 setting implies no axis is controlled by a function.

If a rigid particle is added to a problem, but it does not set any velocity, temperature, or concentration (direction=temperature=concentration=0 or omitted), it will have no affect on the calculations. It may plot in visualization software and therefore appear to be part of the simulation, but it will be identical to the results that would be obtained if it had never been added to the problem.