- Rating
- 2
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
This paper proposes SpatialCanvas, a training-free inference framework that maintains an explicit typed spatial program and an image-bound state for a frozen VLM. The program specifies entity roles, source views, reference frames, operations, and evidence obligations. The VLM supplies local observations, while deterministic operators perform transformations and derivations only when the required role, source, type, unit, and frame conditions are satisfied.
The framework renders intermediate state onto source images and supports targeted re-observation and revision. When the final evidence structure is complete and the derived relation uniquely identifies an answer, selection is deterministic; otherwise, the frozen VLM selects an option using the canvas and state readout. With Qwen3-VL-4B, the paper reports improvements in the “All” score on three benchmarks, together with cumulative ablations, structural-completeness diagnostics, paired correctness transitions, and execution statistics.
Critical strengths
-
The framework separately records grounded marks, frames, derived relations, and evidence dependencies. Compatibility checks reject unsupported combinations of roles, types, sources, or frames, while upstream revisions invalidate and recompute only affected downstream records. The distinction between deterministic answer mapping and VLM fallback makes the execution interface inspectable. Its value lies in exposing the assumptions and provenance of spatial inference, rather than guaranteeing factual correctness.
-
The reported overall gains are 2.4, 9.5, and 2.4 percentage points on MMSI-Bench, MindCube-tiny, and OmniSpatial, respectively. Cumulative ablations show an initial decline after grounding, followed by recovery and gains with the complete pipeline. The paper also reports regressions in PR., Ard., and Pers., alongside 540 harmful revisions in the diagnostic snapshot. Proof-conditioned accuracy varies substantially across datasets, appropriately showing that structural completeness is not a uniform confidence signal.
Critical weaknesses
The observer-frame construction prompts appear to conflate a planar heading convention with the projection of a physical body frame. Appendix B, prompts 2.4 and 2.5, specify SOURCE-IMAGE vectors and map a left-facing profile to physical LEFT=image-down and FRONT=image-left, with the reverse mapping for a right-facing profile. Candidate LEFT and FRONT axes are also required to be approximately perpendicular.
These rules are not generally valid for upright people in ordinary photographs. In a side-on view, the physical left–right axis can lie largely along the viewing direction and have a shortened or degenerate image projection. Moreover, projected orthogonal 3D axes need not remain orthogonal in 2D. A structurally complete frame could therefore encode an inappropriate geometric convention, or the consistency check could reject a valid projected frame. This concern targets the prescribed frame-construction semantics, beyond the already acknowledged limitation that structural validation cannot certify visual correctness.
Questions for authors
-
In which geometric domain are the mappings and orthogonality check in Appendix B, prompts 2.4/2.5, intended to hold? Please distinguish image-plane, observer/body, camera, and world frames, and clarify whether these prompts are restricted to planar tasks. How are depth-aligned or degenerate body-axis projections and nonorthogonal projected axes handled? Controlled examples, the affected task coverage, and the provenance and dimensionality of the transformations in Eq. (5) would help establish the method’s scope.
-
Could you provide a comparison at approximately matched total call budgets to assess the specific contribution of binding checks and targeted refinement? The cumulative ablations control several execution settings, but add components and permit additional observation rounds in Full. A generic decomposition/self-refinement baseline or a Full variant removing source/frame-binding checks separately would strengthen attribution. Without such controls, conclusions should emphasize the benefit of the complete pipeline rather than isolate the proposed checks.
-
Could you reconcile the main tables, diagnostic snapshot, and token statistics through per-question execution records? Please provide evaluator aggregation formulas, run/snapshot identifiers, and paired correctness counts. The diagnostic transitions imply 1,106 Direct and 1,238 Full correct answers, whereas the rounded main-table scores would imply 1,095 and 1,243 if “All” were unweighted per-example accuracy. Please clarify whether weighting or different snapshots explain this difference.