7.48 writelog

Authors

Andrew Howard ahoward(at)usc.edu

Synopsis

The writelog driver can be used to store data from other devices within the Player server. The log files generated in this way can be ``replayed'' using the readlog driver. See the below for some usage examples of the writelog driver.

Interfaces

The writelog driver currently supports the null interface, meaning that it generates no data, and accepts no commands or configuration requests.

Currently, the writelog driver is capable of storing data from the following interfaces: laser, position, wifi.

Configuration file options

Name Type Default Meaning

filename string writelog.log Output log file name

devices list none A list of strings specifiying the devices whose data should be stored. Each device is specified as ``device:index''.

Example: Storing Odometry and Laser Data

The following configuration file will odometry from a Pioneer and laser data from a SickLMS200 to a log file.

  position:0 (driver "p2os_position")
  laser:0 (driver "sicklms200")
  null:0 
  (
    driver "writelog" 
    filename "foo.log" 
    devices ["position:0" "laser:0"]
    alwayson 1
  )

Note that the alwayson flag will cause the driver to start logging data as soon as Player is started, and will continue logging data until Player is stopped.

Look in Section 7.36 for an example that shows how to replay this data using the readlog driver.