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

how to use LDA+U in cp2k with sirius #744

Open
GengSS opened this issue Jul 4, 2022 · 5 comments
Open

how to use LDA+U in cp2k with sirius #744

GengSS opened this issue Jul 4, 2022 · 5 comments

Comments

@GengSS
Copy link

GengSS commented Jul 4, 2022

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 section
In the meanwhile, I also set up the U value under the &KIND section.

      &DFT_PLUS_U
          U_MINUS_J [eV] 3.0
          L 2
      &END DFT_PLUS_U

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*

subdir_hubbard_U0/joblog.2344991: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U1/joblog.2344992: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U2/joblog.2344993: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U3/joblog.2344994: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U4/joblog.2344995: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U5/joblog.2344996: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U6/joblog.2344997: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U7/joblog.2344998: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U8/joblog.2344999: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887
subdir_hubbard_U9/joblog.2345000: ENERGY| Total FORCE_EVAL ( SIRIUS ) energy [a.u.]:         -755.840261090023887

Is there anything wrong with the way I set up the Hubbard U correction?

Thank you very much in advance,
Best,
Geng

@toxa81
Copy link
Collaborator

toxa81 commented Jul 4, 2022

@mtaillefumier can you have a look, please? We probably need to tag the new version, because latest lda+u+v is just merged into develop branch.

@mtaillefumier
Copy link
Collaborator

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.

@mtaillefumier
Copy link
Collaborator

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.

@GengSS
Copy link
Author

GengSS commented Jul 5, 2022

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,
Thank you very much for your reply.
I am using the cp2k pseudo-potentials provided in the GTH_POTENTIALS file.
Best,
Geng

@mtaillefumier
Copy link
Collaborator

Hi geng,

You can try cp2k master if you want to test lda+U+cp2k+sirius. The necessary code was merged during the summer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants