You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being able to select the method can be useful in case GFN2-xTB is not suitable for the system of interest (hydrogen transfers). Also, a possibility to communicate charge and spin to xtb or set a higher electronic temperature would be nice here.
The text was updated successfully, but these errors were encountered:
ms860309
added a commit
to ms860309/pyGSM
that referenced
this issue
Jun 5, 2021
Being able to select the method can be useful in case GFN2-xTB is not suitable for the system of interest (hydrogen transfers). Also, a possibility to communicate charge and spin to xtb or set a higher electronic temperature would be nice here.
Hi,
So, I add some args to support different xtb hamiltonian, accuracy and electronic temperature.
Default value of the xtb hamiltonian is "GFN2-xTB", accuracy is 1.0 and electronic temperature is 300.0K.
Is it reasonable for using these default values?
Seems like GFN2-xTB is hardcoded as method for the
xtb
interface:pyGSM/pygsm/level_of_theories/xtb_lot.py
Line 41 in f1526ee
Being able to select the method can be useful in case GFN2-xTB is not suitable for the system of interest (hydrogen transfers). Also, a possibility to communicate charge and spin to
xtb
or set a higher electronic temperature would be nice here.The text was updated successfully, but these errors were encountered: