[Users] New thorn CactusBase/InitBase

[Erik Schnetter]

There is now a new thorn CactusBase/InitBase.  This thorn can help  
avoid uninitialised or multiply-initialised initial data, especially  
when mesh refinement is used.

This thorn InitBase specifis how initial data are to be set up.  It  
does not set up any initial data by itself, nor does it contain any  
routines which are to be called.  It is merely a convenient place to  
remember how initial data are to be set up, so that other thorns can  
check their actions against this thorn.  The "setup method" can e.g.  
be "initialise all time levels at once analytically", or "initialise  
only the current time level", etc.

The decision how to set up initial data is explicitly made by the  
user in the parameter file.  All thorns participating in initial data  
setup can then check their actions against this decision, reporting  
errors if there is an inconsistency.  The driver can also enforce  
that certain time levels are not to be accessed.

There is one parameter, InitBase::initial_data_setup_method, which  
selects the users' decision.  At the moment, nothing will happen yet  
when InitBase is used.  Future changes to the driver or to initial  
data routines will then contain the consistency checks.

-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/users/attachments/20080203/4b7472ab/attachment.bin