menu.data2

Triangular mesh processing tool, currently very few people use this software, but it allows us to gr

   the part is duplicated 5 times, with INC set to 3, then the node
   from each copy of the part will be assigned to joint numbers 5, 8, 11,
   14, and 17, respectively.
    N to identify the joint node within the part
    P to create a new node by specifying its Cartesian coordinates and material
    C to create a new node by specifying its cylindrical coordinates and
     material
    S to create a new node by specifying its spherical coordinates and material
    V Cartesian coordinate offset of the created node
    DX for a displacement constraint in the x-direction for the new node
    DY for a displacement constraint in the y-direction for the new node
    DZ for a displacement constraint in the z-direction for the new node
    RX for a rotational constraint about the local x-axis for the new node
    RY for a rotational constraint about the local y-axis for the new node
    RZ for a rotational constraint about the local z-axis for the new node
    INC to specify the part replication joint increment such that each
     replication of this joint has a new number
    MINC to specify the part replication material increment such that each
     replication of this joint has a new material number
    LLINC: option which increments the local joint node number when the local
     coordinate transformations are used in the LREP and GREP commands to create
     replications of the part.
    GLINC: option which increments the local joint node number when the
     global coordinate transformations are used in the LEV
     command to create replications of the part.
  MPC: shared nodal (multiple point) constraints for a nodal set.
  LB: nodal displacement and rotation constraints within 
   a local coordinate system.
   Use the LSYS to define a local coordinate system.
  LBI: nodal displacement and rotation constraints within 
   a local coordinate system by index progression.
   Use the LSYS to define a local coordinate system.
  LSYS: define a local coordinate system used by the LB command.
  LSYSINFO: list all of the local coordinate systems.
  OL: identifies a face of the mesh as an outlet for fluid flow.
  OLI: identifies a face of the mesh by index progression 
   as an outlet for fluid flow.
  PLANE: define a boundary plane with options.
    SYMM for symmetry plane. If the plane is not parallel to one of
     the coordinate planes, DYNA3D requires that it pass through
     the global origin.
      VECTOR to constrain nodes along the normal vector
    SYF for symmetry plane with failure
    STON for stonewall with the options
      STICK to select a friction wall
      LIMIT to bound the wall
      MOVE to give the wall motion
      PEN to specify the penalty stiffness scale factor
      DISP to specify the displacement load curve
  PLINFO: write information about defined planes.
  NAMREG: Name a region for the TASCFLOW output file.
  NAMREGI: Name a region for the TASCFLOW output file.
  NR: assign a surface as a non-reflecting boundary.
  NRI: assign surfaces as non-reflecting boundaries by index progression.
  REG: select a region for the REFLEQS boundary condition.
  REGI: select a region for the REFLEQS boundary condition by progression.
  SFB: constrain face nodes using the tangent plane and normal to form a
   local coordinate system.
   First, the normal to the mesh or surface which formed the mesh
   is constructed, for each node.
   This direction becomes the local z-axis.
   Use the ORPT command to orient this direction.
   This is sufficient for some problems, so no flow direction
   is needed to construct a complete local coordinate system.
   When a general purpose local coordinate system is needed to 
   apply local boundary constraints, then a second direction,
   corresponding to the local x-axis must be specified.
   There are several options. A mesh line can be used to select
   the direction, or a vector can be specified.
   If this command is used several times for different regions
   that overlap, the nodes in the overlapping region will
   be assigned two local system boundary constraints which may
   result in the node not being allowed to move or maybe
   not allowed in the simulation.
  SFBI: constrain face nodes using the tangent plane and normal to form a
   local coordinate system by index progression.
   First, the normal to the mesh or surface which formed the mesh
   is constructed, for each node.
   This direction becomes the local z-axis.
   Use the ORPT command to orient this direction.
   This is sufficient for some problems, so no flow direction
   is needed to construct a complete local coordinate system.
   When a general purpose local coordinate system is needed to 
   apply local boundary constraints, then a second direction,
   corresponding to the local x-axis must be specified.
   There are several options. A mesh line can be used to select
   the direction, or a vector can be specified.
   If this command is used several times for different regions
   that overlap, the nodes in the overlapping region will
   be assigned two local system boundary constraints which may
   result in the node not being allowed to move or maybe
   not allowed in the simulation.
  SW: select nodes that may impact a stone wall.
   First use the PLANE command to define the stone wall.
  SWI: select nodes that may impact a stone wall by index progression.
   First use the PLANE command to define the stone wall.
  SYF: assign faces of the mesh to a numbered symmetry plane with failure.
   First use the PLANE command to define the symmetry plane.
  SYFI: assign faces of the meshnodes to a numbered symmetry plane with
   failure by index progression.
   First use the PLANE command to define the symmetry plane.
  TRP: create tracer particles.
