Discrepancy between TDHF and TIMEEV

Problems running VASP: crashes, internal errors, "wrong" results.

Moderators: Global Moderator, Moderator

Post Reply
Message
Author
ashwin_r
Newbie
Newbie
Posts: 5
Joined: Sat Nov 16, 2019 8:58 pm

Discrepancy between TDHF and TIMEEV

#1 Post by ashwin_r » Sun Dec 17, 2023 12:17 am

I'm trying to compare the outputs of a set of time-dependent calculations on LiF using TDHF and TIMEEV algorithms. I'm using a global hybrid XC-functional (AEXX=0.5) in these calculations. (Vasp version 6.4.2; Intel compiler+MKL)

From running a few tests, it appears that, minimally, one has to explicitly set LADDER=.TRUE. for the TIMEEV case otherwise it just reproduces the independent-particle spectrum. With that done, the TIMEEV spectrum now seems to capture the energy of the first excitonic peak correctly but the height is quite wrong. The overall shape of the spectrum with TIMEEV is also quite different from the TDHF case.

My files are attached.
LiF-AEXX0.5.png
You do not have the required permissions to view the files attached to this post.

pedro_melo
Global Moderator
Global Moderator
Posts: 69
Joined: Thu Nov 03, 2022 1:03 pm

Re: Discrepancy between TDHF and TIMEEV

#2 Post by pedro_melo » Thu Dec 21, 2023 11:40 am

Dear ashwin_r,

Thank you for reporting this issue. I am currently working on it and will come back to you with an answer as soon as possible.

Kind regards,
Pedro Melo

pedro_melo
Global Moderator
Global Moderator
Posts: 69
Joined: Thu Nov 03, 2022 1:03 pm

Re: Discrepancy between TDHF and TIMEEV

#3 Post by pedro_melo » Wed Jan 17, 2024 3:50 pm

Dear ashwin_r,

I have found that several default variables are reported with strange values in the OUTCAR you obtained during the time-evolution run. I have also reproduced the issue with my own runs. I am looking into this issue.

Kind regards,
Pedro Melo

ashwin_r
Newbie
Newbie
Posts: 5
Joined: Sat Nov 16, 2019 8:58 pm

Re: Discrepancy between TDHF and TIMEEV

#4 Post by ashwin_r » Fri Jan 19, 2024 10:17 pm

Dear Pedro,

I'll recheck my runs. But for now it seems that the problem is reproducible so I'll look forward to the bug-fix .

Best,
Ashwin

Post Reply