Software
Software copied to clipboard
Thunderloop should call PrimitiveExecutor::stepPrimitive with the actual elapsed time
Description of the task
Thunderloop currently uses a static time, and if the loop ends up running slower than expected, the primitive executor and HRVO are gonna receive the incorrect delta time
Acceptance criteria
- [ ] Call stepPrimitive with a dynamic time
- [ ] Remove time_step from PrimitiveExecutor and HRVOSimulator constructor and class
Blocked By
#2814
@nimazareian Is this still necessary for the new motion planner? We can close it if it isn't.
@nimazareian Is this still necessary for the new motion planner? We can close it if it isn't.
Although the task description is focused around HRVO, it could still be useful to support dynamic delta time for trajectory motion as well