bluerobotics / bluerobotics/ping-viewer
Support telemetry in Ping360 replays
- Dominant language
- C++
- Stars
- 64
- Forks
- 47
- PR merge metrics
- No merged PRs in 30d
Description
## Summary
Telemetry should be integrated in replays via tlogs in the same way as live viewing supports it.
## Additional information
Live viewing allows auto-rotation via telemetry integration, but it's not possible to link a tlog file when doing replays, so the initial correctly-rotated display can only be seen live. This means visual inspection and analysis after a dive requires recording the screen, which seems unnecessary when both relevant data streams are also already being recorded.
Including telemetry in replays also makes it possible to compare display options given the same set of inputs, which can be important when determining the usefulness of a given setting.
Contributor guide
Research direction
Start by tracing how live Ping360 viewing links telemetry and how replay inputs are loaded, focusing on the tlog connection and auto-rotation paths. Done means a replay can use a tlog to produce the same telemetry-driven initial orientation and support comparison of display settings without screen recording.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100