SETS commands:
  DELSET: delete a set.
   If a set was constructed but is no longer needed, then
   it is best to delete it with this command.
   This can be important if an output file is going to be
   written which automatically writes all sets.
   When deleted, the set will not be written to the output
   file and it will not be using memory.
  ESET: add/remove elements to/from a set of elements.
   An element can be a linear or quadratic shell or a
   linear or quadratic brick element.
   Selected elements can be used to create a element set.
   If the element set previously existed, it is first deleted,
   and then recreated as a new set.
   Selected elements can be added by using the union operator.
   This causes any selected elements to be included in a set, if it
   is not already in that set.
   The intersect operator redefines an element set to be only those
   elements which are found to be both in the original set and
   among the selected elements.
   The minus operator removes all elements in a set which are among the
   selected elements.
  ESETI: add/remove elements to/from a set of elements by index
   progression.
   An element can be a linear or quadratic shell or a
   linear or quadratic brick element.
   Selected elements can be used to create a element set.
   If the element set previously existed, it is first deleted,
   and then recreated as a new set.
   Selected elements can be added by using the union operator.
   This causes any selected elements to be included in a set, if it
   is not already in that set.
   The intersect operator redefines an element set to be only those
   elements which are found to be both in the original set and
   among the selected elements.
   The minus operator removes all elements in a set which are among the
   selected elements.
  ESETC: attach a comment to an element set.
  FSET: add/remove faces to/from a set of faces.
   A face can be a linear or quadratic shell or a face of a
   linear or quadratic brick element.
   Selected faces can be used to create a face set.
   If the face set previously existed, it is first deleted,
   and then recreated as a new set.
   Selected faces can be added by using the union operator.
   This causes any selected faces to be included in a set, if it
   is not already in that set.
   The intersect operator redefines a face set to be only those faces
   which are found to be both in the original set and
   among the selected faces.
   The minus operator removes all faces in a set which are among the
   selected faces.
  FSETI: add/remove faces to/from a set of faces by index progression.
   A face can be a linear or quadratic shell or a face of a
   linear or quadratic brick element.
   Selected faces can be used to create a face set.
   If the face set previously existed, it is first deleted,
   and then recreated as a new set.
   Selected faces can be added by using the union operator.
   This causes any selected faces to be included in a set, if it
   is not already in that set.
   The intersect operator redefines a face set to be only those faces
   which are found to be both in the original set and
   among the selected faces.
   The minus operator removes all faces in a set which are among the
   selected faces.
  FSETC: attach a comment to a face set.
  NSET: add/remove nodes to/from a set of nodes.
   Selected nodes can be used to create a node set.
   If the node set previously existed, it is first deleted,
   and then recreated as a new set.
   Selected nodes can be added by using the union operator.
   This causes any selected nodes to be included in a set, if it
   is not already in that set.
   The add operator will always append selected nodes to a set.
   This is used to create ordered node sets where duplicate
   nodes are allowed.
   The intersect operator redefines a node set to be only those nodes
   which are found to be both in the original set and
   among the selected nodes.
   The minus operator removes all nodes in a set which are among the
   selected nodes.
  NSETI: add/remove nodes to/from a set of nodes by index progression.
   Selected nodes can be used to create a node set.
   If the node set previously existed, it is first deleted,
   and then recreated as a new set.
   Selected nodes can be added by using the union operator.
   This causes any selected nodes to be included in a set, if it
   is not already in that set.
   The add operator will always append selected nodes to a set.
   This is used to create ordered node sets where duplicate
   nodes are allowed.
   The intersect operator redefines a node set to be only those nodes
   which are found to be both in the original set and
   among the selected nodes.
   The minus operator removes all nodes in a set which are among the
   selected nodes.
  NSETC: attach a comment to a node set.
  NSETINFO: report the node set names and number of nodes.
  ORPT: choose a method to determine the positive direction of normals on
   a surface. This is used before commands such as SI (sliding interface), 
   N (shell orientation), CV (boundary convection), etc., to determine 
   directions
   of flows, orientations of shells, and other boundary conditions.
   The default method sets orientation depending on the ordering of the nodes.
   When a method is selected, it is always in effect for those following
   commands requiring an orientation method, until a new method is selected.
   The flip option reverses the default direction of orientation.
   This feature can be turned off.
