menu.data1

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

      MARC13 - Open Section Thin-Walled,
      MARC14 - Thin-Walled w/o Warping,
      MARC25 - Thin-Walled,
      MARC76 - Thin-Walled w/o Warping,
      MARC79 - Thin-Walled w/  Warping,
      MARC31 - Elastic Curved Pipe,
      MARC52 - Elastic,
      MARC98 - Elastic w/ Transverse Shear.
    NASTRAN:
      BNA1 which defines the Beam
      BNA2 which defines the Offset Rods with cross section
        CSTYPE 1 for elliptic
        CSTYPE 2 for symmetry about y and z
        CSTYPE 3 for symmetry about y
        CSTYPE 4 for symmetry about z
        CSTYPE 5 for symmetry about y=z=0
        CSTYPE 6 for arbitrary
      BNA3 which defines the Curved Beam
      BNA4 which defines the Elbow & Curved Pipe
      BNA5 which defines the Simple Beam (Bar)
      BNA6 which defines the Rod
      BNA7 which defines the Tube
    NIKE3D: default cross section properties are defined within the material
     definition. To override the default material definition use STHI,
     STHI1, STHI2, TTHI, TTHI1, TTHI2;
    PATRAN: use LDP;
  BSINFO: write information about the defined beam cross sections.
  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.
  LSBSD: List the defined beam cross sections.
   They are listed by number and type. 
   Use BSINFO to get full information about a specific beam cross
   section definition.
  SIND: shell user defined integration rules.
    0 and a list of z-coordinates, weights, and (optional) material numbers or
    1 for equal spacing
BOUNDARY commands:
  DETP: create detonation points and lighting times for high explosives.
   A line of detonators can also be created.
  JD: each numbered joint created by this command assigns constraints
   to a set of nodes to be identified later using the JT command.
   A joint can have up to 16 nodes assigned to it.
   Some joint types require less and any additional nodes assigned to
   that joint will be ignored.  When a node is assigned to a numbered joint, it
   is also assigned a sequence number or local node number within
   that joint definition.
   There are two basic types of joints.
   The first basic type (SJ, RJ, CJ, PJ, UJ, and TJ) require a specific set
   of nodes where each node may play a different role in the behavior of
   the joint.
   The second basic type is an arbitrary set of nodes constraints to share
   certain degrees of freedom. The second basic type is simply multiple
   constrained nodes and can also be accomplished using the MPC command
   in the merge phase.
   Nodes are assigned to the joint definition
   using the JT command either in the part or merge phase.
   It is best to define the joint with JD before referencing it with JT.
   The REPE option makes multiple joint definitions.
   This is useful when parts containing joints are replicated.
   The JT command also allows for a joint number increment
   so that the corresponding nodes in the different copies of the part
   can each be assigned to its corresponding numbered joint.
    SJ for spherical joint
    RJ for revolute joint
    CJ for cylindrical joint
    PJ for planar joint
    UJ for universal joint
    TJ for translational joint
    PNLT for joint penalty used with SJ, RJ, CJ, PJ, UJ, and TJ
    REPE for repeated joint definitions
    SW for spotwelded nodal constraints
    DX, DY, and DZ for shared nodal displacement
    RX, RY, and RZ for shared nodal rotation
  JTINFO: write information about defined joints.
  MPC: shared nodal (multiple point) constraints for a nodal set.
  LSYS: define a local coordinate system used by the LB command.
  LSYSINFO: list all of the local coordinate systems.
  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 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.
  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.
  ESETC: attach a comment to an element set.
  FSETC: attach a comment to a face set.
  NSETC: attach a comment to a node set.
  NSETINFO: report the node set names and number of nodes.
