Error Handling
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 27
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
A new package for error handling with abstract methods to flag errors with different severity from 1) RMF and 2) Robots. Also specify how the robot should react to the error. (wait at current location for human to reset, go wait at a location, etc).
The proposed building blocks/phases for tasks will implement these methods https://github.com/open-rmf/rmf_task/issues/32
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 reading the proposed building blocks and phases in issue #32, then clarify how errors should be flagged for RMF and robots and which robot reactions must be represented. No files or tests are named; done requires an agreed error-handling package design with abstract methods covering severity and responses such as waiting for a human or moving to a location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- robotics
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100