|
Package Summary
Tags | No category tags. |
Version | 1.1.17 |
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-11-26 |
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
Additional Links
Maintainers
- Steve Macenski
- Carl Delsey
Authors
Nav2 Core
This package hosts the abstract interface (virtual base classes) for plugins to be used with the following:
- global planner (e.g.,
nav2_navfn_planner
) - controller (e.g., path execution controller, e.g
nav2_dwb_controller
) - smoother (e.g.,
nav2_ceres_costaware_smoother
) - goal checker (e.g.
simple_goal_checker
) - behaviors (e.g.
drive_on_heading
) - progress checker (e.g.
simple_progress_checker
) - waypoint task executor (e.g.
take_pictures
) - exceptions in planning and control
The purposes of these plugin interfaces are to create a separation of concern from the system software engineers and the researcher / algorithm designers. Each plugin type is hosted in a “task server” (e.g. planner, recovery, control servers) which handles requests and multiple algorithm plugin instances. The plugins are used to compute a value back to the server without having to worry about ROS 2 actions, topics, or other software utilities. A plugin designer can simply use the tools provided in the API to do their work, or create new ones if they like internally to gain additional information or capabilities.
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged nav2_core at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 1.3.4 |
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-12-13 |
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
Additional Links
Maintainers
- Steve Macenski
- Carl Delsey
Authors
Nav2 Core
This package hosts the abstract interface (virtual base classes) for plugins to be used with the following:
- navigators (e.g.,
navigate_to_pose
) - global planner (e.g.,
nav2_navfn_planner
) - controller (e.g., path execution controller, e.g
nav2_dwb_controller
) - smoother (e.g.,
nav2_ceres_costaware_smoother
) - goal checker (e.g.
simple_goal_checker
) - behaviors (e.g.
drive_on_heading
) - progress checker (e.g.
simple_progress_checker
) - waypoint task executor (e.g.
take_pictures
) - exceptions in planning and control
The purposes of these plugin interfaces are to create a separation of concern from the system software engineers and the researcher / algorithm designers. Each plugin type is hosted in a “task server” (e.g. planner, recovery, control servers) which handles requests and multiple algorithm plugin instances. The plugins are used to compute a value back to the server without having to worry about ROS 2 actions, topics, or other software utilities. A plugin designer can simply use the tools provided in the API to do their work, or create new ones if they like internally to gain additional information or capabilities.
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged nav2_core at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 0.3.5 |
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 | eloquent-devel |
Last Updated | 2021-01-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
Additional Links
Maintainers
- Steve Macenski
- Carl Delsey
Authors
Nav2 Core
This package hosts the abstract interface (virtual base classes) for plugins to be used with the following:
- global planner (e.g.,
nav2_navfn_planner
) - controller (i.e, path execution controller, e.g
nav2_dwb_controller
) - goal checker
- recovery behaviors
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged nav2_core at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 1.0.12 |
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 | galactic |
Last Updated | 2022-09-15 |
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
Additional Links
Maintainers
- Steve Macenski
- Carl Delsey
Authors
Nav2 Core
This package hosts the abstract interface (virtual base classes) for plugins to be used with the following:
- global planner (e.g.,
nav2_navfn_planner
) - controller (i.e, path execution controller, e.g
nav2_dwb_controller
) - goal checker
- recovery behaviors
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged nav2_core at Robotics Stack Exchange
|
Package Summary
Tags | No category tags. |
Version | 0.4.7 |
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 | foxy-devel |
Last Updated | 2022-08-31 |
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
Additional Links
Maintainers
- Steve Macenski
- Carl Delsey
Authors
Nav2 Core
This package hosts the abstract interface (virtual base classes) for plugins to be used with the following:
- global planner (e.g.,
nav2_navfn_planner
) - controller (i.e, path execution controller, e.g
nav2_dwb_controller
) - goal checker
- recovery behaviors
Wiki Tutorials
Package Dependencies
System Dependencies
Dependant Packages
Launch files
Messages
Services
Plugins
Recent questions tagged nav2_core 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
Additional Links
Maintainers
- Steve Macenski
- Carl Delsey
Authors
Nav2 Core
This package hosts the abstract interface (virtual base classes) for plugins to be used with the following:
- navigators (e.g.,
navigate_to_pose
) - global planner (e.g.,
nav2_navfn_planner
) - controller (e.g., path execution controller, e.g
nav2_dwb_controller
) - smoother (e.g.,
nav2_ceres_costaware_smoother
) - goal checker (e.g.
simple_goal_checker
) - behaviors (e.g.
drive_on_heading
) - progress checker (e.g.
simple_progress_checker
) - waypoint task executor (e.g.
take_pictures
) - exceptions in planning and control
The purposes of these plugin interfaces are to create a separation of concern from the system software engineers and the researcher / algorithm designers. Each plugin type is hosted in a “task server” (e.g. planner, recovery, control servers) which handles requests and multiple algorithm plugin instances. The plugins are used to compute a value back to the server without having to worry about ROS 2 actions, topics, or other software utilities. A plugin designer can simply use the tools provided in the API to do their work, or create new ones if they like internally to gain additional information or capabilities.