Convert to use a common data description format for interpreting telemetry and creating display
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.
We currently duplicate changes to the groundsystem txt tlm definition files and the CCDD json files to support this element and CTF.
See also https://github.com/nasa/cFS-GroundSystem/issues/61#issuecomment-600096734, EDS is another optional format
Describe the solution you'd like
Use one of the more "standard" tlm definition formats, selectable input directory as location for the format files, with a configurable default. Target endian selectable (if not defined in the format, as in the json case).
Describe alternatives you've considered
Some other shared format (or at least convertable). Note CCDD theoretically converts between a few, including these json and EDS files.
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
Start by reviewing how the groundsystem TXT telemetry definition files and CCDD JSON files are currently used for telemetry interpretation and display. The issue does not identify files, tests, or a settled standard format; completion would require agreeing on the shared format, selectable input directory, default location, and target-endian behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100