Dear Abdullah
Thanks for reporting that issue. Though the input keyword ORDER is defined in the input section &BMHFTD, it is not used in the code. Only the pair potential parameters A, B, C, D, BD, and RMIN, RMAX, and RCUT are considered. It does not matter what you specify for ORDER in your input, the 6th and 8th order dispersion terms are always added using the damping parameter BD.
I will remove the unused input keyword ORDER from the &BMHFT section in the CP2K trunk version.
HTH
Matthias
__________________________________________
Paul Scherrer Institut
Dr. Matthias Krack
OHSA/D07
Forschungsstrasse 111
5232 Villigen PSI
Schweiz
Von: cp...@googlegroups.com <cp...@googlegroups.com>
Im Auftrag von abdullahb...@gmail.com
Gesendet: Montag, 18. Oktober 2021 09:37
An: cp2k <cp...@googlegroups.com>
Betreff: [CP2K:16062] Question about the classical BMHFT potential
Dear CP2K users,
For the classical BMHFT potential, the C_6 (C parameter) and C_8 (D parameter) terms are multiplied by the Tang-Toennies damping functions, i.e. f_6 and f_8 (J. Phys. Chem. B, Vol. 112, No. 4, 2008).
For this, an "ORDER" term (in CP2K) of 6 is needed for f_6 and 8 is needed for f_8. However, for defining this potential between two atoms, only a single "ORDER" term can be defined, for example, like this:
&BMHFTD
atoms Cl Cl
A 100.00000
B 2.89128
C 4.88053
D 45.84421
BD 3.21254
RCUT 10.0
ORDER 6
&END BMHFTD
I am curious to know whether it is possible to set an ORDER for 6 for the f_6 term, which is then multiplied by the C_6 term; and an order of 8 for the f_8 term, which is then multiplied by the C_8 term. I tried the below input file format, but it does not work as CP2K (ver 5.1) stops reading the file and gives an error cause of the missing D parameter in the first part:
&BMHFTD
atoms Cl Cl
A 100.00000
B 2.89128
C 4.88053
BD 3.21254
RCUT 10.0
ORDER 6
&END BMHFTD
&BMHFTD
atoms Cl Cl
D 45.84421
BD 3.21254
RCUT 10.0
ORDER 8
&END BMHFTD
Error:
*******************************************************************************
* ___ *
* / \ *
* [ABORT] *
* \___/ Value requested, but no value set getting value from keyword D of *
* | section BMHFTD *
* O/| *
* /| | *
* / \ input/input_section_types.F:1303 *
*******************************************************************************
Any suggestions would be greatly appreciated.
Thank you.
Best Regards,
Abdullah Bin Faheem
--
You received this message because you are subscribed to the Google Groups "cp2k" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
cp2k+uns...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/cp2k/08f80f7a-2d3d-4e61-8fa1-d648826224d2n%40googlegroups.com.
Dear Abdullah
Correct, different BD values, i.e. b(ij) parameters, are not supported currently.
Best
Matthias
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/f2b5fd9e-e316-4889-85f7-695a200857d8n%40googlegroups.com.
It should not be too difficult to add such flexibility.
Matthias
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/ad606b11-4e54-4186-b459-32581dbaadden%40googlegroups.com.
Maybe, there is no need for a code change. Did you try the following as input:
&BMHFTD
ATOMS Cl Cl
A 100.00000
B 2.89128
C 4.88053
D 0.0
BD 3.21254
RCUT 10.0
&END BMHFTD
&BMHFTD
ATOMS Cl Cl
A 0.0
B 1.0 # does not matter
C 0.0
D 45.84421
BD #any other BD value
RCUT 10.0
&END BMHFTD
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/0ae5c1e4-b49c-42a9-ab0f-8df7977a14f0n%40googlegroups.com.
Well, that are only warnings. The crash after a couple of MD steps could also have a different reason. Did you try one &BMHFTD section for a kind pair and compared it with a spilt &BMHFTD section using the same BD values just to be sure that the section “split” is causing the crash?
M.
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/dc05ee13-aeec-4729-a51f-68e6a5b084e8n%40googlegroups.com.
You are right, Abdullah, the resulting splined pair potentials are different. The additive behavior does not work with the same pair potential section and the same atomic kind pair twice.
I have just committed a fix which will allow for different BD values in the BMHFTD section. The pull request is currently running. You can find the fixed code already here in my fork on github.
HTH
Matthias
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/c1d5bd54-bfee-4441-9759-5adb212207d4n%40googlegroups.com.
BD 1.5 # will use 1.5 for f6 and f8
BD 1.5 2 # will use 1.5 for f6 and 2.0 for f8
There is no f7 term.
Matthias
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/784ed4bc-30dc-4a53-878b-751d58e82d22n%40googlegroups.com.
Right.
To view this discussion on the web visit https://groups.google.com/d/msgid/cp2k/1bbc5f50-c400-4226-b717-a7dadfce0120n%40googlegroups.com.