Navigation delay during multi-robot planning different paths.
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 438
- Forks
- 89
- PR merge metrics
- No merged PRs in 30d
Description
Hi Team,
We have two delivery robots delivery1, delivery2 respectively. We have provided commands i.e, dispatch_go_to_place to two robots simultaneously. we have observed that robots have planed entirely different paths to reach the Target locations as shown in video.
The issue is delivery2 (robot on left hand side) robot is not moving and keep waiting until delivary1 (robot on right hand side) robot reached to target position.
Delivery2 robots started moving only after delivery1 robot reached target location even-though there paths are different .
This behavior will affect productivity and unnecessary delay in robot movement even-though the path is Free.
Is there any way to avoid such delay.
Please find the attached video for reference.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the simultaneous dispatch_go_to_place commands for delivery1 and delivery2, using the attached video as the behavioral reference. Trace why the robot on the left waits despite having a different path; done means both robots begin moving without unnecessary waiting when their paths are free.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100