s2m2: collisions for robots that arrived at their goal
Open
Nobody has claimed this yet.
wontfix
- Dominant language
- C++
- Stars
- 44
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
S2M2 seems to frequently cause collisions when one of the robots is stationary at their goal. For example, swap3 or swap4. This is either an implementation bug on their side, or a conceptual problem.
Contributor guide
No contributing guide indexed for this repository
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
Reproduce the S2M2 behavior using the swap3 and swap4 examples, then inspect the S2M2 implementation and its handling of robots that have reached their goals. Determine whether the collision is caused by an implementation error or by the algorithm's assumptions; done means the stationary-at-goal collision is resolved or the conceptual limitation is clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100