Provide information on simulation tick rate health
Closed this issue · 0 comments
kcnotes commented
After #12 is done, we will be able to track the 'health' of a student's simulator. This is done by checking the number of interpreter steps taken by JS per tick - if it is above a certain threshold, then the robot's actions are healthy and are predictable.
If it falls under a certain number (e.g. 2000), then the student's simulator is running too slow (most likely due to their computer or laptop - e.g. computer not plugged in, or using an old inefficient browser) and it will not be running at the speed sufficient for a competition.
Display an error if the health falls under a certain threshold.