NASA-AMMOS / NASA-AMMOS/AIT-GUI
MCT Adaptation issues: Realtime Timestamps <cubesat issue>
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 15
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
MCT expects to plot incoming timestamps at the time type received on the plot. Currently the adaptation assigns Date.Now() to incoming telemetry so they're simply plotted as received. This is insufficient for cubesat operations. See also https://github.com/NASA-AMMOS/AIT-Core/issues/356 and #204
Timestamps on incoming telemetry should represent the SCLK,ERT,or SCET (SCET is most important) of the incoming telemetry point so that MCT can plot it accordingly.
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 file or test is named. Start by tracing the adaptation's use of Date.Now() for incoming telemetry and review AIT-Core issue #356 and issue #204 for context. Done means incoming timestamps represent SCLK, ERT, or SCET, with SCET prioritized, so MCT can plot telemetry at the correct time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100