ACCEL– Acceleration for Load
The ACCEL Bulk Data Entry can be used to define acceleration loads to all grids in the model. These loads can vary over sections of the model. The locations of the acceleration loads can be defined at specific locations (LOCi) along a particular direction (DIR).
(1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
ACCEL |
SID |
CID |
N1 |
N2 |
N3 |
DIR |
|
|
|
|
LOC1 |
VAL1 |
LOC2 |
VAL2 |
... |
|
|
|
|
|
Field |
Contents |
SID |
Acceleration load set identification number. (Integer > 0) |
CID |
Coordinate system identification number. = 0: references the basic coordinate system Default = 0 (Integer > 0, or blank) |
N1,N2,N3 |
Acceleration load vector components in the coordinate system CID. (Real, a minimum of one Ni should not be set to 0.0) |
DIR |
Component direction of the acceleration load variation (Character; one of X, Y, or Z) |
LOCi |
Location of the scale factor to the applied acceleration load along direction DIR in the coordinate system CID. (Real) |
VALi |
Load scale factor at the location LOCi (Real) |
1. | The acceleration load applied to all grid points in the model is given by: |
Where, a is the acceleration load and N is a vector with components N1, N2, and N3.
The scale factor VAL for each grid in the model is automatically determined by linear interpolation between VALi for the DIR component of the corresponding LOCi between which the required grid point lies. If the GRID point’s DIR coordinate in the coordinate system CID is outside the range specified by LOCi, the corresponding VAL is determined either from VAL1 or VALn (Figure 1). A minimum of two pairs of (LOCi and VALi) should be specified.
Figure 1: Acceleration Load Factor (VAL) vs Location along DIR (LOC)
2. | The acceleration loads specified in the ACCEL entry can be combined with other loads, such as FORCE, MOMENT, GRAV, ACCEL1, and ACCEL2, through the LOAD Subcase Information Entry. The SID on the ACCEL entry should be unique with regard to any other load entry. |
3. | The acceleration load does not include effects, due to mass on SPOINTs. |
4. | This card is represented as a force load in HyperMesh. |