Papers › FilterNet: Harnessing Frequency Filters for Time Series Forecasting

FilterNet: Harnessing Frequency Filters for Time Series Forecasting

3 Nov 2024arXiv:2411.01623archive 2025-07-28

Kun Yi, Jingru Fei, Qi Zhang, Hui He, Shufeng Hao, Defu Lian, Wei Fan

While numerous forecasters have been proposed using different network architectures, the Transformer-based models have state-of-the-art performance in time series forecasting. However, forecasters based on Transformers are still suffering from vulnerability to high-frequency signals, efficiency in computation, and bottleneck in full-spectrum utilization, which essentially are the cornerstones for accurately predicting time series with thousands of points. In this paper, we explore a novel perspective of enlightening signal processing for deep time series forecasting. Inspired by the filtering process, we introduce one simple yet effective network, namely FilterNet, built upon our proposed learnable frequency filters to extract key informative temporal patterns by selectively passing or attenuating certain components of time series signals. Concretely, we propose two kinds of learnable filters in the FilterNet: (i) Plain shaping filter, that adopts a universal frequency kernel for signal filtering and temporal modeling; (ii) Contextual shaping filter, that utilizes filtered frequencies examined in terms of its compatibility with input signals for dependency learning. Equipped with the two filters, FilterNet can approximately surrogate the linear and attention mappings widely adopted in time series literature, while enjoying superb abilities in handling high-frequency noises and utilizing the whole frequency spectrum that is beneficial for forecasting. Finally, we conduct extensive experiments on eight time series forecasting benchmarks, and experimental results have demonstrated our superior performance in terms of both effectiveness and efficiency compared with state-of-the-art methods. Code is available at this repository: https://github.com/aikunyi/FilterNet

PaperPDFCodeCode Syntology ranMethod as code

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

By repository: official repository: 2 samples from 1 repository, 2 ran (2 with no instrument failure; 0 where Syntology's instrument failed); found in paper text by Syntology: 18 samples from 3 repositories, 12 ran (10 with no instrument failure; 2 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.

No sample is linked to this paper from 2 of its repositories that Syntology harvested for other papers:

Levels written between 2026-09-22 and 2026-09-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 2 of the 14 samples that ran have no recorded date.

aikunyi/filternet officialmentioned in papermentioned on GitHubpytorchSyntology: 2 samples, 2 ran (0 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

20 samples harvested: 14 ran (of which 1 constructed an object rather than computing a result; 12 with no instrument failure: 5 honoured, 1 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 6 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.

5ran · honoured contract
1ran · violated contract
2ran · our draft was wrong
6ran
6unverified

Licence: 5 of the 20 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 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

aikunyi/filternet official repository 2 samples, 2 ran (0 instrument-failed) · 0 unverified
cal_accuracy in 15 papers utils/tools.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 3c40a10623118d49 · report fixture: signature y_pred:ndarray/1/int, y_true:ndarray/1/int · returned float64 · level recorded, date not recorded
adjustment in 5 papers utils/tools.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · a8ddfb9279c3224c · report fixture: signature gt:ndarray/1/int, pred:ndarray/1/int · returned tuple · level recorded, date not recorded
aikunyi/FreTS found in paper text by Syntology 1 sample, 1 ran (0 instrument-failed) · 0 unverified
Model in 227 papers models/FreTS.py ran Apache-2.0 (permissive) · d320822331f5ef05 · report fixture: returned Model · level recorded 2026-09-22
wanghq21/MICN found in paper text by Syntology 5 samples, 1 ran (0 instrument-failed) · 4 unverified
CORR in 19 papers utils/metrics.py ran · violated contract fingerprinted no licence file found · pointer only · 03d63d172032b256 · report fixture: signature pred:ndarray/2/float, true:ndarray/2/float · returned float32 · level recorded 2026-09-24
MAE in 46 papers utils/metrics.py unverified no licence file found · pointer only · 75f44993b096bf76 · report
RSE in 21 papers utils/metrics.py unverified no licence file found · pointer only · b40a11875ebd0cd2 · report
time_features in 21 papers utils/timefeatures.py unverified no licence file found · pointer only · ed90b1ac380a468e · report
time_features_from_frequency_str in 20 papers utils/timefeatures.py unverified no licence file found · pointer only · f8544563682146e5 · report
ant-research/Pyraformer found in paper text by Syntology 12 samples, 10 ran (2 instrument-failed) · 2 unverified
dataset_parameters long_range_main.py ran · our draft was wrong Apache-2.0 (permissive) · 2c381e7c9e1219be · report fixture: signature args:Args/0/?, dataset:str/0/str · returned Args · level recorded 2026-09-25
gen_covariates data_loader.py ran · honoured contract Apache-2.0 (permissive) · f48b56feaccf9194 · report fixture: signature times:ndarray/1/object, num_covariates:int/0/int · returned ndarray · level recorded 2026-09-25
gen_covariates preprocess_elect.py ran · honoured contract Apache-2.0 (permissive) · 614ba542a3cd4f70 · report fixture: signature times:ndarray/1/object, num_covariates:int/0/int · returned ndarray · level recorded 2026-09-25
get_all_v data_loader.py ran Apache-2.0 (permissive) · 18f1be69d346efd2 · report fixture: signature train_data:Tensor/2/float, train_end:int/0/int, seq_len:int/0/int, pred_len:int/0/int, window_stride:int/0/int, type:str/0/str · returned Tensor · level recorded 2026-09-25
get_k_q pyraformer/graph_attention.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 308b15ff903370f8 · report fixture: signature q_k_mask:Tensor/2/int · returned Tensor · level recorded 2026-09-25
get_mask in 119 papers
census: 9 implementations from 10 papers, 9 distinct outputs across 7 buckets, one shared input per bucket
pyraformer/Layers.py ran Apache-2.0 (permissive) · 5e73be8826ea1181 · report fixture: signature input_size:int/0/int, window_size:list/1/int, inner_size:int/0/int, device:device/0/? · returned tuple · level recorded 2026-09-25
get_q_k pyraformer/graph_attention.py ran Apache-2.0 (permissive) · 29fc69aabb4915c6 · report fixture: signature input_size:int/0/int, window_size:int/0/int, stride:int/0/int, device:str/0/str · returned Tensor · level recorded 2026-09-25
get_subsequent_mask in 17 papers pyraformer/Layers.py ran Apache-2.0 (permissive) · d9606e9421f56201 · report fixture: signature input_size:int/0/int, window_size:list/1/int, predict_step:int/0/int, truncate:bool/0/bool · returned Tensor · level recorded 2026-09-25
refer_points in 15 papers pyraformer/Layers.py ran Apache-2.0 (permissive) · c3f3fa218d235d6a · report fixture: signature all_sizes:list/1/int, window_size:list/1/int, device:device/0/? · returned Tensor · level recorded 2026-09-25
sample_mining_scheduler long_range_main.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 2dca999d536a049d · report fixture: signature epoch:int/0/int, batch_size:int/0/int · returned int · level recorded 2026-09-25
prepare_dataloader in 7 papers long_range_main.py unverified Apache-2.0 (permissive) · b688d662492743b0 · report
preprocess_elect data_loader.py unverified Apache-2.0 (permissive) · dc7d51e598eebc2f · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for FilterNet (graph method: FilterNet). 1 brick; individually on a fixture: 1 ran (of which 1 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified; the one sample that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. Model entry · level 1 · ran · d320822331f5ef05

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2411.01623") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Time SeriesTime Series Forecasting

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

AttentionSoftmax

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