Difference between revisions of "Description Command"

From OSUPDOCS
Jump to navigation Jump to search
Line 20: Line 20:
; <tt>Comment #1,#2,...</tt>
; <tt>Comment #1,#2,...</tt>
: Enter any number of arguments. The arguments are evaluated (and they may be expressions) and placed in the analysis description after the word "Comment:".
: Enter any number of arguments. The arguments are evaluated (and they may be expressions) and placed in the analysis description after the word "Comment:".
; <tt>Header</tt>
; <tt>Header ... EndHeader</tt>
: Enter any number of lines of free-format text to describe the simulations and end the description with an <tt>EndHeader</tt> command. For example:
: Enter any number of lines of free-format text to describe the simulations and end the description with an <tt>EndHeader</tt> command. For example:
  Header
  Header

Revision as of 10:24, 25 May 2013

It is good practice to annotate MPM and FEA command files with a description of the calculations being created.

XML Input Files

In XML input files, a Description block can contain any free-format text description of the analysis:

<Description>
This simulation will be a 3D analysis of a high-speed impact
on an inclined plate.
</Description>

Scripted Input Files

In scripted input files, you build the description by using multiple commands for common elements that belong in a good analysis description. The commands are:

Title #1
Give one-line title for the calculations in #1.
Name #1
Enter you name in #1.
Comment #1,#2,...
Enter any number of arguments. The arguments are evaluated (and they may be expressions) and placed in the analysis description after the word "Comment:".
Header ... EndHeader
Enter any number of lines of free-format text to describe the simulations and end the description with an EndHeader command. For example:
Header
This simulation will be a 3D analysis of a high-speed impact
on an inclined plate.
EndHeader