NASA-AMMOS / NASA-AMMOS/AIT-GUI
MCT Adaptation query issues: minmax/rollups <Cubesat issue>
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 15
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
The MCT Adaptation does not support minmax telemetry queries.
Minmax queries are used to make plots that are data-efficient but visually correct for the size of a screen.
Influx DB supports rollup queries, and MCT supports them via the minmax option and size field on query parameters.
These should be used to generate queries to rollups configured in InfluxDB. Note that this may also require some configuration on the AIT-Core side.
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
Start by tracing how the MCT Adaptation handles telemetry query parameters, especially the minmax option and size field. Then inspect how rollups are configured on the AIT-Core side and how queries are generated for InfluxDB. Done means minmax requests produce queries against the appropriate configured rollups, including any required AIT-Core configuration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100