Papers › Multi Time Scale World Models

Multi Time Scale World Models

27 Oct 2023NeurIPS 2023 11arXiv:2310.18534archive 2025-07-28

Vaisakh Shaj, Saleh Gholam Zadeh, Ozan Demir, Luiz Ricardo Douat, Gerhard Neumann

Intelligent agents use internal world models to reason and make predictions about different courses of their actions at many scales. Devising learning paradigms and architectures that allow machines to learn world models that operate at multiple levels of temporal abstractions while dealing with complex uncertainty predictions is a major technical hurdle. In this work, we propose a probabilistic formalism to learn multi-time scale world models which we call the Multi Time Scale State Space (MTS3) model. Our model uses a computationally efficient inference scheme on multiple time scales for highly accurate long-horizon predictions and uncertainty estimates over several seconds into the future. Our experiments, which focus on action conditional long horizon future predictions, show that MTS3 outperforms recent methods on several system identification benchmarks including complex simulated and real-world dynamical systems. Code is available at this repository: https://github.com/ALRhub/MTS3.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 14 code samples: 13 from 1 repository linked to this paper, 1 identical to code harvested from another paper's repository. Across all 14: 12 ran (of which 5 constructed an object rather than computing a result; 10 with no instrument failure: 2 honoured, 0 violated, 8 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 13 samples from 1 repository, 11 ran (9 with no instrument failure; 2 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

alrhub/mts3 officialmentioned in papermentioned on GitHubpytorchSyntology: 13 samples, 11 ran (2 instrument-failed) · 2 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

14 samples harvested: 12 ran (of which 5 constructed an object rather than computing a result; 10 with no instrument failure: 2 honoured, 0 violated, 8 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · honoured contract
2ran; the contract check could not run
8ran
2unverified

Licence: 14 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from alrhub/mts3. 1 sample is listed last, in a group without a repository. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. For 2 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

alrhub/mts3 official repository 13 samples, 11 ran (2 instrument-failed) · 2 unverified
Control agent/worldModels/MTS3.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · a6c02ae873ff7281 · report fixture: returned Control · level recorded 2026-09-22
Encoder in 278 papers agent/worldModels/MTS3.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 7d3e190be7631dfb · report fixture: returned Encoder · level recorded 2026-09-22
ProcessNoise agent/worldModels/MTS3.py ran · metamorphic tier: deterministic no licence file found · pointer only · 3fb8f2094388f956 · report fixture: returned ProcessNoise · level recorded 2026-09-22
SplitDiagGaussianDecoder agent/worldModels/MTS3.py ran · metamorphic tier: deterministic no licence file found · pointer only · afac0da42e97ad06 · report fixture: returned SplitDiagGaussianDecoder · level recorded 2026-09-22
Update agent/worldModels/MTS3.py ran · metamorphic tier: deterministic no licence file found · pointer only · 03733ecb5029b01e · report fixture: returned Update · level recorded 2026-09-22
cov_linear_transform agent/worldModels/MTS3.py ran; the contract check could not run (RAISES) · metamorphic tier: well formed no licence file found · pointer only · df530ba8e40002bc · report fixture: signature tm:list/1/Tensor, covar:list/1/Tensor, mem:bool/0/bool · returned list · level recorded 2026-09-22
elup1 agent/worldModels/MTS3.py ran · honoured contract fingerprinted no licence file found · pointer only · 6137076d036ffe8f · report fixture: signature x:Tensor/2/float · returned Tensor · level recorded 2026-09-22
gaussian_linear_transform agent/worldModels/MTS3.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic no licence file found · pointer only · f7be596b58d2637e · report fixture: signature tm:list/1/Tensor, mean:Tensor/2/float, covar:list/1/Tensor, mem:bool/0/bool · returned tuple · level recorded 2026-09-22
gaussian_nll in 8 papers utils/Losses.py ran fingerprinted no licence file found · pointer only · 67dea81cea22a2b4 · report fixture: signature target:Tensor/2/float, predicted_mean:Tensor/2/float, predicted_var:Tensor/2/float · returned Tensor · level recorded 2026-09-24
mse in 78 papers
census: 5 implementations from 6 papers, 4 distinct outputs across 3 buckets, one shared input per bucket
utils/Losses.py ran fingerprinted no licence file found · pointer only · 278f1cd19d7744ca · report fixture: signature target:Tensor/2/float, predicted:Tensor/2/float · returned Tensor · level recorded 2026-09-24
rmse in 44 papers utils/Losses.py ran fingerprinted no licence file found · pointer only · a2da722a97faba18 · report fixture: signature target:Tensor/2/float, predicted:Tensor/2/float · returned Tensor · level recorded 2026-09-24
MTS3 agent/worldModels/MTS3.py unverified no licence file found · pointer only · cca68898f6f9c63c · report
Predict agent/worldModels/MTS3.py unverified no licence file found · pointer only · 947ea097bca462e0 · report
Repository not located 1 sample, 1 ran (0 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
elup1_inv repository not located ran · honoured contract licence of this copy not recorded · ed3fa67aaa04d2e4 · report fixture: signature x:Tensor/0/float · returned Tensor · level recorded 2026-09-22

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Multi Time Scale State Space (MTS3) model (graph method: Multi Time Scale State Space (MTS3) model). 11 bricks; individually on a fixture: 9 ran (of which 5 constructed an object rather than computing a result; 7 with no instrument failure: 2 honoured, 0 violated, 5 with no contract checked; 2 where Syntology's instrument failed) · 2 unverified. The assembly has not been run end-to-end.

  1. MTS3 entry · level 0 · unverified · cca68898f6f9c63c
  2. Encoder helper · level 1 · ran · 7d3e190be7631dfb
  3. Predict helper · level 0 · unverified · 947ea097bca462e0
  4. SplitDiagGaussianDecoder helper · level 1 · ran · afac0da42e97ad06
  5. Update helper · level 1 · ran · 03733ecb5029b01e
  6. elup1 helper · level 1 · ran · honoured contract · 6137076d036ffe8f
  7. Control helper · level 1 · ran · a6c02ae873ff7281
  8. ProcessNoise helper · level 1 · ran · 3fb8f2094388f956
  9. gaussian_linear_transform helper · level 1 · ran; the contract check could not run (RAISES) · f7be596b58d2637e
  10. elup1_inv helper · level 1 · ran · honoured contract · ed3fa67aaa04d2e4
  11. cov_linear_transform helper · level 1 · ran; the contract check could not run (RAISES) · df530ba8e40002bc

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2310.18534") returns these assemblies with each brick's role and wiring (how to connect).

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Focus

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections