-
Notifications
You must be signed in to change notification settings - Fork 9
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
Quantum caclulations crash with 'unknown error' #186
Comments
Hi @simonlichtinger thanks for the report, unfortunately, this has been an issue for a while now with the QCEngine interface to Psi4 in that some failure modes result in no useful error report our original issue is here and is still not resolved. Although if this case is a consistent source of failure it may help to improve the error reporting from psi4 and I will look into it. In the meantime, you may wish to change the level of theory to HF by creating and editing a fitting workflow and using that with BespokeFit?
Yes currently we don't support using an implicit solvent for the QM data generation but this should be straightforward to add as the QCEngine/Psi4 interface does support this its just a case of passing the settings via the interface and its something we could look at adding if it would be of use to you? |
Thanks @jthorton . I will try running with HF and implicit solvent then. Since this takes hours to fail (if it does), and I feel a little bit shaky on understanding the docs right, could you please confirm that these workflows are appropriate for ... ... using the HF method:
... using an implicit solvent (if this does indeed what I think it would do? Or is something else needed to make this happen? If so, that would certainly be a very useful feature for anyone with charged / highly dipolar ligands!)
Thanks, |
@simonlichtinger the HF workflow looks correct, the implicit solvent one while correct won't work as we don't pass on the implicit solvent settings and this will require some changes to BespokeFit to get working which we can look at adding. |
So I've tried around with this now. Unfortunately, running the following python script:
led to this error:
The command line
So there seems to be a problem with the fitting? Is there any way of retrying the fitting btw without re-doing all of the quantum calculations? As for implicit solvent, that would be a very useful feature, please do implement it if you have a chance. |
Strange it looks like the script ran into an error when trying to get the version from psi4, this could possibly be due to an oversubscription of resources, as the qc compute workers setting To save the progress you can add the --directory option to the command which is the location a database will be saved to meaning you can resubmit jobs and reuse cached data. If the optimisation did not converge with the default settings then you can edit them, the available ones are listed here, when building a workflow schema you will then need to save the file to json and supply it in the CLI under the option |
Thanks for the suggestion. It seems that indeed the 'auto' setting in the python script is what triggers the bug, it appears to run if I set a number of cores. With the CLI, I was now able to do a fit and obtain a forcefield, I will open an separate issue in due course about the interpretation of this. |
Dear bespoke fit devs,
Setup and how to reproduce
Ubuntu 18.04 LTS
Installation was the working consensus out of #183 , where psi4 version 1.6 was installed from the psi4 channel instead of conda-forge.
Input molecule file:
ala-ala.sdf.zip
Running command:
What happens
The software reaches the qc-generation step and spends several hours with this on 12 cores. Then the following error happens:
The created output file is:
output.zip
What else I've tried
Nothing else. Because bespoke fit has such little verbosity, I've not been able to see where this comes from or at what stage it happens.
Further note
I have previously noted that in QM geometry optimisations, this ligand sometimes behaves weird, at the level of B3LYP (but not HF), in that protons change location and the bonding pattern changes. I've previously attributed that to the fact that a dipeptide with charged termini might not be stable in vacuum, and an implicit solvent has fixed this. However, I have no way of telling whether this is the issue here because no intermediate files seem to be saved and since implicit solvent is not supported to my knowledge(?) I have not been able to try this out.
Many thanks
Simon
The text was updated successfully, but these errors were encountered: