Why is there no safety scanner standard msg?
Open
Nobody has claimed this yet.
backlog
- Dominant language
- C++
- Stars
- 393
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
I'm talking about the safety scanners that have fields of different shapes and output whether an obstacle is detected within that field.
What is your opinion on having a standard msg for that? I don't think any other existing "common" msg is suitable.
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
Review the repository's existing .msg and .srv interface files and compare their field shapes and obstacle-detection semantics with the proposed safety-scanner message. Since the issue asks for an opinion rather than naming a target file or test, define the message requirements and acceptance criteria before proposing any change.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100