AI & ML
ReliFlow: Reliability-Calibrated Residual Transport for Combinatorial Single-Cell Perturbation Prediction
arXiv stat.ML0 views
arXiv:2611.23999v1 Announce Type: new Abstract: Predicting the transcriptional response to combined perturbations requires distinguishing interactions between interventions from errors in their individual effect estimates. The latter become more pronounced when single-perturbation evidence is sparse or withheld. We introduce a conditional flow-matching model that estimates the reliability of single-gene effects from training-only cross-fitting and uses those estimates to calibrate the additive source distribution. The velocity is decomposed into a known correction of the additive reference and a learned residual transport field. On Norman genetic perturbations, reduces mean absolute error (MAE) from 0.142 to 0.131 for unseen combinations of observed singles and from 0.198 to 0.178 when constituent singles are withheld. On held-out ComboSciPlex drug combinations, MAE decreases from 0.191 to 0.176. Non-additive residual correlation improves from 0.574 to 0.638, and component ablations identify the contribution of reliability weighting. The results indicate that accounting for uncertain constituent effects improves generalization to unseen genetic and chemical combinations, with a moderate increase in training cost.
Source:https://arxiv.org/abs/2611.23999PreviousOptimal Deep Nonparametric Regression with Uniformly Bounded Lipschitz ConstantsNextHow Reward Gain Imbalance Shapes Ranking: Rethinking Rubric-Based Reward Aggregation
Related posts
Prompt, Workflow, Agent or Agentic System: Which One Does Your Process Need?
0dev.to
Running Claude Code and Codex from your phone: the official options, and the self-hosted app I built
0dev.to
Unlocking Enhanced Visuals: Dlss5 Without Extra Load --An unofficial side-story version
0dev.to
Fiona the Hippo Died After Eating a Hat. But How Does a Hat Kill a Hippo?
0Wired

Why ChatGPT Cites Review Sites Instead of Your Company Website
0dev.to
Basalt walkthrough is up: why 776 tok/s needs the whole card to itself
0dev.to