Skip to content
  • P 21/a symmetry not found

    Geometry Editing
    5
    0 Votes
    5 Posts
    117 Views

    Good! The clean way is:

    CRYSTAL
    1 0 0
    P 21/A

    I guess the extra "1"s you put are safe as they correspond to the identity operator.

  • Raman CPHF restart

    Vibrational Spectroscopies: IR, Raman, INS
    6
    0 Votes
    6 Posts
    207 Views

    Yes sure. No problem.
    I'm copying it here below.
    Thank you for the help

    Daria

    Furfural CRYSTAL 0 0 0 19 7.83542762 10.92181175 14.94182734 90.000000 90.000000 90.000000 33 8 1.907561246186E-01 3.035506248522E-01 4.408415126674E-01 8 -4.953260939445E-01 3.221701934644E-01 3.435788389827E-01 6 2.036695655476E-01 3.000622663369E-01 3.482645168957E-01 6 4.363374159111E-02 2.908170991680E-01 3.122160878064E-01 1 1.581732742072E-02 2.880586476013E-01 2.419150131741E-01 6 -7.402527715589E-02 2.893444053747E-01 3.842913887226E-01 1 -2.109486401803E-01 2.822752418693E-01 3.798189138779E-01 6 2.099722211847E-02 2.968688203007E-01 4.606664256414E-01 1 -9.310483322231E-03 2.937832972654E-01 -4.691825366176E-01 6 3.647591498990E-01 3.132132214593E-01 3.052219591009E-01 1 3.550467304924E-01 3.168499490771E-01 2.320173417360E-01 8 2.803460822693E-01 -3.091160241316E-01 4.442088720927E-01 8 -4.110526913885E-01 -3.641439806750E-01 3.516630126321E-01 6 2.872037985115E-01 -3.695128622796E-01 3.626185432797E-01 6 1.245767077225E-01 -3.991101749711E-01 3.362778399038E-01 1 9.163169834882E-02 -4.467733390550E-01 2.755816936910E-01 6 1.226510841197E-02 -3.550438914407E-01 4.034527830796E-01 1 -1.250093786328E-01 -3.609739865930E-01 4.033488316714E-01 6 1.122081912874E-01 -3.009269785992E-01 4.671425614917E-01 1 8.596288473646E-02 -2.539158941058E-01 -4.709004162095E-01 6 4.474098992917E-01 -3.907868742186E-01 3.203804132925E-01 1 4.349587971852E-01 -4.336723578587E-01 2.540887571847E-01 8 1.068738713332E-01 -3.851604875541E-02 3.194441316968E-01 8 -2.354778627755E-01 -1.170305051641E-02 3.709929081706E-01 6 5.921416878240E-02 -5.109842318475E-03 4.052174692072E-01 6 2.027905991547E-01 1.001107546720E-02 4.563966208009E-01 1 2.038099671676E-01 3.508046669402E-02 -4.738476409789E-01 6 3.453540637796E-01 -1.523126326522E-02 4.003413693017E-01 1 4.790458182320E-01 -1.335338648893E-02 4.173410231626E-01 6 2.808235437569E-01 -4.461452496729E-02 3.184022003331E-01 1 3.367732131084E-01 -7.306049141011E-02 2.558072164743E-01 6 -1.187612609562E-01 6.696688015001E-03 4.250681762815E-01 1 -1.454796120848E-01 3.516201574611E-02 4.940534466886E-01 FREQCALC NUMDERIV 2 INTENS INTRAMAN INTCPHF END END BASISSET POB-TZVP-REV2 DFT B3LYP-D3 XLGRID ENDdft SHRINK 4 4 TOLDEE 10 SCFDIR LEVSHIFT 6 1 FMIXING 30 TOLINTEG 7 7 7 7 14 EXCHSIZE 13220300 BIPOSIZE 13220300 ENDscf
  • 0 Votes
    4 Posts
    204 Views

    Hi,

    Hmmm...even though the SI file of the paper you have shared does point to using HSE06, it remains not entirely clear whether its parameters were kept default or altered (for all systems together or individually for instance).

    There are also differences between what different codes consider as "default" settings. For example, within the code used in the paper (VASP, nice code, no doubt), the defaults for HSE06 read (taken from https://www.vasp.at/wiki/index.php/List_of_hybrid_functionals) :
    $$ \omega= 0.2\ \mathring{A} , \quad c = 0.25, \quad \text{correlation}=\text{PBE}, $$ with the first number reading the range separation parameter (omega) and the second the fraction of exact exchange used (c).

    Within CRYSTAL (also nice code, no doubt), these read (taken from the manual, page 138):
    $$ \omega= 0.11\ a_0^{-1}, \quad c = 0.25, \quad \text{correlation}=\text{PBE}, $$ adopting the same labels.

    Not sure about the exact definition of units (perhaps a developer can comment if this is indeed Bohr radius as assumed?), but you can already see the subtle differences having to be taken into account when comparing between codes.

    A few other thoughts worth considering:

    In the paper, the structure was optimized with PBEsol and on top of that geometry HSE06 was applied as a single-point calculation. Not sure about the exact composition of those ZIFs, but the structural differences could play a significant role as well (planewave codes are very costly when optimizing a structure with hybrid functionals). Here is also a good read on this topic: doi.org/10.1088/2516-1075/aafc4b

    One final small comment. Within the PAW formalism implemented in VASP, scalar relativistic effects are included in the pseudopotentials by default. No problem, cool feature, but should be taken into account when comparing results, especially for heavier elements (longer discussion found here https://blog.vasp.at/forum/viewtopic.php?t=902)

    Hope this helps!

    Cheers,
    Aleks

  • Mixed Basis Sets for SOC

    Spin-Orbit Coupling and SCDFT
    3
    1 Votes
    3 Posts
    140 Views

    Thanks Jacques! These are very informative.
    The information for specific basis sets is helpful, I will try them.

  • 0 Votes
    3 Posts
    137 Views

    Hello Prof. Erba,

    Thank you for providing the reference and relevant pages. This is very useful.

    Best,
    Danny

  • Basis Sets for Spin-Orbit

    Spin-Orbit Coupling and SCDFT
    7
    0 Votes
    7 Posts
    206 Views

    Thank you so much
    this helped a lot

  • 0 Votes
    3 Posts
    126 Views

    Thank you very much for the detailed explanation—this really helped clarify things for me! The plot and your explanation made it all very clear.

  • 0 Votes
    11 Posts
    277 Views

    Your response is incredibly valuable—thank you so much.I suspect that the DIIS/Anderson extrapolation might have 'hit' a local minimum, so the density guess in iteration 8 happened to yield a total energy extremely close to that of the previous step, resulting in a very small ΔE.
    CYC 0 ETOT(AU) -8.456120523718E+03 DETOT -8.46E+03 tst 0.00E+00 PX 1.00E+00
    CYC 1 ETOT(AU) -8.390242659622E+03 DETOT 6.59E+01 tst 0.00E+00 PX 1.00E+00
    CYC 2 ETOT(AU) -8.391027170997E+03 DETOT -7.85E-01 tst 3.34E-03 PX 1.13E-01
    CYC 3 ETOT(AU) -8.391734802465E+03 DETOT -7.08E-01 tst 2.44E-03 PX 1.02E-01
    CYC 4 ETOT(AU) -8.392064543836E+03 DETOT -3.30E-01 tst 8.38E-04 PX 4.49E-02
    CYC 5 ETOT(AU) -8.392086825687E+03 DETOT -2.23E-02 tst 1.24E-04 PX 1.72E-02
    CYC 6 ETOT(AU) -8.392095974656E+03 DETOT -9.15E-03 tst 2.86E-05 PX 9.66E-03
    CYC 7 ETOT(AU) -8.392097542826E+03 DETOT -1.57E-03 tst 3.85E-06 PX 4.81E-03
    CYC 8 ETOT(AU) -8.392097541980E+03 DETOT 8.46E-07 tst 5.41E-06 PX 3.18E-03
    CYC 9 ETOT(AU) -8.392098065539E+03 DETOT -5.24E-04 tst 4.69E-06 PX 3.18E-03
    While this DETOT value satisfies the default energy convergence criterion, the corresponding values suggest that the electron density had not yet fully stabilized. This aligns well with your suggestion that tightening the convergence threshold would lead to a more reliable result.
    Thank you again for your guidance.

  • Usage of the RESTART Keyword

    Geometry Optimisations
    6
    0 Votes
    6 Posts
    167 Views

    Many thanks for your detailed explanation and for checking the code — that definitely clarifies things. I really appreciate your help!

  • Error in Projected DOS Atom Indices

    Density-of-States
    3
    0 Votes
    3 Posts
    96 Views

    Oh yes, right. My apologies. I did not notice this. Thank you Giacomo!

  • COHP calculations Issue

    Moved Density-of-States
    3
    0 Votes
    3 Posts
    129 Views

    Hi,

    Can you try to re-run the COHP calculation by using:

    COHP 16 500 200 360 2 12 0

    instead of

    COHP 16 500 200 360 1 12 0

    This should generate a file COHP.DAT
    Let me know how this goes.

  • 0 Votes
    4 Posts
    118 Views

    Hi Alessandro and Giacomo,

    Thank you for the clear and helpful explanations!

    I tried running the calculation with 32 cores, and it indeed helped with memory management. I’ll continue experimenting to optimize performance. Really appreciate your guidance and the references!

  • 0 Votes
    10 Posts
    317 Views

    you're the best, thank you for going extra mile

  • 0 Votes
    3 Posts
    98 Views

    Thank you very much, that worked (but not restart)

  • Spin polarised calculation

    Moved Single-Point Calculations
    6
    0 Votes
    6 Posts
    234 Views

    Dear Eleonora and Aleks,

    Thank you so much for the detailed explanation and for sharing the corrected input/output file. That really clarified the issue. I tried your suggested settings with FMIXING and SPINLOCK adjustments, and the geometry optimization is running well with no errors. Have a nice day!

    Best,
    Aparajita

  • 0 Votes
    2 Posts
    111 Views

    Hi,

    I think that the best way to proceed in this case would be to restart the calculation one or more times. To do this, you just have to make sure that the scratch folder is not deleted when the calculation stops. Basically, you would run a first job with:

    FREQCALC END

    Then, after the first calculation stops (maybe because you reached a wall clock time limit) you would run a second job restarting from the first as:

    FREQCALC RESTART END

    In order to make this restart work, you need a few files from the previous job to be placed in the scratch folder of the new job: FREQINFO.DAT, fort.13 and fort.9 (to be renamed fort.20 in the new folder).

    If needed, you can repeat this restart process multiple times until completion of the frequency calculation.

    Hope this helps,

  • geometry optimization runs out of cycles

    Geometry Optimisations
    3
    0 Votes
    3 Posts
    122 Views

    thank you

  • 0 Votes
    5 Posts
    175 Views

    very grateful, I will run it again but not sure what to do here if it aborts again

  • Input MOF geometry problem

    Geometry Editing
    8
    0 Votes
    8 Posts
    204 Views

    GiacomoAmbrogio

    Dear Ambrogio,

    Thank you so much! the problem has been perfectly solved.

    All the best,

    wang

  • Anisotropic Shrinking Factor

    Single-Point Calculations
    3
    0 Votes
    3 Posts
    91 Views

    Hey,

    Thank you. It works now. This Forum is a great idea!