Repository navigation
Drive two robots at once over the office fleet - #3
Merged
Merged
Conversation
The two-site survey, over Open-RMF. Each scout carries the instrument its own site reads, so the mission cannot be done by one robot, and with the policy's independent runs dispatched together both go_to_place tasks are submitted in the same instant and RMF routes two robots across the office at once. Measured, north dirty and south clean: 67.5 s dispatched a node at a time, 51.5 s dispatched together. The saving is one drive across the office. mission_check puts the six conjuncts to the state the fleet left behind and reads the transcripts: the relay was spoken to twice, the observer by nobody.
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.
The two-site survey of
eplansys_demo, over Open-RMF.Each scout carries the instrument its own site reads, so the mission cannot be done by one robot.
northis bound totinyRobot1and drives to the pantry,southtotinyRobot2and the lounge;relayandobserverare bound to nothing, because the first is only ever spoken to and the second is the one the mission keeps in the dark.With the policy's independent runs dispatched together —
parallel:=true, the default here — bothgo_to_placetasks are submitted in the same instant and RMF routes two robots across the office at once. That is the part the one-site mission cannot show: its policy sends one robot, and the fleet has nothing to arbitrate.Measured
Office fleet, headless, north dirty and south clean:
The saving is one drive across the office.
mission_checkputs all six conjuncts to the state the fleet left behind and reads the radio transcripts:What is in here
config/office_sites.json, the task map: two agents bound to the two office robots, two sites at different waypoints, and the four speech acts.launch/survey_sites_rmf_launch.py, on websocket port 7880 so that it and the one-site demo can be up at once.The bridge is unchanged. Nothing here needed it to be.
What it still does not establish
The scan outcomes are the map's fallbacks, chosen by
north:andsouth:, because anrmf_demosadapter drives robots and senses nothing. That limitation is the one already recorded for the one-site mission, and it is unchanged: what the fleet adds is the driving, the traffic management and the arbitration, not the finding.