Papers › Modelling Cellular Perturbations with the Sparse Additive Mechanism Shift Variational...

Modelling Cellular Perturbations with the Sparse Additive Mechanism Shift Variational Autoencoder

5 Nov 2023NeurIPS 2023 11arXiv:2311.02794archive 2025-07-28

Michael Bereket, Theofanis Karaletsos

Generative models of observations under interventions have been a vibrant topic of interest across machine learning and the sciences in recent years. For example, in drug discovery, there is a need to model the effects of diverse interventions on cells in order to characterize unknown biological mechanisms of action. We propose the Sparse Additive Mechanism Shift Variational Autoencoder, SAMS-VAE, to combine compositionality, disentanglement, and interpretability for perturbation models. SAMS-VAE models the latent state of a perturbed sample as the sum of a local latent variable capturing sample-specific variation and sparse global variables of latent intervention effects. Crucially, SAMS-VAE sparsifies these global latent variables for individual perturbations to identify disentangled, perturbation-specific latent subspaces that are flexibly composable. We evaluate SAMS-VAE both quantitatively and qualitatively on a range of tasks using two popular single cell sequencing datasets. In order to measure perturbation-specific model-properties, we also introduce a framework for evaluation of perturbation models based on average treatment effects with links to posterior predictive checks. SAMS-VAE outperforms comparable models in terms of generalization across in-distribution and out-of-distribution tasks, including a combinatorial reasoning task under resource paucity, and yields interpretable latent structures which correlate strongly to known biological mechanisms. Our results suggest SAMS-VAE is an interesting addition to the modeling toolkit for machine learning-driven scientific discovery.

PaperPDFConference PDFCodeCode 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.

Syntology holds a reference implementation of SAMS-VAE, generated from the paper text (not the authors' code), at level 2 on Syntology's ladder: V2 “two implementations GENERATED from the paper's signature and spec agree numerically (1e-6) on fixture inputs” “neither of the two ever read the authors' own code, so V2 measures how unambiguously the paper specifies the method, not fidelity to the authors' implementation (measured 2026-09-11, commit 75eaa77: cross_checked_by is a second LLM on 2,628 of 2,831 served samples)” (quoted from Syntology's server card). No rung compares this code against the authors' implementation. For agents: get_reference_implementation(name='SAMS-VAE') (how to connect); the free check have('2311.02794') needs no token.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 12 code samples harvested from 1 repository linked to this paper: 7 ran (of which 7 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified; every one of the 7 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 12 samples from 1 repository, 7 ran (7 with no instrument failure; 0 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-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

insitro/sams-vae officialmentioned in paperpytorchSyntology: 12 samples, 7 ran (0 instrument-failed) · 5 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

