[Feature request]:
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.
Description
We’re currently working on an Open‑RMF deployment and encountered a situation where we need to restrict only one robot in a fleet from accessing a specific lane or location.
We initially attempted to use lane closures, but realized that since the planner instance is shared fleet-wide, the closure affects all robots in the fleet. Our idea is to assign a dedicated planner instance per robot to allow robot-specific constraints like lane restrictions.
Would you consider this a viable solution, or are there any unintended side effects or better design alternatives within RMF?
@mxgrey
Implementation Considerations
No response
Alternatives
No response
Additional information
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
No files, tests, or entry points are identified. Start by reviewing the shared planner behavior and lane-closure handling described in the issue, then compare the per-robot planner proposal with possible alternatives. Done would be a documented design decision that addresses robot-specific restrictions and unintended side effects.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100