You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* [coverage_planning] make it build on rolling with F2C v1.2.1
* fix Werror=maybe-uninitialized
* restore tests and add missing ament_index_cpp to CMakeLists
* update demo launcher for Gazebo Ignition
* explicitly add models to avoid errors
* move robot pose and polygon to (0,0)
In GZ Ignition, tb3 publishes its ground truth pose as odometry with respect to its start position. Even when spawning the model at (5,5), the map->base_link transform is 0 because the robot did not drive.
This causes navigation to fail as the robot pose is too far from the start of the path.
* Add .gitignore
Copied from ros-navigation/navigation2
* Restore robot pose & polygon to (5,5)
and add (5,5) to map->odom tf as it is the transform from world/map frame to the robot's initial pose
* Update row_coverage_demo_launch.py to Gazebo Ignition
* Note on F2C version
* Update test workflow
* lint and format
* add BTCPP_format to BT xmls
* CI: change F2C branch and update to Jazzy & Noble
* try F2C v1.2.1
* [tmp] ignore F2C compile errors
* Update lint step to jazzy
* test with cartesian polygon
* Revert "try F2C v1.2.1"
This reverts commit cb65987.
* Revert "[tmp] ignore F2C compile errors"
This reverts commit 8164091.
* [tmp] rm failing test in opennav_coverage_bt
* switch test to cartesian_frame
* restore non-cartesian field test
* Revert "[tmp] rm failing test in opennav_coverage_bt"
This reverts commit 6a61940.
* restore rclcpp:shutdown()
Without the shutdown: The tests are passing in `RUN_ALL_TESTS()`, the test itself is failing with timeout. Most probably because `server_thread.join()` hangs forever.
opennav_coverage works with Field2Cover v1.2.1. The newest version v2.0.0 is not supported at the moment.
40
+
41
+
To install Fields2Cover, clone it into a colcon workspace and build with `colcon build`.
42
+
43
+
- Humble & Iron: Use tag `v1.2.1`
44
+
- Jazzy & rolling: Use branch `v1.2.1-devel`
45
+
37
46
## Interfaces
38
47
39
48
The two main interfaces are `NavigateCompleteCoverage` and `ComputeCoveragePath`. The first is the action definition to request the BT Navigator's `CoverageNavigator` plugin to navigate usign a Complete Coverage task input. The latter is an analog to the `PlannerServer`'s action definition for computing Complete Coverage paths using the `opennav_coverage` action server. See `opennav_coverage_msgs` for complete details.
0 commit comments