Alneos/vega

Distinguishing OPTISTRUCT from NASTRAN in VEGA

Closed this issue · 1 comments

ThomasAbballe commented

A lot of NASTRAN files used in the industry don't come from NASTRAN but from other programs based on NASTRAN, like OPTISTRUCT. However, there are some differences between the OPTISTRUCT and the NASTRAN format. One, among others, is the default value of the SOL command: 101 for NASTRAN (meaning only static mechanical problems are available), 200 for OPTISTRUCT (all mechanical problems available).

VEGA read OPTISTRUCT file as NASTRAN ones and, of course, misunderstanding ensues. On our example, without SOL command, the dynamic problems are translated as static ones.

We should develop a way for VEGA to distinguish OPTISTRUCT files from NASTRAN files. A solution may be to treat OPTISTRUCT has a separate language, inherited (as in C++ inherited) from NASTRAN.

While awaiting developments, users should provide NASTRAN compatible files (i.e manually adding SOL 200 to their files, and so on)