Skip to content
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

Default POTCAR settings for Lanthanides not compatible with Hybrid DFT #309

Open
utf opened this issue Oct 3, 2019 · 5 comments
Open

Default POTCAR settings for Lanthanides not compatible with Hybrid DFT #309

utf opened this issue Oct 3, 2019 · 5 comments
Labels

Comments

@utf
Copy link
Member

utf commented Oct 3, 2019

Trying to run a hybrid calculation on a systems containing Lanthanide elements (specifically Dy and Er) I ran into an error:

 internal error in SET_CORE_WF: core electrons incorrect 

Apparently, this is because some of the lanthanide potentials are not compatible with hybrid DFT (https://cms.mpi.univie.ac.at/vasp-forum/viewtopic.php?t=11307). The default Dy and Er POTCARs are Dy_3 and Er_3, instead we should be using just Dy and Er.

Interestingly, my calculation with Pr ran fine even though the POTCAR used was Pr_3. Some testing to see which POTCARs are compatible with hybrid DFT is needed.

@mkhorton
Copy link
Contributor

mkhorton commented Oct 3, 2019

I'm a bit confused by that thread -- if you use, say, the Gd_3 POTCARs are your calculations charged-balanced? It says there are 18 electrons for the Gd and 9 electrons for the Gd_3. Either way that seems short an electron? Also the Gd POTCAR we're using is now almost 20 years old . . . (I understand your question is about Dy/Er)

@computron
Copy link
Contributor

I didn't understand the part about charge-balanced (is part of the thread missing)?

But for Gd I've had problems in the past: Gd_3 doesn't play well with hybrid, but Gd is very difficult to converge for systems I've tried.

@mkhorton
Copy link
Contributor

mkhorton commented Oct 3, 2019

I'm just very confused by what these pseudopotentials are doing. It doesn't help that there's no documentation on how they were generated.

@mkhorton
Copy link
Contributor

mkhorton commented Oct 8, 2019

@utf did you find out any additional info on this? Hoping to start a conversation here about modernizing our pseudopotential choices, so this might be helpful :)

@utf
Copy link
Member Author

utf commented Jan 2, 2020

After some testing, I've found this isn't an issue when using the latest pseudo potentials.

@itsduowang itsduowang added the bug label Feb 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants