NASA-AMMOS / NASA-AMMOS/AIT-Core
MCT Adaptation Dictionary issues <Cubesat issues>
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 56
- Forks
- 35
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 3
Description
- Dictionary should be organizer. Current dictionary is a flat list, which cases performance and UI issues if you have large numbers of channels in MCT (10k+ typically)
- Plugin for dictionary should be extensible and able to add more sources by config. IE for some cubesats you'll have cubesat dictionary 1, cubesat dictionary 2, cubesat ancillary data (ground station etc) 1, cubesat ancillary data 2.
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 reviewing the current MCT dictionary representation and the plugin configuration entry point. Define how the dictionary should be organized for large channel counts and how multiple cubesat and ancillary-data sources can be selected by configuration; done means both requirements are supported without the stated performance and UI issues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100