noetic

Overview

grep for ROS bag files and live topics.

Searches through ROS messages and matches any message field value by regular expression patterns or plain text, regardless of field type. Can also look for specific values in specific message fields only.

By default, matches are printed to console. Additionally, matches can be written to a bagfile or HTML/CSV/Parquet/Postgres/SQL/SQLite, or published to live topics.

Supports both ROS1 and ROS2. ROS environment variables need to be set, at least ROS_VERSION.

In ROS1, messages can be grepped even if Python packages for message types are not installed. Using ROS1 live topics requires ROS master to be running.

Using ROS2 requires Python packages for message types to be available in path.

Supports loading custom plugins, mainly for additional output formats.

Example usage

Search for "my text" in all bags under current directory and subdirectories:

• grepros -r "my text"

Print 30 lines of the first message from each live ROS topic:

• grepros --max-per-topic 1 --lines-per-message 30 --live

Find first message containing "future" (case-insensitive) in my.bag:

• grepros future -I --max-count 1 --name my.bag

Find 10 messages, from geometry_msgs package, in "map" frame, from bags in current directory, reindexing any unindexed bags:

• grepros frame_id=map --type geometry_msgs/* --max-count 10 --reindex-if-unindexed

Pipe all diagnostics messages with "CPU usage" from live ROS topics to my.bag:

• grepros "CPU usage" --type *DiagnosticArray --no-console-output --write my.bag

Find messages with field "key" containing "0xA002", in topics ending with "diagnostics", in bags under "/tmp":

• grepros key=0xA002 --topic *diagnostics --path /tmp

Find diagnostics_msgs messages in bags in current directory, containing "navigation" in fields "name" or "message", print only header stamp and values:

• grepros --type diagnostic_msgs/* --select-field name message \
          --print-field header.stamp status.values -- navigation

Print first message from each lidar topic on host 1.2.3.4:

• ROS_MASTER_URI=http://1.2.3.4::11311 \
  grepros --live --topic *lidar* --max-per-topic 1

Export all bag messages to SQLite and Postgres, print only export progress:

• grepros -n my.bag --write my.bag.sqlite --no-console-output --no-verbose --progress
  
  grepros -n my.bag --write postgresql://user@host/dbname \
          --no-console-output --no-verbose --progress

Patterns use Python regular expression syntax, message matches if all match. '*' wildcards use simple globbing as zero or more characters, target matches if any value matches.

Note that some expressions may need to be quoted to avoid shell auto-unescaping or auto-expanding them, e.g. linear.x=2.?5 should be given as "linear.x=2\.?5".

Installation

Using pip

• pip install grepros

This will add the grepros command to path.

Requires ROS Python packages (ROS1: rospy, roslib, rosbag, genpy; ROS2: rclpy, rosidl_runtime_py).

If you don't want to install the ROS1 stack, and are only interested in using bag files, not grepping from or publishing to live topics, minimal ROS1 Python packages can also be installed separately with:

• pip install rospy rosbag roslib roslz4 \
      --extra-index-url https://rospypi.github.io/simple/

Using apt

If ROS apt repository has been added to system:

• sudo apt install ros-noetic-grepros  # ROS1
  
  sudo apt install ros-foxy-grepros    # ROS2

This will add the grepros command to the global ROS1 / ROS2 environment.

Using catkin

In a ROS1 workspace, under the source directory:

• git clone https://github.com/suurjaak/grepros.git
  cd grepros
  catkin build --this

This will add the grepros command to the local ROS1 workspace path.

Using colcon

In a ROS2 workspace, at the workspace root:

• git clone https://github.com/suurjaak/grepros.git src/grepros
  colcon build --packages-select grepros 

This will add the grepros command to the local ROS2 workspace path.

Homepage

Documentation and more examples at github.com/suurjaak/grepros.

Use GitHub to report bugs or submit feature requests. [View active issues]