Walker command line parameters

Keyword -c, --control

Specify the control file name [REQUIRED]

This keyword is used to specify the name of the control file from which detailed user input is parsed.

Expected type: string

Keyword -h, --help

Display one-liner help on all command-line arguments

Get a short one-liner help on all command-line arguments from an executable. It also triggers the help from the Charm++ runtime system and in addition to that of the executable, it also lists command-line arguments from Converse Machine, Tracing, Load Balancer, Record/Replay, and Charm++ command-line parameters.

Keyword -C, --helpctr

Display one-liner help on all control file keywords

This keyword can be used to get a short one-liner help on all control file keywords from an executable.

Keyword -H, --helpkw

Display verbose help on a single keyword

This keyword can be used to get a verbose help on a single command-line argument or control-file keyword (i.e., help on keyword) from an executable.

Expected type: string

Keyword -L, --license

Show license information

This keyword is used to display license information for the executable/tool on the standard output and exit successfully.

Keyword -x, --particles

Specify the name of the particles position output file

This keyword is used to specify the name of the output file in which to store particles positions during a simulation.

Expected type: string

Keyword -p, --pdf

Specify the name of the PDF output file

This keyword is used to specify the name of the output file in which to store probability density functions (PDFs) during a simulation.

Expected type: string

Keyword -q, --quiescence

Enable quiescence detection

This keyword is used to enable the quiescence detection feature of Charm++, used to catch logic errors in the asynchronous control flow, resulting in deadlocks. This is useful for automated testing and debugging and does have some overhead, so it is off by default.

Keyword -O, --screen

Specify the screen output file

This option is used to set the screen output file name. The default is "\<executable\>_screen.log".

Expected type: string

Keyword -s, --stat

Specify the name of the statistical moments output file

This keyword is used to specify the name of the output file in which to store statistical moments during a simulation.

Expected type: string

Keyword -S, --state

Enable verbose chare state screen output

This keyword is used to enable verbose Charm++ chare state collection and screen output. The chare state is displayed after a run is finished and the data collected is grouped by chare id (thisIndex), and within groups data is ordered by the time-stamp when a given chare member function is called. See src/Base/ChareState.hpp for details on what is collected. Note that to collect chare state, the given chare must be instrumented. Note that if quescence detection is enabled, chare state collection is also automatically enabled, but the chare state is only output if quiescence is detected (which also triggers an error).

Keyword -t, --trace

Disable call and stack trace

This keyword can be used to disable the on-screen call trace and stack trace after an exception is thrown. Trace output is on by default and in some cases, the call and stack trace can be huge and not very helpful, hence this command line option.

Keyword -v, --verbose

Select verbose screen output

This keyword is used to select verbose screen-output as opposed to the default quiet output. With quiet output only the most important messages are echoed to screen.

Keyword -V, --version

Show version information

This keyword is used to display version information for the executable/tool on the standard output and exit successfully.

Keyword -u, --virtualization

Set degree of virtualization

This option is used to set the degree of virtualization (over-decomposition). The virtualization parameter is a real number between 0.0 and 1.0, inclusive, which controls the degree of virtualization or over-decomposition. Independent of the value of virtualization the work is approximately evenly distributed among the available processing elements. For zero virtualization (no over-decomposition), the work is simply decomposed into total_work/numPEs, which yields the smallest number of Charm++ chares and the largest chunks of work units. The other extreme is unity virtualization, which decomposes the total work into the smallest size work units possible, yielding the largest number of Charm++ chares. Obviously, the optimum will be between 0.0 and 1.0, depending on the problem.

Expected type: real

Lower bound: 0.000000

Upper bound: 1.000000

Expected valid choices: real between [0.000000...1.000000] (both inclusive)