[Documentation] [TitleIndex] [WordIndex

Package Summary

Improved ROS message filters

  • Maintainer status: developed
  • Maintainer: Timo Röhling <timo.roehling AT fkie.fraunhofer DOT de>
  • Author: Timo Röhling <timo.roehling AT fkie.fraunhofer DOT de>
  • License: Apache-2.0
  • Source: git https://github.com/fkie/message_filters.git (branch: master)

Overview

This library is a replacement for the ROS message_filters package. It is written in modern C++ and more type-safe than the original version.

The data flow is modeled with a pipeline metaphor, where data always flows from a source to a sink. A filter is both source and sink for data, possibly with different data types. For integration with ROS, the library provides a number of subscribers and publishers which act as sources or sinks of the data flow.

Language Requirements

The library requires C++14 or better. Starting with Ubuntu 18.04 (ROS Melodic), GCC uses C++14 as default dialect. For older versions, you may or may not succeed by passing the command line option -std=gnu++1y to the compiler.

Design

The filters are written to be as data agnostic as possible. Therefore, many filters can process arbitrary data types and are not restricted to ROS messages. A few filters need access to ROS header information, such as time stamp or TF frame identifier.

Technically, the pipeline processing is executed by nested calls to receive and send functions. The library is thread-safe and exception-safe, but you are expected to handle your own exceptions in your callbacks. Exceptions which propagate through the library will abort processing for the message that caused the exception, and if not caught eventually by a preceding filter in the pipeline, terminate the program.

Certain filters, such as the Buffer or the TfFilter, can work with ROS callback queues for convenient data processing.

Available Filters

See the API documentation for more details.

Customizing Filters

While you are free to derive your own classes from the one of the base classes, most programs will merely want to register a custom callback function for their application logic.

Unlike the original message_filters, which mixed custom callbacks and filter chaining, this library keeps those concepts distinct. Therefore, there are two dedicated filters, UserFilter and SimpleUserFilter, for callback processing.

The SimpleUserFilter works almost like a regular ROS callback, but it expects a boolean return value that determines if the data is passed on to subsequent filters in the pipeline (if any), or if processing terminates. You can use this type of filter to consume data at the end of the pipeline, or if you want to literally filter out invalid data.

The UserFilter is more generic and can be used if your filter outputs differ from its inputs. You can implement pretty much any kind of transforming filter.

A third filter UserSource is a simple data source which can be used as callback in third-party code.


2019-10-19 12:41