19.01.2015 Views

MOLPRO

MOLPRO

MOLPRO

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

8 VARIABLES 45<br />

LENBUF length of integral buffer (file 1)<br />

NTR<br />

LTR<br />

NCACHE<br />

IASYN<br />

MXMBLK<br />

MXMBLN<br />

NCPUS<br />

MINBR1<br />

length of integral records (must be multiple of 3·ltrack)<br />

disk sector length assumed in CI (default 1 is reasonable)<br />

machine cache size in bytes<br />

if nonzero, use asynchronous I/O on CONVEX<br />

column/row block size for mxma<br />

link block size for mxma<br />

maximum number of cpus to be used in multitasking<br />

min number of floating point ops per processor<br />

MXDMP highest file number to be treated as dump file with full functionality (1 ≤ .<br />

MXDMP≤ .3).<br />

The MXDMP option is for experts only! This prevents basis and geometry information from<br />

being written to dump files with higher file number than the given value, and can sometimes be<br />

useful for counterpoise corrected geometry optimizations. Note that some functionality is lost<br />

by giving this option, and errors will result unless all input is correct!<br />

8 VARIABLES<br />

Data may be stored in variables. A variable can be of type string, real or logical, depending on<br />

the type of the expression in its definition. Any sequence of characters which is not recognized<br />

as expression or variable is treated as string. In this section, we will discuss only real and logical<br />

variables. String variables will be discussed in more detail in section 8.3. Variables can be used<br />

anywhere in the input, but they can be set only outside the input blocks for specific programs.<br />

For example, if a variable is used within the input block for HF, it must have been set before the<br />

HF{...} input block.<br />

<strong>MOLPRO</strong> automatically stores various results and data in system variables (see section 8.8.1),<br />

which can be used for further processing. A new feature of <strong>MOLPRO</strong>2002 is that most system<br />

variables are write protected and cannot be overwritten by the user. The input is automatically<br />

checked before the job starts, and should a system variable be set in the input the job will stop<br />

immediately with an error message. Only in some exceptions (see section 8.4), system variables<br />

can be modified using the SET command (but not with the simple NAME=value syntax). Note<br />

that due to the changed usage and syntax of the SET command, compatibility with <strong>MOLPRO</strong>92<br />

input syntax is no longer maintained.<br />

8.1 Setting variables<br />

A variable can be defined using<br />

variable1=value1, variable2=value2, . . .<br />

A variable definition is recognized by the equals sign in the first field of the input card. For<br />

example,<br />

THRESH,ENERGY=1.d-8,GRADIENT=1.d-5<br />

does not define variables; here ENERGY and GRADIENT are options for the THRESH directive.<br />

Variables can have different types:

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

Saved successfully!

Ooh no, something went wrong!