Papers › Reconstructing dynamics from sparse observations with no training on target system

Reconstructing dynamics from sparse observations with no training on target system

28 Oct 2024arXiv:2410.21222archive 2025-07-28

Zheng-Meng Zhai, Jun-Yin Huang, Benjamin D. Stern, Ying-Cheng Lai

In applications, an anticipated situation is where the system of interest has never been encountered before and sparse observations can be made only once. Can the dynamics be faithfully reconstructed from the limited observations without any training data? This problem defies any known traditional methods of nonlinear time-series analysis as well as existing machine-learning methods that typically require extensive data from the target system for training. We address this challenge by developing a hybrid transformer and reservoir-computing machine-learning scheme. The key idea is that, for a complex and nonlinear target system, the training of the transformer can be conducted not using any data from the target system, but with essentially unlimited synthetic data from known chaotic systems. The trained transformer is then tested with the sparse data from the target system. The output of the transformer is further fed into a reservoir computer for predicting the long-term dynamics or the attractor of the target system. The power of the proposed hybrid machine-learning framework is demonstrated using a large number of prototypical nonlinear dynamical systems, with high reconstruction accuracy even when the available data is only 20% of that required to faithfully represent the dynamical behavior of the underlying system. The framework provides a paradigm of reconstructing complex and nonlinear dynamics in the extreme situation where training data does not exist and the observations are random and sparse.

PaperPDFCodeCode Syntology ran

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 9 code samples harvested from 1 repository linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 1 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 9 samples from 1 repository, 9 ran (6 with no instrument failure; 3 where Syntology's instrument failed). 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 on 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

Zheng-Meng/Dynamics-Reconstruction-ML officialmentioned on GitHubpytorchMITSyntology: 9 samples, 9 ran (3 instrument-failed) · 0 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

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 1 violated, 5 with no contract checked; 3 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · violated contract
2ran · our draft was wrong
1ran; the contract check could not run
5ran

Licence: 0 of the 9 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 Zheng-Meng/Dynamics-Reconstruction-ML. “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”. “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.

Zheng-Meng/Dynamics-Reconstruction-ML official repository 9 samples, 9 ran (3 instrument-failed) · 0 unverified
calculate_success_rate response/chaos_transformer_read_and_test_data_revision.py ran · violated contract fingerprinted MIT (permissive) · 7d0306a3f2eab718 · report fixture: signature loss_ml_in:ndarray/1/float, loss_threshold:float/0/float · returned float64 · level recorded 2026-09-26
combined_loss_function transformer_encoder.py ran MIT (permissive) · 3bbac76d75336a41 · report fixture: signature outputs:Tensor/2/float, targets:Tensor/2/float, smoothness_loss_fn:callable/0/?, mse_weight:float/0/float, smoothness_weight:float/0/float · returned Tensor · level recorded 2026-09-26
func_foodchain chaotic_systems.py ran MIT (permissive) · 9c704e9f2ce5900e · report fixture: signature x:ndarray/1/float, t:float/0/float, params:ndarray/1/float · returned ndarray · level recorded 2026-09-26
func_lorenz chaotic_systems.py ran MIT (permissive) · 2e0f972dd943252d · report fixture: signature x:ndarray/1/float, t:float/0/float, params:ndarray/1/float · returned ndarray · level recorded 2026-09-26
func_rossler chaotic_systems.py ran MIT (permissive) · 3a38282f95f88c56 · report fixture: signature x:ndarray/1/float, t:float/0/float, params:ndarray/1/float · returned ndarray · level recorded 2026-09-26
interpolate_sequence response/chaos_transformer_read_and_test_interpolation.py ran; the contract check could not run (RAISES) MIT (permissive) · 6a3610447f84830c · report fixture: signature masked_seq:ndarray/3/float, method:str/0/str · returned ndarray · level recorded 2026-09-26
mask_data_transformer utils.py ran MIT (permissive) · 43bab82dae4edf53 · report fixture: signature x:ndarray/2/float, mask_ratio:float/0/float, mask_as:int/0/int · returned tuple · level recorded 2026-09-26
read_and_normalize_chaos utils.py ran · our draft was wrong MIT (permissive) · 4b65c1e65e800d4c · report fixture: signature file_path:str/0/str, data_read_length:int/0/int · returned tuple · level recorded 2026-09-26
read_and_preprocess_directory_chaos utils.py ran · our draft was wrong MIT (permissive) · 53469f74ef05781e · report fixture: signature directory_path:str/0/str, data_read_length:int/0/int · returned tuple · level recorded 2026-09-26

Tasks

Hybrid Machine LearningTime Series Analysis

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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