Closed kirk0830 closed 1 month ago
@PeizeLin I think it makes scence (at least partially) to always keep consistency between numerical orbitals and pseudopotentials especially in aspect of how many electrons are treated as valence electrons. So it seems for big-core pseudopotentials my way to generate orbitals is reasonable. Do you have any idea about why this segfault happens?
@PeizeLin I think it makes scence (at least partially) to always keep consistency between numerical orbitals and pseudopotentials especially in aspect of how many electrons are treated as valence electrons. So it seems for big-core pseudopotentials my way to generate orbitals is reasonable. Do you have any idea about why this segfault happens?
Could you upload the input files please? I can't login Bohrium due to the restricted permissions.
@PeizeLin I think it makes scence (at least partially) to always keep consistency between numerical orbitals and pseudopotentials especially in aspect of how many electrons are treated as valence electrons. So it seems for big-core pseudopotentials my way to generate orbitals is reasonable. Do you have any idea about why this segfault happens?
Could you upload the input files please? I can't login Bohrium due to the restricted permissions.
Hi Peize, sorry for this late reply, following I attach my test suites: t_pbe_pslnc031sg1510_DDTT.zip t_hse_pslnc031sg1510_DDTT.zip You can try any one of them. Regards!
Describe the bug
Due to pslibrary norm-conserving version 0.3.1 only keep one s and one p orbitals treated as valence electrons, unlike SG15 which keeps one s, one p and one d, numerical atomic orbitals configuration may need to change from 2s2p2d1f (SG15) to 2s2p1d for DZP and 3s3p3d2f to 3s3p2d for TZDP. However, after changing the configuration,
dft_functional pbe
can still run smoothly but fordft_functional hse
it fails. stdout is like:for HSE, running_scf.log printed memory warnings
while PBE does not have such warnings:
for more detailed results, see abacustest: PBE (success): https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-319827 HSE (fail): https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-23383e HSE (try again but still fail): https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-3d06c5
Expected behavior
I dont think it is an expected behavior, because I also have generated orbitals with electronic configuration 2s2p2d1f and 3s3p3d2f, instead of 2s2p1d or 3s3p2d. For HSE these jobs run smoothly: https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-89f65e
To Reproduce
PBE (success): https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-319827 HSE (fail): https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-23383e HSE (try again but still fail): https://labs.dp.tech/projects/abacustest/?request=GET%3A%2Fapplications%2Fabacustest%2Fjobs%2Fjob-abacustest-v0.3.53-3d06c5
Environment
Additional Context
NaN
Task list for Issue attackers (only for developers)