GAMESS-UK now contains two separate modules for performing Table-CI calculations, the original Conventional module that involves explicit storage of the CI hamiltonian on disk, and a new, semi-direct module that avoids explicit storage of the hamiltonian, and is capable of handling significantly larger secular problems. While the Conventional module will ultimately be phased out, our intention at this stage is to support both, so that the data requirements and file handling characteristics of both are described below.
Table-CI calculations are performed under control of the RUNTYPE CI specification, with data input characterising the nature of the CI introduced by a data line with the keyword MRDCI in the first data field. Termination of this data is accomplished by presenting a valid Class 2 directive, such as VECTORS or ENTER.
Before detailing example data files for performing both Conventional and Semi-direct Table-CI calculations on the X1A1 state of formaldehyde, we mention some general points on conducting such calculations.
A crucial requirement in running the Table-CI modules is an understanding of the treatment of symmetry. Unlike the SCF and direct-CI modules, the molecular orbitals are automatically reordered at the outset of the CI into groups belonging to the same irreducible representation, with the ordering within each group dictated by the ordering encountered at orbital generation time (i.e. at SCF time). Note that each representation has an associated index number e.g. in a system of C2v symmetry the four representations a1, b1, b2 and a2 have associated index numbers of 1,2 3 and 4 respectively. Groups of orbitals of common representation are ordered by virtue of increasing representation sequence number, so that in a C2v system all molecular orbitals of a1 symmetry would occur first in the list (with the occupied orbitals preceding the virtual orbitals in the subset), followed by the orbitals of b1 symmetry (again with the DOMOS preceding the VMOS), followed by orbitals of b2 symmetry (DOMOS before VMOS) and finally, orbitals of a2 symmetry. Any subsequent reference to the orbitals, for example when specifying the reference functions, must be in this revised numbering scheme. Let us consider an example to try and clarify this point. Consider again the output from the closed shell SCF calculation on H2CO, in particular the symmetry adapted basis set information,
=============================
IRREP NO. OF SYMMETRY ADAPTED
BASIS FUNCTIONS
=============================
1 12
2 4
3 6
=============================
and the list of MOs printed at convergence:
===============================================
M.O. IRREP ORBITAL ENERGY ORBITAL OCCUPANCY
===============================================
1 1 -20.48275080 2.0000000
2 1 -11.28286952 2.0000000
3 1 -1.40833443 2.0000000
4 1 -0.86648626 2.0000000
5 3 -0.69818828 2.0000000
6 1 -0.63034883 2.0000000
7 2 -0.52027278 2.0000000
8 3 -0.43433094 2.0000000
9 2 0.14397469 0.0000000
10 1 0.27419771 0.0000000
11 3 0.36740523 0.0000000
12 1 0.45123743 0.0000000
13 2 0.93266602 0.0000000
14 3 1.02032602 0.0000000
15 1 1.02498516 0.0000000
16 1 1.14613786 0.0000000
17 3 1.27971217 0.0000000
18 1 1.57176247 0.0000000
19 2 1.86744709 0.0000000
20 1 1.91087974 0.0000000
21 3 1.98262324 0.0000000
22 1 3.31460342 0.0000000
===============================================
Based on the reordering scheme outlined above, the table below outlines
the sequence numbers of the MOs both prior to and after reordering.
Note that a list of irreducible representations (IRreps) and their
associated indices for each of the abelian point groups are given in
Table 7. With the molecular orbitals reordered thus, the
user must apply the revised numbering scheme in specification of, for
example, the reference configurations. Thus consider the SCF
configuration for H2CO in terms of the doubly occupied SCF
m.o.s:
| m.o. | 1a1 | 2a1 | 3a1 | 4a1 | 1b2 | 5a1 | 1b1 | 2b2 |
| SCF ordering | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
| Table ordering | 1 | 2 | 3 | 4 | 17 | 5 | 13 | 18 |
1 2 3 4 5 13 17 18
would define the SCF configuration for H2CO. Note that an
additional integer is required in specifying the number of open-shell
orbitals (NONO, non-identically coupled orbitals) in each function.
This value is specified first in the CONF data sequence, and would
typically be followed by a sequence of NONO integers defining the
orbitals in question. In the present case NONO is zero, as all m.o.s
are doubly occupied, so that the full CONF data line would be:
0 1 2 3 4 5 13 17 18
| IRrep | IRrep | SCF Sequence | Table-CI | Occupation |
| No. | No. | Sequence No. | No. | |
| a1 | 1 | 1 | 1 | 2.0 |
| 2 | 2 | 2.0 | ||
| 3 | 3 | 2.0 | ||
| 4 | 4 | 2.0 | ||
| 6 | 5 | 2.0 | ||
| 10 | 6 | 0.0 | ||
| 12 | 7 | 0.0 | ||
| 15 | 8 | 0.0 | ||
| 16 | 9 | 0.0 | ||
| 18 | 10 | 0.0 | ||
| 20 | 11 | 0.0 | ||
| 22 | 12 | 0.0 | ||
| b1 | 2 | 7 | 13 | 2.0 |
| 9 | 14 | 0.0 | ||
| 13 | 15 | 0.0 | ||
| 19 | 16 | 0.0 | ||
| b2 | 3 | 5 | 17 | 2.0 |
| 8 | 18 | 2.0 | ||
| 11 | 19 | 0.0 | ||
| 14 | 20 | 0.0 | ||
| 17 | 21 | 0.0 | ||
| 21 | 22 | 0.0 |
| 1a122a123a124a121b22(5a16a1)(1b12b1)2b22 | (1) |
4 5 6 13 14 1 2 3 4 17 18where the four orbitals, 5(5a1), 6(6a1), 13(1b1) and 14(2b1) precede the doubly occupied orbitals in the list.
| Point Group | IRrep | Sequence No. |
| Cs | a' | 1 |
| a'' | 2 | |
| C2 | a | 1 |
| b | 2 | |
| Ci | ag | 1 |
| au | 2 | |
| C2v | a1 | 1 |
| b1 | 2 | |
| b2 | 3 | |
| a2 | 4 | |
| C2h | ag | 1 |
| au | 2 | |
| bu | 3 | |
| bg | 4 | |
| D2h | ag | 1 |
| b3u | 2 | |
| b2u | 3 | |
| b1g | 4 | |
| b1u | 5 | |
| b2g | 6 | |
| b3g | 7 | |
| au | 8 |
There is a formal limit of 200,000 selected configurations derived from an initial list of configurations generated by single plus double excitations from a user-specified list of reference functions. The selection and extrapolation procedure may be applied on up to twenty roots of a given secular problem.
.
.
MRDCI
ADAPT
TRAN
TABLE
SELECT
CI
DIAG
.
.
would be typical of that required when the user is explicitly
constructing the TABLE data set in a given run of the program. Since
TABLE generation is somewhat expensive, it will be more usual for the
user to allocate a pre-generated version of the data set prior to
executing the Table-CI modules. This allocation process and detailed
locations of TABLE are, of course, machine specific, and will be
outlined at the appropriate points in Parts 12-16 of the Manual. In
this case the TABLE data line is simply omitted from the data sequence
shown above, thus:
.
.
MRDCI
ADAPT
TRAN
SELECT
CI
DIAG
.
.
Note that failure to correctly allocate TABLE when using the
above sequence will lead to an error condition.
SUPER OFF NOSYM
in the SCF run.
| File | Contents | Generated by | Required by |
| Sub-Module | Sub-Module | ||
| FTN022 | Symmetry Adapted Integrals | ADAPT | TRAN |
| FTN031 | Transformed Integrals | TRAN | SELECT, CI |
| FTN033 | Partial Matrix Elements | SELECT | CI |
| FTN034 | Partial Matrix Elements | SELECT | CI |
| FTN035 | CI Hamiltonian | CI | DIAG |
| FTN036 | CI Vectors | DIAG | NATORB |
| PROP, TM |
A Conventional Table-CI calculation is to performed on the formaldehyde molecule, using the SCF configuration as the sole reference function. A valid data sequence for performing such a calculation is shown below.
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 1M/1R
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT
TRAN
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
ROOTS 1
THRESH 30 10
CI
DIAG
EXTRAP 2
ENTER
The following points should be noted:
The sequence of data lines defining the Conventional Table-CI calculation is terminated by the VECTORS directive. Let us now consider a Conventional Table-CI calculation on the 2B2 state of H2CO+, again using the SCF configuration as the sole reference function. A valid data sequence for performing such a calculation is shown below, where we are still performing all the computation in a single job.
TITLE
H2CO+ - 2B2 - 3-21G CISD TABLE-CI CALCULATION
CHARGE 1
MULT 2
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT
TRAN 5
SELECT
SYMMETRY 3
SPIN 2
CNTRL 15
SINGLES 1
CONF
1 18 1 2 3 4 5 13 17
ROOTS 1
THRESH 30 10
CI
DIAG
EXTRAP 2
ENTER
Considering the changes to the closed-shell run, the following points
should be noted:
Run I: The SCF Job
TITLE
H2CO - 3-21G SCF PRIOR TO TABLE-CI CALCULATION
SUPER OFF NOSYM
ZMATRIX ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
ENTER
The only obvious point to note is the use of the SUPER directive in
requesting full integral list generation required in the subsequent
symmetry adaption and integral transformation.
Run II: The Table-CI Job
RESTART
TITLE
H2CO - 3-21G TABLE-CI 1M/1R
SUPER OFF NOSYM
BYPASS SCF
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT
TRAN
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
ROOTS 1
THRESH 30 10
CI
DIAG
EXTRAP 2
ENTER
Considering the changes to the complete run, the following points should be noted:
Run IIa: The Transformation Job
RESTART
TITLE
H2CO - 3-21G TABLE-CI 1M/1R -TRANSFORMATION
SUPER OFF NOSYM
BYPASS SCF
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT
TRAN
SELECT BYPASS
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
ROOTS 1
THRESH 30 10
CI BYPASS
DIAG BYPASS
EXTRAP 2
ENTER
Thus BYPASS is appended to the data lines requesting those
Table-CI sub-modules (SELECT, CI and DIAG)
to deactivate the associated
processing.
Run IIb: The Table-CI Job
RESTART
TITLE
H2CO - 3-21G TABLE-CI 1M/1R - SELECTION AND CI
SUPER OFF NOSYM
BYPASS SCF
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT BYPASS
TRAN BYPASS
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
ROOTS 1
THRESH 30 10
CI
DIAG
EXTRAP 2
ENTER
Now BYPASS is appended to both the ADAPT and TRAN data lines, since the
associated processing has been completed in the previous job.
In the examples above we have assumed that all MOs, typically generated at SCF time, are active in the subsequent CI calculation. In many instances however this will not be the case, for the user may wish to
TRAN CORE DISCARD
2 0 0 0 ... core MOs
1 2
1 0 1 0 ... discarded MOs
12 6
where two additional data lines are associated with each category, the
first specifying the number of orbitals within each IRrep, the
second the sequence number of the orbitals in question. Note again that
the sequence numbers refer to the numbering within each IRrep.
Thus if we were to also freeze the 1b2 orbital, the revised TRAN
data would appear as follows:
TRAN CORE DISCARD
2 0 1 0 ... core MOs
1 2 1
1 0 1 0 ... discarded MOs
12 6
Before detailing the Table-CI data, we should mention that the revised
numbering scheme used in the specification of, for example, the
reference configurations is that in effect after the freezing and
discarding of orbitals. Having effectively removed three orbitals of
a1 symmetry and one of b2 from the subsequent CI, the table
below presents the final orbital numbering to be used in CONF
specification:
| IRrep | IRrep | SCF Sequence | Table-CI | Occupation |
| No. | No. | Sequence No. | No. | |
| a1 | 1 | 3 | 1 | 2.0 |
| 4 | 2 | 2.0 | ||
| 6 | 3 | 2.0 | ||
| 10 | 4 | 0.0 | ||
| 12 | 5 | 0.0 | ||
| 15 | 6 | 0.0 | ||
| 16 | 7 | 0.0 | ||
| 18 | 8 | 0.0 | ||
| 20 | 9 | 0.0 | ||
| b1 | 2 | 7 | 10 | 2.0 |
| 9 | 11 | 0.0 | ||
| 13 | 12 | 0.0 | ||
| 19 | 13 | 0.0 | ||
| b2 | 3 | 5 | 14 | 2.0 |
| 8 | 15 | 2.0 | ||
| 11 | 16 | 0.0 | ||
| 14 | 17 | 0.0 | ||
| 17 | 18 | 0.0 |
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 1M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT
TRAN CORE DISCARD
2 0 0 0
1 2
1 0 1 0
12 6
SELECT
SYMMETRY 1
SPIN 1
CNTRL 12
SINGLES 1
CONF
0 1 2 3 10 14 15
ROOTS 1
THRESH 30 10
CI
DIAG
EXTRAP 2
ENTER
The following points should be noted:
Specification of additional reference functions in the Table-CI input data is accomplished through the CONF directive, with each reference function characterised by an additional data line of integers defining
| Reference | 1a1 | 2a1 | 3a1 | 4a1 | 1b2 | 5a1 | 1b1 | 2b2 | 2b1 | 3b2 |
| Function | ||||||||||
| 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 |
| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 2 | 2 | 0 |
| 3 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 2 |
| 4 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 |
CONF
0 1 2 3 4 5 13 17 18 .. Ref.1
0 1 2 3 4 5 14 17 18 .. Ref.2
0 1 2 3 4 5 13 17 19 .. Ref.3
4 13 14 18 19 1 2 3 4 5 17 .. Ref.4
The full data input for the job would be as follows:
RESTART
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT
TRAN
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
ROOTS 1
THRESH 30 10
CI
DIAG
EXTRAP 2
ENTER
.
.
MRDCI
ADAPT
TRAN
SELECT
CI
DIAG
.
.
In practice the SELECT module will always require input,
characterising for example the nature of the reference
configurations, selection attributes etc, but in many instances the
defaults of the other sub-modules will hold so that the associated
data input may be omitted. Clearly this omission of data
requires a firm understanding of the defaults in effect, which
will only be apparent after the detailed description
of directives presented in section 5. For the moment we illustrate
this by considering the simplified data file for the
multi-reference calculation on H2CO above:
RESTART
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
SELECT
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
ENTER
The following points should be noted:
In the examples considered above, we have assumed that the Table-CI job completes in the time allocated. This may not be the case and we need consider restarting the computation in a controlled fashion. Such a requirement may be met in RUNTYPE CI processing when:
Adaptation and Transformation
RESTART CI
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
SELECT BYPASS
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
CI BYPASS
DIAG BYPASS
ENTER
Selection and Hamiltonian Construction
RESTART CI
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT BYPASS
TRAN BYPASS
SELECT
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
DIAG BYPASS
ENTER
Diagonalisation
RESTART CI
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
ADAPT BYPASS
TRAN BYPASS
SELECT BYPASS
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
CI BYPASS
ENTER
The formal limits that apply to conventional calculations are significantly extended in the semi-direct module. There is now a limit of 800,000 selected configurations derived from an initial list of configurations generated by single plus double excitations from a user-specified list of reference functions, the number of which may not exceed 256. The selection and extrapolation procedure may now be applied on up to thirty roots of a given secular problem.
Semi-direct Table-CI calculations are performed under control of the RUNTYPE CI specification, with data input characterising the nature of the CI introduced by a data line with the keyword MRDCI in the first data field and the keyword DIRECT in the second field. Termination of this data is again accomplished by presenting a valid Class 2 directive, such as VECTORS or ENTER.
Note that while the Conventional and Semi-direct modules are based on the same Table-CI algorithm, there are significant differences in both file utilisation and data requirements. The most significant of these are highlighted below:
.
.
MRDCI DIRECT
TABLE
SELECT
CI
NATORB
.
.
would be typical of that required when the user is explicitly
constructing the TABLE data set in a given run of the program. This is
now the recommended route in semi-direct calculations, rather than the
user allocating a pre-generated version of the data set prior to
executing the Table-CI modules. Note that failure to correctly
allocate table-ci when using the above sequence will lead to an error
condition.
SUPER OFF NOSYM
in the SCF run.
| File | Contents | Generated by | Required by |
| Sub-Module | Sub-Module | ||
| FTN031 | Transformed | Transformation | SELECT, CI |
| Integrals | module | ||
| FTN033 | Partial Matrix Elements | SELECT | CI |
| FTN034 | Partial Matrix Elements | SELECT | CI |
| FTN042 | Zero-order vectors | SELECT | CI |
| FTN012 | Configuration data | SELECT | CI |
| FTN036 | CI Vectors | CI | NATORB |
| PROP, TM |
Note again that specification of additional reference functions in the Table-CI input data is again accomplished through the CONF directive; in contrast to CONF specification in the conventional module, however, the data lines specifying the configurations are now terminated by a single data line containing the character string END in the first data field. Each reference function is characterised by an additional data line of integers defining
| Reference | 1a1 | 2a1 | 3a1 | 4a1 | 1b2 | 5a1 | 1b1 | 2b2 | 2b1 | 3b2 |
| Function | ||||||||||
| 1 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 |
| 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 2 | 2 | 0 |
| 3 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 0 | 0 | 2 |
| 4 | 2 | 2 | 2 | 2 | 2 | 2 | 1 | 1 | 1 | 1 |
CONF
0 1 2 3 4 5 13 17 18 .. Ref.1
0 1 2 3 4 5 14 17 18 .. Ref.2
0 1 2 3 4 5 13 17 19 .. Ref.3
4 13 14 18 19 1 2 3 4 5 17 .. Ref.4
END .. the directive terminator
The full data input for the job would be as follows:
TITLE
H2CO - 3-21G BASIS - semi-direct MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES ALL
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
ROOTS 1
THRESH 2 2
CI
NATORB
ENTER
Now let us consider performing the closed-shell calculation above in a
sequence of jobs, where the first job carries out the SCF, the second
the Table-CI calculation. Valid data sequences for performing the
calculation are shown below.
Run I: The SCF Job
TITLE
H2CO - 3-21G SCF PRIOR TO TABLE-CI CALCULATION
SUPER OFF NOSYM
ZMATRIX ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
ENTER
The only obvious point to note is the use of the SUPER directive in
requesting full integral list generation required in the subsequent
symmetry adaption and integral transformation.
Run II: The Table-CI Job
RESTART
TITLE
H2CO - 3-21G BASIS - semi-direct MRDCI 4M/1R
SUPER OFF NOSYM
BYPASS SCF
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES ALL
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
ROOTS 1
THRESH 2 2
CI
NATORB
ENTER
Considering the changes to the complete run, the following points
should be noted:
Run IIa: The Transformation Job
RESTART
TITLE
H2CO - 3-21G TABLE-CI 4M/1R -TRANSFORMATION
SUPER OFF NOSYM
BYPASS SCF
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
TABLE BYPASS
SELECT BYPASS
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES ALL
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
ROOTS 1
THRESH 2 2
CI BYPASS
NATORB BYPASS
ENTER
Thus BYPASS is appended to the data lines requesting those
Table-CI sub-modules (SELECT, CI and NATORB) to deactivate the associated
processing.
Run IIb: The Table-CI Job
RESTART
TITLE
H2CO - 3-21G TABLE-CI 4M/1R - SELECTION AND CI
SUPER OFF NOSYM
BYPASS SCF TRAN
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 16
SINGLES ALL
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
ROOTS 1
THRESH 2 2
CI
NATORB
ENTER
Now that TRAN is now appended to the BYPASS directive
since the associated processing has been completed in the
previous job.
In order to simplify the process of configuration specification and data preparation, the semi-direct module now provides a set of default options that require little or no data input. While these defaults are not expected to cover most in-depth requirements, they do provide a starting point for users, and a route to subsequent, more extensive calculations. To illustrate this default working of the module, we consider below a number of example calculations.
A Semi-direct Table-CI calculation is to performed on the formaldehyde molecule. Given the following data sequence:
TITLE
H2CO - 3-21G DEFAULT TABLE-CI OPTIONS
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
ENTER
then the calculation undertaken will be based on the following;
numbers of open shells and corresponding main configurations 0 1 2 3 4 5 13 17 18 .. SCF configuration 0 1 2 3 4 6 13 17 18 .. 5a1 -> 6a1 double 2 5 6 1 2 3 4 13 17 18 .. 5a1 -> 6a1 single 0 1 2 3 4 5 14 17 18 .. 1b1 -> 2b1 double 2 13 14 1 2 3 4 5 17 18 .. 1b1 -> 2b1 single 0 1 2 3 4 5 13 17 19 .. 2b2 -> 3b2 double 2 18 19 1 2 3 4 5 13 17 .. 2b2 -> 3b2 single
THRESH 10 10
ROOTS 1
Thus this default selection process involves construction of an explicit
zero-order Hamiltonian H0 (over the reference functions described
above) followed by perturbative selection of configurations with
respect to the lowest root of H0. The minimum threshold to be
used in selection (Tmin) is 10 micro-Hartree, with an increment of
10 uH to be used in defining the higher-threshold case to be solved in
the process of extrapolation [39].
The sequence of data lines defining the Semi-direct Table-CI calculation is terminated by the VECTORS directive. Note at this stage that the full data specification corresponding to the defaults generated from the above data file is as follows:
TITLE
H2CO - 3-21G - EXPLICIT DATA FOR DEFAULT MRDCI SETTINGS -113.43885803
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
ACTIVE
1 TO 22 END
MRDCI DIRECT
TABLE
SELECT
CNTRL 16
SPIN 1
SYMM 1
SINGLES ALL
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 6 13 17 18
2 5 6 1 2 3 4 13 17 18
0 1 2 3 4 5 14 17 18
2 13 14 1 2 3 4 5 17 18
0 1 2 3 4 5 13 17 19
2 18 19 1 2 3 4 5 13 17
END
THRESH 10 10
ROOTS 1
CI
NATORB
CIVEC 1
ENTER
Let us now consider a Semi-direct Table-CI calculation on the 2B2 state of H2CO+, again using default options available within the module. A valid data sequence for performing such a calculation is shown below, where we are still performing all the computation in a single job.
TITLE
H2CO+ 2B2 3-21G - DEFAULT MRDCI SETTINGS -113.06446075
MULT 2
CHARGE 1
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
ENTER
Considering the changes to the closed-shell run, the following points
should be noted:
numbers of open shells and corresponding main configurations 1 18 1 2 3 4 5 13 17 .. SCF configuration 1 18 1 2 3 4 6 13 17 .. 5a1 -> 6a1 double 3 5 6 18 1 2 3 4 13 17 .. 5a1 -> 6a1 single 1 18 1 2 3 4 5 14 17 .. 1b1 -> 2b1 double 3 13 14 18 1 2 3 4 5 17 .. 1b1 -> 2b1 single 1 18 1 2 3 4 5 13 19 .. 1b2 -> 3b2 double 3 17 18 19 1 2 3 4 5 13 .. 1b2 -> 3b2 single
The sequence of data lines defining the Semi-direct Table-CI calculation is again terminated by the ENTER directive. Note at this stage that the full data specification corresponding to the defaults generated from the above data file is as follows
TITLE
H2CO+ 2B2 3-21G - EXPLICIT DATA FOR DEFAULTS -113.06446075
MULT 2
CHARGE 1
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
OPEN 1 1
ACTIVE
1 TO 22 END
MRDCI DIRECT
TABLE
SELECT
CNTRL 15
SPIN 2
SYMM 3
SINGLES ALL
CONF
1 18 1 2 3 4 5 13 17
1 18 1 2 3 4 6 13 17
3 5 6 18 1 2 3 4 13 17
1 18 1 2 3 4 5 14 17
3 13 14 18 1 2 3 4 5 17
1 18 1 2 3 4 5 13 19
3 17 18 19 1 2 3 4 5 13
END
THRESH 10 10
ROOTS 1
CI
NATORB
CIVEC 1
ENTER
In the examples above we have assumed that all MOs, typically generated at SCF time, are active in the subsequent CI calculation. In many instances however this will not be the case, for the user may wish to
The freezing of core, or inner-shell, orbitals is achieved by nominating the sequence nos. of those orbitals to be frozen under control of the CORE directive. The discarding of orbitals is performed under control of the ACTIVE directive, which specifies the sequence nos. of the active set of orbitals to appear in the CI. Note that the sequence numbers to be specified refer to the input orbitals, typically those produced by the SCF code, and not the Table reordered orbital as in the conventional module.
Consider the previous H2CO calculation. Suppose we wish to freeze both the O1s and C1s orbitals (with SCF sequence numbers 1 and 2 respectively) and to discard the two highest-energy virtual orbitals (with SCF sequence numbers 21 and 22): The CORE and ACTIVE data will then appear as follows
CORE
1 2 END
ACTIVE
3 TO 20 END
The core orbitals are both of a1 symmetry, and have sequence
numbers 1 and 2. The virtual orbitals are of b2 (SCF sequence no.
21) and a1 (SCF sequence no. 22) symmetry, and as the highest
orbital of each IRrep, correspond to the 6th orbital of b2
symmetry and the 12th orbital of a1 symmetry respectively. Before
detailing the Table-CI data, we should mention that the revised
numbering scheme used in the specification of, for example, the
reference configurations is, as in the conventional case, that in
effect after the freezing and discarding of orbitals. Having
effectively removed three orbitals of a1 symmetry and one of
b2 from the subsequent CI, the table below presents the final
orbital numbering to be used in CONF specification:
| IRrep | IRrep | SCF Sequence | Table-CI | Occupation |
| No. | No. | Sequence No. | No. | |
| a1 | 1 | 3 | 1 | 2.0 |
| 4 | 2 | 2.0 | ||
| 6 | 3 | 2.0 | ||
| 10 | 4 | 0.0 | ||
| 12 | 5 | 0.0 | ||
| 15 | 6 | 0.0 | ||
| 16 | 7 | 0.0 | ||
| 18 | 8 | 0.0 | ||
| 20 | 9 | 0.0 | ||
| b1 | 2 | 7 | 10 | 2.0 |
| 9 | 11 | 0.0 | ||
| 13 | 12 | 0.0 | ||
| 19 | 13 | 0.0 | ||
| b2 | 3 | 5 | 14 | 2.0 |
| 8 | 15 | 2.0 | ||
| 11 | 16 | 0.0 | ||
| 14 | 17 | 0.0 | ||
| 17 | 18 | 0.0 |
TITLE
H2CO - 3-21G BASIS - valence direct-MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
CORE
1 2 END
ACTIVE
3 TO 20 END
MRDCI DIRECT
TABLE
SELECT
SYMMETRY 1
SPIN 1
CNTRL 12
SINGLES ALL
CONF
0 1 2 3 10 14 15
0 1 2 3 11 14 15
0 1 2 3 10 14 16
4 10 11 15 16 1 2 3 14
END
ROOTS 1
THRESH 2 2
CI
NATORB
ENTER
The following points should be noted:
To simplify the data-driven loading of sub-modules, the program assumes a default loading order so that, assuming no additional data input is required by a given sub-module i.e., the default attributes of that sub-module are in effect, the user may omit explicit specification of the module from the data input. The assumed default is shown below:
.
.
MRDCI DIRECT
TABLE
SELECT
CI
NATORB
.
.
In practice the SELECT module will require input (except in cases where
the default configuration generation described above is used),
characterising for example the nature of the reference configurations,
selection attributes etc, but in many instances the defaults of the
other sub-modules will hold so that the associated data input may be
omitted. Clearly this omission of data requires a firm understanding
of the defaults in effect, which will only be apparent after the
detailed description of directives presented in Part 6. For the
moment we illustrate this by considering the simplified data file for
the multi-reference calculation on H2CO above:
RESTART
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI
SELECT
CNTRL 16
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
THRESH 2 2
ENTER
The following points should be noted:
CONF OCCUPATION
2 2 2 2 2 2 2 2 0 0 0
2 2 2 2 2 2 0 2 2 0 0
2 2 2 2 2 2 2 0 0 0 2
2 2 2 2 2 2 1 1 1 0 1
END
where the occupations specified correspond to the occupancies of the
input SCF MOs. At this stage we leave it to the user to confirm that
this data is equivalent to the CONF specification in the example above.
In the examples considered above, we have assumed that the Table-CI job completes in the time allocated. This may not be the case and we need consider restarting the computation in a controlled fashion. Such a requirement may be met in RUNTYPE CI processing when:
Integral Transformation
RESTART CI
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
TABLE BYPASS
SELECT BYPASS
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
CI BYPASS
NATORB BYPASS
ENTER
Configuration Selection
RESTART CI
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
SELECT
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
CI BYPASS
NATORB BYPASS
ENTER
Diagonalisation and Natural Orbital Generation
RESTART CI
TITLE
H2CO - 3-21G DEFAULT BASIS - MRDCI 4M/1R
SUPER OFF NOSYM
ZMAT ANGSTROM
C
O 1 1.203
H 1 1.099 2 121.8
H 1 1.099 2 121.8 3 180.0
END
RUNTYPE CI
MRDCI DIRECT
SELECT BYPASS
SINGLES 1
CONF
0 1 2 3 4 5 13 17 18
0 1 2 3 4 5 14 17 18
0 1 2 3 4 5 13 17 19
4 13 14 18 19 1 2 3 4 5 17
END
CI
NATORB
ENTER