-
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
Fix fci init_guess #85
Conversation
Happy to merge. |
Hi Charlie, could we call this something more meaningful than |
f9d8e92
to
ec70d79
Compare
The pyscf initial guess for |
Codecov ReportPatch coverage:
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more Additional details and impacted files@@ Coverage Diff @@
## master #85 +/- ##
==========================================
- Coverage 71.72% 71.70% -0.03%
==========================================
Files 133 133
Lines 18460 18458 -2
Branches 2573 2514 -59
==========================================
- Hits 13241 13235 -6
- Misses 4486 4494 +8
+ Partials 733 729 -4
... and 11 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
This fixes the control of initial guesses within the FCI solver, which I came across in the process of trying to fix #84.
I would suggest we merge this after #69 for simplicity; it's not anything high priority.
8502952 added the function
to control the generation of initial guesses for FCI wavefunctions. This seems to have intended passing
solver_opts={"init_guess":None}
to result in an initial guess of the HF determinant, rather than the CISD wavefunction. However, due to inheritance within the code interpretingNone
as the user not passing anything in this actually results ininit_guess="default"(="CISD")
by the time it gets into this function.As a fix I've just changed this option to instead require "None" or "none". I've also added a test checking the energy of a prematurely terminated calculation correctly starting from the HF initial guess, which is hopefully OK so long as the first step of a davidson is deterministic (which I wouldn't be certain of, but seems OK in initial testing and we'll find out from the CI...).