|
|
Package Summary
| Tags | No category tags. |
| Version | 1.0.1 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aerostack2/aerostack2.git |
| VCS Type | git |
| VCS Version | humble-devel |
| Last Updated | 2023-04-25 |
| 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
- CVAR-UPM
Authors
AS2_behavior library
Aerostack2 uses Behaviors to handle mission execution
Each behavior is separated in a behavior Server and a behavior client. They are similar to rclcpp actions but with some differences. - Each behavior server only attends to a single goal (client) at each moment. - Feedback is visible for all nodes - They extend start, stop, and feedback with modify, pause, resume, and behavior state data.
We use ros2 services for: - start - modify (the same syntax than start) - pause (std_srvs::srv::Empty) - resume (std_srvs::srv::Empty) - stop (std_srvs::srv::Empty)
We use ros2 topics for: - Feedback - State
We take advantage of ros2 action message definitions: - Goal: will be used in start and modify services - Feedback: Will be used in feedback - Response: (Maybe in state, or in inmediate behaviors)
We difference between Inmediate, Recurrent and Regular (or goal oriented) behaviors: - Inmediate: act like a service, they dont give Fb and cannot be paused or modified. - Recurrent: they give feedback until they are stopped or paused. - Goal Oriented: they keep runing until a termination condition is met.
Changelog for package as2_behavior
1.0.1 (2023-04-25)
- Merge pull request #223 from aerostack2/200-unify-maintainer-in-packagexmls Maintainer unified to CVAR-UPM
- Maintainer unified to CVAR-UPM
- Merge pull request #212 from aerostack2/211-nodes-should-use-aerostack2-node-create-timer-method-not-create-wall-timer Nodes use Aerostack2 Node Create Timer method, not create wall timer
- Change create wall timer to as2 create timer
- Merge pull request #198 from aerostack2/197-as2_core-change-behaviour-to-behavior 197 as2 core change behaviour to behavior
- Update basic_server_test.cpp
- Clang format
- Change behaviour to behavior
- Contributors: Miguel Fernandez-Cortizas, RPS98, pariaspe
1.0.0 (2023-03-18)
0.2.2 (2022-12-20)
0.2.1 (2022-12-19)
- Merge pull request #18 from aerostack2/fix_tests Fix tests
- as2_behavior reformatted
- excution typo in as2_behavior resolved
- Merge pull request #4 from aerostack2/as2_behaviors Change as2 behaviors
- Change as2 behaviors
- as2_behavior stop_srv addded and stop bug fixed
- px4 extended and ci actions
- aerostack2 pkg added
- Contributors: Miguel, Miguel Fernandez-Cortizas, RPS98, Rafael P
Wiki Tutorials
Source Tutorials
Package Dependencies
| Deps | Name | |
|---|---|---|
| 1 | ament_cmake | |
| 1 | ament_lint_auto | |
| 1 | ament_cmake_clang_format | |
| 1 | ament_cmake_cppcheck | |
| 1 | ament_cmake_cpplint | |
| 1 | rclcpp | |
| 1 | as2_core | |
| 2 | std_msgs | |
| 1 | as2_msgs | |
| 3 | std_srvs |
System Dependencies
Launch files
Messages
Services
Plugins
Recent questions tagged as2_behavior at answers.ros.org
|
|
Package Summary
| Tags | No category tags. |
| Version | 0.2.2 |
| License | BSD-3-Clause |
| Build type | AMENT_CMAKE |
| Use | RECOMMENDED |
Repository Summary
| Checkout URI | https://github.com/aerostack2/aerostack2.git |
| VCS Type | git |
| VCS Version | galactic |
| Last Updated | 2022-12-20 |
| Dev Status | DEVELOPED |
| CI status | No Continuous Integration |
| Released | UNRELEASED |
| Tags | No category tags. |
| Contributing |
Help Wanted (0)
Good First Issues (0) Pull Requests to Review (0) |
Package Description
Additional Links
Maintainers
- Miguel Fernandez-Cortizas
- Computer Vision And Aerial Robotics Group (UPM)
Authors
AS2_behavior library
Aerostack2 uses Behaviors to handle mission execution
Each behavior is separated in a behavior Server and a behavior client. They are similar to rclcpp actions but with some differences. - Each behavior server only attends to a single goal (client) at each moment. - Feedback is visible for all nodes - They extend start, stop, and feedback with modify, pause, resume, and behavior state data.
We use ros2 services for: - start - modify (the same syntax than start) - pause (std_srvs::srv::Empty) - resume (std_srvs::srv::Empty) - stop (std_srvs::srv::Empty)
We use ros2 topics for: - Feedback - State
We take advantage of ros2 action message definitions: - Goal: will be used in start and modify services - Feedback: Will be used in feedback - Response: (Maybe in state, or in inmediate behaviors)
We difference between Inmediate, Recurrent and Regular (or goal oriented) behaviors: - Inmediate: act like a service, they dont give Fb and cannot be paused or modified. - Recurrent: they give feedback until they are stopped or paused. - Goal Oriented: they keep runing until a termination condition is met.
Changelog for package as2_behavior
Forthcoming
0.2.2 (2022-12-20)
0.2.1 (2022-12-19)
- Merge pull request #18 from aerostack2/fix_tests Fix tests
- as2_behavior reformatted
- excution typo in as2_behavior resolved
- Merge pull request #4 from aerostack2/as2_behaviors Change as2 behaviors
- Change as2 behaviors
- as2_behavior stop_srv addded and stop bug fixed
- px4 extended and ci actions
- aerostack2 pkg added
- Contributors: Miguel, Miguel Fernandez-Cortizas, RPS98, Rafael P
Wiki Tutorials
Source Tutorials
Package Dependencies
| Deps | Name | |
|---|---|---|
| 1 | ament_cmake | |
| 1 | ament_lint_auto | |
| 1 | ament_cmake_clang_format | |
| 1 | ament_cmake_cppcheck | |
| 1 | ament_cmake_cpplint | |
| 1 | rclcpp | |
| 1 | as2_core | |
| 2 | std_msgs | |
| 1 | as2_msgs | |
| 3 | std_srvs |