Bulk Data Entry Defines scalar points.
Format
| (1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
| SPOINT |
ID1 |
ID2 |
ID3 |
ID4 |
ID5 |
ID6 |
ID7 |
ID8 |
|
Alternate Format
| (1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
| SPOINT |
ID1 |
"THRU" |
ID2 |
|
|
|
|
|
|
Example
| (1) |
(2) |
(3) |
(4) |
(5) |
(6) |
(7) |
(8) |
(9) |
(10) |
| SPOINT |
3 |
18 |
1 |
4 |
16 |
2 |
6 |
THRU |
|
| |
8 |
47 |
99 |
THRU |
128 |
|
|
|
|
Definitions
| Field |
Contents |
SI Unit Example |
| ID# |
Unique scalar point identification number. No default (0 >
Integer)
|
|
Comments
- A scalar point defined by its appearance
on the connection entry for a scalar element (see the CELAS,
CMASS, and CDAMP entries) does not need to
appear on an SPOINT entry.
- This entry is used primarily to define
scalar points appearing in single-point or multipoint constraint equations to which
no scalar elements are connected.
- If the alternate format is used, all
scalar points ID1 through ID2 are defined.
ID1 must be less than ID2.
- Alternate format can be combined with
regular format, and it can span across continuation lines.
- This card is represented as a node in
HyperMesh.