4.2.8. CMOCORR ¤¶
Warning
This program is not available in OpenMolcas
4.2.8.1. Description¶
The CMOCORR is a small utility that is used to compare orbital spaces for two orbital vector files. This is useful for checking that a calculation has maintained the orbital spaces intended by the user.
4.2.8.2. Dependencies¶
The CMOCORR program requires two orbitals files as input generated by any of the modules that produces orbitals.
4.2.8.3. Files¶
4.2.8.3.1. Input files¶
Two orbitals files with the names CMOREF and CMOCHK are needed by the program, and it is the responsability of the user to make the proper links to these files, no links are done automatically.
4.2.8.3.2. Output files¶
There are no output files.
4.2.8.4. Input¶
Below follows a description of the input to CMOCORR The input for each module is preceded by its name like:
&CMOCORR
Argument(s) to a keyword, either individual or composed by several entries, can be placed in a separated line or in the same line separated by a semicolon. If in the same line, the first argument requires an equal sign after the name of the keyword. Note that all character in a keyword is necessary, not only the first four.
- DoMetric
Compare the metric of the two files. If the files correspond to different geometries the metric will be different.
- DoSpaces
Compare the orbitals spaces of the two files. This keyword implies DoMetric.
- DoOrbitals
Compare the orbitals one by one in the two files. This keyword implies DoMetric and DoSpaces.
- sortcmo
Sort the orbitals according to the type index. This might be necessary if one of the files are created by LUSCUS for example.
- Thresholds
This keyword is followed by two parameters, \(t_1\) and \(t_2\), the first specifying at what overlap to report that orbitals from the two files have a small overlap. In addition, orbitals in the reference file with best match is located. The second parameter is similar, but no search for matching orbitals is done. The defaults are \(t_1\)=0.6 and \(t_2\)=0.8.
- End of input
This keyword terminates the reading of the input.
4.2.8.4.1. Input examples¶
First we have the bare minimum of input. This will only check that the files have the same number of orbitals and symmetries.
&CMOCORR
The next example is almost as simple, and all checks are perfomed.
&CMOCORR
DoOrbitals