Beamsection Collectors and Beamsection

Beamsection Collectors

Beamsection collectors collect and organize beamsections and are used in HyperBeam to organize 1D beam section data.

Nastran Cards

Card Description
BELTS / Output activation and format/file selection for kinematic animation output.

Beamsections

Beamsection entities store 1D beam cross-section data.

Beamsections can be created from geometry, elements, or from solver standard sections, that is, I-Sections, H-Sections, and so on.

All sections can be created and modified in HyperBeam. Generic sections and Standard sections can also be created in the Model Browser and modified in the Entity Editor.

The default section type and attribute values assigned to the beamsection vary based on the solver interface.

On import, each 1D beam property card within a solver deck is automatically imported as a beamsection entity and a property entity with associated beamsection. The beamsection entity holds the 1D beam section data (A, I, and so on..., and/or Dimensions) and is associated to the property entity which has a 1D property card image. The beamsection association to a property is what transfers the 1D section data to the 1D property solver card for export. Editing of all 1D beam section data is accomplished through HyperBeam.

Generic Sections

Generic sections define sections without defining actual cross-section geometry. Areas, inertias, centroids, and other coefficients are supported directly through spreadsheet data entry of values.

Shell Sections

Shell sections define thin cross-sections with geometric lines or 1D elements. Once the cross-section is created, it can be further edited in HyperBeam.


Figure 1.

Solid Sections

Solid sections define solid cross-sections with surfaces, lines that form a closed loop, or 2D elements. Once the cross-section is created it can be further edited in the Entity Editor or HyperBeam.


Figure 2.

Standard Sections

Standard sections to define solver supported cross-sections. Each supported solver interface has a library of supported solver cross-sections. For standards sections, only the dimensions of the section are necessary as input.


Figure 3.