# END

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

## Format

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
END TYPE NAME

## Example

(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
END FEMODEL Bumper
(1) (2) (3) (4) (5) (6) (7) (8) (9) (10)
END HYPRBEAM Square

## Definitions

Field Contents SI Unit Example
TYPE Specifies the entity type that will be defined by the END Data Entry.
HYPRBEAM
Data required for the definition of an arbitrary beam section will be specified between the BEGIN and END 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.

NAME This field specifies the name of the entity that is defined by the END entry.

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

(Character String)

1. The BEGIN and END Bulk Data Entries can be used in conjunction to define a part within the full model (for TYPE = FEMODEL).
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. There can be multiple sections of arbitrary beam data; one for each beam section.
5. An example set of data for the definition of an arbitrary beam section is:
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