Flow Matching with Missing Data
summary
The gist
The gist The Missing-Data Flow Matching method trains flow matching from partially observed data by treating missing coordinates as latent variables, proving that this correction is exact rather than
In short
Missing-Data Flow Matching (MDFM) trains flow matching models directly from data with missing coordinates by treating those missing values as latent variables. It proves this correction is exact, meaning training on incomplete data is mathematically equivalent to training on complete data under certain conditions. This method handles real-world missingness better than standard techniques.
Key concepts
- Flow Matching
- A technique used to train generative models by learning a continuous path between a simple distribution and the target data distribution. It works by matching the learned transition paths of a neural network to the actual data points, allowing for smooth generation of new samples.
- Missing-Data Flow Matching (MDFM)
- A method that addresses missing coordinates in training data by treating them as latent variables. Instead of failing when coordinates are missing, MDFM averages the flow matching loss over all possible values the missing coordinates could take, ensuring the training remains consistent.
- Oracle Objective
- The ideal objective function that would be achieved if one had access to all complete data points. The paper proves that under specific conditions (MCAR), using incomplete data with true completions results in an objective value exactly equal to the objective achieved by using all complete data.
Terminology used across episodes
This episode discusses
- Flow Matching with Missing Data · Paper Radio
- not-MIWAE: Deep Generative Modelling with Missing not at Random Data
- Adam: A Method for Stochastic Optimization
- MissDiff: Training Diffusion Models on Tabular Data with Missing Values
- CFMI: Flow Matching for Missing Data Imputation
The paper
Flow Matching with Missing Data · Read on arXiv
Fairoz Nower Khan, Nabuat Zaman Nahim, Peizhong Ju
Department of Computer Science, University of Kentucky
Transcript
Introduction to the show: ident: AI Radio. Generated commentary on the latest Artificial Intelligence papers.
Tom: I'm Tom, and with me are Jane, Lu, senior AI researcher at Tsinghua, Meng, lead engineer at a mysterious AI startup and Lalam, the in-house Large Language Model.
Jane: Today's paper: "Flow Matching with Missing Data".
Tom: The gist The Missing-Data Flow Matching method trains flow matching from partially observed data by treating missing coordinates as latent variables, proving that this correction is exact rather than approximate.
Jane: First, who's behind it and why it matters.
Paper summary: Tom: Building on that idea of treating missing coordinates as latent variables, the paper "Flow Matching with Missing Data" introduces Missing-Data Flow Matching, or MDFM. They show how this method trains flow matching directly from data where some coordinates are missing, by averaging the loss over those possible values > #pg3.
Jane: The key theoretical finding they establish is that for oracle completions under missing completely at random, the population objective equals complete-data flow matching > #pg2. This means the missingness itself doesn't fundamentally change what flow matching learns from the underlying distribution of your training data > #pg2.
Lu: They also provide a finite-sample variance decomposition showing that one oracle completion matches complete-data variance exactly, and this single completion is optimal if you have a fixed evaluation budget > #pg2.
Meng: From an engineering standpoint, that means we don't need a perfect imputation pipeline upfront; you just need your AI model for filling in the blanks to be really good at capturing the structure of the data because that's where you spend your modeling energy > #pg3.
Tom: So they are saying that if you have a good completion model, its performance is directly tied to how close that completion is to the truth, measured by something called the conditional Wasserstein distance to the truth > #pg3.
Jane: And while they nail the MCAR case, they flag missing not at random scenarios as an open problem because determining the necessary posterior conditions on that missingness mask is generally hard without more structural information > #pg2.
Lalam: This points toward future work where we might need to develop specific techniques for those MNAR scenarios, focusing on identifiability, which could improve how AI systems handle real-world incomplete information > #pg3.
Conclusion: Tom: So wrapping up on "Flow Matching with Missing Data," the authors from Tsinghua University show that this correction for missing data is exact when you have true completions under missing completely at random > #pg2.
Jane: They took standard flow matching, which assumes fully observed training data, and adapted it for situations where some coordinates are missing by treating those coordinates as latent variables > #pg2.
Tom: And the big finding is that training on incomplete data actually works just as well as training on complete data under those specific conditions > #pg2.
Lu: This means missingness itself doesn't fundamentally change what flow matching learns from the underlying distribution of your data, but it does shift the difficulty to how well you can model those missing parts > #pg3.
Meng: For an engineer, that means we just need our AI model for filling in the blanks to be really good at capturing the structure of the data because that's where you spend your modeling effort > #pg3.
Lalam: If you look at how this could improve culture, it suggests that AI systems used in things like drug discovery or climate modeling can handle incomplete information much more robustly than they currently do > #pg3.
Tom: Exactly. But there is one big caveat they bring up, which is missing not at random scenarios where the missingness pattern itself has some hidden structure that’s not completely random > #pg2.
Jane: That MNAR part is still tricky because you need a lot of extra information about why things are missing to figure out what the true distribution actually looks like > #pg2.
Tom: So this paper gives us a strong foundation for MCAR data, but it also clearly shows us where the next big research challenges lie in handling more complex real-world missingness > #pg2.
More episodes
- 2605.28858-An End-to-End PyTorch Interface for Differentiable PDE Solvers: A RANS Model-Correction Study
- 2605.21646-Alike Parts: A Feature-Informed Approach to Local and Global Prototype Explanations
- 2605.19947-Exploiting Non-Negativity in DAG Structure Learning
- 2605.22593-Do Deep Ensembles Actually Capture Uncertainty in Graph Neural Networks?
- 2606.01051-Interaction-Limited Safe Continuous-Time RL for Dynamical Medical Treatment
- 2606.04028-Novel Aspects of IEEE SA P3109 Arithmetic Formats for Machine Learning
- 2606.06818-Terastal: Layer-Variant-based Scheduling for Real-Time Multi-DNN Workloads on Heterogeneous Accelerators
- 2607.24921-Simplex Demixing: Disentangling Multiple Light-Flavor Jets at Colliders
- 2606.10909-Non-linear mechanical field reconstruction coupling recurrent neural networks with physics-informed graph neural networks
- 2606.12487-PhaseQuant: Mitigating Activation Quantization Collapse via Residual-Stream Dynamics