-
Notifications
You must be signed in to change notification settings - Fork 45
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
Readers and writers for NWChem system library format #169
Comments
NWChem doesn't run with the basis sets BSE now gives; it gives an error about a string being too long. |
Looks like we need another set of parsers and writers for NWChem, since the system library format is incompatible with the input format 🤡 |
hmm is this due to some (semi) recent change to NWChem? And do we now have to version parsers/writers? |
I am pretty sure that you do not need to put each individual element into it's own basis set block. Just tried it on the latest development version and it works without that (haven't tried the latest release). I am not sure about the general contractions, but I would suspect that this is true. One would have to try it. |
It works in the input, but not if you read the basis set from file. |
OK. I didn't try from the file. Sorry about that confusion. |
Basis sets in NWChem format don't work with NWChem.
If you look at the NWChem manual
https://nwchemgit.github.io/Basis.html#how-to-use-basis-files-from-httpswwwbasissetexchangeorg-new-in-2019
there's actually several things wrong at present. At the bare minimum
For instance, this is what BSE gives as cc-pVDZ for H and He
In contrast, what NWChem expects is
Note especially that the basis set is defined separately for each atom; there's an
end
between all the entries and a newbasis
statement for each element.The text was updated successfully, but these errors were encountered: