-
Notifications
You must be signed in to change notification settings - Fork 30
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
FCISolver expects max_memory = remaining memory in PySCF #54
Comments
Could you make a MWE of this issue? |
Sure, here is the script:
|
Can I see the output of this:
It hasn't converged yet, but it isn't crashing. |
sure, here's what it returns |
I added 'mol.max_memory = 20000' in my input file and LASSCF is running and hasn't crushed yet, will see how it goes. |
max_memory in the FCI kernel call in lasci_sync was incorrectly overwritten to *remaining* memory, causing incorrect exceptions to be raised. Just unset that kwarg since the corresponding member is set correctly at object initialization.
Yeah it probably won't but see my recent commit to the dev branch above. This was caused by an actual bug I just found in which |
no problem running calculations now |
PySCF apparently wants "remaining memory" on entry to fcisolver kernel. CSFSolver currently wants "maximum memory" (the config input by user) instead. Fix calling lines in LASSCF functions to the CSFSolver behavior for now. Maybe the CSFSolver behavior needs to change? Maybe the PySCF behavior needs to change?
There were other points in my code where I did the same thing: passed remaining memory as max_memory. However, I just discovered that the reason I did this is that this is PySCF convention: the FCISolver kernel is written to expect remaining memory. I don't like this and it's hard to change CSFSolver to match it. Commit 21a1a51 matches the LASSCF calling functions to the CSFSolver expected behavior for now, but I have to change the latter (or convince the PySCF maintainers to change their FCISolver behavior) if I ever want to migrate CSFSolver to PySCF... |
I have updated my dev branch:
but still had the error message:
The shared path has the same issue
The text was updated successfully, but these errors were encountered: