Papers › Vertical Federated Learning with Missing Features During Training and Inference

Vertical Federated Learning with Missing Features During Training and Inference

29 Oct 2024arXiv:2410.22564archive 2025-07-28

Pedro Valdeira, Shiqiang Wang, Yuejie Chi

Vertical federated learning trains models from feature-partitioned datasets across multiple clients, who collaborate without sharing their local data. Standard approaches assume that all feature partitions are available during both training and inference. Yet, in practice, this assumption rarely holds, as for many samples only a subset of the clients observe their partition. However, not utilizing incomplete samples during training harms generalization, and not supporting them during inference limits the utility of the model. Moreover, if any client leaves the federation after training, its partition becomes unavailable, rendering the learned model unusable. Missing feature blocks are therefore a key challenge limiting the applicability of vertical federated learning in real-world scenarios. To address this, we propose LASER-VFL, a vertical federated learning method for efficient training and inference of split neural network-based models that is capable of handling arbitrary sets of partitions. Our approach is simple yet effective, relying on the sharing of model parameters and on task-sampling to train a family of predictors. We show that LASER-VFL achieves a 𝒪(1/√(T)) convergence rate for nonconvex objectives and, under the Polyak-Łojasiewicz inequality, it achieves linear convergence to a neighborhood of the optimum. Numerical experiments show improved performance of LASER-VFL over the baselines. Remarkably, this is the case even in the absence of missing features. For example, for CIFAR-100, we see an improvement in accuracy of 19.3% when each of four feature blocks is observed with a probability of 0.5 and of 9.5% when all features are observed. The code for this work is available at https://github.com/Valdeira/LASER-VFL.

PaperPDFCodeCode Syntology ranMethod as code

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 14 code samples harvested from 1 repository linked to this paper: 10 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; 6 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 4 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: 14 samples from 1 repository, 10 ran (4 with no instrument failure; 6 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-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

valdeira/laser-vfl officialmentioned in papermentioned on GitHubpytorchMITSyntology: 14 samples, 10 ran (6 instrument-failed) · 4 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

14 samples harvested: 10 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; 6 where Syntology's instrument failed) · 4 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
4ran · our draft was wrong
2ran; the contract check could not run
1ran
4unverified

Licence: 0 of the 14 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 valdeira/laser-vfl. “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.

valdeira/laser-vfl official repository 14 samples, 10 ran (6 instrument-failed) · 4 unverified
create_vocab in 5 papers models/mimic_model_utils.py ran · our draft was wrong MIT (permissive) · f072b73bd6e99eec · report fixture: signature file:str/0/str · returned dict · level recorded 2026-09-25
drop_mask models/model_utils.py ran · violated contract MIT (permissive) · 68a9caf3d546a3af · report fixture: signature plug_mask:Tensor/2/bool, p_drop:float/0/float · returned Tensor · level recorded 2026-09-26
get_block_from_input models/mlp.py ran MIT (permissive) · 199475957adeabb0 · report fixture: signature x:tuple/1/Tensor, i:int/0/int, num_clients:int/0/int · returned Tensor · level recorded 2026-09-26
get_f1 in 6 papers methods/laser.py ran · honoured contract fingerprinted MIT (permissive) · 9ae52284718dca6a · report fixture: signature true_positive:int/0/int, false_positive:int/0/int, false_negative:int/0/int · returned float · level recorded 2026-09-22
powerset_except_empty utils.py ran · our draft was wrong MIT (permissive) · e01b59a9fae0804f · report fixture: signature n:int/0/int · returned list · level recorded 2026-09-26
random_argmax_along_axis methods/ensemble.py ran; the contract check could not run (RAISES) MIT (permissive) · f2757b67c45c9a98 · report fixture: signature tensor:Tensor/2/float, axis:int/0/int · returned Tensor · level recorded 2026-09-25
slice_cifar_block models/resnet18.py ran; the contract check could not run (RAISES) MIT (permissive) · ef3138827a00dc20 · report fixture: signature x:Tensor/4/float, partition:tuple/1/tuple · returned Tensor · level recorded 2026-09-26
split_into_chunks in 9 papers models/lstm.py ran · our draft was wrong fingerprinted MIT (permissive) · 8d2e97e2a9f5617b · report fixture: signature lst:list/1/int, K:int/0/int · returned list · level recorded 2026-09-25
task_to_hyperparameters models/model_utils.py ran · honoured contract MIT (permissive) · b87834f1696a21ae · report fixture: signature dataset:str/0/str · returned tuple · level recorded 2026-09-26
time_decorator methods/laser.py ran · our draft was wrong MIT (permissive) · 606bc3d38cb0e034 · report fixture: signature func:callable/0/?, args:tuple/1/int, kwargs:dict/0/? · returned function · level recorded 2026-09-22
create_batches in 13 papers models/mimic_model_utils.py unverified MIT (permissive) · 8205a45bb88f06e9 · report
init in 55 papers models/mimic_model_utils.py unverified MIT (permissive) · d4531a69fbf2a306 · report
setup_task utils.py unverified MIT (permissive) · 526af6c6453d5dff · report
train_laser methods/laser.py unverified MIT (permissive) · b74bfdd5b8f5829f · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for LASER-VFL (graph method: LASER-VFL). 3 bricks; individually on a fixture: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. The assembly has not been run end-to-end.

  1. train_laser entry · level 0 · unverified · b74bfdd5b8f5829f
  2. get_f1 metric · level 1 · ran · honoured contract · 9ae52284718dca6a
  3. time_decorator helper · level 1 · ran · our draft was wrong · 606bc3d38cb0e034

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2410.22564") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Federated LearningVertical Federated Learning

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