- Rating
- 2
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
The paper proposes canonical-output conditioning: external cues are expressed in the coordinates of a generated task representation and applied through a shared quadratic energy. GOF trains a LiDAR-conditioned diffusion prior over orientation fields without route inputs. Geometric adapters handle four route interfaces, and inference-time guidance comes from Orientation Mixing, re-noising, and spatial/history sectors. On six SemanticKITTI sequences, the paper shows fixed-prior interface reuse and reports 0.29 m mean ADE vs 0.38 m for deterministic OrField in the full system. It also runs intent, readout, temporal-conditioning, and map-perturbation experiments.
Critical strengths
I think the interface-reuse claim is well supported. Table 1 keeps GOF’s prior and four-sector layout fixed, swaps route interfaces, and drops temporal history. The paired intent study also controls observations and seeds: GOF follows the changed intent in 1022/1024 pairs vs 911/1024 for Conditional Training. That’s good evidence for field-level control without a trained route-input channel. The component studies are useful too. Re-noising cuts mean ADE from 0.44 to 0.31 m on all six sequences, and the readout-crossover and conflicting-history controls help clarify what trajectory extraction and temporal conditioning actually contribute.
Critical weaknesses
The accuracy gain from the conditioning architecture is still unclear. With the same greedy readout, the headline 0.38 vs 0.29 m becomes 0.31 vs 0.29 m, and both hit 96% HitRate (Table 9). GOF also has a richer cue/history setup, and the matched smoothed single-route result is missing. So the paper supports interface reuse more than a matched accuracy advantage.
The methodological step is also modest: the readouts come from OrField, Orientation Mixing is basically a gradient step on a quadratic energy, and backward Universal Guidance already does clean-estimate guidance. The DPS baseline is also underspecified, so its large deficit is hard to judge.
Questions for authors
- What does GOF get with the smoothed single-route input, no history, and a shared readout, compared with the learned-route models in their matched setting?
- How does GOF compare with backward Universal Guidance using the same field prior, quadratic energy, route cues, and denoiser budget?
- For DPS, what objective, differentiation variable, guidance scale, tuning protocol, and actual denoiser-evaluation count were used?