Papers › Identification of Negative Transfers in Multitask Learning Using Surrogate Models

Identification of Negative Transfers in Multitask Learning Using Surrogate Models

25 Mar 2023arXiv:2303.14582archive 2025-07-28

Dongyue Li, Huy L. Nguyen, Hongyang R. Zhang

Multitask learning is widely used in practice to train a low-resource target task by augmenting it with multiple related source tasks. Yet, naively combining all the source tasks with a target task does not always improve the prediction performance for the target task due to negative transfers. Thus, a critical problem in multitask learning is identifying subsets of source tasks that would benefit the target task. This problem is computationally challenging since the number of subsets grows exponentially with the number of source tasks; efficient heuristics for subset selection do not always capture the relationship between task subsets and multitask learning performances. In this paper, we introduce an efficient procedure to address this problem via surrogate modeling. In surrogate modeling, we sample (random) subsets of source tasks and precompute their multitask learning performances. Then, we approximate the precomputed performances with a linear regression model that can also predict the multitask performance of unseen task subsets. We show theoretically and empirically that fitting this model only requires sampling linearly many subsets in the number of source tasks. The fitted model provides a relevance score between each source and target task. We use the relevance scores to perform subset selection for multitask learning by thresholding. Through extensive experiments, we show that our approach predicts negative transfers from multiple source tasks to target tasks much more accurately than existing task affinity measures. Additionally, we demonstrate that for several weak supervision datasets, our approach consistently improves upon existing optimization methods for multitask learning.

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 9 code samples harvested from 2 repositories linked to this paper: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 2 where Syntology's instrument failed) · 0 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: 9 samples from 2 repositories, 9 ran (7 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.

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.

neu-statsml-research/task-modeling officialmentioned in paperjaxMITSyntology: 8 samples, 8 ran (1 instrument-failed) · 0 unverified report
virtuosoresearch/task-modeling officialmentioned in paperjaxSyntology: 1 sample, 1 ran (1 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

9 samples harvested: 9 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 1 honoured, 0 violated, 6 with no contract checked; 2 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.

1ran · honoured contract
2ran · our draft was wrong
6ran

Licence: 1 of the 9 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. 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.

neu-statsml-research/task-modeling official repository 8 samples, 8 ran (1 instrument-failed) · 0 unverified
booleans_processing in 9 papers transformers/modeling_tf_utils.py ran MIT (permissive) · a37e8f716afbe0c3 · report fixture: signature config:MockConfig/0/?, output_attentions:NoneType/0/?, output_hidden_states:NoneType/0/?, return_dict:NoneType/0/?, use_cache:NoneType/0/? · returned dict · level recorded 2026-09-24
convert_pytorch_state_dict_to_flax in 21 papers transformers/modeling_flax_pytorch_utils.py ran MIT (permissive) · f37141ae02c0de99 · report fixture: signature pt_state_dict:dict/0/?, flax_model:MockFlaxModel/0/? · returned dict · level recorded 2026-09-24
convert_tf_weight_name_to_pt_weight_name in 6 papers transformers/modeling_tf_pytorch_utils.py ran fingerprinted MIT (permissive) · 5f5d99a0dee8c2b1 · report fixture: signature tf_name:str/0/str, start_prefix_to_remove:str/0/str · returned tuple · level recorded 2026-09-25
dummy_loss in 11 papers transformers/modeling_tf_utils.py ran MIT (permissive) · 55a65bc77a8a31d3 · report fixture: signature y_true:EagerTensor/2/float, y_pred:EagerTensor/2/float · returned EagerTensor · level recorded 2026-09-24
find_pruneable_heads_and_indices in 19 papers transformers/modeling_utils.py ran · our draft was wrong MIT (permissive) · 6d254a1b39c650ff · report fixture: signature heads:list/1/int, n_heads:int/0/int, head_size:int/0/int, already_pruned_heads:set/0/? · returned tuple · level recorded 2026-09-24
keras_serializable in 11 papers transformers/modeling_tf_utils.py ran MIT (permissive) · 756e9ec5f7912d3e · report fixture: signature cls:callable/0/? · returned type · level recorded 2026-09-25
quick_gelu in 43 papers transformers/modeling_flax_utils.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · a66d2b78670c85e1 · report fixture: signature x:ArrayImpl/2/float · returned ArrayImpl · level recorded 2026-09-24
rename_key_and_reshape_tensor in 22 papers transformers/modeling_flax_pytorch_utils.py ran MIT (permissive) · 5c0eb4c5f8c5c1de · report fixture: signature pt_tuple_key:tuple/1/str, pt_tensor:ndarray/2/float, random_flax_state_dict:dict/0/?, model_prefix:str/0/str · returned tuple · level recorded 2026-09-25
virtuosoresearch/task-modeling official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
add_trainer_arguments train_multitask.py ran · our draft was wrong MIT (permissive) · 4c533c884362c414 · report fixture: signature parser:ArgumentParser/0/? · returned ArgumentParser · level recorded 2026-09-22

Tasks

Multi-Task Learning

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Linear Regression

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