Response to
Reviewer btN3
- Q1. How often does a scored chunk actually retrieve a relevant first visit, and do independent training runs support the 200 s optimum?
- Does the bank content matter at long spans? (bank-content ablation at inference, new)
- Q2. Do the external comparisons hold when realized motion is matched, and what does CaR look like in the camera-following diagnostic?
Q1. How often does a scored chunk actually retrieve a relevant first visit, and do independent training runs support the 200 s optimum?
We replayed the training sampler on the 380 training segments (4,000 spans per setting, ten scored chunks each) with the
training retrieval score, and counted a latent as relevant when it sees at least half of the chunk's view frustum
(0.3 and 0.7 give the same picture). Pre-window history only, because the window is read directly.
| max span | a relevant first visit exists | top-6 contains one | ... given one exists | median age of retrieved visit | older than 30 s | spans <= 30 s |
|---|---|---|---|---|---|---|
| 100 s | 82.7% | 76.4% | 92.5% | 16.8 s | 27% | 22.6% |
| 200 s | 91.0% | 82.6% | 90.7% | 24.5 s | 44% | 10.2% |
| 400 s | 95.5% | 86.3% | 90.3% | 37.0 s | 55% | 5.0% |
Two readings follow. (i) Longer spans help because more first visits are in range and retrieved visits are older, not because retrieval
gets better: conditional hit rate is flat to slightly lower. (ii) Raising the cap from 200 s to 400 s also halves the share of
short spans (10.2% -> 5.0%) and doubles the mean span (106 s -> 206 s). So the 400 s decline can come from coverage, from this change
in the span distribution, or from both. We cannot separate them with the runs we have, so we now state in Sec. 4.3 that 200 s is best
*in our tested setup* and present saturation only as a hypothesis.
Variance: the numbers in the paper vary rollout seeds on one trained model. [PENDING: G2] we trained 200 s and 400 s again with a different
training seed; [fill in: ordering preserved / not preserved, with the new Revisit values]. With two trainings per configuration we do not claim a standard deviation.
Does the bank content matter at long spans? (bank-content ablation at inference, new)
We kept the trained 200 s / 400 s models and changed only what the bank holds at inference (20 web walks, first 60 s, one rollout seed; the top-6 row is the paper's five-seed mean):
| model | top-6 retrieval | random bank | no bank | bank from another video |
|---|---|---|---|---|
| 200 s: Revisit / Gain | 0.467 / 0.359 | 0.228 / 0.122 | 0.121 / 0.041 | 0.138 / -0.002 |
| 400 s: Revisit / Gain | 0.396 / 0.285 | 0.184 / 0.088 | 0.083 / 0.013 | 0.132 / 0.005 |
Both long-span models depend on the retrieved content: removing the bank, or filling it with frames from another video, takes Gain to about zero, and random frames from the same video recover only about a third. Same-seed top-6 values (0.464 / 0.363 and 0.390 / 0.299) are close to the five-seed means. This is evidence that the 400 s model uses its memory; it does not explain why 400 s is below 200 s.
Q2. Do the external comparisons hold when realized motion is matched, and what does CaR look like in the camera-following diagnostic?
*Camera following, five rollout seeds, CaR included* (first 60 s, v5 web walks; direction agreement / correlation with prescribed yaw / implied horizontal FOV, target 90 deg):
| system | direction | correlation | implied FOV |
|---|---|---|---|
| Memorizon 100 / 200 / 400 s | 0.987 / 0.986 / 0.986 | 0.956 / 0.958 / 0.955 | 90.4 / 90.2 / 90.2 |
| CaR | 0.990 | 0.959 | 60.2 |
| LingBot-World-v2 | 0.976 | 0.879 | 72.5 |
| Matrix-Game 3.0 | 0.971 | 0.866 | 98.1 |
| Infinite-World | 0.961 | 0.888 | 108.6 |
| DreamX-World 1.0 | 0.952 | 0.815 | 133.4 |
| HY-World 1.5 | 0.906 | 0.696 | 123.6 |
CaR follows the path as well as we do; its implied FOV of 60 deg is consistent with a narrower camera, not with a worse path. The other four are clearly worse.
*Returns stratified by realized yaw error.* Yaw is estimated from the generated video (phase correlation); it sees rotation, not translation, and is not a pose estimate.
We report two versions: one that assumes every camera has a 90 deg field of view, and one that rescales each video so its turn amplitude matches the prescribed path (this removes the effect of a different field of view, e.g. CaR's 60 deg, and keeps only unsteady turning).
Revisit / Gain over five rollout seeds, returns with error <= 10 deg, per-video calibrated:
| system | Revisit (mean ± seed std) | Gain | pairs |
|---|---|---|---|
| Memorizon 100 s | 0.441 ± 0.018 | 0.305 | 536 |
| Memorizon 200 s | 0.483 ± 0.010 | 0.361 | 457 |
| Memorizon 400 s | 0.435 ± 0.022 | 0.310 | 443 |
| CaR | 0.425 ± 0.016 | 0.289 | 592 |
| HY-World 1.5 | 0.329 ± 0.039 | 0.146 | 92 |
| Matrix-Game 3.0 | 0.302 ± 0.043 | 0.104 | 108 |
| Infinite-World | 0.275 ± 0.026 | 0.164 | 140 |
| LingBot-World-v2 | 0.163 ± 0.032 | 0.006 | 55 |
| DreamX-World 1.0 | 0.139 ± 0.039 | 0.029 | 113 |
Without calibration (90 deg assumed) the picture for the other four models is the same; CaR then has only 200 of its pairs in this bin (its 60 deg field of view reads as large error), with Revisit 0.490 and Gain 0.341.
Honest summary: among well-aligned returns, CaR is within seed noise of Memorizon 100 s and 400 s, and Memorizon 200 s is ahead of it by about 0.06 Revisit and 0.07 Gain; HY-World, Matrix-Game, Infinite-World, LingBot and DreamX remain far lower.
Most returns of the other systems fall in the > 25 deg bin, which is the confound the reviewer describes. We therefore (a) move the camera-following discussion into Sec. 4.2, (b) describe the cross-system ranking as indicative and the within-backbone ablations as the primary evidence for memory, and (c) no longer claim a clear margin over CaR from the 60 s table alone.
Fold-back and other returns give the same picture (split in the supplementary tables).