| Author(s): | Erik Schnetter <schnetter@cct.lsu.edu> |
| Date: | July 06 2007 |
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 repository remembering how initial data are to be set up, so that other thorns can check their actions against this thorn.
There are several possibilities:
This thorn does not set up any initial data by itself. It only selects the mechanism; it is the responsibility of other thorns to follow this specification. If all other thorns follow this specification, then they are guaranteed to interact nicely. If other thorns ignore this specification, then end-users may be surprised and may have difficulties setting up parameter files which work correctly.
initial_data_setup_method | Scope: restricted | KEYWORD |
Description: Procedure for setting up initial data
| ||
| Range | Default: init_some_levels | |
init_some_levels | Set up at least one time level; other time levels are scratch space
| |
init_single_level | Set up exactly one time level; other time levels are not accessed
| |
init_two_levels | Set up exactly two time levels; other time levels are not accessed
| |
init_all_levels | Set up all active time levels
| |
Implements:
initbase
This section lists all the variables which are assigned storage by thorn CactusBase/InitBase. Storage can either last for the duration of the run (Always means that if this thorn is activated storage will be assigned, Conditional means that if this thorn is activated storage will be assigned for the duration of the run if some condition is met), or can be turned on for the duration of a schedule function.
NONE