-
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
Using the ANI to compute the single point energy and use xTB for geometry optimisation #157
Comments
Hi @xiki-tempula you must be reading my mind!! this is something I am currently looking to implement. This would allow users to select two different QC specifications to perform torsiondrives with the first to do the geometry optimisation and the second to perform single-point calculations. Ill let you know when we have a working proof of concept to try out! |
Thanks. Eager to try it out when it is available. |
@jthorton While we are at this issue. I think it would be nice to do the single point energy with psi4 as well. So one did the geometry optimisation with xTB and do the energy calculation with psi4 or ANI. |
@xiki-tempula Yes that should be possible my current implementation makes the options for the torsiondrives and single points fully configurable so users can pick any engine supported by QCEngine for either task! |
@jthorton Thanks. I wonder how should I do it? |
Yeah that's something that is not quite clear yet, you will have ultimate control by editing the workflow json files but we should come up with a way to edit this via the CLI as well. I think something similar to what you suggest would be a good start. |
@jthorton Thanks. I was wondering if I could have the default the workflow json files so I could try edit things and see how it goes? Thanks. |
Hi @xiki-tempula, I have a working prototype of this in #167 if you wanted to try it out and let me know how it goes? The PR introduces extra CLI arguments which let you specify a single point specification with the flag |
Sorry, just to be sure. So currently I cannot use xTB for geometry optimisation and psi4 for single point energy. So I would imagine that if I wish to do xTB + ANI, it would be |
That's what I found in testing using xtb + psi4 for a long time causes it to crash but xtb and ani was fine. Yes, that command looks correct! |
Hi @jthorton sorry for the delay. I'm picking out this issue again. I wonder if the branch is still up to date? where I added in
Where I got
Please also find my conda env attached |
Hi @xiki-tempula, this branch fell out of sync and needs updating to work with new versions of the toolkit, I'll look into updating this and getting it back online for testing soon. |
Hi, I wonder if this branch will be merged to the main? Thank you. |
In #152 (comment), it is mentioned that
Of course as we use QCEngine to do our QC reference generation you can use any supported package, however with ANI we often hit geometry optimisation convergence issues in testing but you are welcome to try yourself just add the following to your run command --default-qc-spec torchani ani2x none
I wonder if it is possible to use xTB for geometry optimisation and ANI for energy calculation? So as to skip the geometry optimisation convergence issue with ANI.
The text was updated successfully, but these errors were encountered: