19.01.2015 Views

MOLPRO

MOLPRO

MOLPRO

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

3 DEFINITION OF <strong>MOLPRO</strong> INPUT LANGUAGE 8<br />

Here START: is a label, and CCSD(T) is a command.<br />

Strings containing blanks can be entered using quotes. For instance, ’This is a string’<br />

is interpreted as one string, but This is a string is a sequence of four strings in four<br />

subsequent fields. Strings in quotes are not converted to upper case.<br />

Input lines may be concatenated using \ at the end of the line(s) to be continued. Any number<br />

of lines may be concatenated up to a total length of 1024 characters (only 500 characters are<br />

possible on older IBM systems).<br />

Filenames may be up to 31 characters long, provided that long filenames are supported by the<br />

Unix system used. An exception are older CRAY systems, which allow only 8 characters for<br />

the names of binary <strong>MOLPRO</strong> files.<br />

3.2 Commands<br />

A command invokes a particular program. It may be followed by local input for this program,<br />

enclosed in curley brackets 1<br />

The general format is either<br />

COMMAND, options<br />

or<br />

{ COMMAND,options<br />

directives<br />

data<br />

}<br />

Examples for commands are HF, MP2, CCSD(T), MCSCF, MRCI. Examples for directives<br />

are OCC, CLOSED, WF, PRINT. Directives can be in any order, unless otherwise<br />

noted. Data can follow certain directives. For the format of options, directives and data see<br />

subsections 3.3, 3.5, and 3.6, respectively.<br />

In the following, such a sequence of input will be denoted a command block. Special command<br />

blocks are the geometry and basis blocks.<br />

The options given on the command line may include any options relevant to the current program.<br />

For instance, in DF-LMP2-R12 this could be options for density fitting, local, explicit, and/or<br />

thresholds. Alternatively, options can be specified on individual directives like<br />

DFIT,options<br />

LOCAL,options<br />

EXPLICIT,options<br />

THRESH,options<br />

In these cases, only the options belong to the corresponding directive are valid; thus, if an option<br />

for EXPLICIT would be specified, e.g., on the DFIT directive, an error would result. This error<br />

would be detected already in the input prechecking stage.<br />

1 Depending on the parameter STRICTCHECK in file lib/variable.registry the program may tolerate<br />

directives given after commands without curley brackets. The program checks for ambiguities in the input. A<br />

directive is considered ambiguous if a command or procedure with the same name is known, and the directive<br />

is not in a command block (i.e., no curley brackets are used). STRICTCHECK=0: The input checker tolerates<br />

ambiguous directives if they a are followed by a non ambiguous directive which is valid for the current command.<br />

STRICTCHECK=1: The input checker does not tolerate any ambiguous directives. STRICTCHECK=2: The input<br />

checker does not tolerate any directives outside curley brackets. The default is STRICTCHECK=0, which gives the<br />

maximum possible compatibility to previous Molpro versions.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!