CAD: import CAD/CAM geometry
  USEIGES: include the file that contains the IGES surface and 
   3D curve evaluations.
   If the same surfaces or 3D curves to be evaluated were already
   evaluated in a previous session of TrueGrid and saved using the SAVEIGES
   command, then this command will retrieve the data and save time.
   The surface and 3D curve evaluations command IGESFILE, IGESSD, IGESCD,
   NURBSD, SD or CURD must also be issued after this command to take
   advantage of the data.
  IGES: extract and evaluate all 3D curves and surfaces from an IGES file.
   TrueGrid can use 3D curves, NURBS surfaces, planes, trimmed parametric
   surfaces and surfaces other than bounded surfaces (type 143).  B-Rep solid
   model entities are not evaluated.
   Four arguments are required for this command.
   The first is the file name.
   The second is the first defined surface number to be assigned
   to the first surface in the IGES file.
   The NURBS surfaces are processed first, followed by other surfaces,
   with the planes added last to the set of defined surfaces.
   The next argument is the first defined 3D curve number to be
   assigned to the first 3D curve encountered in the IGES file.
   The last argument is the transformation to be applied to the surfaces
   and 3D curves.
   This command is the simplest way to use IGES data with the drawback that
   the evaluation of all 3D curves and surfaces may be time consuming.
   To save the evaluations for future re-use, issue the SAVEIGES command.
   The next time this IGES file is used, issue the USEIGES command first to 
   save time in the evaluation of the entities.
  IGESFILE: sort the entities from a CAD/CAM IGES file.
   The PC version of TrueGrid may have difficulty reading an IGES file created on
   a UNIX system because null characters may be included in a string.
   This problem can be solved by opening the IGES file with a text editor and
   making the proper changes.
   TrueGrid can use 3D curves, NURBS surfaces, planes, trimmed parametric
   surfaces and surfaces other than bounded surfaces (type 143).  B-Rep solid
   model entities are not evaluated.
   This command initializes an internal data base that TrueGrid uses
   when specific IGES 3D curves or surfaces are referenced, but this command
   does not evaluate the entities.
   IGES 3D curves and surfaces must be evaluated before they can be displayed in 
   the
   graphics or before a region of the mesh can be placed onto the entity.
   To render a 3D curve, first use the CURD or IGESCD command to evaluate the 
   3D curve.
   To render a NURBS surface, first use SD or NURBSD command to evaluate the
   surface.
   To render a plane, first use the SD or IGESPD command to evaluate the surface.
   To render another surface other than a plane or trimmed surface, use the
   SD or IGESSD command to evaluate the surface.
   The evaluation and display of IGES entities require additional commands 
   because
   it is felt that the number and size of IGES entities may be overwhelming.
   This way the user can select only a subset of the entities to display or use.
   While in the part or merge phase, use the DCD, DACD, ACD, RCD, DCDS commands
   to render evaluated IGES 3D curves and use the DSD, DASD, ASD, RSD, DSDS 
   commands to render evaluated IGES surfaces.
   While in the part phase, use the CUR command to place an edge of the mesh
   along an evaluated 3D curve.
   Use the SF command to place a face of the mesh onto a surface.
   Evaluation of surfaces and 3D curves can be time consuming.
   The alternative is to evaluate the entities once and save the evaluations
   using the SAVEIGES command.
   Before using the same entities in another TrueGrid session, issue the
   USEIGES command.
  IGESCD: a sequence of IGES 3D curves
   from a CAD/CAM IGES file (see IGESFILE)
   are evaluated and each 3D curve is assigned a TrueGrid 3D curve definition
   number.
   Optionally, these 3D curves can be moved within the global coordinate system.
   While in the part or merge phase, use the commands DCD, DACD, ACD, RCD,
   and DCDS commands to select the 3D curves displayed in the graphics.
   While in the part phase, use the CUR command to place a face of the mesh
   along a numbered 3D curve.
  IGESPD: a sequence of IGES planes 
   from a CAD/CAM IGES file (see IGESFILE)
   are evaluated and each plane is assigned a TrueGrid surface definition
   number.
   Optionally, these planes can be moved within the global coordinate system.
   While in the part or merge phase, use the commands DSD, DASD, ASD, RSD,
   and DSDS commands to select the surfaces displayed in the graphics.
   While in the part phase, use the SF command to place a face of the mesh
   onto a numbered surface.
  IGESSD: a sequence of IGES surfaces (other than planes and 
   NURBS surfaces) from a CAD/CAM IGES file (see IGESFILE)
   are evaluated and each surface is assigned a TrueGrid surface definition
   number.
   Optionally, these surfaces can be moved within the global coordinate system.
   While in the part or merge phase, use the commands DSD, DASD, ASD, RSD,
   and DSDS commands to select the surfaces displayed in the graphics.
   While in the part phase, use the SF command to place a face of the mesh
   onto a numbered surface.
  IGESLBLS: toggle the flag to use IGES labels for surfaces.
  NURBSD: a sequence of NURBS surfaces from a CAD/CAM IGES file (see IGESFILE)
   are evaluated and each surface is assigned a TrueGrid surface definition
   number.
   Optionally, these surfaces can be moved within the global coordinate system.
   While in the part or merge phase, use the commands DSD, DASD, ASD, RSD,
   and DSDS commands to select the surfaces displayed in the graphics.
   While in the part phase, use the SF command to place a face of the mesh
   onto a numbered surface.
  SAVEIGES: save the IGES surface and 3D curve evaluations in a file.
   This should be issued after the IGESFILE, IGESSD, IGESCD, NURBSD,
   SD and CURD commands are issued which evaluate selected surfaces and 
   3D curves.
   If some of these same surfaces or 3D curves are required in future 
   TrueGrid sessions, use the command USEIGES before issuing the evaluations
   commands. This will save time.
  VPSD: extract surface definitions from ascii node and polygon data files.
   The node file has one record for each node.
   The first number in the record is the unique positive 
   integer node number, followed
   by the x, y, and z-coordinates in floating point or exponential form.
   These four numbers are comma delimited.
   The polygon data has one record per polygon.
   The first field assigns a group or surface name to the polygon.
   The name is used to sort the polygons into surfaces.
   It is best to group polygons into surfaces so that there are no sharp
   bends in a surface.
   This is followed by a list of ordered node numbers to be connected
   to form the polygon.
   These node numbers refer to the nodes in the node file.
   It is assumed that each polygon is nearly planar.
   Fields in this file are space delimited.
   Each record must be no longer than 128 characters.
   There is also a limit of 30 nodes forming the polygon.
   The set of surfaces can be transformed.
  WIGES: write an IGES file from a list of surfaces. Only those
   surfaces created using the HERMITE option under the SD command
   are allowed at this time.
  WRSD: write two files to contain the coordinates and polygons to
   a polygon surface (VPSD).
  TRIMMING: Select IGES surfaces to be trimmed.
   When this is on, trimmed surfaces will be trimmed by TrueGrid and
   entities related to a trimmed surface will not be evaluated.
   When this is off, then TrueGrid will evaluate IGES surfaces the way
   they were evaluated prior to version 1.2.0.
   This is important because the surfaces will be numbered differently
   and old command files using IGES data may not work properly with
   trimming on.
   This command must be used before reading the IGES file.
   The default is "on".
  LTRIM: select the amount of workspace needed to trim surfaces.
   This command is usually not needed. The default is 2000000.
   Increase the size only if the code makes that suggestion.
