4.1 POSE Command Line Options

Command line options are handled like CHARM++ command line parameters. For namespace purity all POSE command line options have a _pose suffix. They can be inspected by appending a -h to an execution of a POSE program. Command line options override any defaults set in the pose_config.h file

• +stats_pose
  $\circ$ Turn on timing and statistics gathering for internal POSE operations. Produces a small slowdown in program.
  
• +dop_pose
  $\circ$ Turn on timing and statistics gathering for degree of parallelism calculations. Generates log files that can be loaded by ploticus scripts to produce graphs plotting active entities over time. Slows down program dramatically.
  
• +lb_on_pose
  $\circ$ Turn on POSE load balancing.
  
• +store_rate_pose N
  $\circ$ Default checkpointing rate: 1 for every STORE_RATE events.
  
• +spec_window_pose N
  $\circ$ Speculative window size: this is how far (in virtual time units) ahead of GVT posers are allowed to go.
  
• +min_leash_pose N and +min_leash_pose N
  $\circ$ Bounds on the speculative window, these are adjusted by adaptive synchronization strategies.
  
• +leash_flex_pose N
  $\circ$ Granularity of flexibility when speculative window is shrunk or expanded.
  
• +lb_skip_pose N
  $\circ$ This controls the frequency of load balance invocation. 1 in every LB_SKIP executions of the GVT algorithm will invoke load balancing.
• +lb_threshold_pose N
  $\circ$ Minimum threshold for load balancing, default is 4000
• +lb_diff_pose N
  $\circ$ Once the load has been analyzed, we compute the difference between the max and min PE loads. Only if this difference exceeds LB_DIFF do we bother migrating posers.
  
• +checkpoint_gvt_pose N
  $\circ$ Checkpoint to disk approximately every N GVT ticks (N is an integer). The default is 0, which indicates no checkpointing.
• +checkpoint_time_pose N
  $\circ$ Checkpoint to disk every N seconds (N is an integer). The default is 0, which indicates no checkpointing. If both this parameter and +checkpoint_gvt_pose are greater than 0, a warning will be given, the value of this parameter will be set to 0, and POSE will checkpoint based on GVT ticks.

As a technical point, pose command line parsing is done inside the POSE_init() call. Therefore, the most consistent behavior for interleaving pose command line options with user application options will be achieved by calling POSE_init() before handling user application command line arguments.