Papers › Bayesian Uncertainty for Gradient Aggregation in Multi-Task Learning

Bayesian Uncertainty for Gradient Aggregation in Multi-Task Learning

6 Feb 2024arXiv:2402.04005archive 2025-07-28

Idan Achituve, Idit Diamant, Arnon Netzer, Gal Chechik, Ethan Fetaya

As machine learning becomes more prominent there is a growing demand to perform several inference tasks in parallel. Running a dedicated model for each task is computationally expensive and therefore there is a great interest in multi-task learning (MTL). MTL aims at learning a single model that solves several tasks efficiently. Optimizing MTL models is often achieved by computing a single gradient per task and aggregating them for obtaining a combined update direction. However, these approaches do not consider an important aspect, the sensitivity in the gradient dimensions. Here, we introduce a novel gradient aggregation approach using Bayesian inference. We place a probability distribution over the task-specific parameters, which in turn induce a distribution over the gradients of the tasks. This additional valuable information allows us to quantify the uncertainty in each of the gradients dimensions, which can then be factored in when aggregating them. We empirically demonstrate the benefits of our approach in a variety of datasets, achieving state-of-the-art performance.

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

By repository: official repository: 8 samples from 1 repository, 7 ran (4 with no instrument failure; 3 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 on 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.

ssi-research/bayesagg_mtl officialmentioned in papermentioned on GitHubpytorchApache-2.0Syntology: 8 samples, 7 ran (3 instrument-failed) · 1 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

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

2ran · honoured contract
1ran · violated contract
1ran · our draft was wrong
2ran; the contract check could not run
1ran
1unverified

Licence: 0 of the 8 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 ssi-research/bayesagg_mtl. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

ssi-research/bayesagg_mtl official repository 8 samples, 7 ran (3 instrument-failed) · 1 unverified
delta_fn experiments/ChestX_ray14/calc_delta.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · 91108f5574eb04e9 · report fixture: signature a:ndarray/1/float, dataset:str/0/str · returned float64 · level recorded 2026-09-24
delta_fn experiments/utkface/calc_delta.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) · b459d7ee22384921 · report fixture: signature a:ndarray/1/float, dataset:str/0/str · returned float64 · level recorded 2026-09-24
one_hot in 150 papers
census: 18 implementations from 25 papers, 10 distinct outputs across 6 buckets, one shared input per bucket
experiments/CIFAR_MTL/data.py ran · our draft was wrong Apache-2.0 (permissive) · 2ded4a4604e0c9fa · report fixture: signature indices:Tensor/1/int, width:int/0/int · returned Tensor · level recorded 2026-09-24
psd_safe_cholesky BayesAgg_MTL/BayesAggMTL.py ran Apache-2.0 (permissive) · 952afea58c65f3cd · report fixture: signature A:Tensor/2/float, upper:bool/0/bool, out:NoneType/0/?, jitter:NoneType/0/?, max_tries:NoneType/0/? · returned Tensor · level recorded 2026-09-24
str2bool in 533 papers experiments/utils.py ran · violated contract Apache-2.0 (permissive) · 7c508037b40522af · report fixture: signature v:str/0/str · returned bool · level recorded, date not recorded
str_or_float experiments/utils.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · eefc191f062ea49a · report fixture: signature value:str/0/str · returned float · level recorded 2026-09-24
str_to_list in 10 papers experiments/utils.py ran · honoured contract Apache-2.0 (permissive) · 267fdf7ca1571871 · report fixture: signature string:str/0/str · returned list · level recorded 2026-09-24
delta_fn experiments/CIFAR_MTL/calc_delta.py unverified Apache-2.0 (permissive) · 3dc5e431a2586388 · report

Tasks

Bayesian InferenceMulti-Task Learning

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Multi-Task Learning ChestX-ray14 BayesAgg-MTL delta_m −14.96 #1 of 1 Archive leaderboard report
Multi-Task Learning QM9 BayesAgg-MTL ∆m% 53.7 #1 of 5 Archive leaderboard report
Multi-Task Learning UTKFace BayesAgg-MTL delta_m -2.23 #1 of 1 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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