[Carpet] expensive logging of CarpetRegrid[2] parameter changes

[Erik Schnetter]

On Nov 7, 2007, at 09:53:37, Thomas Radke wrote:

> Hi,
>
> CarpetRegrid[2] provides steerable parameters as an interface for  
> other
> thorns to change the grid structure. I just found out that those
> parameters are steered rather frequently which then may cause problems
> when runtime parameter changes are to be logged (eg. as thorn  
> Formaline
> can do): logging every individual parameter change becomes
> runtime-expensive, and the logfile may grow to unreasonable sizes.
>
> As a measure to prevent this situation, we could exlude changes for  
> some
> parameters from being logged. I believe this is not a very good  
> solution
> though.
> Instead we should think about changing the way how thorns can interact
> with CarpetRegrid[2]. Maybe they could communicate via grid variables
> instead of steerable parameters ?

I found in the past that using parameter steering during simulations  
does not work.  There are two main problems.  The first is that there  
is no machine-readable output about parameter values, and the other  
is that parameter settings are often overwritten during recovery.  I  
have therefore already implemented such grid scalars, and these grid  
scalars are used by other thorns, e.g. CarpetTracker.  The parameters  
are only used during initialisation.

I will remove the STEERABLE tags, since they are now outdated.

-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 : /archives/developers/attachments/20071107/fa4b56a3/attachment.pgp