On 01/09/2013 04:35 PM, John J. Low wrote:
> Toon,
>
> Cp2k has been modified so the the "FORCE|" string is not include the force
> output, even if you run an "ENERGY_FORCE" job. I have reviewed the cp2k
> source and I can find the old routines which wrote the "FORCE|" string.
> Unfortunately, cp2k has been modified so that these routines are no longer
> used to write out the force. It is not a simple fix to use the old
> routines because they involve a complicated usage of modules.
>
> Unfortunately, I got distracted by errors in the forces generated by CP2K,
> a new supercomputer, and vacation. I have not been able to modify TAMKIN
> or cp2k to get useful thermodynamics.
>
> I am planning to modify cp2k to be compatible with TAMKIN, it seems like
> the simplest path for me. Although it would not help anyone else, unless
> the cp2k authors include the modification to their source.
>
> Ultimately, the best fix would be to modify TAMKIN. Which I might do when
> I get to it. Could you fix TAMKIN, if I sent you some sample input and
> output from cp2k?
Hi John
I can definitely do that. If possible, please send files for a rather small
system (both single point and frequency). That would allow me to include them
in the unit tests.
> By the way, the errors in forces from cp2k are pretty significant if you
> don't use a huge cutoff for the plane wave basis in the Gaussian Plane Wave
> (GPW) approximation. The Gaussian Augmented Plane Wave (GAPW)
> approximation appears to be better but one needs to fiddle with the
> augmenting gaussians to get acceptable noise in the forces.
Aha, that is interesting. It will probably also affect the computation of the
Hessian as it is obtained with finite differences from several force computations.
B.t.w., the reason we read in the forces is to make sure that certain NMA
methods are applicable. Some of these NMA methods may give weird results if
the Hessian is not computed at a stationary point.
Best Regards,
Toon