-
Notifications
You must be signed in to change notification settings - Fork 42
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
how to use LDA+U in cp2k with sirius #744
Comments
@mtaillefumier can you have a look, please? We probably need to tag the new version, because latest lda+u+v is just merged into |
Hi geng, thank you very much for this report. SIRIUS supports LDA+U (+V) types of calculations but this support is not activated in cp2k. Turning on hubbard correction (which I am a bit surprised it even shows up) is not enough as the information about atoms and constants should be given to sirius. The necessary bit of code is not present in cp2k at the time of this reply. I would suggest you to open an issue in cp2k repository to get this feature added to cp2k. |
Hi geng, Short question. Do you use cp2k pseudo-potentials or external one. The integration of the hubbard sirius functionality will only work with external pp for the time being. I am preparing a patch to support this in cp2k. |
Dear mtailefumier, |
Hi geng, You can try cp2k master if you want to test lda+U+cp2k+sirius. The necessary code was merged during the summer. |
Dear SIRIUS developers,
I am trying to use Hubbard correction with CP2K/sirius,
The
HUBBARD_CORRECTION T
is set in the input under the&PARAMETERS
sectionIn the meanwhile, I also set up the U value under the
&KIND
section.However, I found that all the energies are the same regardless of the Hubbard U value I set in the &DFT_PLUS_U section. This is a bulk Cu2O system, and computed energies are supposed to vary a little bit with different U values.
grep 'ENERGY| Total' subdir_hubbard_U?/joblog*
Is there anything wrong with the way I set up the Hubbard U correction?
Thank you very much in advance,
Best,
Geng
The text was updated successfully, but these errors were encountered: