4 of 8 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 1 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 2 failures of our instrument; 4 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.
"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/2310.09751.json · badge: /api/ran/2310.09751.svg
Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.
| Repository | Role | Ran |
|---|---|---|
| liuxu77/unitime | canonical (classifier label) classifier basis not recorded on the link |
4 ran · 4 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| CORR | Ran ran, violated the contract we drafted |
liuxu77/unitime/utils/metrics.py code served (permissive licence) · get_code("03d63d172032b256") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned float32, ndim 0, dtype family float, shape () as a later run recorded it. The image it ran in was not recorded. If your copy returns the same type, ndim and shape on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| adjustment | Ran ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT) |
liuxu77/unitime/utils/tools.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from decisionintelligence/CATCH, is pointer only (licence: NONE) · get_code("6f19aadea4af692b") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from decisionintelligence/CATCH, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| cal_accuracy | Ran ran, honoured the contract we drafted |
liuxu77/unitime/utils/tools.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from decisionintelligence/CATCH, is pointer only (licence: NONE) · get_code("1a1c47411dbeec1f") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from decisionintelligence/CATCH, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded. |
| get_logger | Ran ran; our contract draft was wrong, not the code |
liuxu77/unitime/utils/logger.py code served (permissive licence) · get_code("f651f9272fd5a62a") How it ranRan in Syntology's sandbox on this synthesized input (drafted by a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API) and returned Logger. The image it ran in was not recorded. If your copy returns the same type on these inputs, it matched what we observed; nothing here checks that. It does NOT mean the output is correct: nothing has compared it to the paper.
|
| MAE | Not yet run unverified (harvested, no recorded run) |
liuxu77/unitime/utils/metrics.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from shangzongjiang/Ada-MSHyper, is pointer only (licence: NONE) · get_code("75f44993b096bf76") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from shangzongjiang/Ada-MSHyper, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded. |
| RSE | Not yet run unverified (harvested, no recorded run) |
liuxu77/unitime/utils/metrics.py pointer only (licence: Apache-2.0); the stored copy get_code serves, from shangzongjiang/Ada-MSHyper, is pointer only (licence: NONE) · get_code("b40a11875ebd0cd2") How it ranThe body of this sample is withheld: this paper's link allows the body inline (Apache-2.0), but get_code serves the stored copy, first harvested from shangzongjiang/Ada-MSHyper, and GitHub detected no licence in that repository when it was checked. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. No invocation recorded. |
| time_features | Not yet run unverified (harvested, no recorded run) |
liuxu77/unitime/utils/timefeatures.py code served (permissive licence) · get_code("9a5fcd4ebfc55d03") How it ranno invocation recorded. |
| time_features_from_frequency_str | Not yet run unverified (harvested, no recorded run) |
liuxu77/unitime/utils/timefeatures.py code served (permissive licence) · get_code("f8544563682146e5") How it ranno invocation recorded. this sample carries JSON test cases instead of a setup block; get_reference_implementation serves them with the level they back. |
Of 8 samples lifted from this paper's linked repositories, 8 carry a function identity and 0 do not. Of the 8 distinct functions with an identity, 8 are also present in other papers whose code we hold (7 with at least one paper dated earlier, 5 the same month, 8 later) and 0 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).
Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.
| Function | Also present in | Earliest-dated | Others named |
|---|---|---|---|
| time_features_from_frequency_str | 19 other papers 6 dated earlier, 2 the same month, 11 later |
2203.05167 (2022-03) TiSAT: Time Series Anomaly Transformer |
2208.04933 (2022-08) Simplified State Space Layers for Sequence Modeling 2305.10721 (2023-05) Revisiting Long-term Time Series Forecasting: An Investigation on Linear Mapping and 16 more not named here |
| RSE | 18 other papers 6 dated earlier, 1 the same month, 11 later |
2202.01381 (2022-02) ETSformer: Exponential Smoothing Transformers for Time-series Forecasting |
2203.05167 (2022-03) TiSAT: Time Series Anomaly Transformer 2207.10941 (2022-07) Respecting Time Series Properties Makes Deep Time Series Forecasting Perfect and 15 more not named here |
| MAE | 17 other papers 5 dated earlier, 1 the same month, 11 later |
2202.01381 (2022-02) ETSformer: Exponential Smoothing Transformers for Time-series Forecasting |
2203.05167 (2022-03) TiSAT: Time Series Anomaly Transformer 2207.10941 (2022-07) Respecting Time Series Properties Makes Deep Time Series Forecasting Perfect and 14 more not named here |
| CORR | 13 other papers 5 dated earlier, 1 the same month, 7 later |
2202.01381 (2022-02) ETSformer: Exponential Smoothing Transformers for Time-series Forecasting |
2203.05167 (2022-03) TiSAT: Time Series Anomaly Transformer 2207.10941 (2022-07) Respecting Time Series Properties Makes Deep Time Series Forecasting Perfect and 10 more not named here |
| time_features | 12 other papers 3 dated earlier, 1 the same month, 8 later |
2305.10721 (2023-05) Revisiting Long-term Time Series Forecasting: An Investigation on Linear Mapping |
2305.18803 (2023-05) Koopa: Learning Non-stationary Time Series Dynamics with Koopman Predictors 2308.08469 (2023-08) LLM4TS: Aligning Pre-Trained LLMs as Data-Efficient Time-Series Forecasters and 9 more not named here |
| adjustment | 4 other papers 1 dated earlier, 3 later |
2308.08469 (2023-08) LLM4TS: Aligning Pre-Trained LLMs as Data-Efficient Time-Series Forecasters |
2402.12694 (2024-02) Revitalizing Multivariate Time Series Forecasting: Learnable Decomposition with Inter-Series Dependencies and Intra-Series Variations Modeling 2411.01623 (2024-11) FilterNet: Harnessing Frequency Filters for Time Series Forecasting and 1 more not named here |
| cal_accuracy | 4 other papers 1 dated earlier, 3 later |
2308.08469 (2023-08) LLM4TS: Aligning Pre-Trained LLMs as Data-Efficient Time-Series Forecasters |
2402.12694 (2024-02) Revitalizing Multivariate Time Series Forecasting: Learnable Decomposition with Inter-Series Dependencies and Intra-Series Variations Modeling 2411.01623 (2024-11) FilterNet: Harnessing Frequency Filters for Time Series Forecasting and 1 more not named here |
| get_logger | 2 other papers 2 later |
2410.00373 (2024-10) Robust Traffic Forecasting against Spatial Shift over Years |
2410.10524 (2024-10) Get Rid of Isolation: A Continuous Multi-task Spatio-Temporal Learning Framework |
Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Multivariate time series forecasting plays a pivotal role in contemporary web technologies. In contrast to conventional methods that involve creating dedicated models for specific time series application domains, this research advocates for a unified model paradigm that transcends domain boundaries. However, learning an effective cross-domain model presents the following challenges. First, various domains exhibit disparities in data characteristics, e.g., the number of variables, posing hurdles for existing models that impose inflexible constraints on these factors. Second, the model may encounter difficulties in distinguishing data from various domains, leading to suboptimal performance in our assessments. Third, the diverse convergence rates of time series domains can also result in compromised empirical performance. To address these issues, we propose UniTime for effective cross-domain time series learning. Concretely, UniTime can flexibly adapt to data with varying characteristics. It also uses domain instructions and a Language-TS Transformer to offer identification information and align two modalities. In addition, UniTime employs masking to alleviate domain convergence speed imbalance issues. Our extensive experiments demonstrate the effectiveness of UniTime in advancing state-of-the-art forecasting performance and zero-shot transferability.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2310.09751")
get_code_for_paper("2310.09751")
have("2310.09751")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2310.09751.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2310.09751)
Connect an agent — have() is free.