Repository navigation
Warehouse A deployments, a PlanSys2 fleet, playgrounds and Zenoh - #1
Merged
Merged
Conversation
- Simulations from easynav_playgrounds (simulation_launch.yaml in each package); rmw_zenoh_cpp by default, with its router. - Each robot keeps its TF under its namespace; navigation_manager relays odom, base_footprint and base_link to /tf for a central RViz (no RobotModel). - New launch arguments to choose each robot's EasyNav, navigation and navigation manager parameters, its RViz and the mission. - Python fake capabilities for the simple_api_py deployment; the fastdds (DDS Router) and farm (Summit, GPS, NavMap) deployments. - Navigation capability: its executor only spun from on_execute(), and a cancel waits for EasyNav's answer, so it no longer disturbs the next goal. - The collaboration mission reports which robot missed which waypoint instead of always announcing success; robot_node takes config_package. - A README per deployment; run instructions point to simulation_launch.yaml. Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
- easyfleet_easynav_deployment and the collaboration deployment in Warehouse A of large_warehouse_world: a 0.2 m costmap of what the lidar sees at its height, routes along every rack aisle, the corridors and to the docks, and the scripts that generate them from the world (sdf_to_costmap.py, aisle_routes.py). - AMCL with reseeding, a 30 m lidar (at 12 m it sees almost nothing in the open areas) and a cylinder at lidar height on each Kobuki so the others see it. - easyfleet_plansys2_warehouse_deployment: four Kobukis, two scouts and two carriers, driven by PlanSys2 (Kairos). The controller builds the problem from the capabilities the robots announce; each action's behavior tree calls them with easyfleet_bt_nodes. The robots share each other as obstacles. Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
…e merged Signed-off-by: Francisco Martín Rico <fmrico@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Needs EasyNavigation/EasyFleet#5 (capability API, TF relay, fleet obstacles,
easyfleet_bt_nodes). Two commits.1. Playgrounds and Zenoh, per-robot TF with a fleet RViz, READMEs and fixes
easynav_playgrounds(simulation_launch.yamlin each package), andrmw_zenoh_cppby default with its router.navigation_managerrelays onlyodom,base_footprintandbase_linkto/tf, for a central RViz with each robot's base and path.simple_api_py; thefastdds(DDS Router) andfarm(Summit, GPS, NavMap) deployments, listed in the README but never committed.on_execute(), and a cancel waits for EasyNav's answer, so it no longer disturbs the next goal.2. Warehouse A deployments and a PlanSys2 fleet
easyfleet_easynav_deployment(one robot) andeasyfleet_easynav_collaboration_deployment(two) in Warehouse A of large_warehouse_world:scripts/sdf_to_costmap.pyandscripts/aisle_routes.py;lidar_targeton each Kobuki (Kobuki: optional lidar target easynav_playgrounds#28).easyfleet_plansys2_warehouse_deployment: four Kobukis, two scouts (perception) and two carriers (manipulation), driven by PlanSys2 with Kairos. The controller builds the PDDL problem from the capabilities the robots announce and reaches the mission's goals in turn; each action's behavior tree calls the robot's capabilities witheasyfleet_bt_nodes.Tested: every package's tests and linters pass. In simulation, one Kobuki reaches a rack aisle 0.15 m from where it believes it is, and the four Kobukis deliver the first goal's two packages in 657 s, all of them within 0.35 m of their estimate along 12 minutes.
The warehouse world comes from juanscelyg/large_warehouse_world (its changes merged in juanscelyg/large_warehouse_world#1).