- Rating
- 1(−1)
- Confidence
- 4(+1)
- Informativeness
- 1
- Presentation
- 1
- Soundness
- 1(−1)
Read review
Paper summary
Text-to-motion generation with trajectory control typically requires additional control networks or costly iterative refinement. This paper proposes Codebook-Geometry Correction (CodeGeo), which leverages part codebooks to define a geometry for minimally correcting generated motions toward prescribed trajectories in at most eight steps, replacing 1,600 refinement iterations. To provide a suitable initialization, Key/Value Control (KV-Control) introduces trajectory-conditioned key/value memory into a frozen masked transformer, using only 10.5M trainable parameters and Anatomy-Aware Part Tokenization (PartVQ). CodeGeo’s metric anisotropy is adapted to the distribution of controlled body parts. Our method achieves 0.24 cm error and 0.067 FID for pelvis control, and 0.25 cm error and 0.072 FID for multi-joint control, outperforming MaskControl’s 0.72 cm error and 0.083 FID.
Critical strengths
- Presents solid and credible engineering results, demonstrating effective trajectory control with high accuracy and improved inference efficiency.
- Provides a practical solution for efficient motion control while preserving motion quality.
Critical weaknesses
-
The paper is difficult to follow due to heavy use of coined terminology, crowded figures, and several formatting issues that make verification harder.
-
The contribution seems primarily an application of standard engineering optimization to motion control, with limited advances in representation learning or generative modeling, so the fit for ICLR is unclear.
-
The paper does not discuss closely related work on damped least-squares inverse kinematics, latent-space editing (e.g., DragGAN and DragDiffusion), or constrained generation (e.g., DPS and RePaint). T-Concat and KV-Control also resemble existing multi-codebook sequence modeling and attention-based conditioning techniques, making the novelty of these components unclear.
-
Table 1 bolds the proposed method rather than the best value in each column. In the pelvis block, it underperforms MaskControl in Top-3 (0.802 vs. 0.809) and FID (0.067 vs. 0.061), and its feed-forward variant performs better in skating (0.0425 vs. 0.0477) and latency (0.17 vs. 0.21 s). This presentation may overstate the method’s overall advantages.
Questions for authors
see weaknesses. If my concerns are adequately addressed, I would consider increasing my score; otherwise, I may consider lowering it.
Final justification
Fundamentally, this work incorporates physical constraints into motion representations through an optimization procedure. However, its main contribution appears to be the application of Gauss–Newton iterations to test-time correction, rather than a novel generative modeling methodology. Gauss–Newton itself is a well-established optimization technique, not introduced by this work. I therefore remain concerned that the contribution is not well aligned with ICLR’s generative modeling community and offers limited methodological insights to the broader motion generation and AIGC communities.
The writing remains very poor. In my assessment, its formulaic phrasing, repetition and weak reasoning give it a pronounced AI-like style. It reads as mechanically assembled technical text rather than a clear account for human readers. The rewrite has not resolved these problems or my concerns about the contribution. Moreover, the current version differs so substantially from the original submission that it is almost a complete rewrite. Given the extent of these changes, I would suggest that the authors consider withdrawing and resubmitting the paper.
9 comments
Thank you for your prompt response and engagement with our paper.
I am the supervisor and corresponding author of this paper (the previous responses were posted by the first author following discussions among all co-authors). We took your feedback very seriously and carried out a comprehensive revision over the weekend to improve the readability of the paper. I would like to address the additional concerns you raised today:
-
Because the main text was densely packed with information, we initially chose a long and descriptive title to help understanding. Now the manuscript has been rewritten for better readability, so we agreed to make a more concise and intuitive title. Our proposed new title is: "Codebook-Geometry Correction for Trajectory-Controlled Text-to-Motion Generation". We will check the OpenReview guidelines regarding title modifications and make this change in the camera-ready version.
-
The blue-highlighted text in the newly uploaded PDF does NOT show general modifications BUT represents newly added parts in response to the reviewers' comments. This is explained in the separate new thread titled "To all reviewers and the AC: revised PDF uploaded, summary of changes." because it should be noticed to all reviewers and chairs. The modifications and polishing are addressed in detail below.
-
Improving readability could not be achieved by simply editing some paragraphs or sentences. As noted in the first author's previous response ("Over the weekend, all co-authors carefully re-read the entire paper and rewrote it thoroughly to improve clarity and flow"), we polished the entire manuscript. From Friday to Sunday, we restructured paragraphs, expanded overly compressed phrasing into clearer expressions, and utilised AI assistance to polish the text. Because nearly every paragraph has major/minor refinements, highlighting every textual difference would have required highlighting almost the entire paper. We had actually discussed the potential risk of misunderstanding if these edits were not highlighted as you pointed out. However, we concluded that there is no point of highlighting the entire paper, and instead chose to state explicitly in our response that the whole manuscript was rewritten. Additionally, please note that the current uploaded version cannot not be the final paper. Expanding the explanations for clarity inevitably increased the length of the paper. Although we moved some parts including the original Figure 3 to the Appendix, the current draft slightly exceeds the ICLR page limit. We will need to shorten the text again for the final version. Due to the limited time remaining in the rebuttal period, we uploaded this version first so that you could evaluate the updated writing style. As you have the original submission on hand, if you compare the original and updated versions side-by-side, you will see how the narrative flow and readability have been improved. To be completely transparent, aside from the parts highlighted in blue, the revised paper has only reorganised and rewritten content from the original submission without any unmentioned technical additions.
All co-authors agree that your feedback has helped make the paper significantly clearer, and we sincerely appreciate your time and guidance throughout this review process. Although little time remains in the discussion period, we are happy to be fully committed to incorporating any further suggestions into the camera-ready version.
Thank you for the detailed clarification.
However, I would like to reiterate that, according to the ICLR review policy, “a pdfdiff will be applied to compare new changes to the paper against the original submission” and “Area chairs and reviewers reserve the right to ignore changes that are significantly different from the original paper.” The policy also explicitly states that “reviewers and area chairs are not required to look at every revision.”
These guidelines make it clear that reviewers and ACs are entitled to understand the differences between the original submission and the revised manuscript, and are not expected to independently compare two PDF versions to identify and assess the changes themselves.
I therefore strongly encourage the authors to explicitly highlight and explain the modifications made to the manuscript, rather than relying on reviewers to conduct a side-by-side comparison. I understand that improving readability may involve extensive rewriting; however, this does not negate the importance of making the revisions transparent and readily identifiable to the reviewers and AC.
Clarification Requests to Authors
Thank you for the detailed response and the revised manuscript. However, I still have several concerns.
First, the title is overly long and seems to frame the work within a rather narrow scope. I encourage the authors to carefully reconsider whether the title and the Introduction accurately reflect the actual scope and contributions of the work.
Second, please ensure that all modifications are consistently highlighted in blue. For example, the revised caption of Figure 1 is not highlighted. I cannot verify whether other modifications are also unmarked, which could potentially mislead reviewers and the AC regarding the extent of the revisions.
Third, I would like to point out that the paper, with the Introduction being one example (not just intro.), differs substantially from the version I originally reviewed. However, only a very small portion of the modifications appears to be highlighted in blue. I have retained a local copy of the original manuscript and would appreciate the authors being transparent about the changes between the two versions.
For example, in the initial version, the first paragraph is:
However, the current version is (without any blue highlights):
Forth, ... .
I appreciate the authors’ efforts, but I believe these issues warrant further attention.
BTW, I trust that, as stated in the manuscript, the authors have used AI tools only within the declared scope. I hope the authors will carefully adhere to the stated boundaries when using such tools.