copychk
The copychk utility creates a new checkpoint file by copying some or all of the data in an existing checkpoint file. It is intended for creating new checkpoint files by selectively copying data from an existing checkpoint file. Note that making a full copy of a checkpoint file can be done using the usual operating system file copy command. The copychk utility assumes familiarity with the checkpoint file internal file numbers used to refer to specific data sets within the file (documented here).
The utility has the following syntax:
$ copychk old-checkpoint-file new-checkpoint-file [data-selection-options]
The available options are documented on the Options tab. If the checkpoint files are not specified, the utility will prompt for them. Incuding the .chk extension is almost always optional (but see below).
Note: The character 0 as the first argument is ignored for backwards compatibility. To copy from a file named 0.chk, use the full file name including the extension.
Data Selection Options
The file number lists referenced below are comma-separated lists of file number without any spaces between items.
FILES list-of-file-nums [TO list-of-file-nums]
Copy only the data in the listed file numbers. If the TO clause is included, then each data set will be placed into the file number in the corresponding list location rather than the original file number.
NOT list-of-file-nums
Copy all data except that corresponding to the listed file numbers.
MO
Equivalent to FILES followed by all the files related to the SCF wavefunction (orbitals, density matrices, etc.)
NoFC
Equivalent to NOT followed by a list of the files containing nuclear forces, force constants and third derivatives.
Options for ONIOM Jobs
The data from a particular ONIOM subcalculation can be copied with any of the three following options. Note that the copy is set up for a standalone (non-ONIOM) calculation for the particular level of theory and model system.
–AB
A is the model (Low, Medium, High), and B is the system (Small/“model,” Medium/“intermediate,” Large/“real”). For a 2-layer ONIOM, one of -LS, -MS or -LM (with -MM valid only for a 2-layer ONIOM=SValue); for compatibility, for 2-layer ONIOMs, -ΗS is equivalent to -MS, and -HL, -HM and -ML are equivalent to -MM. For a 3-layer ONIOM, one of -LS, -MS, -HS, -LM, -MM or -LL (with -HM, -HL and -ML valid for only for ONIOM=SValue).
-OS N
N is the ONIOM subsystem number.
-ONFile FileN
FileN is the ONIOM file number for the desired subcalculation.
The following options are also useful with ONIOM checkpoint files:
-ONFrag N
N specifies the fragment number when the model systems have been split into fragments (required in this case).
-ignore
Change the ONIOM system even if the file is marked as involving a running job. Doing this won’t interfere with the running job, but may produce inconsistent data in the copy.
Other Options
-m=n
Specifies the amount of memory to allocate to the utility, where n is an amount optionally followed by units (the default unit is bytes). This option must precede all other options and command line arguments.
NaN words
Initialize the new checkpoint file with the indicated number of words of NaNs prior to copying any data.
-p
Increments the print flag by one each time it appears.
Copy all files in source.chk to target.chk:
$ copychk source target
Copy all files except file 524:
$ copychk source target not 524
Copy only files 1234 and 9999:
$ copychk source target files 1234,9999
Copy only files 1234, 1111 and 9999, remapping 1234 to 7 and 9999 to 17 (1111 is not remapped in the copy):
$ copychk source target files 1234,9999,1111 to 7,17
Copy a checkpoint file from a 2-layer ONIOM and make the copy suitable for use in a standalone calculation of the high level of theory on the model system:
$ copychk source target -HS
If the ONIOM calculation partitioned the model systems into fragments, then the fragment to be set up must be indicated with onfrag:
$ copychk source target -LS -onfrag 3
