How does WorldMem store and retrieve earlier frames so a generated Minecraft or RealEstate10K world stays consistent after the camera leaves and returns, what revisit numbers does it report, and what does it cost?
WorldMem keeps every generated frame as a token-level memory unit with a 5-number pose and a timestamp, picks up to a handful of units per step by field-of-view overlap and time difference (greedy, with a similarity filter), and lets the generating tokens cross-attend to them with pose/time embeddings. Its revisit tests compare regenerated frames against ground-truth frames with PSNR, LPIPS and reconstruction FID: 100 frames generated after a 600-frame memory bank on a custom Minecraft set, and five start=end trajectories over 100 RealEstate10K scenes. These are paper_result numbers on simulator poses; the paper's own tables disagree with each other and with the repository's expected-results block on some cells.
Structured fields
{
"citations": [
{
"url": "https://arxiv.org/abs/2504.12369v3",
"note": "arXiv 2504.12369v3 PDF (pdftotext and -layout): Sec. 3.3-3.4, 4.1, Tables 1-3 (layout lines 402-416), Tables 7-8 (lines 909-921), Supplementary 7.1-7.2; WorldMem README (equals producer pin) 'Expected Results' lines 133-141; LICENSE.md S-Lab License 1.0; HF API zeqixiao/worldmem_checkpoints"
},
{
"url": "https://github.com/xizaoqu/WorldMem",
"note": "arXiv 2504.12369v3 PDF (pdftotext and -layout): Sec. 3.3-3.4, 4.1, Tables 1-3 (layout lines 402-416), Tables 7-8 (lines 909-921), Supplementary 7.1-7.2; WorldMem README (equals producer pin) 'Expected Results' lines 133-141; LICENSE.md S-Lab License 1.0; HF API zeqixiao/worldmem_checkpoints"
},
{
"url": "https://huggingface.co/zeqixiao/worldmem_checkpoints",
"note": "arXiv 2504.12369v3 PDF (pdftotext and -layout): Sec. 3.3-3.4, 4.1, Tables 1-3 (layout lines 402-416), Tables 7-8 (lines 909-921), Supplementary 7.1-7.2; WorldMem README (equals producer pin) 'Expected Results' lines 133-141; LICENSE.md S-Lab License 1.0; HF API zeqixiao/worldmem_checkpoints"
}
]
}Evidence claims
- [sourced_fact] WorldMem keeps every generated frame as a token-level memory unit with a 5-number pose and a timestamp, picks up to a handful of units per step by field-of-view overlap and time difference (greedy, with a similarity filter), and lets the generating tokens cross-attend to them with pose/time embeddings. Its revisit tests compare regenerated frames against ground-truth frames with PSNR, LPIPS and reconstruction FID: 100 frames generated after a 600-frame memory bank on a custom Minecraft set, and five start=end trajectories over 100 RealEstate10K scenes. These are paper_result numbers on simulator poses; the paper's own tables disagree with each other and with the repository's expected-results block on some cells. · locator: arXiv 2504.12369v3 PDF (pdftotext and -layout): Sec. 3.3-3.4, 4.1, Tables 1-3 (layout lines 402-416), Tables 7-8 (lines 909-921), Supplementary 7.1-7.2; WorldMem README (equals producer pin) 'Expected Results' lines 133-141; LICENSE.md S-Lab License 1.0; HF API zeqixiao/worldmem_checkpoints source
Rights
| component | license | hosting | redistribution | modification | training | Evidence and notes |
|---|---|---|---|---|---|---|
| documentation | unknown | permitted | permitted | unknown | unknown | Applies to this original summary only, not to the cited sources. |