-
Notifications
You must be signed in to change notification settings - Fork 145
Feature: build-in DFTD3 parameters #5378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
Can the functional names in the newly added parameter file correspond to the shorthand names of built-in functionals in Abacus? For example, I noticed that the HSE functional in the parameter file is "hse06," but in Abacus, it is "hse." |
@1041176461 astonishing... I will support it. Seems someone does not know there is another functional named hse03 |
|
@kirk0830 This is a legacy issue. When Abacus originally implemented HSE, it defaulted to HSE06, including the parameters for exx_hybrid_alpha and exx_hse_omega, which are both set to HSE06. If users want to use HSE03, they will need to modify exx_hse_omega themselves. |
|
@1041176461 sounds not a good way. There are many xc functionals built within the same framework but with different parameterization, like PBE, revPBE, PBEsol, and PBE0, PBE38, etc. But I have support such an alias, anyway, see: |
|
@kirk0830 @QuantumMisaka In this case, some warning messages may be needed |
|
@1041176461 yes there will be a warning, but I am considering if in this case a warning_quit is more reasonable... |
|
after discussion with experts in xc, the support on wb97 xc family should be treated with much care, and the fall back strategy is not a good idea. |
|
@QuantumMisaka |
* Feature: build-in DFTD3 parameters with fall-back parameter search strategy * update * correct parameters * correct the annotation at the end of file dftd3.h * support libxc * add annotations * update alias: hse06 -> hse * [pre-commit.ci lite] apply automatic fixes * update the autoset strategy: if user defined, then use * fix compilation error * correct the unittest * xc with _v, _d3 should be carefully treated * give up the so-called fall-back strategy * correct a minor bug * disable the output * support the dft_functional value without the XC_ header * ouch... stupid mistake * Update doc * add more unittests * correct behavior on wb97 functional family according to advice --------- Co-authored-by: pre-commit-ci-lite[bot] <117423508+pre-commit-ci-lite[bot]@users.noreply.github.com>


Linked Issue
Fix #5371
What's changed?