writelog
[Drivers]
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 the file is given in the data logging tutorial.The readlog driver can be used to replay the data (to client programs, the replayed data will appear to come from the real sensors).
The writelog driver logs data independently of any client connections to the devices that it is logging. As long as it's enabled and recording, the writelog driver records data from the specified list of devices at the rate that new data is produced by the first device in that list (so put the fastest one first). Commands are not logged.
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
- none
- Provides
- log : can be used to turn logging on/off
- Requires
The following interfaces are supported in principle but are currently disabled because they need to be updated:
- Configuration requests
- PLAYER_LOG_SET_WRITE_STATE
- PLAYER_LOG_GET_STATE
- PLAYER_LOG_SET_FILENAME
- 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.
- Example
# Log data from laser:0 position2d:0 to "mydata.log" driver ( name "writelog" filename "mydata.log" requires ["laser:0" "position2d:0"] provides ["log:0"] alwayson 1 autorecord 1 )
- Author:
- Andrew Howard