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.

55 ORBITAL MERGING 376<br />

MOVE command. Note, however, that the output vectors which have already been defined are<br />

not skipped as for MOVE.<br />

See also MOVE and EXTRA commands.<br />

55.4 Defining extra symmetries (EXTRA)<br />

EXTRA,exsym,orb1.sym1,orb2.sym2,orb3.sym3,ioff,fac,istart,iend<br />

Works exactly as MOVE, but only input vectors with extra symmetry exsym are considered.<br />

If orb1.sym1 and orb2.sym2 are zero, all input vectors are moved to the output set ordered<br />

according to increasing extra symmetries.<br />

Examples:<br />

EXTRA,1,-4.1<br />

will move the next 4 orbitals in symmetry 1 which have extra symmetry<br />

1. Orbitals which have been moved before are skipped.<br />

EXTRA,2,1.1 will move all orbitals of symmetry 1 which have extra symmetry 2.<br />

Orbitals which have been moved before are skipped.<br />

EXTRA<br />

EXTRA,3,1.1,0.8<br />

See also ADD and MOVE commands.<br />

will move all orbitals (all symmetries) and order them according to<br />

extra symmetries.<br />

Will move all orbitals which have extra symmetry 3 in all symmetries.<br />

Orbitals which have been moved before are skipped.<br />

55.5 Defining offsets in the output set (OFFSET)<br />

OFFSET,iof 1 ,iof 2 ,...,iof 8 ;<br />

Sets offsets in the output vector for symmetries 1 to 8. In subsequent MOVE or ADD commands,<br />

the input vectors are moved to the locations iof i +1 in the output vectors. The offset for individual<br />

ADD or MOVE commands can be modified by the parameter ioff on these cards. This card should<br />

immediately follow the orbital directive to which it applies. Generally, this card is only needed<br />

if the dimensions of input and output vectors are not identical.<br />

If the dimensions of the input orbital sets are smaller than the current basis dimension, the<br />

offsets are determined automatically in the following way: each time an orbital set is read in,<br />

the previous input orbital dimensions are added to the offsets. Hence, this works correctly if the<br />

orbital sets are given in the correct order and if the individual dimensions add up to the current<br />

total dimension. If this is not the case, the offsets should be specified on an OFFSET card which<br />

must follow the orbital directive.<br />

55.6 Projecting orbitals (PROJECT)<br />

PROJECT,namin.file<br />

This command will read vectors from record namin.file. These vectors must have the same dimension<br />

as those of the current calculation. All orbitals defined so far by the ORBITAL, MOVE,<br />

and ADD directives are projected out of the input set. The projected orbitals are then orthonormalized<br />

and moved to the undefined output vectors. This should always yield a complete set of<br />

vectors.

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

Saved successfully!

Ooh no, something went wrong!