Start and stop headless GRIP using NetworkTables #505
|
If I have grip on a roborio and running via deploy then this will start both pipelines which will create unexpected (and really hard to diagnose) issues. |
|
It'll only start both of them if they're both connected to the same NetworkTables server, which is probably a bad idea anyways We could maybe make this only work on headless mode. I doubt anyone would need to use it in GUI mode |
codecov-io
commented
Feb 15, 2016
Current coverage is
|
2 of 5 checks passed
codecov/patch
30.00% of diff hit (target 70.00%)
Details
codecov/project
49.78% (-0.50%) compared to c7cbbb7 at 50.28%
Details
continuous-integration/appveyor/pr
Waiting for AppVeyor build to complete
Details
codacy/pr
Good work! A perfect pull request.
Details
continuous-integration/travis-ci/pr
The Travis CI build passed
Details
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This lets robot programs start and stop GRIP to save CPU without having
to wait for the process to start up again.
For example,
This should be useful for teams that want to do auto alignment in teleop, since they could start and stop vision processing whenever the driver presses the button to auto aim.
Closes #501