For those itching for polarizability derivative orientation information and wondering where it is when you ask for it… what’s included below is a combination of a few points in one, specifically pointing out that the IOp options are not just “another part” of the Gaussian input file (with the IOp Overlays currently linked HERE).

The problem I realized after an email from Gaussian HQ was that, as was the case for the KMLYP density functional call discussed in previous posts about [18]-annulene, “opt” and “freq” keyword combinations are seen as two distinct runs in Gaussian that don’t pass the IOp information along (and, admittedly, I should have remembered that). Specifically, the additional print-out for the polarizability info is called by IOp(7/33=3).

What I provide below is a two-in-one input file that saves you from having to run double-duty input files in the checkpoint file. This also serves as a template for those looking for examples of combining multi-step input files that include mixed basis sets (as many of the problems I’ve been emailed stem from carriage return issues more than anything else). Note that the input file is set to run Raman intensities and produce higher-precision (hpmodes) eigenvectors (so, if you just want to test this, remove the “raman”).

%chk=C4H5Cl_B3LYP_631Gdp_LanL2DZ_IR_Raman.chk
#p scf=tight opt=tight b3lyp/GEN pseudo=read

C4H5Cl_B3LYP_631Gdp_LanL2DZ_IR_Raman Opt

0 1
 C                 -1.74671095   -0.64168298    0.00000000
 H                 -1.53944096   -1.69141587    0.00000000
 C                 -0.73010315    0.25446188    0.00000000
 H                 -0.93737314    1.30419477    0.00000000
 C                  0.73010315   -0.25446188    0.00000000
 H                  0.93737314   -1.30419477    0.00000000
 C                  1.74671095    0.64168298    0.00000000
 H                  1.53944096    1.69141587    0.00000000
 H                 -3.73526840    0.03531673    0.00000000
 Cl                 3.73526840   -0.03531673    0.00000000

C H 0
6-31G(d,p)
****
Cl
Lanl2DZ
****

Cl
Lanl2DZ

--Link1--
%chk=C4H5Cl_B3LYP_631Gdp_LanL2DZ_IR_Raman.chk
#p Geom=Check Guess=Read freq(raman,hpmodes) iop(7/33=3)
 
C4H5Cl_B3LYP_631Gdp_LanL2DZ_IR_Raman Freq
     
0 1

Note the carriage return after the second “0 1″.

For the demo molecule above, additional print-out below.

 Dipole derivatives wrt mode   1:  3.96988D-14 -1.15747D-14 -1.96904D-01
 Polarizability derivatives wrt mode          1
                 1             2             3 
      1   0.000000D+00  0.000000D+00  0.206435D+00
      2   0.000000D+00  0.000000D+00  0.143916D-01
      3   0.206435D+00  0.143916D-01  0.000000D+00
 Vibrational polarizability contributions from mode   1       0.0000000       0.0000000       0.0257731
 IFr=  0 A012= 0.23D-23 0.77D+00 0.13D+00 Act= 0.90D+00 DepolP= 0.75D+00 DepolU= 0.86D+00

Alternately, keep track of the checkpoint file.

In press (DOI:10.1016/j.molstruc.2012.07.051) in the Journal Of Molecular Structure. May go down in history as a hardest-fought paper acceptance. In a similar line of research as the [18]-annulene study, but exploring the infinite limit of geometry and bond length alternation energy barrier for this infinite case. If the numbers are correct, the infinite polyene chains (polyacetylene) do not exhibit bond length alternation because the Peierls’ barrier between the single-double and double-single bond alternate minima is below the vibrational zero-point level. Plenty of ramifications.

Bruce S. Hudson and Damian G. Allis

Abstract. The potential energy of the infinite periodic chain model of polyacetylene (pPA) is symmetric with two equivalent minima separated by the Peierls’ stabilization barrier. In this work it is shown how an energy scale and vibrational energy levels for this highly anharmonic Peierls’ degree of freedom can be estimated. Attention is given to the potential energy increase for large deformations. The Born-Kármán treatment of translational symmetry is applied. Two empirical methods and a direct periodic boundary condition (PBC) density functional theory (DFT) calculations are in semi-quantitative agreement, each leading to the conclusion that pPA has a zero-point level that is above the Peierls’ barrier. The argument does not depend critically on the barrier height or the other parameters of the model or the computation method. It is concluded that pPA will not exhibit bond alternation and that the zero-point average geometry does not preclude possible conductivity.

