-
Notifications
You must be signed in to change notification settings - Fork 169
Parse empirical dispersion corrections #745
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
62e4160
to
fced82d
Compare
d4119fd
to
c5d2959
Compare
Comment to myself: this is still draft while the following issues exist
|
Is this a difference between D3 "zero" and D3BJ? |
@ghutchis if I remember correctly, it's mostly that, but there may have been something else. I started switching from D3(0) to D3(BJ) since not all programs I have access to can do D3(0), strangely. I'll check tonight, also to make sure I don't have changes in a stash. |
The Firefly example seems totally out of left field.. You can always check with dftd3 to get the 'authentic' numbers: That's the Psi4 modified version, but IIRC Lori didn't change anything (https://github.com/loriab/dftd3) |
Here's the current state of this PR. Some of these might just be stray untracked outputs in my work directories. All calculations using BP86.
Filtered just for D3(0) and working,
It looks like the next reasonable tasks are:
Anything for Molpro will have to wait until #872 is done, which will take more time. |
The Q-Chem and Firefly results with
This indicates that
|
I've updated the geometry for the DALTON calculation and now the results are identical. To take a look at the raw outputs, we can see that at least part of the Firefly parameters are different from DALTON and Q-Chem:
The nuclear repulsion energy is also wrong, even before adding the dispersion correction. DALTON:
Q-Chem:
Firefly:
|
Molpro is implemented, but not tested, since there are bigger problems with parsing MO coefficients from the latest version (#872). |
Sorry for the delay. This looks good to me, and I'm in favor of merging. I just have a question:
|
# However, they vary wildly in form and number, making parsing problematic | ||
line = next(inputfile) | ||
while 'Dispersion correction' not in line: | ||
line = next(inputfile) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we do self.skip_lines(inputfile,["Dispersion parameters"])
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It isn't clear if the number of lines to skip is fixed, and we (I?) do this in other places.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think there's some details to fill in here. But given the magnitude of this change, I think Shiv is right and I'm going to merge. We can clean up anything that's left later.
I see in the 8.2.0 (latest version) changelog
which may account for this (I used 8.1.1). It's possible that 8.2.0 has fixed this. I have the 8.2.0 archive, but never registered it to get the password. |
I can't think of anything off the top of my head. What do you think is missing? |
Extends #418 to all parsers. Closes #660. Closes #664.