Stage takes the following command-line options. Where an option can also be set in the configuration file, the command line option takes precedence.
-n
No Player - do not spawn a Player. You can run
Player manually in Stage mode with
player -stage <device dir>. Useful for debugging Player or
if you want to use an alternative interface to Stage
devices.
|
-g
| Disables the Graphical User Interface. |
-o
| Output mode - enables console output showing timing and data throughput information |
-t <timeout in seconds>
| Timeout - Stage will quit after simulating the specified amount of time. Useful for batch runs. |
-u <update period in seconds>
| Stage will attempt to take this much real time (wall-clock time) to perform each update cycle. It does this by computing the cycle, then sleeping (or polling for input) for any remaining time. If the cycle's computation takes longer than the requested cycle time, Stage will run slower than requested. Default is 0.1 seconds. |
-v <simulation time step in seconds>
| Stage will simulate the passing of this much time per update cycle. Default is 0.1 seconds. By changing the ratio of real (-u) and simulated (-v) time, you can make Stage run faster than, slower than, or approximately at real-time. |
-f
| Fast mode - Stage will run as fast as possible; not attempting to match real time. Useful for batch runs. This is slightly more efficient than setting the desired update time to zero seconds (-u 0.0). |
-s
Stopped - Stage will start up with the clock stopped.
You can start and stop the clock by sending Stage a SIGUSR1 signal
(killall -s USR1 stage should do the trick; this command is
provided as the script <stage_root>/tools/pause.).
|