12 samples harvested: 7 ran (of which 7 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified; every one of the 7 samples that ran constructed an object rather than computing a result. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

7ran
5unverified

Licence: 12 of the 12 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 insitro/sams-vae. “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”. For 6 samples that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

insitro/sams-vae official repository 12 samples, 7 ran (0 instrument-failed) · 5 unverified
FixedLogVarianceEncoder sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · a9cf8ed31065ae6b · report fixture: returned FixedLogVarianceEncoder · level recorded 2026-09-22
GaussianLikelihoodFixedVarianceResidualMLP sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic no licence file found · pointer only · 411358440d60d943 · report fixture: returned GaussianLikelihoodFixedVarianceResidualMLP · level recorded 2026-09-22
GaussianLikelihoodResidualMLP sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic no licence file found · pointer only · 14121d981e8241ab · report fixture: returned GaussianLikelihoodResidualMLP · level recorded 2026-09-22
LibraryGammaPoissonSharedConcentrationResidualMLP sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic no licence file found · pointer only · 4263b396193ca7fa · report fixture: returned LibraryGammaPoissonSharedConcentrationResidualMLP · level recorded 2026-09-22
MLP in 375 papers sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 8bfa7c1c5468eb59 · report fixture: returned MLP · level recorded 2026-09-22
PoissonLikelihoodResidualMLP sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic no licence file found · pointer only · 6e188112fecaf2b2 · report fixture: returned PoissonLikelihoodResidualMLP · level recorded 2026-09-22
ResidualMLP sams_vae/models/sams_vae/model.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · a7f8ccbf74242706 · report fixture: returned ResidualMLP · level recorded 2026-09-22
BaseGaussianLikelihoodMLP sams_vae/models/sams_vae/model.py unverified no licence file found · pointer only · 1a4a49f671eaa2a9 · report
BaseLibraryGammaPoissonSharedConcentrationLikelihood sams_vae/models/sams_vae/model.py unverified no licence file found · pointer only · 9e2652f2f9c064e3 · report
BasePoissonLikelihoodMLP sams_vae/models/sams_vae/model.py unverified no licence file found · pointer only · 7d4d48a797381ce9 · report
SAMSVAEModel sams_vae/models/sams_vae/model.py unverified no licence file found · pointer only · e4a1d75cfe86acc9 · report
get_likelihood_mlp sams_vae/models/sams_vae/model.py unverified no licence file found · pointer only · eb2c8efffd66cc02 · 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. For a generated assembly, an independent peer is a second implementation generated separately from the same paper text; neither implementation read the authors' code. At level 2 the two agreed numerically on the fixture's inputs; level 3 is recorded when property tests derived from the paper also passed on both, and each level 3 card prints how many its report lists. 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. A generated assembly's label was set when its code was generated for the method, and no model judged it; its card prints it as "by construction" or "not judged by a model". Where an assembly's phrase has no constructed figure, a brick that ran is not among the harvested samples this build reads, and whether a brick's run only constructed an object is read from that brick's harvested sample, so the figure was not counted; it does not say there were none.

2 assemblies on this paper: 1 harvested, 1 generated.

generated Assembly for SAMS-VAE (graph method: SAMS-VAE), generated from the paper text, not the repository's code. 1 brick; individually on a fixture: 1 ran (1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. Ran end-to-end against an independent peer (level 2).

label matches by construction: the code was generated for this method (not judged by a model)

  1. compute_perturbation_latent entry · level 2 · ran · 125ad574871fa98553e34faee476029f7a05e3a6044094af4b5757d45067c171

harvested Assembly for SAMS-VAE (graph method: SAMS-VAE). 12 bricks; individually on a fixture: 7 ran (of which 7 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 0 violated, 7 with no contract checked; 0 where Syntology's instrument failed) · 5 unverified; every one of the 7 samples that ran constructed an object rather than computing a result. The assembly has not been run end-to-end.

  1. SAMSVAEModel entry · level 0 · unverified · e4a1d75cfe86acc9
  2. get_likelihood_mlp helper · level 0 · unverified · eb2c8efffd66cc02
  3. GaussianLikelihoodFixedVarianceResidualMLP helper · level 1 · ran · 411358440d60d943
  4. GaussianLikelihoodResidualMLP helper · level 1 · ran · 14121d981e8241ab
  5. LibraryGammaPoissonSharedConcentrationResidualMLP helper · level 1 · ran · 4263b396193ca7fa
  6. PoissonLikelihoodResidualMLP helper · level 1 · ran · 6e188112fecaf2b2
  7. BaseGaussianLikelihoodMLP helper · level 0 · unverified · 1a4a49f671eaa2a9
  8. FixedLogVarianceEncoder helper · level 1 · ran · a9cf8ed31065ae6b
  9. ResidualMLP helper · level 1 · ran · a7f8ccbf74242706
  10. BaseLibraryGammaPoissonSharedConcentrationLikelihood helper · level 0 · unverified · 9e2652f2f9c064e3
  11. BasePoissonLikelihoodMLP helper · level 0 · unverified · 7d4d48a797381ce9
  12. MLP helper · level 1 · ran · 8bfa7c1c5468eb59

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="2311.02794") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

DisentanglementDrug Discoveryscientific discovery

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