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

Improve how configs are passed into GNC scripts #165

Open
Thomas-Neill opened this issue Mar 31, 2024 · 0 comments
Open

Improve how configs are passed into GNC scripts #165

Thomas-Neill opened this issue Mar 31, 2024 · 0 comments

Comments

@Thomas-Neill
Copy link
Collaborator

Currently GNC scripts take in multiple command line arguments which correspond to GPS data, for example the mission lap or dropzone. These should probably be combined into one configuration file as we'll never want to "mix and match" different missions and dropzones. (Reasons: it's hard to change on the fly and check whether it's correct, and leaves room open for a new category of error.) Similarly other command-line arguments that aren't location-specific should have defaults too.

Also, for the geofence, we should pass that in through a .plan file rather than a separate file so that both QGroundControl and our script are using the same source of information.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant