SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2506.23596 · ICML · 2025

When Will It Fail?: Anomaly to Prompt for Forecasting Future Anomalies in Time Series

Seong Kim, Min-Yeong Park, Won-Jeong Lee, Gyeong-Moon Park

arXiv · PDF · Open in the Atlas

Code that ran

2 of 4 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, 0 violated it and 0 have no contract verdict; 1 failure of our instrument; 2 no recorded run), measured 2026-11-22; 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/2506.23596.json · badge: /api/ran/2506.23596.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.

RepositoryRoleRan
KU-VGI/AP canonical (classifier label)
classifier basis: plan_row
2 ran · 2 no recorded run
FunctionStatusWhere it lives
PositionalEncoding Ran
ran, honoured the contract we drafted
KU-VGI/AP/layers/PatchTST_layers.py
code served (permissive licence) · get_code("16b9b78d429636b7")
How it ran

Ran 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 Tensor, ndim 2, dtype family float, shape (8, 4) 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.

import torch
import math

torch.manual_seed(0)

ARGS = {
    'q_len': 8,
    'd_model': 4,
    'normalize': True
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
torch — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type Tensor, ndim 2, dtype family float, shape (8, 4) — shape (8, 4) as a later run recorded it
dtype family
int means an integer dtype; float means any other dtype the instrument saw, bool and complex included (fixture_check.py records only these two families)
Environment
image not recorded; re-verify against syntology-harvest-sandbox:v5-deps; not recorded for this sample: the harness installs a cuda-to-cpu shim (cuda_shim.py) before every sample and no run records whether a sample needed it; seed: none by the harness; any seed is in the setup block
get_activation_fn Ran
ran; our contract draft was wrong, not the code
KU-VGI/AP/layers/PatchTST_layers.py
pointer only (licence: Apache-2.0); the stored copy get_code serves, from liubolab/CausalMoE, is pointer only (licence: NONE) · get_code("72b9272542f279c6")
How it ran

The 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 liubolab/CausalMoE, 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.

Coord2dPosEncoding Not yet run
unverified (harvested, no recorded run)
KU-VGI/AP/layers/PatchTST_layers.py
pointer only (licence: Apache-2.0); the stored copy get_code serves, from liubolab/CausalMoE, is pointer only (licence: NONE) · get_code("c3fc6992d1e467f3")
How it ran

The 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 liubolab/CausalMoE, 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.

my_kl_loss Not yet run
unverified (harvested, no recorded run)
KU-VGI/AP/shared_model.py
code served (permissive licence) · get_code("23bc77e564345795")
How it ran

no invocation recorded.

Also present in other papers' code

Of 4 samples lifted from this paper's linked repositories, 4 carry a function identity and 0 do not. Of the 4 distinct functions with an identity, 4 are also present in other papers whose code we hold (4 with at least one paper dated earlier, 0 the same month, 4 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.

FunctionAlso present inEarliest-datedOthers named
PositionalEncoding 16 other papers
9 dated earlier, 7 later
2308.04791 (2023-08)
PETformer: Long-term Time Series Forecasting via Placeholder-enhanced Transformer
2310.00655 (2023-10)
PatchMixer: A Patch-Mixing Architecture for Long-Term Time Series Forecasting
2310.06625 (2023-10)
iTransformer: Inverted Transformers Are Effective for Time Series Forecasting
and 13 more not named here
Coord2dPosEncoding 15 other papers
10 dated earlier, 5 later
2308.04791 (2023-08)
PETformer: Long-term Time Series Forecasting via Placeholder-enhanced Transformer
2310.00655 (2023-10)
PatchMixer: A Patch-Mixing Architecture for Long-Term Time Series Forecasting
2310.06625 (2023-10)
iTransformer: Inverted Transformers Are Effective for Time Series Forecasting
and 12 more not named here
get_activation_fn 15 other papers
11 dated earlier, 4 later
2308.04791 (2023-08)
PETformer: Long-term Time Series Forecasting via Placeholder-enhanced Transformer
2310.00655 (2023-10)
PatchMixer: A Patch-Mixing Architecture for Long-Term Time Series Forecasting
2310.06625 (2023-10)
iTransformer: Inverted Transformers Are Effective for Time Series Forecasting
and 12 more not named here
my_kl_loss 3 other papers
2 dated earlier, 1 later
2110.02642 (2021-10)
Anomaly Transformer: Time Series Anomaly Detection with Association Discrepancy
2312.11976 (2023-12)
When Model Meets New Normals: Test-time Adaptation for Unsupervised Time-series Anomaly Detection
2606.09874 (2026-06)
Disjoint or Overlapping? Inference Windowing for Reconstruction-Based Time Series Anomaly Detection

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.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

Recently, forecasting future abnormal events has emerged as an important scenario to tackle realworld necessities. However, the solution of predicting specific future time points when anomalies will occur, known as Anomaly Prediction (AP), remains under-explored. Existing methods dealing with time series data fail in AP, focusing only on immediate anomalies or failing to provide precise predictions for future anomalies. To address the AP task, we propose a novel framework called Anomaly to Prompt (A2P), comprised of Anomaly-Aware Forecasting (AAF) and Synthetic Anomaly Prompting (SAP). To enable the forecasting model to forecast abnormal time points, we adopt a strategy to learn the relationships of anomalies. For the robust detection of anomalies, our proposed SAP introduces a learnable Anomaly Prompt Pool (APP) that simulates diverse anomaly patterns using signaladaptive prompt. Comprehensive experiments on multiple real-world datasets demonstrate the superiority of A2P over state-of-the-art methods, showcasing its ability to predict future anomalies. Our implementation code is available at https://github.com/KU-VGI/AP.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("2506.23596")
get_code_for_paper("2506.23596")
have("2506.23596")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/2506.23596.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/2506.23596.svg)](https://syntology.ai/paper/2506.23596)

Connect an agent — have() is free.