Skip to content

Conversation

@JWilhelm
Copy link
Member

@JWilhelm JWilhelm commented Dec 5, 2021

  • regularized RI for periodic GW, enables use of large RI basis sets together with the minimum image convention (could be also interesting for periodic RI-Hartree-Fock)
  • diagonalization + inversion instead of Cholesky decomposition + inversion
  • still to do: k-points for self-energy for computing band structures

usage="PERIODIC", &
CALL keyword_create(keyword, __LOCATION__, name="PERIODIC_CORRECTION", &
description="If true, the periodic correction scheme is used employing k-points. "// &
"Method is not recommended to use, use instead PERIODIC_LOW_SCALING which much "// &
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which is much more accurate

CALL keyword_create( &
keyword, __LOCATION__, &
name="MAKE_CHI_POS_DEFINITE", &
description="If true, makes and eigenvalue decomposition of chi(iw,k) and removes negative "// &
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe: makes eigenvalue decomposition of chi(iw,k) positive semi-definite by removing negative values.

src/rpa_util.F Outdated
! ELSE
! ! we have only one kpoint per group
! num_proc_per_kp = para_env%num_pe/nkp
! END IF
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rather remove it for the production code.

src/rpa_main.F Outdated
! "GENERAL", virtual, para_env%num_pe, &
! kpgeneral=kpgeneral, with_xc_terms=.FALSE.)
!
! DEALLOCATE(kpgeneral)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is an info for you but not useful for production code.

IF (.FALSE.) THEN
IF (ASSOCIATED(kpoints_Sigma)) CALL kpoint_release(kpoints_Sigma)
IF (ASSOCIATED(kpoints_Sigma_no_xc)) CALL kpoint_release(kpoints_Sigma_no_xc)
END IF
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same as above.

@fstein93
Copy link
Contributor

fstein93 commented Dec 6, 2021

Maybe, I have overseen it, but have you added a regtest for the regularized RI?

@JWilhelm
Copy link
Member Author

JWilhelm commented Dec 6, 2021

Thank you for reviewing!

The description of keywords is now improved. The regularized RI is implicitly tested using the test "regtest-gw-cubic/G0W0_kpoints_from_Gamma.inp" using the default regularization parameter 1E-2. I agree that it could be a good idea to have a separate, explicit test, that is now "regtest-gw-cubic/G0W0_kpoints_from_Gamma_RI_regularization_1E-3.inp".

Concerning comments in the code: I understand that for production code, such comments should be avoided. As most of the comments will be anyway gone in the future (after completing band structure calculations from GW), might it be acceptable to leave the three comments (12 lines in total)?

@fstein93
Copy link
Contributor

fstein93 commented Dec 7, 2021

I am in favor of removing these lines because a new CP2K release is planned for the near future.

@JWilhelm
Copy link
Member Author

JWilhelm commented Dec 7, 2021

I hope that it is ok now... I will be happy if you could merge the pull request to see whether the other regtester are ok with the code changes. Thank you!

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

Successfully merging this pull request may close these issues.

3 participants