2D CURVE includes the following commands:
  LD: begin the definition of a 2D curve in a plane.
   The local 2D coordinate system axis used to define these 2D curves 
   are labeled x for the ordinate and z for the abscissa.
   This local coordinate system should not be associated with the
   x and z axis of the global 3D coordinate system.
   Check the definition of a specific command using a 2D curve to know how
   the local 2D curve is embedded in the global 3D coordinate system.
   The LD command has many options which can be combined in almost any order to
   produce a complex 2D curve.
   This method is fashioned after the way a draftsman might
   draw a complex 2D curve.
   Each use of an option from the list below appends 
   a 2D curve segment to the composite 2D curve.
   For additional segments, use the APLD dialogue or
   issue any of the options below.
   Once a 2D curve is begun using the LD command, additional curve segments
   can no longer be added to any of the other previously defined 2D curves.
   If a previously defined 2D curve must be modified, it must be re-defined.
   To view the 2D curves, use the LV, LVS and LVI commands.
   2D curves can be used to form 3D surfaces and 3D curves.
   A 2D curve can be rotated about any axis of symmetry
   using the SD command with the CRX, CRY, CRZ, and CR options.
   A 2D curve can be extruded indefinitely in any direction
   using the SD command with the CP option.
   A 2D curve can be combined with another 2D curve to produce a ruled
   surface between the two curves in 3D
   using the SD command with the RULE2D option.
   A 2D curve can be converted to a 3D curve using the CURD command with the
   LD2D3D option.
   The fo