Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update meta file sections for clarity of purpose #113

Open
asgibson opened this issue Feb 1, 2024 · 1 comment
Open

Update meta file sections for clarity of purpose #113

asgibson opened this issue Feb 1, 2024 · 1 comment
Labels
convention Repository coding and documentation standards help wanted Extra attention is needed question Further information is requested

Comments

@asgibson
Copy link
Contributor

asgibson commented Feb 1, 2024

The meta file, which contains information about what received telemetry is expected to look like and how that relates to the running of OnAIR should be examined/updated to make usage more clear.

Specifically, we should discuss whether the "subsystems" label still makes sense and if "order" is descriptive enough to explain what it is.

@asgibson asgibson added help wanted Extra attention is needed question Further information is requested convention Repository coding and documentation standards labels Feb 1, 2024
@asgibson
Copy link
Contributor Author

asgibson commented Feb 1, 2024

For the "order" section, using "frame_order" or "low_level_data_headers" may be more appropriate and descriptive of its use within OnAIR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
convention Repository coding and documentation standards help wanted Extra attention is needed question Further information is requested
Projects
None yet
Development

No branches or pull requests

1 participant