- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes PriorHOSI, which separately learns a human–object interaction prior from OMOMO and a human–scene interaction prior from LINGO, then composes them at inference time. The HOI prior uses relation-aware consistency distillation, while the HSI prior uses body-part-aware SDF residual refinement. During editing, diffusion noise optimization moves the joint human–object motion toward refreshed scene-adapted human targets, while an augmented-Lagrangian constraint preserves object-relative hand positions. On 469 InfBaGel tasks, the paper reports higher task success and hand–object contact, and lower body–object and human–scene penetration than InfBaGel. Object–scene penetration is mixed: the mean and maximum depths increase, while the fraction of penetrating frames decreases.
Critical strengths
-
A useful composition strategy for complementary interaction data. Separately learning HOI and HSI priors addresses the mismatch between coupled object motion and scene-conditioned human motion. Constraining hand positions in the object frame provides a principled way to preserve local contact while allowing global body–object adjustments.
-
A substantial benchmark evaluation with informative ablations. The paper evaluates on 469 InfBaGel tasks, compares against several methods, and includes ablations for scene guidance, contact constraints, relation supervision, and residual refinement. It also reports the object–scene trade-off rather than presenting every metric as an improvement.
Critical weaknesses
-
The optimization objective used for the reported results is not traceable from the paper to the supplementary implementation. Section 3.4 defines the editing objective as scene-target matching plus the contact constraint. However, the default supplementary protocol appears to activate a MetricMotionObjective, which the closed-loop implementation adds to the HSI and relation losses. The objective includes terms for goals, body–object collision, human–scene and object–scene penetration or clearance, foot stance and speed, motion continuity, and trajectory acceleration. Several of these directly target reported evaluation metrics. If these terms were active for Tables 1–3, the method description and ablations omit consequential parts of the optimization. If the supplement represents a different or later configuration, the paper should identify which code and configuration produced the reported results.
-
The benchmark development history needs clarification. The supplementary summary code marks test_set_development as True and states that all 469 tasks had historical development exposure. This flag alone does not establish that test outcomes informed method or hyperparameter choices, but the paper does not explain what was exposed or what decisions followed. Separately, the reported object–scene mean and maximum penetration worsen, and the task-success gain over InfBaGel is 1.71 percentage points without uncertainty estimates in the paper.
Questions for authors
Q1: Were the additional metric-aware terms in the default supplementary protocol active? If so, please report their contribution and ablate them against the objective stated in Section 3.4. If not, please identify the configuration that reproduces the tables.
Q2: Were the additional metric-aware losses applied to the baselines, or are they part of the benchmark’s prescribed evaluation protocol? If they were applied only to PriorHOSI, the comparison may conflate prior composition with direct optimization of the evaluation metrics. If they are part of the protocol, please clarify where it specifies them and how they are used for each method.
Q3: What does the supplement’s test_set_development: True flag mean in this submission? Were method choices, hyperparameters, or stopping decisions made after examining outcomes on these tasks? Please clarify the development history and, if those outcomes informed the final choices, provide an evaluation on tasks not used during development.
Q4: Could you report paired uncertainty estimates for task success and the scene-penetration metrics, and discuss the increase in object–scene mean and maximum penetration?