Check/Modify Parameters

Thorn Cactus

Parameters in Cactus can be either fixed or steerable. Steerable parameters are those which can be modified during a simulation. To change steerable parameters, edit the values and press the submit button. Before applying the new parameter value, Cactus will check that the parameter lies in the allowed range. Note that there is currently no log of parameters which have been modified.

The tables below show the parameter name, current value and description. The default value of each parameter is shown in brackets at the end of the description.

Steerable Parameters

The following parameters are steerable, but you do not have authorisation to change them. To change parameters you must first register on the Simulation Control Page.

cctk_final_time -1Final time for evolution (-1.0)
cctk_full_warnings noGive detailed information for each warning statement (no)
cctk_itlast 50000Final iteration number (10)
highlight_warning_messages yesHighlight CCTK warning messages ? (yes)
max_runtime 0Terminate evolution loop after a certain elapsed runtime (in minutes) (0.0)
terminate iterationCondition on which to terminate evolution loop (iteration)
terminate_next noTerminate on next iteration? (no)

Fixed Parameters

allow_mixeddim_gfs no Allow use of GFs from different dimensions (no)
cctk_brief_output no Give only brief output (no)
cctk_initial_time 0 Initial time for evolution (0.0)
cctk_run_title Description of this simulation ()
cctk_show_banners yes Show any registered banners for the different thorns (yes)
cctk_show_schedule yes Print the scheduling tree to standard output (yes)
cctk_strong_param_check yes Die on parameter errors in CCTK_PARAMCHECK (yes)
cctk_timer_output off Provide output from timers (off)
info_format basic What information do CCTK_INFO() and CCTK_VInfo() print? (basic)
manual_cache_setup no Set the cache size manually (no)
manual_cache_size 0 The size to set the cache to if not done automatically (bytes) (0)
manual_cacheline_bytes 0 The size of a cacheline if not set automatically (bytes) (0)
recovery_mode strict How to behave when recovering from a checkpoint (strict)