From 04a1c9423bb737be706424b2104e27179365243e Mon Sep 17 00:00:00 2001 From: Dean Brettle Date: Tue, 7 Feb 2023 03:29:25 -0800 Subject: [PATCH] Fix small typo. (#5849) "sensors requests" -> "sensor requests" --- docs/reference/robot.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/reference/robot.md b/docs/reference/robot.md index 1c5c9dd07aa..9024d287b39 100644 --- a/docs/reference/robot.md +++ b/docs/reference/robot.md @@ -251,7 +251,7 @@ It means that the step actually lasted the requested number of milliseconds, but It means that the requested step duration could not be respected. When using `wb_robot_step`, the controller code is executed sequentially with the Webots simulation step, i.e., not in parallel. -This is due to the fact that a typical controller reads sensor information, makes some computation, orders motor commands and calls `wb_robot_step` which actually sends the motor commands and sensors requests and waits until Webots completes a simulation step, which may take some time depending on the complexity of the simulation. +This is due to the fact that a typical controller reads sensor information, makes some computation, orders motor commands and calls `wb_robot_step` which actually sends the motor commands and sensor requests and waits until Webots completes a simulation step, which may take some time depending on the complexity of the simulation. During this time, the controller is idle, waiting for Webots to complete its simulation step. On the other hand, prior to starting a new step, Webots waits for all the controllers to send their `wb_robot_step` messages which may induce some idle waiting time in Webots if a controller doesn't send quickly enough its `wb_robot_step` message because it is busy with some computation. If the two computational processes (Webots and controller) are slow, it may be interesting to parallelize them.