Introduced multithreading into system #49
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What type of PR is this? (check all applicable)
Description
The main change in this PR is creating separate threads for the controller and path planner.
The reasoning behind this is that currently every time the path planner is running, the controller is inactive causing large jumps.
This should have the benefit of increasing overall controller frequency, and also consistency in the controller.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Tested a single buggy sim on my computer and it appears to behave as expected. Tested the double buggy sim and seems to behave as expected on my computer also.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above.
have not been included
[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?