PRIMER 22.1

Mixing Small, I10 and Large Format Files within a Model

Mixing Small, I10 and Large Format Files within a Model

Ansys LS-DYNA permits a model to be made up of master and include files using a mixture of small, i10 and large formats, but the syntax and rules are not totally intuitive.

Ansys LS-DYNA rules for reading decks with files in mixed formats.
Rule 1 The format of the master deck is the "default format" for the whole model, including all include files. It is presumed that all include files will be in the same format as the master file unless one of the suffices defined under "rule 2" is used.
  • PRIMER obeys the same rule by default, however unlike Ansys LS-DYNA it inspects any "long=.." or "i10=.." suffix on the *KEYWORD line of an include file, allowing this to supersede any inherited format.
  • PRIMER also writes "long=y" or "i10=y" suffices on the *KEYWORD card of child include files unconditionally if their format is Large or I10.
  • If the child is Small format but the parent file is not PRIMER will add a "long=s" suffix to the *KEYWORD card in the child file to reinforce the point
Rule 2 If an include file is in a format other than this "default format" then its *INCLUDE statement must have one of the following suffices:
% Include file is in I10 format
+ Include file is in Large format
- Include file is in Small format

This is true even if the *KEYWORD card in the child include file has a "long=xx" or "i10=xx" suffix.
Ansys LS-DYNA ignores any such suffix in include files, making the *INCLUDE suffix mandatory.

  • PRIMER does not ignore suffices on *KEYWORD in include files. If they are found they dictate the format of the file
Rule 3 If an *INCLUDE card has a "%", "+" or "-" suffix then all the data on that card must be written in that format.

For example if a parent file is in large format and a transformed child is in small format the correct syntax in the parent is

*INCLUDE_TRANSFORM -
Small format filename
Offsets etc in 8I10 format
Further data in 10 wide fields

This is consistent with the rule that using these suffices on a *keyword alters the format of data on that keyword, but it is not immediately obvious that a parent keyword requiring this suffix to read a child include file in a different format must also format its "own" data in the format of the child.

PRIMER has "Keep existing" and "Automatic" format modes which can potentially lead to different files being written in different formats. If this occurs it will generate output decks obeying the rules above.


Previous | Next