YAML Config Support Added
Description
Implemented a way to use yaml instead of redis
Testing Done
wrote some unit test. Going to field test on Saturday?
Resolved Issues
resolves #3315
Length Justification and Key Files to Review
N/A
Review Checklist
It is the reviewers responsibility to also make sure every item here has been covered
- [X] Function & Class comments: All function definitions (usually in the
.hfile) should have a javadoc style comment at the start of them. For examples, see the functions defined inthunderbots/software/geom. Similarly, all classes should have an associated Javadoc comment explaining the purpose of the class. - [X] Remove all commented out code
- [X] Remove extra print statements: for example, those just used for testing
- [X] Resolve all TODO's: All
TODO(or similar) statements should either be completed or associated with a github issue
probably going to polish this after some field test.
I have tested this on a robot:
this is a prove to work config file:
robot_id: 1
channel_id: 0
network_interface: "wlan0"
kick_coeff: 0.275
kick_constant: 500
chip_pulse_width: 20000
I will work on fixing that sometime this week
This PR is stale because it has been open for 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.
This PR was closed because it has been stalled for 5 days with no activity.
On my end the following works:
# in terminal one
bazel run //software/embedded:thunderloop_main --//software/embedded:host_platform=LIMITED
# in terminal two
./tbots.py run robot_diagnostics_cli
The YAML config in both yaml_reader.hpp and the one pointer by ROBOT_PATH_TO_YAML_CONFIG
robot_id : 1
channel_id : 0
network_interface : enp2s0
kick_coeff : 1.1
kick_constant : 1.2
chip_pulse_width : 1.3
Also, it seems that @annieisawesome2 is taking over this one with TOML instead.