Title Abstract Introduction Framing Model Merging 3 Strategies Setup Results When it wins Conclusions
BMVC 2026 · Submission #259

Unapologetically
Distributed

A call for decentralized Document Analysis — where keeping data apart is not a tax on accuracy, but a route to better generalization.

Core idea
Train separate, merge weights
Datasets
27 · WS / OCR / Tables
OOD-unseen gain
+104% mAP
Data shared
None — only θ
Explore the paper
Abstract

Decentralization as an opportunity, not a tax

Privacy constraints keep archives, governments, and small businesses from pooling document data. Federated learning is usually treated as a necessary evil — a price paid for privacy. This paper argues the opposite: train models separately on each silo, average their weights, and the merged model often generalizes better — especially out-of-distribution and in low-resource regimes.

Centralized vs distributed — drag the slider

Pool everything Keep apart, merge

This is the first study to evaluate distributed learning in Document Analysis along three axes at once: the tasks (word spotting, handwriting/OCR, table recognition), the architectures (RNNs, transformers, graph networks), and the fine-tuning strategies (distillation, layer-wise, end-to-end).

Chapter 1 · Introduction

Why the data can't move

Modern training assumes you can pile all the data in one place. For documents — sensitive administrative records, cultural-heritage collections meant to stay near their origin, confidential SME paperwork — that assumption simply fails. Distributed learning trains where the data lives and shares only the resulting weights.

The threefold hypothesis
i · BETTER TEACHERS
Merged features are more general, so they distill better into small student models.
ii · MULTI-SCRIPT
General enough to absorb entirely new alphabets, even far from the training distribution.
iii · BETTER INIT
A superior starting point for subsequent in-distribution fine-tuning.

"Decentralization is not merely a constraint, but a valuable opportunity to improve model robustness and adaptability."

Chapter 3.1 · Methodology

Model merging, in weight space

A model is just a vector of weights θ ∈ ℝm. Train it on the whole dataset and you get the centralized θD. Train one model per silo and average them — that's the distributed θ̄D. The data never leaves its silo; only the weight vectors are shared.

θ̄D  =  (1/n) · Σi=1…n θdi     (Eq. 3 — the move behind FedAvg, task arithmetic & model soups)
What the average does to the weights

One operation wearing four names

The paper's footnote makes a quiet but central claim: FedAvg, model soups, task arithmetic and MAML are the same move — train separately from a shared init θ⁰, then combine in weight space. Here is that move at the level of individual parameters. Each silo is a strip of weights; the merge is the column-wise mean. Switch how you frame the combination — the resulting vector is bit-for-bit identical.

FedAvg · Model Soup ╱ Task Arithmetic
θ̄ = (1/n) Σ θdᵢ

A task vector τi = θdᵢ − θ⁰ is what one silo learned on top of the shared start. Add the mean of the task vectors back onto θ⁰ and the θ⁰ terms cancel — you land on the plain average. That algebraic cancellation is why the whole family collapses to Eq. 3, and why a result proven for one (e.g. model soups) transfers to the others.

θ⁰ + (1/n)Σ(θdᵢ − θ⁰)  =  θ⁰ + (1/n)Σθdᵢ − θ⁰  =  (1/n)Σθdᵢ  = θ̄

The same point, two constructions — drag the seed or any optimum

This is weight space. The shared seed θ⁰ sits on the left; each silo trains to its own optimum θdᵢ. Switch how you read the merge: as models (the centroid of the optima — model soup / FedAvg) or as task vectors (sum the arrows τᵢ = θdᵢ − θ⁰ from the seed — task arithmetic). The orange ★ does not move: the seed cancels, so both are literally the same vector.

Same compute, same data seen

Decentralizing is not more expensive

A common objection: surely n separate trainings cost more? No. Centralized sees N points for T epochs = N·T steps. Splitting N = n₁+n₂+… into silos gives n₁·T + n₂·T + … = (n₁+n₂+…)·T = N·T. Product is distributive — the budgets are identical. Drag to re-split the data.

Forward/backward steps — centralized vs distributed (T epochs)
Chapter 3.2 · Methodology

Three ways to fine-tune a merged model

The same merged weights are tested through three fine-tuning regimes spanning the breadth of Document Analysis. Pick a strategy:

Word Spotting
Knowledge Distillation
HTR / OCR
Layer-wise · Multi-script
Table Recognition
Graph · End-to-end
Chapter 4 · Experimental Setup

Breadth on purpose

27
Datasets
3
Tasks
9+
Scripts / ciphers
50
Pages in M96 (low-res.)

Datasets span in-pretraining Latin, out-of-domain Latin (artistic fonts, glares, printed distractors), and out-of-vocabulary scripts (Arabic, Chinese, Japanese, Korean, Hindi, Bangla) plus historical ciphers (Copiale, Borg, Vatican). Protocol: train each silo for the same steps as centralized, merge (Eq. 3), then fine-tune 25 epochs on a held-out target and evaluate on its test split.

Dataset map — click a band
Three difficulty bands: in-domain (seen), out-of-domain Latin, and out-of-vocabulary scripts/ciphers.
Chapter 5 · Results

Where the merge pays off

Word Spotting · Table 2

Gains grow as data drifts away from training

In-domain, results are mixed (a small +0.5% on average). But out-of-domain Latin jumps +36.7%, and on unseen alphabets the relative mAP gain is +104% — distributed pretraining shines exactly where generalization is hardest.

mAP gain from distributed pretraining, by domain difficulty
TEXT ENCODER:
Mean mAP — centralized ● vs distributed ◆
Multi-script OCR · Table 3

On a brand-new alphabet, merging can be the difference between learning and not

Personalizing to an unseen script: distributed pretraining beats centralized by ×1.62 on average. The Borg cipher is the extreme — centralized fails outright (0.000), distributed reaches 0.505.

Per-language word accuracy after personalization — click a language above the bars
Table Recognition · Table 5

The honest nuance: distributed wins zero-shot, centralized wins end-to-end

A leave-one-out evaluation. With no target adaptation (zero-shot) the distributed merge leads; as you grant more adaptation (partial → full end-to-end), the advantage shifts to centralized. Pick a regime:

Node & edge accuracy across the four table datasets
Chapter 6 · When it wins

A decision map, not a prescription

The paper's title is a targeted call. Distributed learning is not a universal winner — it dominates in specific regimes. Describe your situation and see which side the evidence favors.

Chapter 6 · Conclusions

A targeted call

DATA-CENTRIC
Best in low-resource regimes

Largest gains on the smallest data (M96, 50 pages) and on independently-learned new alphabets — the gap narrows once data is abundant.

ARCHITECTURE-CENTRIC
Best when few params train

Strongest zero-shot and with light heads (GRU/LSTM); degrades under full end-to-end fine-tuning of heavy models.

DOMAINS
Heritage & SMEs

Scarce annotations, distribution shift, and privacy/access constraints align precisely with where distributed learning helps.

PRIVACY FOR FREE
No data leaves the silo

The same compute, the same data seen — only weights are shared, and often the merged model is better.

Decentralization in Document Analysis is not a universal prescription, but a targeted call — to practitioners under low-resource, low-adaptability, or deployment-constrained conditions, for whom distributed learning is competitive and often superior.