-
 

Package Summary

Tags No category tags.
Version 1.1.16
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/ros-planning/navigation2.git
VCS Type git
VCS Version humble
Last Updated 2024-10-04
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

TODO

Additional Links

No additional links.

Maintainers

  • Carlos Orduno
  • Steve Macenski

Authors

No additional authors.

Behaviors

The nav2_behaviors package implements a task server for executing behaviors.

The package defines:

  • A TimedBehavior template which is used as a base class to implement specific timed behavior action server - but not required.
  • The Backup, DriveOnHeading, Spin and Wait behaviors.

The only required class a behavior must derive from is the nav2_core/behavior.hpp class, which implements the pluginlib interface the behavior server will use to dynamically load your behavior. The nav2_behaviors/timed_behavior.hpp derives from this class and implements a generic action server for a timed behavior behavior (e.g. calls an implmentation function on a regular time interval to compute a value) but this is not required if it is not helpful. A behavior does not even need to be an action if you do not wish, it may be a service or other interface. However, most motion and behavior primitives are probably long-running and make sense to be modeled as actions, so the provided timed_behavior.hpp helps in managing the complexity to simplify new behavior development, described more below.

The value of the centralized behavior server is to share resources amongst several behaviors that would otherwise be independent nodes. Subscriptions to TF, costmaps, and more can be quite heavy and add non-trivial compute costs to a robot system. By combining these independent behaviors into a single server, they may share these resources while retaining complete independence in execution and interface.

See its Configuration Guide Page for additional parameter descriptions and a tutorial about writing behaviors.

See the Navigation Plugin list for a list of the currently known and available planner plugins.

CHANGELOG

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged nav2_behaviors at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 1.2.10
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/ros-planning/navigation2.git
VCS Type git
VCS Version iron
Last Updated 2024-10-02
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

TODO

Additional Links

No additional links.

Maintainers

  • Carlos Orduno
  • Steve Macenski

Authors

No additional authors.

Behaviors

The nav2_behaviors package implements a task server for executing behaviors.

The package defines:

  • A TimedBehavior template which is used as a base class to implement specific timed behavior action server - but not required.
  • The Backup, DriveOnHeading, Spin and Wait behaviors.

The only required class a behavior must derive from is the nav2_core/behavior.hpp class, which implements the pluginlib interface the behavior server will use to dynamically load your behavior. The nav2_behaviors/timed_behavior.hpp derives from this class and implements a generic action server for a timed behavior behavior (e.g. calls an implmentation function on a regular time interval to compute a value) but this is not required if it is not helpful. A behavior does not even need to be an action if you do not wish, it may be a service or other interface. However, most motion and behavior primitives are probably long-running and make sense to be modeled as actions, so the provided timed_behavior.hpp helps in managing the complexity to simplify new behavior development, described more below.

The value of the centralized behavior server is to share resources amongst several behaviors that would otherwise be independent nodes. Subscriptions to TF, costmaps, and more can be quite heavy and add non-trivial compute costs to a robot system. By combining these independent behaviors into a single server, they may share these resources while retaining complete independence in execution and interface.

See its Configuration Guide Page for additional parameter descriptions and a tutorial about writing behaviors.

See the Navigation Plugin list for a list of the currently known and available planner plugins.

CHANGELOG

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged nav2_behaviors at Robotics Stack Exchange

Package Summary

Tags No category tags.
Version 1.3.2
License Apache-2.0
Build type AMENT_CMAKE
Use RECOMMENDED

Repository Summary

Checkout URI https://github.com/ros-planning/navigation2.git
VCS Type git
VCS Version jazzy
Last Updated 2024-10-02
Dev Status DEVELOPED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Package Description

Nav2 behavior server

Additional Links

No additional links.

Maintainers

  • Carlos Orduno
  • Steve Macenski

Authors

No additional authors.

Behaviors

The nav2_behaviors package implements a task server for executing behaviors.

The package defines:

  • A TimedBehavior template which is used as a base class to implement specific timed behavior action server - but not required.
  • The Backup, DriveOnHeading, Spin and Wait behaviors.

The only required class a behavior must derive from is the nav2_core/behavior.hpp class, which implements the pluginlib interface the behavior server will use to dynamically load your behavior. The nav2_behaviors/timed_behavior.hpp derives from this class and implements a generic action server for a timed behavior behavior (e.g. calls an implmentation function on a regular time interval to compute a value) but this is not required if it is not helpful. A behavior does not even need to be an action if you do not wish, it may be a service or other interface. However, most motion and behavior primitives are probably long-running and make sense to be modeled as actions, so the provided timed_behavior.hpp helps in managing the complexity to simplify new behavior development, described more below.

The value of the centralized behavior server is to share resources amongst several behaviors that would otherwise be independent nodes. Subscriptions to TF, costmaps, and more can be quite heavy and add non-trivial compute costs to a robot system. By combining these independent behaviors into a single server, they may share these resources while retaining complete independence in execution and interface.

See its Configuration Guide Page for additional parameter descriptions and a tutorial about writing behaviors.

See the Navigation Plugin list for a list of the currently known and available planner plugins.

The TimedBehavior template makes use of a nav2_util::TwistPublisher. The AssistedTeleop behavior makes use of a nav2_util::TwistSubscriber.

CHANGELOG

Wiki Tutorials

This package does not provide any links to tutorials in it's rosindex metadata. You can check on the ROS Wiki Tutorials page for the package.

Launch files

No launch files found

Messages

No message files found.

Services

No service files found

Plugins

Recent questions tagged nav2_behaviors at Robotics Stack Exchange

No version for distro rolling. Known supported distros are highlighted in the buttons above.
No version for distro noetic. 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 bouncy. Known supported distros are highlighted in the buttons above.
No version for distro crystal. Known supported distros are highlighted in the buttons above.
No version for distro eloquent. Known supported distros are highlighted in the buttons above.
No version for distro dashing. Known supported distros are highlighted in the buttons above.
No version for distro galactic. Known supported distros are highlighted in the buttons above.
No version for distro foxy. Known supported distros are highlighted in the buttons above.
No version for distro lunar. 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 indigo. Known supported distros are highlighted in the buttons above.
No version for distro hydro. Known supported distros are highlighted in the buttons above.
No version for distro kinetic. Known supported distros are highlighted in the buttons above.
No version for distro melodic. Known supported distros are highlighted in the buttons above.