-
Notifications
You must be signed in to change notification settings - Fork 8
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
ebcc wavefunctions #126
ebcc wavefunctions #126
Conversation
… and moved ebcc solver to using this by default.
…al issues when rotating CCSD wavefunctions in general.
…ests with long runtimes are tagged veryslow.
f871ba9
to
50d423a
Compare
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #126 +/- ##
==========================================
+ Coverage 71.57% 71.78% +0.21%
==========================================
Files 145 147 +2
Lines 19357 19555 +198
Branches 3111 3163 +52
==========================================
+ Hits 13854 14038 +184
- Misses 4738 4748 +10
- Partials 765 769 +4
☔ View full report in Codecov by Sentry. |
I'd prefer to keep the |
That sounds good- I thought that might be the case, but wanted to verify that was the only cause of failures before bothering you with it |
done, will be live once the CI runs through |
…n by default, but veryslow tests can be run if desired.
Reverted and running, I think this is complete |
This adds CC wavefunction objects which use
ebcc
as a backend, rather thanpyscf
, along with tests for this functionality. With this we'll have a bit more flexibility in our wavefunction specifications, as it's compatible with arbitrary CC ansatzes. This is a prerequisite to making more use of coupled electron-boson clusters.I've also included a small tweak to the
pyproject.toml
which allows tests tagged veryslow to be run; previously our configuration was actually blocking running these tests, even when requested.