[Developers] IO::recover = autoprobe

Erik Schnetter schnetter at cct.lsu.edu
Tue Dec 18 00:38:11 CST 2007


On Dec 17, 2007, at 19:38:37, Luca Baiotti wrote:

> Hi,
>
> I have used (by mistake) the following settings:
>
> IO::recover                             = autoprobe
> IO::recover_dir                         = "checkpoint"
> IO::recover_file                        = "checkpoint.chkpt.it_83200"
>
> while I should have used
>
> IO::recover                             = manual
>
>
> However, what should be the behaviour in this case? I think it should
> check whether the specified checkpoint file exist and, in case the
> checkpoint file was found, recover from it or, otherwise, start from
> initial data. But I have experienced a different behaviour, namely  
> that
> the run started from initial data, even if the checkpoint file existed
> in the specified directory.
>
> Could some developer please check?


With autoprobe, the parameter recover_file is ignored.  Cactus is  
supposed to look into recover_dir and restart from the latest  
checkpoint found there.  If there is no checkpoint, it is supposed to  
start from scratch.

I am using the autoprobe feature regularly, and it works fine for me.

There could have been something wrong with the checkpoint files or  
with the specification of the directory.  Do you still have the  
output from the run, which should contain explanatory comments of the  
recovery routine about whether it found checkpoint files and what it  
was going to do?

-erik

-- 
Erik Schnetter <schnetter at cct.lsu.edu>   http://www.cct.lsu.edu/ 
~eschnett/

My email is as private as my paper mail.  I therefore support encrypting
and signing email messages.  Get my PGP key from www.keyserver.net.




-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://www.cactuscode.org/pipermail/developers/attachments/20071217/bc7852e3/attachment.bin 


More information about the Developers mailing list