-
Notifications
You must be signed in to change notification settings - Fork 4
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
Turbomole: scf_damping not working #6
Comments
The syntax for the SCF damping for Turbomole has been changed, but unfortunately we forgot to update the manual accordingly. The old syntax proved too unflexible; now, you can exactly specify the damping value, for example:
|
Thanks so much for your prompt reply!
This seems only to set the start value. Can I also set the min value?
$scfdamp start=5.500 step=0.05 min=0.10
I guess, I have asked this before. Is there a way to restart with my own control file?
Am 31.10.2022 um 12:12 schrieb Thomas Weymuth:
… The syntax for the SCF damping for Turbomole has been changed, but unfortunately we forgot to update the manual accordingly. The old syntax proved too unflexible; now, you can exactly specify the damping value, for example:
```
scf_damping: true
scf_damping_value: 1.5
```
--
Univ.-Prof. Dr. Peter Burger
Institut fuer Anorganische und Angewandte Chemie
Universitaet Hamburg
Martin-Luther-King-Platz 6
D-20146 Hamburg
Tel.:+49 040 42838 3662
FAX 6097
email: ***@***.***
http://www.chemie.uni-hamburg.de/ac/burger/index.html
|
Unfortunately, both things are not possible. As for the damping, "step" is set to 0.05 while "min" is always set to 0.10. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For Turbomole
scf_damping: 'medium"
is not working
terminate called after throwing an instance of 'YAML::TypedBadConversion'
what(): yaml-cpp: error at line 7, column 21: bad conversion
Only the Boolean "true" works, which seems obvious from the YAML output.
I am using readuct version 4.1.0 - maybe I need a newer frontend?
The text was updated successfully, but these errors were encountered: