Dear Developer
I tried to perform a single point calculation using the PBE0 functional. I found that "Combine HF=0.25 PBEx=0.75 PBEc=1" and "Combine HF=0.25 RPBEx=0.75 PBEc=1" produced the same results. It seems that PBEx and RPBEx is the same in DALTON 2018 and DAL2016. This does not seem right, as these two exchange functionals are different. It seems to me that PBEx is defined as RPBEx (by comparing the results to other program). Could someone suggest a way to fix this? Thanks!
Best,
John
pbe0 functional
-
- Posts: 13
- Joined: 01 Dec 2013, 22:07
- First name(s): John
- Last name(s): Travers
- Affiliation: Boston University
- Country: United States
-
- Posts: 395
- Joined: 27 Jun 2013, 18:44
- First name(s): Hans Jørgen
- Middle name(s): Aagaard
- Last name(s): Jensen
- Affiliation: Universith of Southern Denmark
- Country: Denmark
Re: pbe0 functional
You are right, the RPBEx is wrong (in fact it is PBEx). It has been so since it was introduced in 2005 but it has not been discovered before now. (Code shows it is a cut and paste error.) I do not know how to fix this old C code, maybe someone else does.
-
- Posts: 1210
- Joined: 26 Aug 2013, 13:22
- First name(s): Radovan
- Last name(s): Bast
- Affiliation: none
- Country: Germany
Re: pbe0 functional
I am finally working on fixing this. I will report as soon as I am done.
-
- Posts: 395
- Joined: 27 Jun 2013, 18:44
- First name(s): Hans Jørgen
- Middle name(s): Aagaard
- Last name(s): Jensen
- Affiliation: Universith of Southern Denmark
- Country: Denmark
Re: pbe0 functional
RPBEX has now been fixed on the release/2020 branch on gitlab.
-
- Posts: 13
- Joined: 01 Dec 2013, 22:07
- First name(s): John
- Last name(s): Travers
- Affiliation: Boston University
- Country: United States
Re: pbe0 functional
thanks!
Who is online
Users browsing this forum: No registered users and 1 guest