SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2402.02399 · ICLR · 2025

FreDF: Learning to Forecast in the Frequency Domain

Dacheng Tao, Yuan Shen, Hao Wang, Haoxuan Li, Sen Zhang, Zhichao Chen, Licheng Pan, Degui Yang, Yifei Yang, Xinggao Liu

arXiv · PDF · Open in the Atlas

Code that ran

7 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, 0 violated it and 0 have no contract verdict; 6 failures of our instrument; 1 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/2402.02399.json · badge: /api/ran/2402.02399.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
Master-PLC/FreDF canonical (classifier label)
classifier basis not recorded on the link
7 ran · 0 no recorded run
master-plc/fredf community
Papers with Code archive
0 ran · 1 no recorded run
FunctionStatusWhere it lives
conv1d_fft Ran
ran; our contract draft was wrong, not the code
Master-PLC/FreDF/layers/ETSformer_EncDec.py
code served (permissive licence) · get_code("2af0df7394e58e06")
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 (2, 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 torch.fft as fft
from scipy.fftpack import next_fast_len

torch.manual_seed(0)

# Create small tensors for convolution
# f: signal tensor, shape (2, 4) - batch size 2, length 4
f = torch.randn(2, 4)

# g: kernel/filter tensor, shape (2, 3) - batch size 2, length 3
g = torch.randn(2, 3)

# dim: dimension along which to perform FFT-based convolution
dim = -1

ARGS = {
    "f": f,
    "g": g,
    "dim": dim,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
scipy, 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 (2, 4) — shape (2, 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_frequency_modes Ran
ran, honoured the contract we drafted
Master-PLC/FreDF/layers/FourierCorrelation.py
code served (permissive licence) · get_code("592ea8b254b006db")
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 list, ndim 1, dtype family int; no output shape is stated. The image it ran in was not recorded. If your copy returns the same type and ndim 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 numpy as np

np.random.seed(0)

ARGS = {
    'seq_len': 128,
    'modes': 64,
    'mode_select_method': 'random'
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type list, ndim 1, dtype family int — a list output has no array shape of its own; none is stated
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_mask Ran
ran; our contract draft was wrong, not the code
Master-PLC/FreDF/layers/Pyraformer_EncDec.py
pointer only (licence: MIT); the stored copy get_code serves, from leejaehoon2016/FinTexTS, is pointer only (licence: NONE) · get_code("fd61ceb881a058a2")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from leejaehoon2016/FinTexTS, 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_phi_psi Ran
ran; our contract draft was wrong, not the code
Master-PLC/FreDF/layers/MultiWaveletCorrelation.py
code served (permissive licence) · get_code("f32036738135c8a8")
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 tuple. 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.

import numpy as np
from functools import partial

# Construct valid arguments for get_phi_psi
ARGS = {
    'k': 3,
    'base': 'legendre'
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, sympy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type tuple — a tuple output has no array shape of its own; none is stated
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
legendreDer Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
Master-PLC/FreDF/layers/MultiWaveletCorrelation.py
code served (permissive licence) · get_code("4ef26472da51e3aa")
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 ndarray, ndim 1, dtype family float, shape (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 numpy as np
from scipy.special import eval_legendre

# The function legendreDer takes two parameters:
# k: an integer representing the order
# x: a value or array on which to evaluate the Legendre polynomials

# Looking at the function:
# - k is used in range(k-1, -1, -2) so it should be an integer
# - x is passed to eval_legendre which accepts scalars or arrays
# - The function iterates through odd/even indices based on k

# Create small test values
k = 5  # integer order
x = np.array([0.0, 0.5, -0.5, 1.0])  # small array of evaluation points

ARGS = {
    "k": k,
    "x": x
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy, scipy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 1, dtype family float, shape (4,) — shape (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
phi_ Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
Master-PLC/FreDF/layers/MultiWaveletCorrelation.py
code served (permissive licence) · get_code("a54c8c5c47c6a8b8")
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 ndarray, ndim 1, dtype family float, shape (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 numpy as np

# phi_ takes phi_c (polynomial coefficients), x (input array), and bounds lb, ub
# It creates a Polynomial from phi_c, evaluates it at x, and masks values outside [lb, ub]

# Create polynomial coefficients (small array)
phi_c = np.array([1.0, 2.0, 0.5])

# Create input array with values in and out of bounds
x = np.array([0.2, 0.5, 0.8, 1.5])

# Define bounds
lb = 0.0
ub = 1.0

ARGS = {
    "phi_c": phi_c,
    "x": x,
    "lb": lb,
    "ub": ub,
}
Setup block drafted by
a language model, Claude Haiku 4.5, prompt python_fixture_v1, through the batch API
Imports
numpy — import names as written, not package names to install; a name the repository itself provides is not a package
Returned
type ndarray, ndim 1, dtype family float, shape (4,) — shape (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
refer_points Ran
ran; our contract draft was wrong, not the code
Master-PLC/FreDF/layers/Pyraformer_EncDec.py
pointer only (licence: MIT); the stored copy get_code serves, from leejaehoon2016/FinTexTS, is pointer only (licence: NONE) · get_code("05bdfb126191dbb0")
How it ran

The body of this sample is withheld: this paper's link allows the body inline (MIT), but get_code serves the stored copy, first harvested from leejaehoon2016/FinTexTS, 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.

FourierCrossAttention Not yet run
unverified (harvested, no recorded run)
master-plc/fredf/layers/FourierCorrelation.py
code served (permissive licence) · get_code("02b79096bcca291a")
How it ran

no invocation recorded.

Also present in other papers' code

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, 7 are also present in other papers whose code we hold (7 with at least one paper dated earlier, 7 the same month, 7 later) and 1 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
get_frequency_modes
brick of this paper's assembly: helper
27 other papers
6 dated earlier, 2 the same month, 19 later · 1 only as an assembly brick
2201.12740 (2022-01)
FEDformer: Frequency Enhanced Decomposed Transformer for Long-term Series Forecasting
2304.09184 (2023-04)
Frequency Enhanced Hybrid Attention Network for Sequential Recommendation
2305.13036 (2023-05)
Disentangling Structured Components: Towards Adaptive, Interpretable and Scalable Time Series Forecasting
and 24 more not named here
phi_ 24 other papers
7 dated earlier, 2 the same month, 15 later · 1 only as an assembly brick
2201.12740 (2022-01)
FEDformer: Frequency Enhanced Decomposed Transformer for Long-term Series Forecasting
2205.08897 (2022-05)
FiLM: Frequency improved Legendre Memory Model for Long-term Time Series Forecasting
2304.05206 (2023-04)
The Capacity and Robustness Trade-off: Revisiting the Channel Independent Strategy for Multivariate Time Series Forecasting
and 21 more not named here
get_phi_psi 23 other papers
6 dated earlier, 2 the same month, 15 later · 1 only as an assembly brick
2201.12740 (2022-01)
FEDformer: Frequency Enhanced Decomposed Transformer for Long-term Series Forecasting
2205.08897 (2022-05)
FiLM: Frequency improved Legendre Memory Model for Long-term Time Series Forecasting
2305.13036 (2023-05)
Disentangling Structured Components: Towards Adaptive, Interpretable and Scalable Time Series Forecasting
and 20 more not named here
legendreDer 23 other papers
6 dated earlier, 2 the same month, 15 later · 1 only as an assembly brick
2201.12740 (2022-01)
FEDformer: Frequency Enhanced Decomposed Transformer for Long-term Series Forecasting
2205.08897 (2022-05)
FiLM: Frequency improved Legendre Memory Model for Long-term Time Series Forecasting
2305.13036 (2023-05)
Disentangling Structured Components: Towards Adaptive, Interpretable and Scalable Time Series Forecasting
and 20 more not named here
conv1d_fft 18 other papers
3 dated earlier, 2 the same month, 13 later
2202.01381 (2022-02)
ETSformer: Exponential Smoothing Transformers for Time-series Forecasting
2305.13036 (2023-05)
Disentangling Structured Components: Towards Adaptive, Interpretable and Scalable Time Series Forecasting
2307.01616 (2023-07)
SageFormer: Series-Aware Framework for Long-term Multivariate Time Series Forecasting
and 15 more not named here
get_mask 13 other papers
2 dated earlier, 2 the same month, 9 later
2305.13036 (2023-05)
Disentangling Structured Components: Towards Adaptive, Interpretable and Scalable Time Series Forecasting
2307.01616 (2023-07)
SageFormer: Series-Aware Framework for Long-term Multivariate Time Series Forecasting
2402.16516 (2024-02)
Generative Pretrained Hierarchical Transformer for Time Series Forecasting
and 10 more not named here
refer_points 13 other papers
2 dated earlier, 2 the same month, 9 later
2305.13036 (2023-05)
Disentangling Structured Components: Towards Adaptive, Interpretable and Scalable Time Series Forecasting
2307.01616 (2023-07)
SageFormer: Series-Aware Framework for Long-term Multivariate Time Series Forecasting
2402.16516 (2024-02)
Generative Pretrained Hierarchical Transformer for Time Series Forecasting
and 10 more not named here

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

Time series modeling presents unique challenges due to autocorrelation in both historical data and future sequences. While current research predominantly addresses autocorrelation within historical data, the correlations among future labels are often overlooked. Specifically, modern forecasting models primarily adhere to the Direct Forecast (DF) paradigm, generating multi-step forecasts independently and disregarding label autocorrelation over time. In this work, we demonstrate that the learning objective of DF is biased in the presence of label autocorrelation. To address this issue, we propose the Frequency-enhanced Direct Forecast (FreDF), which mitigates label autocorrelation by learning to forecast in the frequency domain, thereby reducing estimation bias. Our experiments show that FreDF significantly outperforms existing state-of-the-art methods and is compatible with a variety of forecast models. Code is available at https://github.com/Master-PLC/FreDF.

For agents

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

get_harvested_code_for_paper("2402.02399")
get_code_for_paper("2402.02399")
have("2402.02399")

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

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

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

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

Connect an agent — have() is free.