BEGIN

Bulk Data Entry Indicates the beginning of data that is used to describe a specific entity (or entities) for inclusion in a model. The BEGIN entry is used in conjunction with the END entry to define the data required for a specific entity.

Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
BEGIN TYPE NAME/SEID              

Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
BEGIN FEMODEL Bumper              
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
BEGIN HYPRBEAM Square              
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
BEGIN SUPER SEID
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
BEGIN MASSID 11

Definitions

Field Contents SI Unit Example
TYPE Specifies the entity type that will be defined by the BEGIN Bulk Data Entry.
HYPRBEAM
Data required for the definition of an arbitrary beam section will be specified between the BEGIN and END Bulk Data Entries.
FEMODEL
In a model containing multiple parts, the parts are included within the full model specifying part data between the BEGIN and END Bulk Data Entries (the INCLUDE entry can also be used for part data referencing). The name of the included part should be specified in the NAME field.
SUPER
Allows for definition of a partitioned superelement section.
MASSID
Indicates the following elements in the MASSID section are used as additional mass for a linear combination referred by MASSSET. Typically, any element can be defined to specify the mass section.
  
NAME This field specifies the name of the entity that is defined by the BEGIN entry.

The name of the included part should be specified in the NAME field.

(Character String)

  
SEID Partitioned superelement or mass section identification number.

This entry is valid only when TYPE = SUPER or TYPE = MASSID.

No default (Integer > 0)

  

Comments

  1. The BEGIN and END Bulk Data Entries are used in conjunction to define an entity within the full model.
  2. The INCLUDE entry, similar to almost any other Bulk Data Entry, is allowed between BEGIN and END entries. However, BEGIN and END should exist in the same file.
  3. Models are often defined in separate files, and the block (BEGIN - END) contains only INCLUDE entries. It is possible to duplicate a single part by including the same file(s) in different BEGIN-END blocks.
  4. In case of partitioned (PART) superelement (TYPE = SUPER), the Bulk Data Section can be divided into separate sections for each PART. This division is accomplished by using the BEGIN SUPER entry. These separate sections of the Bulk Data are self-contained and each section contains all geometry, elements, properties, constraints and loading data for that component of the model. Note that there is no entry to mark the ending of a superelement.
  5. There can be multiple sections of arbitrary beam data; one for each beam section.
  6. An example set of data for the definition of an arbitrary beam section is as follows:
    BEGIN,HYPRBEAM,SQUARE
$
GRIDS,1,0.0,0.0
GRIDS,2,1.0,0.0
GRIDS,3,1.0,1.0
GRIDS,4,0.0,1.0
$
CSEC2,10,100,1,2
CSEC2,20,100,2,3
CSEC2,30,100,3,4
CSEC2,40,100,4,1
$
PSEC,100,1000,0.1
$
END,HYPRBEAM