Search the Site Index:





Unfchk

Updated on 12 Feb 2026

This utility is the opposite number to formchk. It converts a formatted checkpoint file to a binary checkpoint file, in a format appropriate to the local computer system. It takes one or two filenames are arguments. For example:

$ unfchk job222.fchk new.chk
Read formatted file "job222.fchk"
Write checkpoint file "new.chk"
LenFI=          2580 MDV=     104857600 DoIMCk=T

By default, the utility applies the extension .fch to the specified formatted checkpoint filename on Windows systems and the extension .fchk on other computer systems. The binary checkpoint file‘s extension is always .chk. The checkpoint filename is optional and defaults to the same base name as the first argument.

The utility will also prompt for the required filenames if no arguments are given:

$ unfchk
Formatted Checkpoint file? water
Read formatted file water.fchk
Write checkpoint file water.chk

Note that formatted checkpoint files can be used as a data exchange format between computer platforms. Use formchk on the originating computer and unfchk on the target computer to “move” a binary checkpoint file between computers of different types.

unfchk can also convert a BAF/FAF to a binary checkpoint file (see Options).

In addition to formatted checkpoint files, unfchk can work with BAF/FAF and create binary checkpoint files containing their data.

-m=N

Specifies the amount of memory to allocate to the utility. The argument N should specify an amount, optionally followed by units (the default unit is bytes).

-c=cpulist

Specifies the list of CPUs/cores that can be used by the utility. On the command line, the list will typically need to be enclosed in quotation marks to protect it from the shell.

-mem

Reads the formatted checkpoint file into memory to avoid having to read it multiple times (failing if there is not enough memory). This is the default. -nomem overrides this behavior.

-update

Updates an existing binary checkpoint file rather than creating a new one. Data which is already in the checkpoint file but is not present in the source file is retained. This is the default when the source file is a BAF/FAF.

-baf

Indicates that the source file is a Gaussian binary array file (BAF). This option is needed only when the extension of the BAF is not .baf.

-faf

Indicates that the source file is a Gaussian Fortran unformatted array file (FAF). This option is needed only when the extension of the FAF is not .faf.

-fixver

Set the version number of the binary checkpoint file to be the current version.

-data

Causes data statements for all quantities on the binary array file to be printed (no checkpoint file is created).

-mopacdensity

The source file is a MOPAC OLDENS file. Note the the utility can only update a checkpoint file which has the correct basis set data, etc.

The following options specify the integer format of the BAF/FAF. Generally, the integer format is detected automatically, but occasionally they may be needed, depending on how the file was written by formchk, Gaussian, or whatever program created it.

-i8

Use this option when the BAF/FAF uses 8-byte integers.

-i4

Use this option when the BAF/FAF uses 4-byte integers.

SideMenu

SideMenu