-
Notifications
You must be signed in to change notification settings - Fork 156
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
Gaussian / xtb interface that provides Hessians #329
Comments
I guess, I start with my usual Gaussian disclaimer. Since I don't have access to Gaussian, I can't test any compatibility features.™ Leaving that aside, thanks for writing this up. Not sure if I want to include something I can't officially support, but I think a link from the documentation, similar to the Orca interface is possible. Also, I would prefer to fix issues in the The information used to infer whether Gaussian specific output should be written or not is currently stored in the input file type and accessible everywhere the molecular structure is available: Lines 800 to 809 in 0a0ed2c
|
Oh that actually looks way easier than I thought, thanks for the pointer. I guess I can just match the turbomole code by adding fres to writeResultsGaussianExternal? That's probably what I should have done from the get go :D I'll PR it when it's ready and tested. |
For the hessian it dependents on what Gaussian is expecting, a non-massweighted unprojected hessian is written here: Lines 475 to 478 in 0a0ed2c
The projected variant is written a few lines later: Lines 493 to 497 in 0a0ed2c
The frequency results object contains only the normal modes and frequencies, it might be necessary to cache the unmodified second deriviatives as well for this purpose. |
I'm try to test the xtb (6.3.2) interface with gaussian. Sorry for the dummy question, I tried many way to solve this issue without success. Really thanks for the great program and methods! |
This comment has been minimized.
This comment has been minimized.
Hey so I believe this is the issue fixed by #362 which is not yet in a released version. If that's the case, your folder should contain a file with name If that is the case, putting a |
It was hidden in the directory! Everything works now. Thansk for the hint and the great job you did on interfacing the hessian in the guassian external format! |
I saw this post and just want to ask is there a way I can run transition structure optimization in xtb? Or is there a way I can calculate hessian using xtb and feed to gaussian to do the transition structure optimization (as in Gaussian there is keyword TS for opt)? |
For Gaussian I can't offer any support here. |
I can attest that it does indeed work with Gaussian and all of its TS tools. In fact, that’s one of the applications that we envisioned from the start and I have been using it for that for a while now. Good luck with your tests! |
Thank you for your comments. I have tried the gsm with the example, but I got Segmentation fault, don't really know what is the problem. @gabegomes Can you share with more details, an example how to run your calculations for TS optimization will be really helpful? |
xtb currently ships with a preliminary interface to Gaussian. However, the basic interface doesn't include the ability to pass Hessian information, which is critical for some optimization problems (such as finding transition states), and can be used to improve the speed of Gaussian's own ab initio optimizations by reading xtb Hessians as initial Hessian guesses. In addition, the current xtb-gaussian interface is a bit fragile with respect to paths for input-output files.
For work we are currently engaged in, I coded a basic single-file Perl script that addresses these problems (based on an earlier Python version by @kjelljorner and @gabegomes ). It's located here, it's pretty robust and quite fast. It doesn't use any external perl packages so it should just work out of the box.
I currently have it licensed under MIT, meaning you can just integrate it directly in xtb if you want. I considered submitting it as a PR but I wasn't sure what your opinions are on introducing Perl code or on interop with Gaussian. If you are interested, I can probably write the necessary fortran code to move the feature into xtb proper, but I'm not sure when I will have time to do so.
Thanks for the great program!
The text was updated successfully, but these errors were encountered: