You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The GBSA method produces different energies if one uses ParamFile option or use hsd input in the dftb_in.hsd. The GFN2 parameters for water taken from Grimme github:
The different approaches result in different energies for SP step of dftb_in.hsd.txt.
hsd.log:Total Energy: -27.0386890418 H -735.7602 eV
txt.log:Total Energy: -26.9614063373 H -733.6572 eV
The problem was spotted then explicit hsd produced exploding SCC after some steps of geometry optimization.
Tested on several versions, including (commit: 4334d64b, base: 23.1) and 23.1 from conda on mac.
It is not clear fore me which method of GBSA parameters are preferred (similar to issue 1279. As I understand two files should result in the same energies.
The text was updated successfully, but these errors were encountered:
The GBSA method produces different energies if one uses ParamFile option or use hsd input in the dftb_in.hsd. The GFN2 parameters for water taken from Grimme github:
or explicitly stating the contents of hsd file
The different approaches result in different energies for SP step of dftb_in.hsd.txt.
The problem was spotted then explicit hsd produced exploding SCC after some steps of geometry optimization.
Tested on several versions, including
(commit: 4334d64b, base: 23.1)
and 23.1 from conda on mac.It is not clear fore me which method of GBSA parameters are preferred (similar to issue 1279. As I understand two files should result in the same energies.
The text was updated successfully, but these errors were encountered: