- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes a training-free approach (FreeSpeed) for modulating the robot execution speed. The paper is motivated by the fact that naively resampling the predicted action chunk may lead to out-of-distribution states and affect the policy performance. Therefore, FreeSpeed uses the inconsistency between adjacent actions within a single chunk as the primary signal for action chunk transformation. Experiments under both simulation and real-world experiments demonstrate the effectiveness of the proposed method.
Critical strengths
-
The paper's perspective is interesting, the method is simple, and the experiment results demonstrate the effectiveness of the proposed method.
-
The paper is well-written, with ideas and experiment results demonstrated clearly.
Critical weaknesses
While I lean towards acceptance of the paper, I have the following concerns:
-
I am confused why FreeSpeed can sometimes improve the performance over the reference model when accelerated or decelerated. For deceleration, I suspect it might be due to that the upsampling process does some smoothing and can somehow improve. But acceleration performs downsampling, and rescaling is actually introducing new actions that may deviate from the training distribution, so that the robot state may have a higher probability of falling into an OOD scenario. Moreover, Figure 4 indicates that scaling mostly happens at free-motion stages (instead of physical interaction stages). These stages, under pick and place tasks, should just be using the robot to approach the object or carrying the object around. Thus, I do not see how these stages could affect performance, and would like the authors to clarify more on these aspects.
-
FreeSpeed seems to be sensitive to be very sensitive to the choice of decay rate . The generalizability of the method remains questionable, as a good range of could vary substantially over different benchmarks, requiring much parameter tuning.
Questions for authors
-
I am not sure about the practicability of 'slowing down' for robots. Most robots already execute very slowly (also as this paper's real-world demonstrations show) , slowing them done further does not seem necessary. The upsampling process seems more like a smoothing technique. Also, the paper does not clearly explain what are the upsampling and downsampling algorithms they use.
-
For Figure 4(b), the acceleration case could degenerate to the 1x reference prediction, while the deceleration one cannot. What is the purpose of design that the deceleration one cannot converge to the factor of 1?
8 comments
Response to reviewer B9W9 (2/6)
Response to Weakness 1 (continued):
The observation-distribution analysis in Figure 6b supports the effect of this modulation. On Task 60 under the 2× command, the median distance from the observations of FreeSpeed to the training data is 1.09 times that of the reference, compared with 1.79 times for vanilla resampling and 1.68 times for w/o CR. In this analysis, the observation distribution shift of FreeSpeed is therefore smaller.
In response to: "I am confused why FreeSpeed can sometimes improve the performance over the reference model when accelerated or decelerated. For deceleration, I suspect it might be due to that the upsampling process does some smoothing and can somehow improve."
2) Higher success on some tasks is accompanied by lower success on others.
You observe that FreeSpeed achieves a higher success rate than the reference on some tasks. Table 2 also contains tasks on which it is lower than the reference, and the mean success rate over the ten tasks is close to the reference.
The paired outcomes from identical initial states further illustrate this. Over the 500 initial states, the 1× reference succeeds on 444 and FreeSpeed under the 2× command on 443, so the two success rates are statistically the same. There are 36 initial states on which the reference fails and FreeSpeed succeeds, and 37 on which the reference succeeds and FreeSpeed fails. The sets of initial states on which the two methods succeed therefore differ, but the changes in the two directions largely cancel overall. The same holds under deceleration. FreeSpeed performs no interpolation or smoothing under deceleration. It only splits each predicted increment into smaller steps along its original direction, so results above the reference on individual tasks also belong to this two-way change. The cause of this change is explained in point 3.
In response to: "These stages, under pick and place tasks, should just be using the robot to approach the object or carrying the object around. Thus, I do not see how these stages could affect performance, and would like the authors to clarify more on these aspects."
3) The free-motion phase affects the state at the subsequent grasp.
As described above, the modification that FreeSpeed applies during free motion does not directly cause an out-of-distribution state that would make the task fail. If your question is why modifying the speed in this phase can still lead to a higher success rate than the reference, our analysis of individual cases suggests the following explanation.
A change in execution during the approach phase changes the robot state and the observation at each replan, which in turn affects the actions predicted by the policy and the position at which the gripper closes. Even if the rescaling factor is close to 1 near the grasp, the state in which the robot enters this phase may already differ from the reference. The gripper command is not rescaled in magnitude, but this does not guarantee that the gripper closes at the same time and position.
Task 69 shows the largest increase in success among the ten tasks, from 80% for the reference to 94% for FreeSpeed. FreeSpeed succeeds from nine initial states on which the reference fails, and it fails from two on which the reference succeeds. Figure A8 in Appendix E.7 shows both directions of outcome change through two pairs of keyframes on this task. From initial state 20, the reference closes the gripper beside the box, with its fingers closing on empty space, whereas FreeSpeed grasps the box. From initial state 32, the box slips out after FreeSpeed closes off-center, whereas the reference succeeds.
These examples offer one possible explanation for the two-way change in the paired outcomes. A change in the approach can align a grasp that would otherwise miss the object, and it can also make a grasp fail that would otherwise succeed. Free motion therefore does not complete the grasp directly, but it can still affect task success by changing the state at the subsequent interaction.
We would be glad to clarify further if you have any other questions.
Revision: Appendix E.7 adds the paired analysis of success and failure from identical initial states, and Figure A8 shows the paired keyframes of Task 69 from initial states 20 and 32.
Response to reviewer B9W9 (3/6)
Weakness 2: FreeSpeed seems to be sensitive to be very sensitive to the choice of decay rate . The generalizability of the method remains questionable, as a good range of could vary substantially over different benchmarks, requiring much parameter tuning.
Response: Thank you for your careful reading and comments. Regarding the sensitivity and generalizability of the decay rate , we make two points. First, all evaluations in this paper use the same fixed , which is not adjusted per benchmark or policy. Second, the single-task sweep in Figure 7b shows a wide effective range of , within which both the success rate and the actual acceleration are maintained. The revised manuscript adds to Section 5.7 the task used in the sweep, the result of the default value on this task, and a statement that all constants are kept the same across all experiments.
1) The fixed parameters are used directly in all evaluation settings. was determined on three LIBERO-90 tasks, Tasks 2, 18, and 34. All results reported afterwards across benchmarks, policies, and the real robot were obtained with this fixed setting, without readjusting or the endpoint mappings for any evaluation environment. Specifically, the remaining LIBERO-90 tasks with Flow Matching, the four LIBERO suites with and Fast-WAM, Robomimic with Diffusion Policy, the four real-robot tasks, and the seven commanded rates all use the same set of constants. The transfer of the method across these settings therefore does not rely on per-benchmark tuning.
2) The single-task sweep shows a wide effective range.
Figure 7b sweeps on LIBERO-90 Task 2 under the 2× command, with 50 rollouts per value and a logarithmic horizontal axis. The default setting gives a success rate of 88% and a realized rate of 1.28×, matching the result in Table 2. As varies from 22 to 140, the success rate ranges from 86% to 98% and the realized rate from 1.18× to 1.31×. On this task, the effective values are therefore not confined to a narrow interval around the default, and actual acceleration is retained within this range.
We would be glad to clarify further if you have any other questions.
Revision: The last paragraph of Section 5.7 now states the task used in the sensitivity analysis and its results, and that all constants are identical across all experiments.
Response to reviewer B9W9 (1/6)
We sincerely thank Reviewer B9W9 for the insightful and constructive comments. We are glad that you recognize the perspective of this work, the simplicity of the method, and the validation of its effectiveness in simulation and real-robot experiments, and we appreciate your positive assessment of the writing. Below we respond to each weakness and question, and we hope that these responses address your concerns. A revised manuscript has also been uploaded, with all additions and changes marked in blue.
Weakness 1: I am confused why FreeSpeed can sometimes improve the performance over the reference model when accelerated or decelerated. For deceleration, I suspect it might be due to that the upsampling process does some smoothing and can somehow improve. But acceleration performs downsampling, and rescaling is actually introducing new actions that may deviate from the training distribution, so that the robot state may have a higher probability of falling into an OOD scenario. Moreover, Figure 4 indicates that scaling mostly happens at free-motion stages (instead of physical interaction stages). These stages, under pick and place tasks, should just be using the robot to approach the object or carrying the object around. Thus, I do not see how these stages could affect performance, and would like the authors to clarify more on these aspects.
Response: Thank you for your careful reading and comments. Your questions help us clarify the role of rescaling and how free motion affects task success. Your comment raises three points, and we respond to each in turn, quoting the corresponding sentences before each response. They concern whether rescaling pushes the robot out of distribution, why FreeSpeed sometimes exceeds the reference, and how the free-motion phases can affect performance. The paired analysis behind the second and third points has been added to Appendix E.7 of the revised manuscript.
In response to: "But acceleration performs downsampling, and rescaling is actually introducing new actions that may deviate from the training distribution, so that the robot state may have a higher probability of falling into an OOD scenario. Moreover, Figure 4 indicates that scaling mostly happens at free-motion stages (instead of physical interaction stages)."
1) FreeSpeed limits the enlargement of the step length under acceleration.
Please allow us to first clarify the acceleration logic of FreeSpeed. Under acceleration, FreeSpeed downsamples the action chunk predicted by the policy. Under the 2× command, for example, the number of steps executed per chunk is roughly halved. To cover the displacement of the original chunk in fewer control steps, the skipped motion has to be compensated. Otherwise, downsampling alone would only discard part of the trajectory. The policy would then need two inferences to complete the original motion, which takes the same number of action steps and, at the same control frequency, the same execution time. For this reason, both baselines by default compensate the full displacement, which is equivalent to a rescaling factor of 2 under the 2× command. Vanilla resampling adds the skipped increments to the retained ones, and w/o CR multiplies the retained increments by the commanded rate.
FreeSpeed uses the same downsampling stride but limits the rescaling factor to between 1 and 1.8 according to cosine inconsistency. When the directions are consistent, the factor is close to 1.8. As the inconsistency increases, the factor moves toward 1. Relative to the factor of 2 used by w/o CR, FreeSpeed therefore limits the enlargement of the step length rather than increasing it from the original 1× step length. Any test-time change of speed moves the policy away from the 1× reference, so every such method is out of distribution to some degree, and FreeSpeed is designed to keep this shift as small as possible. Our analysis in Section 5.5 (Figure 6 and Appendix E.4) shows that keeping the step length close to the original prediction keeps the observations close to the training distribution.
Your observation about Figure 4 is accurate. Relative to the original increments predicted by the policy, the step length is enlarged mainly in the free-motion phases. In our hypothesis, these phases are exactly where acceleration is safe and does not lower the success rate, that is, where test-time modulation yields a free gain in speed. Taking the nominal displacement compensation of a factor of 2 as the reference, FreeSpeed lowers the factor to close to 1 near grasping and placement, so the suppression of step-length enlargement is stronger in these phases.