Skip to content

Nastran parser does not handle newer ANSA conventions

Although the Nastran format does not support names for shells etc, both Hypermesh and ANSA have their own conventions for using/misusing comments to convey that extra information. The nastran parser needs an update to handle the newer ANSA conventions that are now circulating. The benefit is that this will allow more direct use of Nastran surface files elsewhere (eg, snappy).

cross-ref EP2299

@martin.lichtmes

Some notes (courtesy Martin Lichtmes)

Type 1 - ANSA 19.0.1:

Region names contained in comment line immediately above respective PSHELL line.

  • Header info:
    ANSA version Output format specification [MSC|NX|AUTODESK] (no effect on file content detected)

  • Footer info:
    $ANSA_NAME_COMMENTS etc. but not relevant for region naming PSHELL info: Region names in commentary line immediately above (single string)

Type 2 - ANSA 23.1.0:

Region names contained in footer section as part of $ANSA_NAME_COMMENT (fourth semicolon-separated entry).

  • Header info:
    ANSA version Output format specification [MSC|NX|AUTODESK] (no effect on file content detected)
  • Footer info:
    $ANSA_NAME_COMMENT relevant for region naming PSHELL info: No relevant/commentary information for region naming

Type 3 - Possibly ANSA/unknown:

Region names contained in comment line immediately above respective PSHELL line.

  • Header info: None
  • Footer info: None

PSHELL info: Region names in commentary line immediately above (single string)

Edited by Mark OLESEN