10.5.4 Direct Generation of “Cube” Files

As an alternative to the output format discussed above, all of the $plots data may be output directly to a sub-directory named plots in the job’s scratch directory, which must therefore be saved using the –save option described in Section 2.7. The plotting data in this sub-directory are not written in the plot.* format described above, but rather in the form of so-called “cube” file, one for each orbital or density that is requested. The cube file format is a standard one for volumetric data and consists of a small header followed by the orbital or density values at each grid point, in ASCII format. (Consult Ref. 378 for the complete format specification.) Because the grid coordinates themselves are not printed (their locations are implicit from information contained in the header), each individual cube file is much smaller than the corresponding plot.* file would be. Cube files can be read by many standard (and freely-available) graphics programs, including MacMolPlt^{85, MacMolPlt} and VMD.^{407, VMD} VMD, in particular, is recommended for generation of high-quality images for publication. Cube files for the MOs and densities requested in the $plots section are requested by setting MAKE_CUBE_FILES to TRUE, with the $plots section specified as described in Section 10.5.3.

The following example illustrates the generation of cube files for a ground and an excited-state density, including the corresponding spin densities. In this example, the plots sub-directory of the job’s scratch directory should contain files named dens.N.cube (total density for state $N$, where $N=0$ or 1 represents the ground and first excited state, respectively), dens_alpha.N.cube and dens_beta.N.cube (${\rho }_{\alpha }$ and ${\rho }_{\beta }$ for each state), and dens_spin.N.cube (${\rho }_{\alpha }-{\rho }_{\beta }$ for each state.)

Cube files are also available for natural transition orbitals (Sections 7.15.2 and 10.5.2) by setting MAKE_CUBE_FILES to NTOS, although in this case the procedure is somewhat more complicated, due to the state-specific nature of these quantities. Cube files for the NTOs are generated only for a single excited state, whose identity is specified using CUBEFILE_STATE. Cube files for additional states are readily obtained using a sequence of Q-Chem jobs, in which the second (and subsequent) jobs read in the converged ground- and excited-state information using SCF_GUESS and SKIP_CIS_RPA.

An additional complication is the manner in which to specify which NTOs will be output as cube files. When MAKE_CUBE_FILES is set to TRUE, this is specified in the $plots section, in the same way that MOs would be specified for plotting. However, one must understand the order in which the NTOs are stored. For a system with $N_{\alpha }$ $\alpha$-spin MOs, the occupied NTOs $1,2,\mathrm{\dots },N_{\alpha }$ are stored in order of increasing amplitudes, so that the $N_{\alpha }$’th occupied NTO is the most important. The virtual NTOs are stored next, in order of decreasing importance. According to this convention, the principle NTO pair consists of the final occupied orbital and the first virtual orbital, for any particular excited state. Thus, orbitals $N_{\alpha }$ and $N_{\alpha }+1$ represent the most important NTO pair, while orbitals $N_{\alpha }-1$ and $N_{\alpha }+2$ represent the second most important NTO pair, etc..

Cube files for Natural Bond Orbitals (for either the ground state or any CIS, RPA, of TDDFT excited states) can be generated in much the same way, by setting MAKE_CUBE_FILES equal to NBOS, and using CUBEFILE_STATE to select the desired electronic state. CUBEFILE_STATE = 0 selects ground-state NBOs. The particular NBOs to be plotted are selected using the $plots section, recognizing that Q-Chem stores the NBOs in order of decreasing occupancies, with all $\alpha$-spin NBOs preceding any $\beta$-spin NBOs, in the case of an unrestricted SCF calculation. (For ground states, there is typically one strongly-occupied NBO for each electron.) NBO cube files are saved to the plots sub-directory of the job’s scratch directory. One final caveat: to get NBO cube files, the user must specify the AONBO option in the $nbo section, as shown in the following example.