In press (DOI:10.1016/j.molstruc.2012.05.016) in the Journal Of Molecular Structure (Volume 1023, 12 September 2012, Pages 212–215) in the special issue: MOLECULAR VIBRATIONS AND STRUCTURES: THEORY AND EXPERIMENT — A collection of papers dedicated to Professor Jaan Laane on the occasion of his 70th birthday.

This paper on the “actual” geometry of [18]-annulene is part of several larger stories addressing a larger polyene (or larger-polyene) issue. First among these is the meaning of experimental results obtained by various spectroscopic methods (in this case, using previous X-ray, Raman (with the C2 (blue) and D6h (red) simulated spectra shown in the image above), IR, and NMR data that produce different results within the limitations of the methods to study the single molecule). Second is the quality of the theoretical method for reproducing certain types of spectroscopic data. In the case of the [N]-annulene series, the ever-present B3LYP density functional is found to produce the time-average geometry of [18]-annulene found in X-ray data, but another density functional (in this case, KMLYP), finds that bond-alternate minima exist. Third is the importance of the zero-point level in the treatment of systems for which bond-alternate geometries exist with transition-state barriers calculated to be below the zero-point level in the classical approximation of nuclear positions (the Born-Oppenheimer Approximation).

NOTE 1: The KMYLP density functional is called in Gaussian with the following keyword set:

BLYP iop(3/76=1000005570) iop(3/77=0000004430) iop(3/78=0448010000)

NOTE 2: Optimization and Frequency calculations must be performed as TWO SEPARATE CALCULATIONS. The iop-called density functional does not carry itself over between opt + freq (or other properties) in the same input file. If you opt + freq in the same input file, you will Opt with KMLYP but freq with BLYP. This will be obvious by the number of imaginary modes.

Bruce S. Hudson and Damian G. Allis

Abstract. [18]-annulene has been of great interest from the structural point of view of its bond alternation. High-level calculations based on structures selected for agreement with NMR spectra lead to a bond-alternate C2 form over a non-alternating planar D6h structure deduced from diffraction, infrared (IR) and electronic spectral studies. Here it is shown that computed Raman spectra for the D6h and C2 forms are expected to be very different. However, two equivalent non-D6h bond-alternate minima of D3h or C2 geometries are separated by only a small barrier along a motion that involves CC stretching and compression. It is shown here that the zero-point level is above the barrier for this species. In light of that fact, the NMR calculations are reconsidered with inclusion of zero-point level averaging.

This post was instigated by Syracuse University Professor of Chemistry and well-known non-blogger Tim Korter concerning efforts to, I believe, generate proper Møller–Plesset Perturbation Theory Of The 4th Order (MP4, and also testing coupled cluster CCSD(T) calculations) intermolecular potentials for improving terms for Grimme dispersion-corrected density functional theory (DFT) calculations with the Gaussian09 package (a program for which many people grumble about various issues but which is, by nearly all metrics, a fantastic set of quantum chemical programs). The examples below, using water only, are just for ease-of-testing, which produce the following results based on the form of the input of the molecular coordinates. For those wondering why, z-matrices are the preferred format for performing SCAN or other automated trajectory calculations (an absolutely useless format, in my opinion, now that we have computers that can handle more than five atoms).

1. Molecular coordinates defined in the z-matrix (obviously in z-matrix format) and “z-matrix” called in the opt keyword…

#p scf=tight opt(tight,z-matrix) MP4/aug-cc-pVTZ
 
h2o test 1
 
0 1
O              
H                  1    0.96000000
H                  1    0.96000000    2  109.50000032

… produces:

 ************************************************
 ** ERROR IN INITNF. NUMBER OF VARIABLES (  0) **
 **   INCORRECT (SHOULD BE BETWEEN 1 AND 50)   **
 ************************************************

2. Molecular coordinates defined in the z-matrix (obviously in z-matrix format) and “z-matrix” NOT called in the opt keyword…

#p scf=tight opt=tight MP4/aug-cc-pVTZ
 
h2o test 2
 
0 1
O              
H                  1    0.96000000
H                  1    0.96000000    2  109.50000032

… produces:

 ************************************************
 ** ERROR IN INITNF. NUMBER OF VARIABLES (  0) **
 **   INCORRECT (SHOULD BE BETWEEN 1 AND 50)   **
 ************************************************

3. Molecular coordinates defined by variables in the z-matrix (obviously in z-matrix format) and “z-matrix” called in the opt keyword…

#p scf=tight opt(tight,z-matrix) CCS(D)/aug-cc-pVTZ
 
h2o test 3
 
0 1
O              
H                  1    B1
H                  1    B1     2  A1 

