- Rating
- 4(+1)
- Confidence
- 2
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 2
Read review
Paper summary
This paper studies continual learning for flow-matching generative models, aiming to learn new tasks while preserving earlier ones without replaying stored training samples. It is motivated by the cost of generating replay samples and the errors that can accumulate when these samples are used for later updates. The proposed trajectory replay method trains the new model to match a frozen historical model at intermediate points along its generation trajectories. It combines this supervision with learning from the incoming data. A MeanFlow extension reduces the sampling work needed to obtain these intermediate states. The paper provides a theoretical interpretation of how the update balances old and new tasks. Experiments cover synthetic distributions, class-incremental image generation, single-cell perturbation modeling, and microscopy batch streams, reporting improvements in sample quality, retention, and replay efficiency.
Critical strengths
I find the method intuitive and well motivated. It addresses both forgetting and the cost of replay by learning from intermediate teacher states instead of fully generated samples. The analysis explains how old and new tasks are balanced under ideal assumptions. The experiments support improved retention and sample quality across several settings, including when replay weights follow a simple rule without validation-based tuning.
The evaluation combines controlled simulations with image generation and biological applications, allowing the method to be assessed beyond a single benchmark. The reported runtime comparisons support a practical benefit over online generative replay. The MeanFlow experiments also show that trajectory replay can often use fewer sampling steps while maintaining similar performance. This is useful when teacher sampling is expensive, although the additional training overhead means MeanFlow is not always faster.
Critical weaknesses
-
The current comparisons leave some uncertainty about what produces the gains. The method changes both how replay states are obtained and how the student learns from the teacher. However, the closest distillation baseline uses a different generative framework. The theory explains the intended mixture under ideal assumptions, but does not establish which change accounts for the practical improvement. The replay methods also allocate different proportions of each batch to old and new tasks. A comparison that controls these choices would make the contribution of trajectory replay clearer.
-
The microscopy evaluation does not directly establish whether the model preserves the response to each perturbation. The reported scores compare image distributions after pooling across perturbations. These scores would not change if generated images were reassigned to different perturbations within the same experimental batch. This limits the evidence for preserving treatment responses, although the results still support improved retention of batch-level image distributions. The latest batch also shows slightly worse sample quality than generative replay in the reported comparison, despite better retention of older batches. This trade-off should be discussed alongside the overall improvement.
Questions for authors
1.Could you add a flow-matching version of generative distillation that generates teacher samples, adds noise back to them, and matches the teacher’s velocity predictions? Keeping the teacher, training setup, replay weighting, and old/new sample allocation matched would help isolate the benefit of sampling along the teacher’s trajectories. Please compare sample quality, retention, and actual training time under these matched conditions.
2.Could you provide an evaluation that checks whether generated microscopy images reflect the intended perturbations, beyond matching the overall image distribution? A measure that detects incorrect perturbation labels would address this concern. Otherwise, please narrow the microscopy conclusion to the distributional retention supported by the current evaluation.
3.Could you clarify which data are used to select the adaptive replay weight in the transcriptomics experiments? The methods refer to training strata, while the table captions refer to validation. Please explain whether these are separate data and what historical information must remain available. The paper already allows old-task validation data, so the question is which conclusions apply when that information is unavailable.
5 comments
Rebuttal comment 2
W2a / Q2. Perturbation-level fidelity on RxRx1
We thank the reviewer for this suggestion. Our pooled evaluation follows Zhang et al. (2025) and Jones et al. (2026), generating one image per test condition so that generated and reference sets share the same perturbation-by-batch composition. We agree that pooled scores are invariant to reassigning images across perturbations, and so establish retention of batch-level distributions rather than of individual treatment responses.
We therefore compared the final checkpoints of trajectory replay and generative replay per perturbation (new Table 15). In each batch (U2OS-01, -02, -03), we generated images for the 100 evaluation perturbations and the negative control, and compared them with real test images of that batch in DINOv2 space, using two measures that collapse under reassignment:
- Effect retrieval. Each perturbation's effect is its mean feature minus the batch's control mean. We report top-5 accuracy of retrieving the real effect among the 100 perturbations by cosine similarity, against a within-batch label-shuffle null (chance 0.05).
- Conditional KID between each perturbation's generated images and real images of the same (matched) or other (mismatched) perturbations, averaged over perturbations. KID is unbiased at these small sample sizes (about 32 generated and 50 real images), unlike FID.
Both methods preserve perturbation-specific signal: retrieval lies far above the null for every seed (), and generated images are always closer in KID to their own perturbation than to others. Trajectory replay, however, preserves it better on the older batches, with higher retrieval (0.40 vs. 0.30 on U2OS-01, 0.27 vs. 0.23 on U2OS-02) and lower KID (2.47 vs. 4.06 and 1.54 vs. 2.28), while the two methods are on par on the latest batch, U2OS-03 (0.40 vs. 0.38 retrieval, 1.76 vs. 1.75 KID).
Paper edits. We added the perturbation-level evaluation to App. D.6 (Table 15).
W2b. Trade-off on the latest batch
We agree this should be discussed. On the newest batch (U2OS-03), trajectory replay trails generative replay by 1–2 FID points (28.6–28.8 vs. 27.0–27.7; Table 14), while retaining earlier batches far better: about 30 FID points on U2OS-01 and 4 on U2OS-02, for a 5-point gain on the pooled stream. Since the newest data is available during the update, naive fine-tuning, generative replay and trajectory replay all fit it within a narrow range (26.0–28.9 FID, close to joint training's 26.6), whereas retention is where they differ. We view this small cost as the stability–plasticity trade-off inherent to replay. At the perturbation level, the two methods are on par on this batch (Table 15; see W2a).
Paper edits. We now discuss the latest-batch trade-off in App. D.6.2.
Q3. Data used for adaptive replay weight selection
We thank the reviewer for catching this inconsistency. Adaptive is selected on validation cells held out from each training stratum, i.e., cells from the same context–perturbation categories seen during training that are not used to train the model. The term "training strata" in App. D.5.1 and Table 9 refers to these categories rather than to the training cells themselves.
Regarding historical information, adaptive selection therefore requires held-out cells from past tasks, used only to score candidate weights and never for training. When no historical data is available, the equal-task schedule applies, as it requires no data at all, and the corresponding rows of Tables 11 and 12 show the results that hold in that setting.
Paper edits. We clarified in App. D.5.1 and Table 9 that selection uses held-out validation cells.
Dear Reviewer mPkD,
Thank you again for your detailed suggestions. Before the discussion period closes on November 18 (AoE), we wanted to briefly follow up. We ran the controlled comparisons you asked for (matched distillation in Fig. 19, batch allocation in Table 8) and a perturbation-level evaluation on RxRx1 (Table 15).
We would be grateful to hear whether this resolves your concerns, and are happy to clarify anything further.
The Authors
Rebuttal comment 1
We thank mPkD for taking the time to review our submission. We appreciate the overall positive feedback and the valuable suggestions to improve the quality and breadth of our contribution. Changes are highlighted in red in the updated manuscript.
Before presenting the additional experiments, we would like to clarify one point. Generative distillation already uses the same even old/new split with loss weighting as trajectory replay, so batch allocation differs only for generative replay, which we control for in W1b.
We ran the requested controlled comparisons.
Paper edits. We report the matched distillation comparison (new Fig. 19) and the batch-allocation control (Table 8) in App. D.3.2, and summarize the former in Sec. 4.3.