[Other issue]: Unexpected Traffic Scheduler Jump
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 438
- Forks
- 89
- 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.
Description
I'm using RMF (Iron build from source) to manage traffic for my robots. I’ve encountered a critical issue where the traffic scheduler for robot 2 unexpectedly jumps forward. This causes robot 1 to end its waiting state prematurely, believing the shared junction is clear, even though robot 2 has not yet left the shared area.
https://github.com/user-attachments/assets/53d74634-bdd9-4314-b1c6-ce1fb774657f
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 with the attached video and the description of the traffic scheduler jumping forward for robot 2. Trace the scheduler state around robot 1's premature release of the shared junction, then establish a reproducible case using the reported RMF Iron-from-source setup. Done means the scheduler no longer advances robot 2's progress before it leaves the shared area.
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
- 25/100