B1 0.96000000    
A1 109.50000032

… produces:

Normal termination of Gaussian 09 at Fri Apr 27 11:28:33 2012.

4. Molecular coordinates defined by variables in the z-matrix (obviously in z-matrix format) and “z-matrix” NOT called in the opt keyword…

#p scf=tight opt=tight MP4/aug-cc-pVTZ
 
h2o test 4
 
0 1
O              
H                  1    B1
H                  1    B1     2  A1 

B1 0.96000000    
A1 109.50000032

… produces:

Normal termination of Gaussian 09 at Fri Apr 27 11:28:33 2012.

So, a solution, for when the dreaded…

 NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-NEF-
 NUMERICAL EIGENVECTOR FOLLOWING MINIMUM SEARCH
 INITIALIZATION PASS


 ************************************************
 ** ERROR IN INITNF. NUMBER OF VARIABLES (  0) **
 **   INCORRECT (SHOULD BE BETWEEN 1 AND 50)   **
 ************************************************

… error appears, the simple solution is to re-define your system.

In the interest of wasting a few cycles, I ran a series of the same calculations with other post-Hartree-Fock methods [B3LYP, MP2, MP4, CCS(D), CCSD(T)] to see how pervasive the issue with coordinate definitions might be. It appears to be limited only to MP4 and CCSDT (CCS(D) worked but took an unbelievably long time for Option 3 above), meaning people generally running significant molecules likely have never come across the issue.

And happy new year.

I had thought this was something involving Gaussian09 memory usage until I restarted a machine and found the same problem occurring in Ubuntu. Below is a quick fix (and reminder for the future).

Checking disk space with df -all :

user@machine:~$ df -all
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1            147550696   5863896 134191632   5% /
proc                         0         0         0   -  /proc
none                         0         0         0   -  /sys
none                         0         0         0   -  /sys/fs/fuse/connections
none                         0         0         0   -  /sys/kernel/debug
none                         0         0         0   -  /sys/kernel/security
none                   3053752       260   3053492   1% /dev
none                         0         0         0   -  /dev/pts
none                   3058264         0   3058264   0% /dev/shm
none                   3058264        84   3058180   1% /var/run
none                   3058264         0   3058264   0% /var/lock
none                   3058264         0   3058264   0% /lib/init/rw
none                         0         0         0   -  /var/lib/ureadahead/debugfs
nfsd                         0         0         0   -  /proc/fs/nfsd
binfmt_misc                  0         0         0   -  /proc/sys/fs/binfmt_misc

… we find /var/lib/ureadahead/debugfs both existing but taking up no space to speak of. Several seconds later (after a reboot), we find the following…

user@machine:~$ df -all
Filesystem           1K-blocks      Used Available Use% Mounted on
/dev/sda1            147550696   5864268 134191260   5% /
proc                         0         0         0   -  /proc
none                         0         0         0   -  /sys
none                         0         0         0   -  /sys/fs/fuse/connections
none                         0         0         0   -  /sys/kernel/debug
none                         0         0         0   -  /sys/kernel/security
none                   3053752       260   3053492   1% /dev
none                         0         0         0   -  /dev/pts
none                   3058264         0   3058264   0% /dev/shm
none                   3058264        84   3058180   1% /var/run
none                   3058264         0   3058264   0% /var/lock
none                   3058264         0   3058264   0% /lib/init/rw
none                 147550696   5864268 134191260   5% /var/lib/ureadahead/debugfs
nfsd                         0         0         0   -  /proc/fs/nfsd
binfmt_misc                  0         0         0   -  /proc/sys/fs/binfmt_misc

Properly updated machines (as per below) both do not contain this /var/lib/ureadahead/debugfs directory and do not subsequently “blow up” and eat disk space (to date. This may not be the real problem, but disk space usage will increase to +60% and, to my mind, the machine will noticeably slow down).

Fix Steps:

sudo aptitude update
sudo aptitude upgrade

Update your 10.04. Some web pages report that the problem with /var/lib/ureadahead/debugfs is attributable to a bug in mountall (now fixed. See bugs.launchpad.net/ubuntu/+source/mountall/+bug/736512).

sudo mv /etc/init/ureadahead.conf /etc/init/ureadahead.conf.disable

If you do NOT perform this move, the machine restart will produce the same /var/lib/ureadahead/debugfs error above. Kudos to ubuntuguide.net/howto-fix-ureadahead-problem-after-upgrading-to-ubuntu-10-04 for pointing this out.

sudo shutdown -r now

System restart, problem (for me, at least) solved.