GAUSSIAN STEP MISMATCH
I run into this weird error all the time in Gaussian when doing optimization or frequency restarts. This is a big problem for me because a lot of times I run these on a large number of processors, but in a queue with a relatively short max wall time. Searching the web for this error yields one hit, and it’s in Chinese and not helpful even under Google translate.
Error originates: RdWrOT: IFlag = 2 Data mismatch
Search? I only get here. And the results aren’t exactly useful …
你给出的信息太少了,能不能多贴一点出来?
Anyway this almost always seems to be a problem with the collision of the previous and current route. Often I have to increase the number of optimization or SCF cycles because my systems are large and I do optimizations with diffuse functions, which tend to be pretty ill-behaved. Here’s the total head of the log:
******************************************
Gaussian 03: AM64L-G03RevE.01 11-Sep-2007
29-Mar-2009
******************************************
%chk=freq_min60.chk
%nprocshared=8
Will use up to 8 processors via shared memory.
%nproclinda=16
Will use up to 16 processors via Linda.
%mem=100MW
Default route: MaxDisk=200GB
----------------------------------------------------------------------
# freq=restart b3lyp/6-31+g(d) geom=allcheckpoint guess=read int=fmmna
toms=300 scf=tight
----------------------------------------------------------------------
1/10=4,30=1,35=1/3;
99//99;
GradGradGradGradGradGradGradGradGradGradGradGradGradGradGradGradGradGrad
Berny optimization.
Restoring state from the checkpoint file "freq_min60.chk".
Title: min60
Route: # opt b3lyp/6-31+g(d) geom=allcheckpoint guess=read int=fmmnat
oms=300 optcyc=1000 scfcyc=1000
RdWrOT: IFlag = 2 Data mismatch
MaxStp (old) = 504 MaxStp (new) = 2
MaxJob (old) = 1 MaxJob (new) = 1
RdWrOT: Data mismatch on MaxStp/MaxJob
Error termination via Lnk1e in /apps/steele/g03-E.01/l103.exe at Sun Mar 29 01:19:04 2009.
Job cpu time: 0 days 0 hours 0 minutes 13.6 seconds.
File lengths (MBytes): RWF= 49 Int= 0 D2E= 0 Chk= 56 Scr= 1
Command exited with non-zero status 1
I’m posting this more so this error comes up in Google to Vdov so maybe, maybe someone can tell me about it (no one, including people who really know the software well, has been able to provide an acceptable explanation thus far). If the two routes are both optimizations, for instance, you can usually get around this error by eliminating the opt cycle specification in the new restarted route. But if you’re moving the guess and geometry to some new calculation, it’s nearly impossible to get around this. The solution is almost always to create a formatted checkpoint file (formchk) and convert back (unfchk), so the route disappears. You could also obviously do this by specifying the new geometry as a Z-matrix in the initial calculation, but I much prefer to read my initial guess from the checkpoint, so this is not a good option in many cases. Starting the calculation and then restarting from the new binary checkpoint file usually does the trick, as there are appear to be no collisions in the route cycles.
Anyway, cheers. Hopefully someone who knows something about this will let me know.
A while ago I 