SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 2310.02206 · 2023

Chunking: Continual Learning is not just about Distribution Shift

arXiv · PDF · Open in the Atlas

Code that ran

5 of 5 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; 4 failures of our instrument; 0 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/2310.02206.json · badge: /api/ran/2310.02206.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
tlee43/chunking-setting canonical (classifier label)
classifier basis not recorded on the link
5 ran · 0 no recorded run
FunctionStatusWhere it lives
calculate_output_image_size Ran
ran; our contract draft was wrong, not the code
tlee43/chunking-setting/backbone/EfficientNet.py
pointer only (licence: NONE) · get_code("7e7efa6d1976111a")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, tlee43/chunking-setting 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.

conv3x3 Ran
ran; our contract draft was wrong, not the code
tlee43/chunking-setting/backbone/ResNet18.py
pointer only (licence: NONE) · get_code("4c2989ace7c5c0da")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, tlee43/chunking-setting 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.

drop_connect Ran
ran; the contract check could not run (RAISES, DEP_MISSING or TIMEOUT)
tlee43/chunking-setting/backbone/EfficientNet.py
pointer only (licence: NONE) · get_code("f1e3c822763f3ebb")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, tlee43/chunking-setting 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_width_and_height_from_size Ran
ran, honoured the contract we drafted
tlee43/chunking-setting/backbone/EfficientNet.py
pointer only (licence: NONE) · get_code("1e2dad967f965366")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, tlee43/chunking-setting 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.

project Ran
ran; our contract draft was wrong, not the code
tlee43/chunking-setting/models/agem.py
pointer only (licence: NONE) · get_code("5d65b508e8b1cbad")
How it ran

The body of this sample is withheld: GitHub detected no licence in this paper's repository, tlee43/chunking-setting 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.

Also present in other papers' code

Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 5 are also present in other papers whose code we hold (5 with at least one paper dated earlier, 3 the same month, 5 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
conv3x3 27 other papers
10 dated earlier, 3 the same month, 13 later, 1 same year, order not determinable
2010.05595 (2020-10)
Rethinking Experience Replay: a Bag of Tricks for Continual Learning
2108.06552 (2021-08)
Continual Semi-Supervised Learning through Contrastive Interpolation Consistency
2203.12817 (2022-03)
Continual Learning and Private Unlearning
and 24 more not named here
drop_connect 23 other papers
13 dated earlier, 2 the same month, 8 later · 2 only as an assembly brick
1905.11946 (2019-05)
EfficientNet: Rethinking Model Scaling for Convolutional Neural Networks
1912.01588 (2019-12)
Leveraging Procedural Generation to Benchmark Reinforcement Learning
2010.00475 (2020-10)
FSD50K: An Open Dataset of Human-Labeled Sound Events
and 20 more not named here
project 11 other papers
5 dated earlier, 2 the same month, 3 later, 1 same year, order not determinable
2010.05595 (2020-10)
Rethinking Experience Replay: a Bag of Tricks for Continual Learning
2206.04016 (2022-06)
SYNERgy between SYNaptic consolidation and Experience Replay for general continual learning
aaai_26161 (2023 (year only))
Sparse Coding in a Dual Memory System for Lifelong Learning
and 8 more not named here
calculate_output_image_size 10 other papers
3 dated earlier, 7 later · 2 only as an assembly brick
1905.11946 (2019-05)
EfficientNet: Rethinking Model Scaling for Convolutional Neural Networks
2201.04021 (2022-01)
Optimization Planning for 3D ConvNets
2304.10177 (2023-04)
Regularizing Second-Order Influences for Continual Learning
and 7 more not named here
get_width_and_height_from_size 6 other papers
1 dated earlier, 5 later
2304.10177 (2023-04)
Regularizing Second-Order Influences for Continual Learning
2404.04002 (2024-04)
Continual Learning with Weight Interpolation
2407.15793 (2024-07)
CLIP with Generative Latent Replay: a Strong Baseline for Incremental Learning
and 3 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

Work on continual learning (CL) has thus far largely focused on the problems arising from shifts in the data distribution. However, CL can be decomposed into two sub-problems: (a) shifts in the data distribution, and (b) dealing with the fact that the data is split into chunks and so only a part of the data is available to be trained on at any point in time. In this work, we look at the latter sub-problem, the chunking of data. We show that chunking is an important part of CL, accounting for around half of the performance drop from offline learning in our experiments. Furthermore, our results reveal that current CL algorithms do not address the chunking sub-problem, only performing as well as plain SGD training when there is no shift in the data distribution. Therefore, we show that chunking is both an important and currently unaddressed sub-problem and until it is addressed CL methods will be capped in performance. Additionally, we analyse why performance drops when learning occurs on identically distributed chunks of data, and find that forgetting, which is often seen to be a problem due to distribution shift, still arises and is a significant problem. We also show that performance on the chunking sub-problem can be increased and that this performance transfers to the full CL setting, where there is distribution shift. Hence, we argue that work on chunking can help advance CL in general.

For agents

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

get_harvested_code_for_paper("2310.02206")
get_code_for_paper("2310.02206")
have("2310.02206")

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

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

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

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

Connect an agent — have() is free.