Home › Code › CORR

CORR

Syntologyentry name in harvested code

Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record.

CORR appears in the code Syntology harvested for 19 papers, as 4 distinct code bodies found in 20 places (a place is one code body under one paper). Of the 19 papers, 16 with a sample that ran: 16 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument. 3 of the code bodies carry a behaviour fingerprint.

What this page is not. Routines are grouped here by the exact string of their function or class name. Nothing asserts that two samples named CORR do the same thing, share code, or are comparable; the name is a string, not an identity. Behaviour outputs (what a fingerprinted sample returned on the shared battery) are not in this export and are not shown here; get_code(code_sha256="…") returns this sample's fingerprint on the shared battery, with the battery's shuffled null and lift; not shown on this site (how to connect). "Ran" means executed on a synthesized fixture, not that the code is correct or reproduces a paper.

Samples Syntology

The 4 distinct code bodies named CORR: 3 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 1 honoured, 2 violated, 0 with no contract checked; 0 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. One tile per status, in the site's fixed vocabulary, each code body counted once:

1ran · honoured contract
2ran · violated contract
0ran · our draft was wrong
0ran; the contract check could not run
0ran
1unverified
3fingerprinted

Licence is a property of each copy, so it is counted per place: 8 of the 20 places are pointer only (Syntology does not serve that copy's text); at 2 of those this paper's copy is under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text (hover the licence cell for why). This site shows no code text for any sample; every row below links to the file in its repository where the record names one.

“Ran” means the sample executed on a synthesized input; it does not mean the output is correct. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “the contract check could not run” (RAISES, DEP_MISSING or TIMEOUT; hover a row's label for which) are failures of Syntology's instrument, not of the code, and those samples did run. The ran count above is every status except unverified, the same rule as each paper page; “with no instrument failure” is honoured, violated and ran with no contract checked. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Papers

19 papers shown of 19, newest first; 20 places in the table. A paper with no recorded date is placed by the month its arXiv id encodes, shown in the Date column as YYYY-MM (from id). One row per place: a paper whose repository defines the name more than once appears more than once, and the same code body held for several papers appears once under each, with the same status. Titles and dates are the archive's archive 2025-07-28 for papers in the archive, and the graph's for 1 papers added by Syntology; 1 papers have no page here and are shown by their id only (arXiv: for an arXiv id; an id from another venue, such as ACL Anthology or AAAI, is named as that venue's id, never as an arXiv id). Status and fingerprint are Syntology's record of each code body; licence is recorded for each place. The File cell ends with the code body's 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.

PaperDateFileStatus SyntologyLicence
Extreme Adaptive Transformer for Time Series Forecasting EXTREME ADAPTIVE TRANSFORMER FOR TIME SERIES FORECASTING added by Syntology 2026-07 (from id) sanzexstha/Exformer/utils/metrics.py e6663d05846f08ea ran · violated contract fingerprinted Apache-2.0 (permissive)
Extreme Adaptive Transformer for Time Series Forecasting EXTREME ADAPTIVE TRANSFORMER FOR TIME SERIES FORECASTING added by Syntology 2026-07 (from id) sanzexstha/Exformer/utils/metrics_dan.py 03d63d172032b256 ran · violated contract fingerprinted Apache-2.0 (permissive)
TimeKAN: KAN-based Frequency Decomposition Learning Architecture for Long-term Time Series Forecasting 10 Feb 2025 huangst21/timekan/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted Apache-2.0 (permissive)
FilterNet: Harnessing Frequency Filters for Time Series Forecasting 3 Nov 2024 wanghq21/MICN/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted no licence file found · pointer only
Ada-MSHyper: Adaptive Multi-Scale Hypergraph Transformer for Time Series Forecasting 31 Oct 2024 shangzongjiang/Ada-MSHyper/utils/metrics.py 8c76ef42a9443f81 unverified no licence file found · pointer only
TimeBridge: Non-Stationarity Matters for Long-term Time Series Forecasting 6 Oct 2024 hank0626/timebridge/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted MIT (permissive)
Are Self-Attentions Effective for Time Series Forecasting? 27 May 2024 dongbeank/CATS/utils/metrics.py 8c76ef42a9443f81 unverified MIT (permissive) here; the stored copy is pointer only
GinAR: An End-To-End Multivariate Time Series Forecasting Model Suitable for Variable Missing 18 May 2024 chengqingyu/ginar/metric/main_metric.py fc47588462c311f2 ran · honoured contract fingerprinted no licence file found · pointer only
TimeMachine: A Time Series is Worth 4 Mambas for Long-term Forecasting 14 Mar 2024 atik-ahamed/timemachine/TimeMachine_supervised/utils/metrics.py 8c76ef42a9443f81 unverified Apache-2.0 (permissive) here; the stored copy is pointer only
Revitalizing Multivariate Time Series Forecasting: Learnable Decomposition with Inter-Series Dependencies and Intra-Series Variations Modeling 20 Feb 2024 Levi-Ackman/Leddam/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted no licence file found · pointer only
STanHop: Sparse Tandem Hopfield Model for Memory-Enhanced Time Series Prediction 28 Dec 2023 magics-lab/stanhop/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted MIT (permissive)
BasisFormer: Attention-based Time Series Forecasting with Learnable and Interpretable Basis 31 Oct 2023 nzl5116190/Basisformer/evaluate_tool.py 03d63d172032b256 ran · violated contract fingerprinted no licence file found · pointer only
UniTime: A Language-Empowered Unified Model for Cross-Domain Time Series Forecasting 15 Oct 2023 liuxu77/unitime/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted Apache-2.0 (permissive)
Multi-scale Transformer Pyramid Networks for Multivariate Time Series Forecasting 23 Aug 2023 GRYGY1215/MTPNet/utils/metrics.py e6663d05846f08ea ran · violated contract fingerprinted Apache-2.0 (permissive)
TEST: Text Prototype Aligned Embedding to Activate LLM's Ability for Time Series 16 Aug 2023 scxsunchenxi/test/losses/metrics.py 03d63d172032b256 ran · violated contract fingerprinted no licence file found · pointer only
Koopa: Learning Non-stationary Time Series Dynamics with Koopman Predictors 30 May 2023 thuml/Koopa/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted MIT (permissive)
Respecting Time Series Properties Makes Deep Time Series Forecasting Perfect 22 Jul 2022 origamisl/rtnet/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted Apache-2.0 (permissive)
TiSAT: Time Series Anomaly Transformer 10 Mar 2022 kevaldoshi17/TiSAT/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted MIT (permissive)
ETSformer: Exponential Smoothing Transformers for Time-series Forecasting 3 Feb 2022 salesforce/etsformer/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted BSD-3-Clause (permissive)
IJCAI id ijcai2025_0747 ChujieXu/CDPNet/utils/metrics.py 03d63d172032b256 ran · violated contract fingerprinted MIT (permissive)

This site shows no code text; each File cell links to the file on GitHub at the repository's current default branch, which may have changed since the 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 under a permissive licence, but the stored copy of the same code that Syntology serves is not cleared for its text. 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 cell for the reason. Per-sample records for a paper are on its paper page under "Code Syntology ran".

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