Papers › Localize-and-Stitch: Efficient Model Merging via Sparse Task Arithmetic

Localize-and-Stitch: Efficient Model Merging via Sparse Task Arithmetic

24 Aug 2024arXiv:2408.13656archive 2025-07-28

Yifei He, Yuzheng Hu, Yong Lin, Tong Zhang, Han Zhao

Model merging offers an effective strategy to combine the strengths of multiple finetuned models into a unified model that preserves the specialized capabilities of each. Existing methods merge models in a global manner, performing arithmetic operations across all model parameters. However, such global merging often leads to task interference, degrading the performance of the merged model. In this work, we introduce Localize-and-Stitch, a novel approach that merges models in a localized way. Our algorithm works in two steps: i) Localization: identify tiny (1% of the total parameters) localized regions in the finetuned models containing essential skills for the downstream tasks, and ii) Stitching: reintegrate only these essential regions back into the pretrained model for task synergy. We demonstrate that our approach effectively locates sparse regions responsible for finetuned performance, and the localized regions could be treated as compact and interpretable representations of the finetuned models (tasks). Empirically, we evaluate our method on various vision and language benchmarks, showing that it outperforms existing model merging methods under different data availability scenarios. Beyond strong empirical performance, our algorithm also facilitates model compression and preserves pretrained knowledge, enabling flexible and continual skill composition from multiple finetuned models with minimal storage and computational overhead. Our code is available at https://github.com/uiuctml/Localize-and-Stitch.

PaperPDFCodeCode Syntology ran

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

By repository: official repository: 7 samples from 2 repositories, 7 ran (2 with no instrument failure; 5 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.

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

uiuctml/localize-and-stitch officialmentioned in papermentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
yifei-he/localize-and-stitch officialmentioned in papermentioned on GitHubpytorchMITSyntology: 6 samples, 6 ran (4 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.

Code Syntology ran Syntology

7 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 5 where Syntology's instrument failed) · 0 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 · our draft was wrong
2ran

Licence: 0 of the 7 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 2 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.

uiuctml/localize-and-stitch official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
select_trainable_parameters language/main_localize_stitch.py ran · our draft was wrong MIT (permissive) · 883ebc0d4d55db02 · report fixture: signature model:callable/0/? · returned dict · level recorded 2026-09-22
yifei-he/localize-and-stitch official repository 6 samples, 6 ran (4 instrument-failed) · 0 unverified
create_log_dir in 7 papers vision/src/main_dataless_localize_stitch.py ran · our draft was wrong MIT (permissive) · 3053d2bdc3ea5c89 · report fixture: signature path:str/0/str, filename:str/0/str · returned Logger · level recorded, date not recorded
input_example_to_string in 10 papers language/src/dataset.py ran · our draft was wrong MIT (permissive) · e768e25ca95f70cd · report fixture: signature example:Example/0/?, sep_token:str/0/str · returned str · level recorded 2026-09-24
input_example_to_tuple in 10 papers language/src/dataset.py ran · our draft was wrong MIT (permissive) · fbef70dc7c700501 · report fixture: signature example:Example/0/? · returned list · level recorded 2026-09-24
parse_data_arguments language/args.py ran · our draft was wrong MIT (permissive) · b2160a3a2b890e58 · report fixture: signature dataset_name:str/0/str · returned Namespace · level recorded 2026-09-24
text_classification_metrics in 8 papers language/src/processors.py ran MIT (permissive) · b62076c5483738dc · report fixture: signature task_name:str/0/str, preds:ndarray/1/int, labels:ndarray/1/int · returned dict · level recorded 2026-09-24
tokenize_multipart_input in 8 papers language/src/dataset.py ran MIT (permissive) · e3eed9fd49cd08fb · report fixture: signature input_text_list:list/1/str, max_length:int/0/int, tokenizer:MockTokenizer/0/?, task_name:str/0/str, prompt:bool/0/bool, template:NoneType/0/?, label_word_list:NoneType/0/?, first_sent_limit:NoneType/0/?, other_sent_limit:NoneType/0/?, gpt3:bool/0/bool, truncate_head:bool/0/bool, support_labels:NoneType/0/? · returned dict · level recorded 2026-09-24

Tasks

Model CompressionTask Arithmetic

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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