Check/Modify Parameters

Thorn PUGH

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.

initialize_memory noneHow to initialize memory for grid variables at allocation time (none)
storage_report_every 0How often to provide a report on storage information (0)
storage_verbose noReport on memory assignment (no)

Fixed Parameters

cacheline_mult 4001 Multiplier for cacheline number (4001)
enable_all_storage no Enable storage for all GFs? (no)
ghost_size -1 The width of the ghost zone in each direction (-1)
ghost_size_x 1 The width of the ghost zone in the x direction (1)
ghost_size_y 1 The width of the ghost zone in the y direction (1)
ghost_size_z 1 The width of the ghost zone in the z direction (1)
global_nsize -1 The size of the grid in each spatial direction (-1)
global_nx 10 The size of the grid in the x direction (10)
global_ny 10 The size of the grid in the y direction (10)
global_nz 10 The size of the grid in the z direction (10)
info none Provide additional information about what PUGH is doing (none)
local_nsize 40 The size of the grid in each spatial direction (-1)
local_nx -1 The size of the grid in the x direction (-1)
local_ny -1 The size of the grid in the y direction (-1)
local_nz -1 The size of the grid in the z direction (-1)
local_size_includes_ghosts yes Does the local grid size include the ghost zones? (yes)
overloadabort yes Overload Abort driver function (yes)
overloadarraygroupsizeb yes Overload ArrayGroupSizeB driver function (yes)
overloadbarrier yes Overload Barrier driver function (yes)
overloaddisablegroupcomm yes Overload DisableGroupComm driver function (yes)
overloaddisablegroupstorage yes Overload DisableGroupStorage driver function (yes)
overloadenablegroupcomm yes Overload EnableGroupComm driver function (yes)
overloadenablegroupstorage yes Overload EnableGroupStorage driver function (yes)
overloadevolve yes Overload Evolve driver function (yes)
overloadexit yes Overload Exit driver function (yes)
overloadgroupdynamicdata yes Overload GroupDynamicData driver function (yes)
overloadmyproc yes Overload MyProc driver function (yes)
overloadnprocs yes Overload nProcs driver function (yes)
overloadparallelinit yes Overload ParallelInit driver function (yes)
overloadquerygroupstorageb yes Overload QueryGroupStorageB driver function (yes)
overloadsyncgroup yes Overload SyncGroup driver function (yes)
padding_active no Pad 3D arrays so they line up on cache lines? (no)
padding_address_spacing 24 Number of CCTK_REALs to space starting addresses in lowest padding_cacheline_bits bits (24)
padding_cacheline_bits 12 Number of bits which have to be unique to pad properly for cache lines (12)
padding_size 4112 How many CCTK_REALs to pad by; we have to noodle around with the starting address, so if there isn't enough space we may not be able to pad (4112)
partition automatic Is the partition manual (automatic)
partition_1d_x Tells how to partition on direction X ()
partition_2d_x Tells how to partition on direction X ()
partition_2d_y Tells how to partition on direction y ()
partition_3d_x Tells how to partition on direction X ()
partition_3d_y Tells how to partition on direction y ()
partition_3d_z Tells how to partition on direction z ()
periodic no Periodic boundary conditions (no)
periodic_x yes Periodic boundary conditions in x-direction (yes)
periodic_y yes Periodic boundary conditions in y-direction (yes)
periodic_z yes Periodic boundary conditions in z-direction (yes)
processor_topology automatic How to determine the processor topology (automatic)
processor_topology_1d_x 0 No of Procs in X direction (0)
processor_topology_2d_x 0 No of Procs in X direction (0)
processor_topology_2d_y 0 No of Procs in X direction (0)
processor_topology_3d_x 0 No of Procs in X direction (0)
processor_topology_3d_y 0 No of Procs in X direction (0)
processor_topology_3d_z 0 No of Procs in X direction (0)
timer_output no Print time spent in communication (no)