6 of 6 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 2 have no contract verdict; 3 failures of our instrument; 0 no recorded run), measured 2026-11-21; 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/2202.06258.json · badge: /api/ran/2202.06258.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 |
|---|---|---|
| thuml/Flowformer | canonical (classifier label) classifier basis not recorded on the link |
6 ran · 0 no recorded run |
| Function | Status | Where it lives |
|---|---|---|
| batch_index_select | Ran ran; our contract draft was wrong, not the code |
thuml/Flowformer/Flowformer_CV/utils.py code served (permissive licence) · get_code("908619be92da9903") 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 Tensor, ndim 3, dtype family float, shape (2, 2, 3) 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.
|
| build_dataset | Ran ran on a synthesized input |
thuml/Flowformer/Flowformer_CV/datasets.py code served (permissive licence) · get_code("09d8970cc61c5886") 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 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.
|
| build_transform | Ran ran on a synthesized input |
thuml/Flowformer/Flowformer_CV/datasets.py code served (permissive licence) · get_code("984b0cb17eae025e") 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 Compose. 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.
|
| get_lr | Ran ran, honoured the contract we drafted |
thuml/Flowformer/Flowformer_RL/utils.py pointer only (licence: MIT); the stored copy get_code serves, from yjzhang96/UTI-VFI, is pointer only (licence: NONE) · get_code("7337f1f5ff01dcd0") How it ranThe 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 yjzhang96/UTI-VFI, 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_pos_encoder | Ran ran; our contract draft was wrong, not the code |
thuml/Flowformer/Flowformer_TimeSeries/models/Flowformer.py code served (permissive licence) · get_code("48ee0364b1d8b847") 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 type. 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.
|
| make_dir | Ran ran; our contract draft was wrong, not the code |
thuml/Flowformer/Flowformer_RL/utils.py pointer only (licence: MIT); the stored copy get_code serves, from silihuang-ai/idt, is pointer only (licence: NONE) · get_code("42958997018c3581") How it ranThe 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 silihuang-ai/idt, 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. |
Of 6 samples lifted from this paper's linked repositories, 6 carry a function identity and 0 do not. Of the 6 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 2 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 |
|---|---|---|---|
| get_lr | 25 other papers 14 dated earlier, 11 later · 2 only as an assembly brick |
1605.07148 (2016-05) Backprop KF: Learning Discriminative Deterministic State Estimators |
1606.00915 (2016-06) DeepLab: Semantic Image Segmentation with Deep Convolutional Nets, Atrous Convolution, and Fully Connected CRFs 1904.01355 (2019-04) FCOS: Fully Convolutional One-Stage Object Detection and 22 more not named here |
| batch_index_select | 10 other papers 1 dated earlier, 9 later · 1 only as an assembly brick |
2106.02034 (2021-06) DynamicViT: Efficient Vision Transformers with Dynamic Token Sparsification |
aaai_25860 (2023 (year only)) CF-ViT: A General Coarse-to-Fine Method for Vision Transformer 2304.10716 (2023-04) Joint Token Pruning and Squeezing Towards More Aggressive Compression of Vision Transformers and 7 more not named here |
| make_dir | 8 other papers 3 dated earlier, 5 later |
1910.01741 (2019-10) Improving Sample Efficiency in Model-Free Reinforcement Learning from Images |
2004.04136 (2020-04) CURL: Contrastive Unsupervised Representations for Reinforcement Learning 2010.09163 (2020-10) D2RL: Deep Dense Architectures in Reinforcement Learning and 5 more not named here |
| get_pos_encoder | 2 other papers 1 dated earlier, 1 later |
2010.02803 (2020-10) A Transformer-based Framework for Multivariate Time Series Representation Learning |
2410.17918 (2024-10) Addressing Asynchronicity in Clinical Multimodal Fusion via Individualized Chest X-ray Generation |
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-21.
Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.
Transformers based on the attention mechanism have achieved impressive success in various areas. However, the attention mechanism has a quadratic complexity, significantly impeding Transformers from dealing with numerous tokens and scaling up to bigger models. Previous methods mainly utilize the similarity decomposition and the associativity of matrix multiplication to devise linear-time attention mechanisms. They avoid degeneration of attention to a trivial distribution by reintroducing inductive biases such as the locality, thereby at the expense of model generality and expressiveness. In this paper, we linearize Transformers free from specific inductive biases based on the flow network theory. We cast attention as the information flow aggregated from the sources (values) to the sinks (results) through the learned flow capacities (attentions). Within this framework, we apply the property of flow conservation into attention and propose the Flow-Attention mechanism of linear complexity. By respectively conserving the incoming flow of sinks for source competition and the outgoing flow of sources for sink allocation, Flow-Attention inherently generates informative attentions without using specific inductive biases. Empowered by the Flow-Attention, Flowformer yields strong performance in linear time for wide areas, including long sequence, time series, vision, natural language, and reinforcement learning. The code and settings are available at this repository: https://github.com/thuml/Flowformer.
The same record, over MCP at https://syntology.ai/mcp:
get_harvested_code_for_paper("2202.06258")
get_code_for_paper("2202.06258")
have("2202.06258")
The run record, dated, one paper per request, free:
curl https://syntology.ai/api/ran/2202.06258.json
A badge for a README (the split and the date, never a ratio):
[](https://syntology.ai/paper/2202.06258)
Connect an agent — have() is free.