micro-ROS / micro-ROS/micro_ros_diagnostics
Aggregation in the bridge
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 10
- Forks
- 10
- PR merge metrics
- No merged PRs in 30d
Description
Allow bridge to be configured to aggregate diagnostic status messages before sensing a diagnostic array.
E.g. aggregate for a certain duration (publishing array with fixed rate), or aggregate until status for a defined set of diagnostic tasks was received.
Depends on #26, might become more relevant with #16.
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 with the bridge entry point and dependency issue #26, since no file or test is named in this issue. Compare the proposed fixed-duration and defined-task-set aggregation modes, then establish how configuration should select between them. Done means the bridge supports an agreed aggregation behavior before publishing diagnostic arrays.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- embedded-iot, observability-sre
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100