restarting optimization after timeout
Posted: Fri Mar 11, 2016 2:52 pm
Is there any reasonable possibility to restart a vmc optimization after a timeout called by max_runtime?
The outfile does tell you that the next iteration will not fit into the allotted timeslot, but restarting is not possible using the --continue flag.
Is there any reasonable method to do so? Simply putting the last correlation.out to correlation.data and restarting the calculation with a reduced number of cycles is most likely not a good idea, since one would then use the same random seed as in the first part of the calculation. Reading in config.in would be possible by using opt_vmc, but the config.in file may be flagged as having been produced by opt and not by vmc, depending on when the calculation stopped.
Is there any good solution to that other than "Give your calculation enough runtime?" It would be great if the optimization could simply resume where it has stopped. In principle, I guess all relevant information has to be there: a config file and the last correlation.out, it was working with.
Thanks,
Katharina
The outfile does tell you that the next iteration will not fit into the allotted timeslot, but restarting is not possible using the --continue flag.
Is there any reasonable method to do so? Simply putting the last correlation.out to correlation.data and restarting the calculation with a reduced number of cycles is most likely not a good idea, since one would then use the same random seed as in the first part of the calculation. Reading in config.in would be possible by using opt_vmc, but the config.in file may be flagged as having been produced by opt and not by vmc, depending on when the calculation stopped.
Is there any good solution to that other than "Give your calculation enough runtime?" It would be great if the optimization could simply resume where it has stopped. In principle, I guess all relevant information has to be there: a config file and the last correlation.out, it was working with.
Thanks,
Katharina