NASA-AMMOS / NASA-AMMOS/AIT-GUI
AIT GUI should plot telemetry based on the telemetry timestamp, not the message recieve time <cubesat issue>
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 15
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Related to #204
AIT GUI publishes telemetry as it receives it, not based on any timestamp associated with the telemetry. This can work if all telemetry is realtime and in order; however, for cubesats that's not always the case. In a historical downlink of cubesat telemetry, a mixture of realtime telemetry packets and recorded telemetry packets may come down, depending on the design of the satellite. Additionally, recorded telemetry packets can come down as binary files for later processing (different issue) but in particular the capability needed here is for AIT GUI to be aware of the timestamp of the incoming telemetry and plot it at the right time in the GUI.
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
No files or tests are named. Start by tracing the telemetry reception and plotting entry points, using related issue #204 for context, and identify how telemetry timestamps are exposed. Done means mixed realtime, recorded, and out-of-order telemetry is plotted by telemetry timestamp rather than message receipt time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- data-visualization, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100