-
Notifications
You must be signed in to change notification settings - Fork 52
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
NWChem "driver" arguments within autodE #260
Comments
Hi, Any updates about this? Thanks E77 |
Hi! Sorry for missing this – as of autodE v1.3.0 NWChem uses the inbuilt optimisers rather than those available in NWChem, due to my limited success with them (not being able to optimise butane for example..). Unfortunately that means there's no configuration options like you mentioned as the autodE optimisers e.g. crfo have a hard coded values, which is far from ideal. There are issues to improve this e.g. #265 and #262 which should make their way into v1.4.0. In the mean time if you need to use configurable NWChem it may be best to revert to v1.2, or create an autodE fork and modify those parameters if you're happy diving into the code! hope that's helpful 😄 |
@t-young31 It should be possible to add some extra config options to |
Hi Please go ahead :-) Thanks a lot E77 |
Hello,
What would be the ideal way to tune up NWChem driver when configuring a python script for autodE? Something like introducing these lines:
driver
clear
trust xx
maxiter yyy
end
Thanks a lot
E77
The text was updated successfully, but these errors were encountered: