-
Notifications
You must be signed in to change notification settings - Fork 12
Add tool for listing inputs and outputs of OSGAR module #1029
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I miss there some better description of what the code do and how to use it.
Can you add some comments (documentation) in the code?
|
ACK, this was actually experiment (or PoC - Proof of Concept), that it is possible ... originally coded in osgar-apps, but it has sense for all OSGAR users. If you consider it valuable I will later extend it and add argparse there. The original motivation were some renames, which surely broke my configuration, so this was the first step towards automatic config check (or fill in in & out optional fields). Thanks m. |
|
Automatic config check sounds good. |
|
well, it is not perfect ... tested: but I had to add try-except in order to overcome required config parameters. As long as they are AFTER register it is probably OK. OTOH sensor modules are probably expected to fail: hmm, there will be some bug, mmt |
|
OK, now it looks better: |
|
This i got for imu: The some drivers are not well standardized.. |
tajgr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be valuable in the future.
This is a simple (i.e. not perfect) tool for listing OSGAR module inputs and outputs: