[Bug]: Attempts to collide or enter even though the path is preempted.
Nobody has claimed this yet.
- 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
ubuntu22.04
Open-RMF installation type
Binaries
Other Open-RMF installation methods
No response
Open-RMF version or commit hash
2.3.0
ROS distribution
Humble
ROS installation type
Source build
Other ROS installation methods
No response
Package or library, if applicable
No response
Description of the bug
I am running a simulation in which 4 TinyRobots repeat pick and drop actions at specific points.. However, as seen in the video, there are symptoms of a collision or an attempt to enter even though the path has been preempted.
Steps to reproduce the bug
- Run TinyRobot simulation
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 running the TinyRobot simulation with four robots repeating the described pick-and-drop actions, then compare the collision and entry behavior with the preempted paths shown in the attached videos. No source files, tests, or expected behavior are identified, so completion would require locating the relevant path-preemption behavior and establishing a reproducible expected result.
Written by the indexing model from the issue text.
Assessment
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100