orbiternassp / orbiternassp/NASSP
CM DSE requires further implementation
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 213
- Forks
- 74
- Avg merge
- 2d 1h
- Merged PRs (30d)
- 6
Description
Right now rudimentary tape motion control is simulated and nothing else. The DSE should actually record the PCM telemetry to a file in the orbiter directory. This would enable the use of DSE for debugging later - If someone reports a systems simulation issue, we could ask them to reproduce it with the DSE recording and then send us the DSE file. Enabling MCC to remotely control the DSE through the uplink would even allow the MCC software to identify abnormal conditions, make a DSE dump of it, then package the DSE dump with an error report file for investigation.
This would be somewhat dependent on PCM system work to implement the unimplemented parameters (which would be required before tackling Issue #13 anyway) in order to make the recorded data actually useful.
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 with the existing rudimentary tape motion control and the dependent PCM system work, including the unimplemented parameters mentioned in the issue. Determine how the DSE can record PCM telemetry to a file in the orbiter directory; done means a useful DSE recording can be produced for later debugging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- data
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100