ELEMENT commands:
  OFFSET: offset node and element numbers.
   The result of this command is an altering of the numbering of nodes
   and/or elements in the output for keyword driven codes.
   All other diagnostics and graphics do not reflect
   this altering of the numbered nodes and/or elements. Most keyword
   driven codes have one list of elements. In this case, only use the
   BRICKOFF option to this command to alter the element numbering.
  OR: orientation of 3D element local coordinate axes.
   The first two axis can be selected.
   There is no restriction for solid elements.
   Shell element orientation selection is restricted to the directions
   in the plane of the shell elements.
  N: orientation of normals on shell elements toward a point
   set by the ORPT command in the MESH menu.
   Note that the ORPT must be used first before using this command.
  SIND: shell user defined integration rules.
    0 and a list of z-coordinates, weights, and (optional) material numbers or
    1 for equal spacing
  BIND: Hughes-Liu beam user defined integration points.
  BSINFO: write information about the defined beam cross sections.
   The result of this command is an altering of the numbering of nodes
   and/or elements in the output for keyword driven codes.
   All other diagnostics and graphics do not reflect
   this altering of the numbered nodes and/or elements. Most keyword
   driven codes have one list of elements. In this case, only use the
   BRICKOFF option to this command to alter the element numbering.
  SSF: project a shell onto an interpolated surface and calculate
   variable shell thicknesses.
   The surface of projection must be of type INTP, a surface interpolated
   between two other defined surfaces.
   The nodes of the shells are placed along the interpolated surface.
   The thickness of the shell at each node is calculated by projecting
   the node to the first surface used to define the interpolated surface.
   The line starting at this point in the normal direction is intersected
   with the second surface used to define the interpolated surface.
   The distance along this line to the second surface is the thickness 
   at that node.
   This is done for each node for each shell.
  SSFI: project a shell onto an interpolated surface and calculate
   variable shell thicknesses by index progression.
   The surface of projection must be of type INTP, a surface interpolated
   between two other defined surfaces.
   The nodes of the shells are placed along the interpolated surface.
   The thickness of the shell at each node is calculated by projecting
   the node to the first surface used to define the interpolated surface.
   The line starting at this point in the normal direction is intersected
   with the second surface used to define the interpolated surface.
   The distance along this line to the second surface is the thickness 
   at that node.
   This is done for each node for each shell.
  TH: thickness of thin shell elements.
  THI: thickness of thin shell elements by index progression.
  THIC: part default shell element thickness.
  BSD: global beam element cross section definition.
   A cross section is referenced by every beam.
   Each beam is defined by two end nodes and either a third node or
   a coordinate triple to define the orientation of the cross section
   local coordinate system of the beam.
   Through out TG, the local coordinate system for the beam element
   is referred to by x, y, and z.
   They corresponding to the longitudinal axis
   of the beam stretched between the first two nodes, the orthogonal
   component from the first node to the third node/coordinate, and
   the third direction orthogonal to the first two directions, respectively.
   The thickness parameters STHI, STHI1, STHI2, TTHI, TTHI1, and TTHI2
   are the distances from the center to the boundary of the element.
   They are the half thicknesses used by DYNA3D and NIKE3D.
   Other parameters are used to define specific dimensions for the
   different types of cross sections.
   When there is the possibility of specifying a quantity different
   at each end, there will be one option which assigns the same value
   to both ends, and then two addition options, one for each end.
   These two options are distinguished by the suffix of 1 and 2, respectively.
   When multiple beams are generated from information at two ends, some
   quantities such as thickness are linearly interpolated.
   Other quantities, such as cross section area and moments are not
   interpolated.
   In this latter case, the values found at the first cross section
   are broadcast throughout the string of beams.
   Some of the parameters in the cross section definition are also definable
   within the definition of the individual beams.
   The value of these parameters within the beam definition take
   precedent over this beam cross section definition.
   The parameters in this cross section definition are code dependent.
   The parameters available for each code are listed.
   The STHI, STHI1, STHI2, TTHI, TTHI1, TTHI2, AREA, SCAREA, IXX, IYY,
   IZZ and LDP options can be
   used any time.
    ABAQUS: the *BEAM SECTION card is generated using CSTYPE with
      7 which defines a Pipe cross section,