LOADLIB
I/O Options EntryUsed to define the external libraries and external files to be loaded into OptiStruct.
External functions can be implemented within dynamic libraries (.dll) under Windows, shared libraries (.so) under Linux, by using Altair Compose Open Matrix Language (.oml) on Windows, and external files by using Microsoft Excel (.xls or .xlsx) on Windows.
Format
LOADLIB = type, group, path
Definitions
| Argument | Options | Description |
|---|---|---|
| type | <DRESP3, MATUSR,
MATUSHT, QVOL,
PCONV, QBDY,
SPCD> No default |
Identifier that defines
the type of library or file to be loaded into OptiStruct.
|
| group | <Character string> No default |
group identifier that is referenced by a DRESP3, MATUSR, MATUSHT, PCONVLIB, QVOLLIB, QBDYLIB, or SPCDLIB Bulk Data Entry. |
| path | <Path including file
name and extension> No default |
The path to the external shared or dynamic library to be loaded. |
Comments
- Absolute paths (those starting with a drive letter or a slash) will be used as they are defined on the LOADLIB card. Relative library or file paths will be appended to the path corresponding to the input deck's location.
- The total length of information on this card is limited to 200 characters (including the card name and spaces between arguments). This data can be on a single line or span multiple continuation lines. Refer to I/O Options and Subcase Information Entries Guidelines for an example showing how to enter long file names on multiple lines.
- The application or external library to use is solely based on the file extension identified via the path argument.