1.7. Major Scope Definitions for an Input File
The typical input file will have the structure shown in the two examples below. The major scopes – SIERRA, procedure, and region – are delineated with input lines for command blocks. Comment lines are included that indicate some of the key scopes that will appear within the major scopes. Note the indentation used to clarify scopes. An example of the structure an explicit dynamic (Presto) input file is shown:
BEGIN SIERRA <string>some_name
#
# All command blocks and command lines in the SIERRA
# scope appear here. The PROCEDURE PRESTO command
# block is the beginning of the next scope.
#
# function definitions
# material descriptions
# description of mesh file
#
BEGIN PRESTO PROCEDURE <string>procedure_name
#
# time step control
#
BEGIN PRESTO REGION <string>region_name
#
# All command blocks and command lines in the
# region scope appear here
#
# specification for output of result
# specification for restart
# boundary conditions
# definition of contact
#
END [PRESTO REGION <string>region_name]
END [PRESTO PROCEDURE <string>procedure_name]
END [SIERRA <string>some_name]
This is an example of an implicit (Adagio) input file:
BEGIN SIERRA <string>some_name
#
# All command blocks and command lines in the SIERRA
# scope appear here. The PROCEDURE ADAGIO command
# block is the beginning of the next scope.
#
# function definitions
# material descriptions
# description of mesh file
#
BEGIN ADAGIO PROCEDURE <string>procedure_name
#
# time step control
#
BEGIN ADAGIO REGION <string>region_name
#
# All command blocks and command lines in the
# region scope appear here
#
# solver commands
# specification for output of result
# specification for restart
# boundary conditions
# definition of contact
#
END [ADAGIO REGION <string>region_name]
END [ADAGIO PROCEDURE <string>procedure_name]
END [SIERRA <string>some_name]