[Users] Termination condition: max_runtime

[Erik Schnetter]

On Dec 6, 2006, at 16:22:09, Ian Hinder wrote:

> Hi,
>
> I have recently started to use the Cactus termination condition
> 'max_runtime' defined in Cactus/src/param.ccl.  However, from  
> looking at
> Cactus/src/main/CactusDefaultEvolve.c it looks like the start time is
> computed only on the first step of the evolution; i.e. it does not
> include the time taken for initial data.  If the initial data
> computation is significant then the max_runtime is not correct.
>
> Would it be straightforward to set the start time before the initial
> data is computed?

This is an issue of the driver.

This is accidentally already corrected in the development version of  
Carpet.  The stable version keeps track of the time itself.  See the  
file Evolve.cc; the corresponding variable is called initial_runtime,  
which is set too late.  The development version calls the routine  
CCTK_RunTime() instead, which returns the correct value.

-erik

-- 
Erik Schnetter <schnetter at cct.lsu.edu>

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/users/attachments/20061206/59905d42/attachment.bin