Carlier Group Gaussian User Manual - Virginia Tech
Carlier Group Gaussian User Manual - Virginia Tech
Carlier Group Gaussian User Manual - Virginia Tech
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
56<br />
<strong>Carlier</strong> <strong>Group</strong> <strong>Gaussian</strong> <strong>User</strong> <strong>Manual</strong><br />
Appendix 1: Why your calculation failed<br />
(not yet updated for g09)<br />
1) If Calculation does not start on giving the qsub command:<br />
• because of a wrong pathway specified in the .sh file.<br />
• Because of the presence of ampersand at the end of nohup command<br />
• If you see your job queued up: You have specified more memory or processors<br />
than currently available, or you have surpassed the number of jobs allowed.<br />
If the calculation failed after starting (you will have the *.rwf, *.scr and *.out files in your<br />
directory) Commonly occurring errors and causes:<br />
2) Charge and multiplicity card seems defective: Charge is bogus.<br />
Reason: There is an extra space between your title line and your description<br />
3) End of file in ZSymb.<br />
Error termination via Lnk1e in /apps/packages/gaussian03c02/g03/l101.exe<br />
Reason: This means that there is no space after the last geometry line. You need to<br />
have at least 1 space after geometry specification.<br />
4) The combination of multiplicity 1 and 39 electrons is impossible.<br />
Reason: check your charge and multiplicity – one of them is wrong!<br />
5) Convergence criterion not met or Convergence failure -- run terminated.<br />
Reason: There is a problem with convergence during geometry optimization. Try<br />
opt=tight or opt=vtight<br />
6) Error termination request processed by link 9999. Error termination via Lnk1e in<br />
/apps/packages/gaussian03c02/g03/l9999.exe at Sat Nov 15 10:43:07 2008.<br />
Reason: This is also a convergence issue, though I have usually seen this occur after a<br />
number of cycles (usually more than a day of computational time) and could also be<br />
due to lack of sufficient resources. Try using MaxCycle=N to increase the number of cycles.<br />
7) No Z-matrix found on checkpoint file.<br />
Cartesian coordinates read from the checkpoint file: thfer.chk<br />
FileIO operation on non-existent file.<br />
Reason: This happens if you specify geom=checkpoint but forget to make the .chk<br />
file.<br />
8) Symbolic Z-matrix:<br />
Charge = 0 Multiplicity = 1<br />
There are no atoms!<br />
Reasons: 1. You forgot to paste your geometry or specify geom=checkpoint<br />
2. You have specified geometry but have forgotten to put a description.