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

dynamic_robot_state_publisher package from dynamic_robot_state_publisher repo

dynamic_robot_state_publisher

Package Summary

Tags No category tags.
Version 1.1.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/peci1/dynamic_robot_state_publisher.git
VCS Type git
VCS Version master
Last Updated 2019-03-17
Dev Status DEVELOPED
Released RELEASED

Package Description

Improved ROS robot_state_publisher which can update the robot model via dynamic_reconfigure.

Additional Links

Maintainers

  • Martin Pecka

Authors

  • Martin Pecka

dynamic_robot_state_publisher

Improved ROS robot_state_publisher which can update the robot model via dynamic_reconfigure.

Nodes

dynamic_robot_state_publisher

Use this node as a replacement for robot_state_publisher/robot_state_publisher.

It behaves the same way, except it also spawns a dynamic reconfigure server in the node's namespace. This server can receive updates of the robot model, to which it reacts by reloading the robot model.

Rationale

This package was created as one of the workarounds to issue Reload robot model (e.g. during calibration).

If you read that issue, you learn that this problem is quite complex and this package is a solution just to a subclass of the problems. E.g. 3rd party packages do not expect the robot_description parameter to change, and so you have to somehow tell them to do so (e.g. by restarting their nodes).

One of the things that this package does and is probably aginst good practices is it tries to delete static transforms that disappeared after model reload. This deletion is implemented by reconnecting the frames to virtual frame DynamicRobotStatePublisher::DELETED_STATIC_TFS_FRAME. This effectively breaks the assumption that a static TF is valid all the time. These static TFs are not. You have to count with that in the rest of your codebase.

Alternatives

CHANGELOG

Changelog for package dynamic_robot_state_publisher

1.1.1 (2019-03-05)

  • Allowed deleting static TF frames that disappeared.
  • Fixed deadlock.
  • Contributors: Martin Pecka

1.0.0

  • First version.
  • Initial commit
  • Contributors: Martin Pecka

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged dynamic_robot_state_publisher at answers.ros.org

dynamic_robot_state_publisher package from dynamic_robot_state_publisher repo

dynamic_robot_state_publisher

Package Summary

Tags No category tags.
Version 1.1.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/peci1/dynamic_robot_state_publisher.git
VCS Type git
VCS Version master
Last Updated 2019-03-17
Dev Status DEVELOPED
Released RELEASED

Package Description

Improved ROS robot_state_publisher which can update the robot model via dynamic_reconfigure.

Additional Links

Maintainers

  • Martin Pecka

Authors

  • Martin Pecka

dynamic_robot_state_publisher

Improved ROS robot_state_publisher which can update the robot model via dynamic_reconfigure.

Nodes

dynamic_robot_state_publisher

Use this node as a replacement for robot_state_publisher/robot_state_publisher.

It behaves the same way, except it also spawns a dynamic reconfigure server in the node's namespace. This server can receive updates of the robot model, to which it reacts by reloading the robot model.

Rationale

This package was created as one of the workarounds to issue Reload robot model (e.g. during calibration).

If you read that issue, you learn that this problem is quite complex and this package is a solution just to a subclass of the problems. E.g. 3rd party packages do not expect the robot_description parameter to change, and so you have to somehow tell them to do so (e.g. by restarting their nodes).

One of the things that this package does and is probably aginst good practices is it tries to delete static transforms that disappeared after model reload. This deletion is implemented by reconnecting the frames to virtual frame DynamicRobotStatePublisher::DELETED_STATIC_TFS_FRAME. This effectively breaks the assumption that a static TF is valid all the time. These static TFs are not. You have to count with that in the rest of your codebase.

Alternatives

CHANGELOG

Changelog for package dynamic_robot_state_publisher

1.1.1 (2019-03-05)

  • Allowed deleting static TF frames that disappeared.
  • Fixed deadlock.
  • Contributors: Martin Pecka

1.0.0

  • First version.
  • Initial commit
  • Contributors: Martin Pecka

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged dynamic_robot_state_publisher at answers.ros.org

dynamic_robot_state_publisher package from dynamic_robot_state_publisher repo

dynamic_robot_state_publisher

Package Summary

Tags No category tags.
Version 1.1.1
License BSD
Build type CATKIN
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/peci1/dynamic_robot_state_publisher.git
VCS Type git
VCS Version master
Last Updated 2019-03-17
Dev Status DEVELOPED
Released RELEASED

Package Description

Improved ROS robot_state_publisher which can update the robot model via dynamic_reconfigure.

Additional Links

Maintainers

  • Martin Pecka

Authors

  • Martin Pecka

dynamic_robot_state_publisher

Improved ROS robot_state_publisher which can update the robot model via dynamic_reconfigure.

Nodes

dynamic_robot_state_publisher

Use this node as a replacement for robot_state_publisher/robot_state_publisher.

It behaves the same way, except it also spawns a dynamic reconfigure server in the node's namespace. This server can receive updates of the robot model, to which it reacts by reloading the robot model.

Rationale

This package was created as one of the workarounds to issue Reload robot model (e.g. during calibration).

If you read that issue, you learn that this problem is quite complex and this package is a solution just to a subclass of the problems. E.g. 3rd party packages do not expect the robot_description parameter to change, and so you have to somehow tell them to do so (e.g. by restarting their nodes).

One of the things that this package does and is probably aginst good practices is it tries to delete static transforms that disappeared after model reload. This deletion is implemented by reconnecting the frames to virtual frame DynamicRobotStatePublisher::DELETED_STATIC_TFS_FRAME. This effectively breaks the assumption that a static TF is valid all the time. These static TFs are not. You have to count with that in the rest of your codebase.

Alternatives

CHANGELOG

Changelog for package dynamic_robot_state_publisher

1.1.1 (2019-03-05)

  • Allowed deleting static TF frames that disappeared.
  • Fixed deadlock.
  • Contributors: Martin Pecka

1.0.0

  • First version.
  • Initial commit
  • Contributors: Martin Pecka

Wiki Tutorials

See ROS Wiki Tutorials for more details.

Source Tutorials

Not currently indexed.

Package Dependencies

System Dependencies

No direct system dependencies.

Dependant Packages

No known dependants.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

No plugins found.

Recent questions tagged dynamic_robot_state_publisher at answers.ros.org

No version for distro indigo. Known supported distros are highlighted in the buttons above.
No version for distro ardent. Known supported distros are highlighted in the buttons above.
No version for distro jade. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.