lasp / lasp/space_packet_parser
Investigate converting XTCE to Electronic Data Sheets format
Open
enhancement
help wanted
question
- Dominant language
- Python
- Stars
- 39
- Forks
- 15
- Avg merge
- 2d 16h
- Merged PRs (30d)
- 12
Description
Summary
EDS are used by some missions to describe packet structures. EDS is advertised as a similar configuration mechanism to XTCE in that it describes packet structures (confirm this understanding).
Driving Requirements
- Build an example of converting an XTCE document to EDS, similar to our CSV to XTCE converter but the other direction. This should demonstrate at a basic level what is required to map between these two formats (XTCE and EDS).
- Build an example of starting from an EDS file and building an XTCE definition from it to parse packets. This can be a contrived, simple example to demonstrate the pattern for creating a packet definition in memory from an EDS file.
- Analyze and produce a summary report on the feasibility and complexity of building a conversion system between EDS and XTCE into the Space Packet Parser library and supporting EDS-based configuration (via parsing EDS to an XTCE definition in memory). Consider the scope of each data model and the fidelity of mapping between the two.
Resources
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.
Assessment
This issue has not been assessed yet.