.cfg file
From Murray Wiki
Jump to navigationJump to search
When initiating Player, you will use a command of the form player project.cfg
. Each .cfg file consists of a set of drivers for each element of the environment.
If Player is interacting with Stage, the .cfg file will contain a driver that provides "simulation:0"
, a plugin libstageplugin
and a worldfile.
Sample .cfg file
Written during MVWTfest_January_2007 by Kevin Oishi
# steelebot-simple based on simple.cfg # load the Stage plugin simulation driver driver ( name "stage" provides ["simulation:0" ] plugin "libstageplugin" # load the named file into the simulator worldfile "steelebot-simple.world" ) # load the map file driver ( name "stage" provides ["map:0"] model "mvwt" ) # steelebot / stage interface #1 (provides position2d) driver ( name "stage" provides ["position2d:0"] model "robot1" ) # steelebot/stage interface #2 driver (name "stage" provides ["6666:position2d:0"] model "robot2") # I don't know what this is...useful? ## Demonstrates use of a Player "abstract driver": one that doesn't ## interface directly with hardware, but only with other Player devices. ## The VFH driver attempts to drive to commanded positions without ## bumping into obstacles. #driver #( # name "vfh" # provides ["position2d:1"] # requires ["position2d:0" "laser:0" ] #)