(1) Firstly I carried out an entirely new run, and got the file
run1.restart;
(2) then I modified the input file with the following lines (and
deleted the FORCE_EVAL%SUBSYS section):
&EXT_RESTART
RESTART_FILE_NAME run1.restart
RESTART_POS
RESTART_VEL
RESTART_CELL
RESTART_COUNTERS FALSE
RESTART_AVERAGES FALSE
RESTART_KG_THERMOSTAT FALSE
RESTART_THERMOSTAT FALSE
&END EXT_RESTART
After the this run, I got the run2.restart;
(3) And I continued to carry out the third run with run2.restart, but
failed because coordinates and velocities are missing in run2.restart.
Is there any additional switch to turn on the coordinates and
velocities writing in restart file when I restart from the previous
run? Or is this a minor flaw for CP2K with unexpected operations?
Thanks in advance!
Who told you to delete the SUBSYS section?
Did you find this written somewhere?
Teo.
> --
> You received this message because you are subscribed to the Google
> Groups "cp2k" group.
> To post to this group, send email to cp...@googlegroups.com.
> To unsubscribe from this group, send email to cp2k
> +unsub...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/
> group/cp2k?hl=en.
>
Zhigang
> > group/cp2k?hl=en.- 隐藏被引用文字 -
>
> - 显示引用的文字 -
rather than adding more words into the input reference on the usage
of the EXT_RESTART section,
it is enough that you don't put too much imagination in the
construction of your input files.
If you find somewhere a single sentence about the redundancy you have
imagined please let us know and I
will personally remove it. Until then, the usage of the EXT_RESTART
section should be already pretty clear.
Nonetheless, if you think that the information on this topic should
be improved feel free to modify the pages here on the
google group.
Teo