Search the Site Index:





formchk g16

[wonderplugin_tabs id=”17″ inline=”1″]
[wonderplugin_tab_content]

Description

formchk converts the data in a Gaussian checkpoint file into formatted forms that are suitable for input into a variety of visualization software. By default, formchk creates a text version of the checkpoint file known as the “formatted checkpoint file.” formchk can also generate “matrix element files” via various options. (see Options)

formchk has the following syntax:

formchk [options] chkpt-file [formatted-file]

where chkpt-file is the name of the binary checkpoint file to be formatted and formatted-file is the name for the resultant output file. If the name of the formatted file is omitted, it defaults to the base name of the checkpoint file with .fchk.

For example, the following command will produce the formatted checkpoint file propell.fchk from the checkpoint file propell.chk:

$ formchk propell.chk propell.fchk

The conventional extension for formatted checkpoint files is .fchk on Unix systems and other computers supporting variable-length extensions.

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 create a binary checkpoint file. Always include the -3 option when moving files between different types of computers (see options).

[/wonderplugin_tab_content]
[wonderplugin_tab_content]

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).

-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.

-p=n

Use n processors (deprecated in favor of -c).

-3

Produce a version 3 formatted checkpoint file, including all features supported in Gaussian 25. This is also the format used by Gaussian 09 and Gaussian 16. This is the default.

-2

Produce a version 2 formatted checkpoint file, the version used with Gaussian 03.

-0

Produce a formatted checkpoint file that is backwardly compatible with all previous versions of Gaussian.

-c

Causes the molecular mechanics atom types to appear in the formatted checkpoint file as strings rather than integers.

-pesirc

If IRC data is to be written to the formatted checkpoint file, take it from the PES data structure object if it’s available. The default operation is to write IRC data from the OT file.

-p

Increment the debug print flag by one for each appearance of this option.

-mopacdensity

Write a file for MOPAC OLDENS input instead of a formatted checkpoint file.

BAF and FAF options

-baf

Generates a binary array file (BAF) from the specified checkpoint file instead of a formatted checkpoint file. -raw is a synonym for this option.

-faf

Writes a Fortran unformatted array file from the specified checkpoint file instead of a formatted checkpoint file. -mat is a synonym for this option.

-i4

-i8

Writes the binary array file using 4-byte or 8-byte integers (respectively) in the output file even if Gaussian is a different size integer. On 32-bit computers, the former is the only option and the default; on 64-bit computers, the latter is the default.

-min

Do not write arrays which are dimensioned NShell or NBasis to the BAF.

-allatoms

Include inactive atoms in the binary array file.

-files="(list)"

When combined with the -baf option, includes the contents of the specified internal Gaussian file(s) within the generated BAF. For example, the following option:

$ formchk -files="(123,(456,offset=1,integer=27)))" -baf fox7_dimer.chk fox7_dimer.baf

will cause the contents of internal file 123 (assumed by default to be real values), the 27 integers in internal file 456 starting after the first (8-byte) word, and any real values following the integers, to be included within fox7_dimer.baf.

ONIOM options

-r

Restore coordinate data for the general case in an ONIOM checkpoint file (i.e., the low-level on the real system). This is useful if the checkpoint file is from an ONIOM job which died in the middle of an ONIOM calculation but one wants to put the real system structure and other information in the formatted checkpoint file, e.g., to read the structure into GaussView in order to modify it.

The formatted checkpoint file can be set up for a particular ONIOM subcalculation with any of the three following options:

–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.

[/wonderplugin_tab_content]
[/wonderplugin_tabs]

Last updated on: 20 May 2025. [G25 Rev. A.01]

SideMenu

SideMenu