The writelog driver will write data from another device to a log file. Each data message is written to a separate line. The format for each supported interface is given below.
The readlog driver can be used to replay the data (to client programs, the replayed data will appear to come from the real sensors).
For help in remote-controlling logging, try playervcr. Note that you must declare a log device to allow logging control.
Note that unless you plan to remote-control this driver via the log interface (e.g., using playervcr), you should specify the
alwayson option in the configuration file so that logging start when Player starts.
- Compile-time dependencies
- log : can be used to turn logging on/off
The writelog driver takes as input a list of devices to log data from. The driver with the highest data rate should be placed first in the list. The writelog driver can will log data from the following interfaces:
- Configuration requests
- Configuration file options
- filename (string)
- Default: "writelog_YYYY_MM_DD_HH_MM.log", where YYYY is the year, MM is the month, etc.
- Name of logfile.
- autorecord (integer)
- Default: 0
- Default log state; set to 1 for continous logging.
- camera_save_images (integer)
- Default: 0
- Save camera data to image files as well as to the log file. The image files are named "writelog_YYYY_MM_DD_HH_MM_camera_II_NNNNNNN.pnm", where II is the device index and NNNNNNN is the frame number.
requires ["laser:0" "position:0"]
Generated on Tue May 3 14:16:12 2005 for Player by 1.3.6