2.2 Running Stage

Before running stage, first make sure the Player executable can be found in your path (Stage will automatically start an instance of Player, so it needs to know where to find the Player executable). For example, try:

      $ which player

and make sure it returns a valid Player executable path, such as

      ~/player-1.3/bin/player

If not, set your PATH variable to include the Player binary directory. For example, in BASH do:

  
      $ export PATH=$PATH:$HOME/player-1.2/bin

The general command line to run Stage is:

 
      stage [options] <filename.world>

By convention, Stage configuration files end with a `.world' extension and are referred to as 'world files'. A world file specifies what stage must simulate. The user can override some of the world file settings at run time using the command-line options described below. If all is well, Stage will start up, load the world file, and spawn an Player. Each step causes a message on standard output, so a sample invocation and start up would look like this:

 
        $ stage worlds/everything.world

         ** Stage  v1.3 ** 
        [World worlds/everything.world]
        [Server localhost:6601]
        ** Player v1.3 ** [Stage /tmp/stageIO.username.0]

At this point you should be able to interact with objects in the world with the GUI (try dragging things around) and access sensors and actuators through Player. Try using the Player client program (<player_root>/utils/playerv/playerv) to see the output from some sensors.