State logs are recordings of world state information from Gazebo. State includes pose, velocity, acceleration, and forces applied to all links of all models. Gazebo will only record state information for models that change over time. A state log file contains a header, the initial world description, and a time series of state.
Gazebo ships with a logging utility that is accessed via the
gz log command.
View the help information using:
gz help log
gz log -h
Tip: Check out the tutorial on logging and playback for an overview of ways to record a log.
Start by removing old log files
rm -rf ~/.gazebo/log/*
We will use the PR2 world to create a state log file.
Start by running the Gazebo server with the
-r command line option
gzserver -r worlds/pr2.world
After a few seconds, stop the server using ctrl-c.
A new time stamped directory should exist in
~/.gazebo/log with one subdirectory and a
state.log file. Here is an example
You can verify this log file by replaying it in Gazebo.
gazebo -p ~/.gazebo/log/*/gzserver/state.log
gz log command line tool provides mechanisms for stepping through a log file and echoing the contents of a log file to screen. The echo to screen feature can be combined with a filter to produce a log file that contains specific information such as just the pose of models and links.
Try echoing the recorded state log file to screen.
gz log -e -f ~/.gazebo/log/*/gzserver/state.log
You should see a lot of information scroll by.
Now let's remove all velocity, acceleration, and force information from the log file. This will leave just pose information.
gz log -e -f ~/.gazebo/log/*/gzserver/state.log --filter *.pose/*.pose
--filter option is a flexible command line argument to extract information from a log file.
Some guidelines for using the
/ to separate entities in a hierarchy, for example
. to access an entity's property, for example
Some available properties are:
Link: pose, velocity, acceleration, wrench
Pose, velocity, acceleration or wrench: x, y, z, r (roll), p (pitch), a (yaw)
* as a wildcard, for example
 to match any of the lower level properties, for example
It is also possible to filter based on simulation time using a Hz filter. For example, we can output state information at 30 Hz using:
gz log -e -f ~/.gazebo/log/*/gzserver/state.log -z 30
These filters can be combined and piped to a file for playback. This may take some time depending on the size of the state.log.
gz log -e -f ~/.gazebo/log/*/gzserver/state.log -z 30 --filter *.pose/*.pose > /tmp/filtered_state.log
This log file can then be replayed in Gazebo
gazebo -p /tmp/filtered_state.log