How does VMem index past views with surfels, what is its cycle-trajectory revisit test, and which parts of its release are open, gated or conflicting?

VMem keeps the past views as images but indexes them through a coarse surfel model: each surfel stores which views saw it, new target cameras render the surfels to vote for the top-K most relevant past views, and an image-set generator (Stable Virtual Camera, SEVA) generates the next views from those. Its main contribution to evaluation is a cycle-trajectory protocol (go out, return along the same path, score every 10 frames of the return) with LPIPS/PSNR/SSIM plus rotation and translation distance of camera poses re-estimated from the generated frames. The tables contain rows that are identical across methods, which should be checked before reuse. Code is MIT-labelled but vendors a CC BY-NC-SA component, and the weights sit behind a Hugging Face access gate. Curator qualifications: Code licences: root LICENSE 'MIT License' 'Copyright (c) 2025 Runjia Li'; extern/CUT3R/LICENSE 'CUT3R is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 License' with an empty holder line 'Copyright [2025–present]'. HF API: gated 'auto', tags 'license:apache-2.0', cardData license apache-2.0, files README.md and vmem_weights.pth, lastModified 2025-06-24; card body not opened (gated). Table 2 (RealEstate10K cycles): ViewCrafter [43] and SEVA [46] (K = 17) rows identical '0.401 11.82 0.217 24.72 0.902 0.492'. Additional inconsistency not stated by the candidate: Table 2 'VMem (K = 4)' (LPIPS 0.397, PSNR 15.72, SSIM 0.297, Rdist 0.821, Tdist 0.392) equals Table 4's K=17 'Camera Distance (SEVA [46])' row (0.397 15.72 0.297 0.821 0.392), while Table 4's K=4 VMem row is 0.381 14.82 0.275 0.793 0.124. Table 2 VMem (K = 17) equals Table 4 VMem K=17 (consistent). v3 is the latest arXiv version, so the rows were not corrected there. Ablation numbers in F1 match Table 4. Excerpts: 7 text excerpts present; three table-row excerpts present in the layout extraction (plain extraction interleaves columns). Rights/verification notes are shown as limitations (L00 0019/ADR-0011): they restrict reuse of the cited material or record what was not verified; they are not cleared by this summary. Limitations: [rights_conflict_record] Code rights conflict (MIT vs CC BY-NC-SA component) and gated weights: component permissions unknown; no gate accepted. Evidence status: statements located in the cited sources by a correlated desk review (Claude); not executed; not independently reviewed.

{
  "citations": [
    {
      "url": "https://arxiv.org/abs/2506.18903v3",
      "note": "arXiv 2506.18903v3 PDF (pdftotext -layout), page 6 Tables 2 and 4; Sec. 3.1, 4.1, 4.3, 4.4, App. D; arXiv abs page observed 2026-10-22: submission history v1 23 Jun 2025, v2 10 Jul 2025, v3 14 Aug 2025 (v3 latest); vmem 39291e4f LICENSE: 'MIT License' 'Copyright (c) 2025 Runjia Li'; vmem 39291e4f extern/CUT3R/LICENSE; vmem 39291e4f README.md (equals producer pin); HF API models/liguang0115/vmem (equals producer pin)"
    },
    {
      "url": "https://github.com/runjiali-rl/vmem",
      "note": "arXiv 2506.18903v3 PDF (pdftotext -layout), page 6 Tables 2 and 4; Sec. 3.1, 4.1, 4.3, 4.4, App. D; arXiv abs page observed 2026-10-22: submission history v1 23 Jun 2025, v2 10 Jul 2025, v3 14 Aug 2025 (v3 latest); vmem 39291e4f LICENSE: 'MIT License' 'Copyright (c) 2025 Runjia Li'; vmem 39291e4f extern/CUT3R/LICENSE; vmem 39291e4f README.md (equals producer pin); HF API models/liguang0115/vmem (equals producer pin)"
    },
    {
      "url": "https://huggingface.co/liguang0115/vmem",
      "note": "arXiv 2506.18903v3 PDF (pdftotext -layout), page 6 Tables 2 and 4; Sec. 3.1, 4.1, 4.3, 4.4, App. D; arXiv abs page observed 2026-10-22: submission history v1 23 Jun 2025, v2 10 Jul 2025, v3 14 Aug 2025 (v3 latest); vmem 39291e4f LICENSE: 'MIT License' 'Copyright (c) 2025 Runjia Li'; vmem 39291e4f extern/CUT3R/LICENSE; vmem 39291e4f README.md (equals producer pin); HF API models/liguang0115/vmem (equals producer pin)"
    }
  ]
}