The crucial line to making sure the new calculation starts where the old one finished is the keyword
initial_state=device_configuration
Never mind what nlprint says :-) It's defined in a certain way when applied to each type of object, and so nlprint(configuration) prints the geometry.
You actually don't have the option to restart from an interrupted run in ATK 10.8 because the self-consistent state is only saved to the NC file when the calculation finishes. We'll introduce checkpoint files soon.
| 122 E = -765.983 dE = 3.034982e-04 dH = 4.211894e-05 |
| 123 E = -765.983 dE = 2.804950e-08 dH = 4.217083e-05 |
| 124 E = -765.983 dE = 1.747253e-08 dH = 4.211418e-05 |
| 125 E = -765.983 dE = 3.189939e-09 dH = 4.215133e-05 |
| 126 E = -765.983 dE = 1.969966e-09 dH = 4.215458e-05 |
| 127 E = -765.983 dE = 1.499757e-09 dH = 4.215810e-05 |
| 128 E = -765.983 dE = 2.668173e-08 dH = 4.215502e-05 |
these are my last few electronic iterations any body have any suggestions how to get this to converge its keep doing this and then jumps to 10^-3