<div>Hi,</div><div><br></div><div>The vdw functionaliity supported by SIRIUS can be activated with the option VDW_FUNCTIONAL FUNC_VDWDF (or one the two others options) that you have to add in the parameters section (<i>c.f. the attached file</i>). I picked a different pp file but it does not matter much. <br></div><div>You will need to use the current development version of cp2k though. <br></div><div><br></div><div>If you already use it, then a<b> git pull -r</b> and <b>make .... </b>will be needed. the VDW support in SIRIUS was not on by default previously but you mentioned you compiled SIRIUS with it. </div><div><br></div><div>I would still consider this as experimental. The library seems robust but we never really tested deeply so any comment / problem reporting is welcome. <br></div><div><br></div><div>I also remarked that you are doing some lattice relaxation. If you encounter some odd behavior could you report them here so I can have a look. I would really appreciate to get this information back.</div><div><br></div><div>Best</div><div><br></div><div>M.<br></div><div class="gmail_quote"><div dir="auto" class="gmail_attr">Le lundi 5 septembre 2022 à 10:09:08 UTC+2, Dialogicus a écrit :<br/></div><blockquote class="gmail_quote" style="margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div>Thank you for your advice. U<span dir="ltr"><span>nfortunately</span></span>, it doesn't work. <span dir="ltr"><span></span></span> CP2K can't identify FUNC_VDWDF as a keyword or subsection. The out file says</div><div><br></div><div><br></div><div><font size="2">Possible matches for unknown subsection <br><br>FUNC_VDWDF<br><br> enum BEEFVDW in section %__ROOT__%FORCE_EVAL%DFT%KG_METHOD%XC%XC_FUNCTIONAL for keyword _SECTION_PARAMETERS_ score: 103<br> subsection LDA_C_VWN in section %__ROOT__%FORCE_EVAL%DFT%KG_METHOD%XC%XC_FUNCTIONAL score: 103<br> subsection MGGA_C_DLDF in section %__ROOT__%FORCE_EVAL%DFT%KG_METHOD%XC%XC_FUNCTIONAL score: 103<br> subsection GGA_C_CCDF in section %__ROOT__%FORCE_EVAL%DFT%KG_METHOD%XC%XC_FUNCTIONAL score: 103<br> enum BEEFVDW in section %__ROOT__%FORCE_EVAL%DFT%ENERGY_CORRECTION%XC%XC_FUNCTIONAL for keyword _SECTION_PARAMETERS_ score: 103<br><br> *******************************************************************************<br> * ___ *<br> * / \ *<br> * [ABORT] *<br> * \___/ unknown subsection FUNC_VDWDF of section XC_FUNCTIONAL *<br> * | *<br> * O/| *<br> * /| | *<br> * / \ input/input_parsing.F:187 *<br> *******************************************************************************</font></div><div><br></div><div><br></div><div>As far as I understand, this error means invalid syntax for CP2K, but not for SIRIUS. So, is there any way to send information about vdW functional directly to SIRIUS run (e.g. SIRIUS includes this functional automatically in each run)?</div><div><br></div><div>--</div><div>D.<br></div><br><div class="gmail_quote"><div dir="auto" class="gmail_attr"><br></div><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>Hi,</div><div><br></div><div>CP2K implementation of vdw is completely independent of libvdwxc which is used in SIRIUS. It means in practice that <br></div><div><ul><li>there is no direct path in place in cp2k to parse the VDW_POTENTIAL section and find the relevant functional supported in libvdwxc (and SIRIUS).It should probably be added if possible.<br></li><li>the VDW_POTENTIAL section is simply ignored when SIRIUS is initialized. It means that the calculations are correct but simply ignore the vdw corrections.<br></li><li>CP2K documentation is misleading</li></ul><div>If you wish to try a vdwxc functional with SIRIUS, then have a look at the functional supported by libvdwxc (<a href="https://libvdwxc.gitlab.io/libvdwxc/background.html#van-der-waals-forces" rel="nofollow" target="_blank" data-saferedirecturl="https://www.google.com/url?hl=fr&q=https://libvdwxc.gitlab.io/libvdwxc/background.html%23van-der-waals-forces&source=gmail&ust=1662548102861000&usg=AOvVaw0atLcoU1-_vK0S_HhHcrIc">https://libvdwxc.gitlab.io/libvdwxc/background.html#van-der-waals-forces</a>) that fit your needs and then add it to the list of functional XC_FUNC_VDWDF, XC_FUNC_VDWDF2, or XC_FUNC_VDWDFCX to the libxc section of your input file. <br></div><div><br></div><div>something like that might actually work.<br></div></div><div><br></div><div>&XC_FUNCTIONAL<br> &GGA_X_PBE_SOL<br> &END GGA_X_PBE_SOL<br> &GGA_C_PBE_SOL<br> &END GGA_C_PBE_SOL<br></div><div> &FUNC_VDWDF</div><div> &END FUNC_VDWDF</div><div>&END XC_FUNCTIONAL</div><div><br></div><div>let me know if it works or not.<br></div><div><br></div><div>Best</div><div><br></div><div>M.</div><div><br></div><div class="gmail_quote"><div dir="auto" class="gmail_attr">Le vendredi 2 septembre 2022 à 11:02:29 UTC+2, Dialogicus a écrit :<br></div><blockquote class="gmail_quote" style="margin:0 0 0 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><span>Dear CP2K users,</span>
<p><span>As
CP2K manual says it’s possible to use Van der Waals functionals in
the plane-wave calculations with SIRIUS.</span></p>
<p><span>I tried to run <span>Fm3m gold cell optimization using</span> pseudopotential <span><span>PW method</span></span>. VdW interactions were taken into account in
VDW_POTENTIAL subsection with NON_LOCAL type of dispersion functional. However, it seems there’s no difference between
calculations with and without dispersion correction. I suspect the
vdW functionals don’t work in my case.</span></p><p><span><span>My CP2K and SIRIUS are both linked with libvdwxc
library. </span></span></p>
<p><span>I
don’t know what I’m doing wrong. Is any ideas?</span></p>
<p><span>My
input and output files (with and without vdW correction) are attached
below.<br></span></p>
</blockquote></div></blockquote></div></blockquote></div>
<p></p>
-- <br />
You received this message because you are subscribed to the Google Groups "cp2k" group.<br />
To unsubscribe from this group and stop receiving emails from it, send an email to <a href="mailto:cp2k+unsubscribe@googlegroups.com">cp2k+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href="https://groups.google.com/d/msgid/cp2k/c6729c8c-5da6-4da5-876e-ae89a06a4835n%40googlegroups.com?utm_medium=email&utm_source=footer">https://groups.google.com/d/msgid/cp2k/c6729c8c-5da6-4da5-876e-ae89a06a4835n%40googlegroups.com</a>.<br />