[Bug]: Unnecessary Waiting Behavior in Multi-Robot Operation
Open
Nobody has claimed this yet.
bug
- Dominant language
- Python
- Stars
- 439
- Forks
- 90
- PR merge metrics
- No merged PRs in 30d
Description
Before proceeding, is there an existing issue or discussion for this?
- I have done a search for similar issues and discussions.
OS and version
Ubuntu 24.04
Open-RMF installation type
Binaries
Other Open-RMF installation methods
No response
Open-RMF version or commit hash
release-jazzy-250617
ROS distribution
Jazzy
ROS installation type
Binaries
Other ROS installation methods
No response
Package or library, if applicable
No response
Description of the bug
When two robots operate in the same lane, they sometimes experience unnecessary waiting periods. These delays persist until they are forcefully aborted by a 30-second timeout, which negatively impacts system efficiency.
Steps to reproduce the bug
- Deploy two robots running in the same lane with a waiting mechanism.
- Observe their behavior.
- Notice that both robots sometimes remain waiting for traffic while nothing is blocking it .
- The wait is only aborted after an extensive 30-second timeout.
Expected behavior
No response
Actual behavior
No response
Additional information or screenshots
No response
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 issue with two robots operating in the same lane on Ubuntu 24.04, ROS Jazzy, and release-jazzy-250617. Trace the traffic-waiting behavior and its 30-second timeout; done means identifying why clear lanes cause waiting and verifying that unnecessary waits no longer persist.
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
- 30/100