- Rating
- 1
- Confidence
- 4
- Informativeness
- 1
- Presentation
- 3
- Soundness
- 3
Read review
Paper summary
This paper presents Relative Flow Matching (RFM), which centres the flow-matching source on the previous action so that the network predicts a scaled residual rather than the action itself. Since this is essentially a change of variables, the theoretical contribution is limited. The application is the main strength. A one-step policy matches the MPC expert at 50 Hz on a Raspberry Pi and is validated on a real drone, with a clean comparison against MeanFlow. However, the paper's own analyses only partly support its explanation.
Critical strengths
The application result is strong and practical. A one-step policy reaches MPC-level success (95.2%) in 4.7 ms on a Raspberry Pi Zero, well within the 50 Hz control budget.
Critical weaknesses
-
The method's novelty is limited. RFM amounts to an invertible affine change of variables, equivalent to standard flow matching on the scaled residual from the previous action, and its propositions follow directly from this. The results for A2A and Streaming Flow Policy are not reported in the main text, so it is hard to judge how much RFM improves on these closest methods.
-
The paper's explanation of why RFM works is not supported by its own analyses. Calibrating without any anchor already gives much of the transport reduction and changes success on its own, yet the anchor and the σ scaling are never ablated separately.
Questions for authors
-
What are the success rates and latencies of A2A and Streaming Flow Policy on the drone task, and how do they compare with RFM-MF under matched architecture and number of network evaluations?
-
During training, is x_prev the expert's previous action chunk or a chunk generated by the policy? If it is the expert's, how large is the train-test mismatch at deployment?
4 comments
Thank you for the author's reply. I maintain my score due to the limited contributions.
We thank the reviewer for the reply and for the effort they spent reviewing our paper.
Thank you for your reply, I appropriate the contributions in hardware experiments. But I strongly recommend authors submit to ICRA or IROS.
Response to Reviewer t7VY
Response to Reviewer t7VY
Please see also our general response, which covers the points shared across reviews.
We thank Reviewer t7VY for the clear review and for recognising the application result as strong and practical.
W1/Q1 Novelty, A2A and SFP in the main text; matched NFE. Our method defines a continuous interpolation s between standard FM and direct action mapping (A2A) in a residual space, see the general response for more detail. This differs from the previous works discussed in the paper that does not operate with residual flows (thus losing generality with fixed source methods). We find this residual space does not only provide a theoretically sound connection, but also shows 1) Improvement over direct action mapping in absolute space; 2) improved performance at an intermediate anchoring strength s (i.e., in between FM and A2A).
Both A2A and SFP are shown in main text figure 2. We will mention these values in the corresponding results section:
Each baseline uses the architecture of its reference implementation (App. B), with A2A's latent width selected on our task (bigger latent had worse performance). For matched NFE, we evaluated the published A2A weights with a single Euler step: 83.8 ± 4.2 %. At the same single call and practically the same size (0.94M vs 0.96M), RFM-MF leads A2A by 11 points, so the gap is not a matter of step count; six steps remains A2A's intended procedure and its entry in the table. SFP takes one network call per action, so for the single executed action it already runs at one call; at matched NFE RFM-MF leads it by 18 points.
W2 Anchor and σ never ablated separately. Sigma and s were ablated (Figure 4 with full ablation reference to table 5); now also updated and shown in the general response. Rescaling without the anchor gives 77.0 % against MeanFlow's 78.7 %; the anchor in absolute action coordinates 84.8 %; the anchor in RFM's residual coordinates 92.5 %, and 95.9 % in the chained form used for all results. The σ columns of Table 5 give the response to the scale at fixed weights, and the measured σ* is the best scale in every anchored row. This shows that several factors result in the performance gain, with a combined effect that outperforms overall.
Q2 Expert's or policy's x_prev; size of the mismatch. The anchor is the expert's previous action during training and the policy's own previous command at deployment (App. B); no anchor noise is added. Every success rate in the paper is closed loop with the policy's own anchors, so the effect of this mismatch is already contained in the reported numbers. To measure its size, we ran the NMPC as a shadow expert on the states visited by RFM-MF over the 400 held-out episodes. The policy's anchor lies 0.20 (RMS, normalised action units) from the expert's command at the same state; with s = 0.5 half of this enters the source, well within the source's own standard deviation (σ* = 0.276). The residuals the policy generates in closed loop have RMS 0.235 against 0.276 in the demonstrations, so they stay inside the training scale rather than drifting outward. This is consistent with the role of s: with s < 1 an anchor error is contracted rather than passed on in full, and s = 0.5 outperforms s = 1 (Table 5).