Add support in the GUI to set/interpret extended/custom headers
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 78
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
GUI sets/interprets cfs version 1 headers, and then skips data to "support" the other header types. Can't set or display extended or custom header data.
Describe the solution you'd like
Add support, preferably via a generic capability that can be customized (EDS/XTCE or other data description header definition).
Describe alternatives you've considered
Use a more capable/full function ground system if you need v2 or custom headers
Additional context
None
Requester Info
Jacob Hageman - NASA/GSFC
Contributor guide
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 locating the GUI's current CFS version 1 header handling and related tests, then define how extended and custom headers would be described through EDS, XTCE, or another generic definition. Done means the GUI can set and display those headers without skipping their data.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100