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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

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

Package Summary

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

Repository Summary

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 UNMAINTAINED
Released RELEASED
Contributing Help Wanted (-)
Good First Issues (-)
Pull Requests to Review (-)

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito
README
No README found. See repository README.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange

Package Summary

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

Repository Summary

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

Package Description

dynamically set the tf trensformation

Additional Links

Maintainers

  • Ryohei Ueda

Authors

  • Manabu Saito

dynamic_tf_publisher

Publish TF transforms that can be added, changed, re-parented and removed at runtime through services. tf_publish.py keeps a set of transforms and broadcasts them periodically; tf_set.py is a command line client to set one, and tf_reconfigure_publisher.py broadcasts a single transform whose values are tuned through parameters (dynamic_reconfigure on ROS 1).

ROS 1 / ROS 2

The package builds for both ROS 1 (catkin) and ROS 2 (ament_cmake); CMakeLists.txt branches on $ENV{ROS_VERSION}.

Item ROS 1 ROS 2
tf_publish.py yes yes
tf_set.py yes yes
tf_reconfigure_publisher.py yes yes
Services SetDynamicTF, AssocTF, DissocTF, DeleteTF yes yes
dynamic_reconfigure config TfParameter yes - (plain parameters)
samples/sample.launch yes -

There are no ROS 2 launch files; use ros2 run dynamic_tf_publisher <exe>.

tf_publish.py

Node name tf_publish_server. Broadcasts all registered transforms to /tf.

Services:

  • /set_dynamic_tf (dynamic_tf_publisher/SetDynamicTF) – add or update the transform cur_tf (header.frame_id -> child_frame_id), published every 1 / freq seconds.
  • /assoc_tf (dynamic_tf_publisher/AssocTF) – re-parent child_frame to parent_frame, keeping its current pose (e.g. attach an object frame to a gripper).
  • /dissoc_tf (dynamic_tf_publisher/DissocTF) – undo assoc_tf for frame_id, re-attaching it to its original parent.
  • /delete_tf (dynamic_tf_publisher/DeleteTF) – stop publishing the frame header.frame_id.
  • /publish_tf (std_srvs/Empty) – publish the transforms immediately.

ROS 1 only:

  • Also publishes the transforms on ~tf (tf2_msgs/TFMessage).
  • ~use_cache (Bool, default true) – store the transforms on the parameter server and restore them when the node restarts.
  • ~check_update (Bool, default false) – publish only updated transforms, and all of them every ~check_update_sleep_time (default 1.0 s).
  • Exits if the services are already advertised by another tf_publish.py.

On ROS 2, the transforms are broadcast at a fixed 1 Hz (the freq field of SetDynamicTF is not used for the rate).

tf_set.py

Calls /set_dynamic_tf.

tf_set.py x y z (yaw pitch roll | qx qy qz qw) parent child period_msec

The rotation is either three Euler angles applied in z-y-x order or a quaternion; the last argument is the publishing period in milliseconds.

tf_reconfigure_publisher.py

Broadcasts one transform parent_frame_id -> frame_id at 10 Hz with parameters frame_id, parent_frame_id, x, y, z, roll, pitch, yaw. On ROS 1 they are changed with dynamic_reconfigure (TfParameter.cfg), on ROS 2 with ros2 param set.

Usage

ROS 1:

roslaunch dynamic_tf_publisher sample.launch    # tf_publish.py and four tf_set.py calls (map -> desk -> cup, map -> robot -> hand)

rosrun dynamic_tf_publisher tf_publish.py
rosrun dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
rosservice call /assoc_tf "{parent_frame: hand, child_frame: cup}"
rosservice call /dissoc_tf "{frame_id: cup}"

ROS 2:

ros2 run dynamic_tf_publisher tf_publish.py
ros2 run dynamic_tf_publisher tf_set.py 1 0 1 0 0 0 robot hand 1000
ros2 service call /delete_tf dynamic_tf_publisher/srv/DeleteTF "{header: {frame_id: hand}}"

ros2 run dynamic_tf_publisher tf_reconfigure_publisher.py --ros-args \
  -p parent_frame_id:=map -p frame_id:=marker -p x:=1.0

Launch files (ROS 1)

  • samples/sample.launch – starts tf_publish.py and sets map -> desk, desk -> cup, map -> robot and robot -> hand with tf_set.py.
CHANGELOG

Changelog for package dynamic_tf_publisher

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 #1835 from k-okada/ros-version-fallback-ament Fix ROS2 buildfarm binary jobs: ROS_VERSION without ros_environment, boost for jsk_topic_tools

  • 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.

    - package.xml: add a ROS2 buildtool_depend on ros_environment, which sets ROS_VERSION.

    - CMakeLists.txt: when ROS_VERSION is still unset, guess it from AMENT_PREFIX_PATH (bloom's ROS2 debian/rules passes it to cmake, setup.sh and colcon set the environment variable, catkin never does) instead of always assuming ROS1, and warn about it. jsk_tools had no fallback at all and gets the same block. Applies to jsk_ros1_ros2_compat, jsk_tools, jsk_topic_tools, jsk_common, jsk_data, jsk_rosbag_tools, dynamic_tf_publisher, audio_video_recorder and image_view2. Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>

  • Merge pull request #1833 from k-okada/release-3.0.2 3.0.2

  • Contributors: Kei Okada

3.0.2 (2026-11-02)

  • Merge pull request #1832 from k-okada/ros2-compat-install-python [jsk_ros1_ros2_compat] add jsk_ros1_ros2_compat_install_python() and use it
  • [jsk_tools, jsk_data, dynamic_tf_publisher] use jsk_ros1_ros2_compat_install_python() for the ROS2 script install jsk_tools, jsk_data and dynamic_tf_publisher each carried the same foreach(file(READ)/string(REPLACE)/file(WRITE)) block to give their installed ROS2 scripts a python3 shebang. Use the shared helper instead, which also regenerates the copy when the source changes (the inline blocks ran at configure time only, so a rebuild after editing a script installed the stale copy). jsk_ros1_ros2_compat becomes a ROS2 buildtool_depend; it stays off build_depend so that rosidl_auto_generate_interfaces() in dynamic_tf_publisher does not take it as an interface dependency. Co-authored-by: Copilot Autofix powered by AI <<175728472+Copilot@users.noreply.github.com>> Co-Authored-By: Claude Opus 5.5 <<noreply@anthropic.com>>
  • Contributors: Kei Okada

3.0.0 (2026-10-29)

  • Merge pull request #1826 from k-okada/ros2-support Add ROS2 support to jsk_ros1_ros2_compat, dynamic_tf_publisher, jsk_topic_tools, jsk_tools, audio_video_recorder, jsk_data, image_view2, jsk_rosbag_tools

  • [dynamic_tf_publisher] add ROS2 support Single package.xml/CMakeLists.txt branched on $ROS_VERSION, and each of tf_publish.py/tf_set.py/tf_reconfigure_publisher.py rewritten as a single ROS1/ROS2 dual-support file built on the tf2_ros-based ROS1 code from the previous commit, so the tf-handling logic itself does not need to be duplicated between the two versions:

File truncated at 100 lines see the full file

Launch files

Messages

No message files found.

Plugins

No plugins found.

Recent questions tagged dynamic_tf_publisher at Robotics Stack Exchange