Batch script: Script syntax

Warning:

Support for batch script is maintained solely for historical reasons. The preferred way to specify variations on a base data file is to use text data files, specifically variation models. The OrcaFlex spreadsheet offers a facility to generate these text data files.

An OrcaFlex batch script is made up of commands, which are obeyed sequentially, and comments, which are ignored. A comment is a line that is either blank or on which the first non-blank characters are "//". A command can be:

A directive followed by one or more arguments, optionally separated by white space (one or more spaces or tabs). For example, load c:\temp\test.dat, where load is the directive and c:\temp\test.dat is the argument.
An assignment of the form DataName=value, again with optional white space separators. For example: Length = 55.0.

Note that:

Directives, data names, and object names are all case independent.
If your script includes a relative file name then it is taken to be relative to the directory from which the script was loaded.
File names, arguments, variables or values containing spaces or non-alphanumeric characters must be enclosed in single or double quotes and they must not contain the same quote character as is used to enclose them. For example '6" pipe' and "200' riser" are valid, but the following are not valid:

6 inch pipe – contains spaces, so needs to be enclosed in quotes;

6"pipe – contains a double quote, so needs to be enclosed in single quotes;

'6' pipe' – contains a single quote, so needs to be enclosed in double quotes instead of single.