bluerobotics / bluerobotics/cockpit
Expose autopilot firmware information in the data-lake
- Dominant language
- TypeScript
- Stars
- 198
- Forks
- 63
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 57
Description
Per [this comment](https://github.com/bluerobotics/cockpit/issues/1658#issuecomment-2872913716):
> Note that it would be worth implementing an auto-populated data-lake variable for whether the firmware is Sub, so that the MANUAL_CONTROL z-axis scaling could be set correctly.
Potentially useful info:
- family (ArduPilot / PX4 / Unknown)
- type (Copter / Plane / Sub / Rover / Blimp / Unknown)
- sub-type (Boat / Unknown)
- version (string? or separate values for major/minor/patch?)
Contributor guide
No contributing guide indexed for this repository
Research direction
No files, tests, or entry points are named. Start by reviewing the linked issue comment and locating how data-lake variables are defined and populated. Done means exposing the requested firmware family, type, subtype, and version information sufficiently for MANUAL_CONTROL z-axis scaling to identify Sub firmware.
Written by the indexing model from the issue text.
Assessment
- Domain
- data-engineering
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100