ROS index logo ROS Index
  1. Home
  2. Packages
  3. jsk_topic_tools
 
No version for distro humble showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
jazzy

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version 3.0.5
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
jazzy

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version 3.0.5
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
kilted

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version master
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
lyrical

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version master
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
rolling

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version 3.0.5
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

No version for distro github showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
jazzy

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version 3.0.5
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

No version for distro galactic showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
jazzy

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version 3.0.5
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

No version for distro iron showing jazzy. Known supported distros are highlighted in the buttons above.
Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
jazzy

API Docs
Browse Code

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version 3.0.5
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
melodic

API Docs
Browse Code
Wiki

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version master
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange

Package symbol

jsk_topic_tools package from jsk_common repo

audio_video_recorder jsk_common dynamic_tf_publisher jsk_data jsk_ros1_ros2_compat image_view2 jsk_rosbag_tools jsk_tools jsk_topic_tools

ROS Distro
noetic

API Docs
Browse Code
Wiki

Package Summary

Version 3.0.5
License BSD-3-Clause
Build type CATKIN
Use RECOMMENDED

Repository Summary

Description
Checkout URI https://github.com/jsk-ros-pkg/jsk_common.git
VCS Type git
VCS Version master
Last Updated 2026-11-10
Dev Status UNKNOWN
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

jsk_topic_tools

Additional Links

Maintainers

  • Kei Okada
  • Ryohei Ueda
  • Yoshiki Obinata

Authors

  • Kei Okada
  • Yusuke Furuta
  • Yoshiki Obinata
README
No README found. See repository README.
CHANGELOG

Changelog for package jsk_topic_tools

3.0.5 (2026-11-10)

  • Merge pull request #1841 from k-okada/rosdistro-55117-review rosdistro#55117 review: add LICENSE to each package, use SPDX license identifiers
  • use SPDX license identifiers (BSD-3-Clause, Apache-2.0) in package.xml BSD -> BSD-3-Clause and "Apache License 2.0" -> Apache-2.0 in all packages (ros/rosdistro#55117 review: "BSD is ambiguous. The headers show the 3-clause variant, so BSD-3-Clause (SPDX) is preferred."). Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • add LICENSE to each package (BSD-3-Clause, jsk_tools: Apache-2.0) The ROS2 release review of jsk_common in ros/rosdistro#55117 says (https://github.com/ros/rosdistro/pull/55117#issuecomment-6757665510): > - [ ] At least one of the following must be present > - [ ] Top level license file: None. There is no LICENSE/COPYING at > the repo root (tree @ cbbd0ab). > - [ ] Per package license files: None. No package directory has a > license file. The license text only appears in source-file headers > (e.g. deprecated_relay.h#L1-L33, BSD-3-Clause, "JSK Lab"). Since jsk_tools is Apache-2.0 and the others are BSD-3-Clause, add a license file to each package instead of one at the top level. The BSD ones use the same text as the source headers, "Copyright (c) <year>-, JSK Lab" where <year> is when the package.xml was added, and jsk_tools has the Apache License 2.0 text from apache.org. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.4 (2026-11-04)

3.0.3 (2026-11-03)

  • Merge pull request #1836 from k-okada/filtered-relay-ros2 [jsk_topic_tools] Add filtered_relay.py for ROS1 and ROS2 (based on #1757)

  • [jsk_topic_tools] filtered_relay: support ROS2 What does not map one-to-one onto jsk_ros1_ros2_compat, branched on ROS_VERSION with the ROS1 code left as is:

    - ROS2 has no AnyMsg: poll the type of ~input with a timer and subscribe once it is known (subscribe(), ROS2 only).

    - rclpy's publish() takes one message: publish the ~transform result as is if it is an ~output_type message, else build one from its field values (rclpy messages take keyword arguments only), as rospy's publish(*res) does. std_msgs/Empty: publish(self.output_class()). Add a ROS2 pytest, install the script on ROS2, and a ros2 run example in the document. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: use jsk_ros1_ros2_compat Replace rospy/roslib calls that have a jsk_ros1_ros2_compat equivalent, passing the node (None on ROS1). The ROS1-only parts (rospy.AnyMsg, rospy.Subscriber, rospy.resolve_name) are left as they are, so this works the same on ROS1. Done mechanically with the sed script in the commit message. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools] filtered_relay: fix e.message for Python 3 Python 3 exceptions have no .message, so reporting a wrong ~transform raised AttributeError. 2to3 does not convert this (it has nothing to change in this file), so it is done by hand. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • [jsk_topic_tools/filtered_relay] Add test and document

  • [jsk_topic_tools] Add filtered relay

  • Merge pull request #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • Merge pull request #1834 from pazeshun/array-to-heatmap [jsk_ros1_ros2_compat, jsk_topic_tools, jsk_rosbag_tools] Add array heatmap tools with ROS 1 and ROS 2 support

  • [jsk_topic_tools] package.xml: add boost build_depend for ROS2 transform_merger and static_transform_pose_stamped include boost/shared_ptr.hpp and boost/make_shared.hpp. ROS1 gets boost through roscpp and the repository-wide CI gets it from other packages, but the buildfarm builds each package with only its own build dependencies, where the build fails with "boost/shared_ptr.hpp: No such file or directory". Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Guess ROS_VERSION from AMENT_PREFIX_PATH when unset, depend on ros_environment The ROS2 binary jobs of the buildfarm failed at find_package(catkin): they install only the build dependencies, none of which pulls in ros_environment, so $ENV{ROS_VERSION} is empty and the fallback at the top of CMakeLists.txt chose ROS1.

File truncated at 100 lines see the full file

Launch files

Messages

Services

Plugins

Recent questions tagged jsk_topic_tools at Robotics Stack Exchange