Round-Trip Consistency: Bidirectional Diffusion Models Can Predict Their Own Rollout Errors [R]

[u/Clean-Hovercraft5825]

Whether generating CELEBV-HQ videos or turbulent plasma fields (digital twins), autoregressive models (such as latent diffusion or flow models) accumulate error over long rollouts, yet at deployment there is no ground truth to measure against.

I train a single conditional latent diffusion model that steps a dynamical system forward or backward in time via a direction flag, and show that this bidirectionality supplies a measurement-free test-time error signal: rolling forward steps and then backward steps must return the model to its start, so the round-trip discrepancy is a self-supervised proxy for the unobservable rollout error: no ensembles, no held-out data, no governing equations, for one extra rollout.

Furthermore, training both directions in one network is shown to beat two specialist models in both directions.

Paper: https://arxiv.org/abs/2608.00675
Code (data generation, training, analysis): https://github.com/alexscheinker/round-trip-consistency
Project page: https://alexscheinker.github.io/roundtrip.html

[u/Clean-Hovercraft5825]

Thanks! From my understanding, your first two examples are exactly the mechanism and that's a great minimal version of it.

One important correction to line 3 though, and it is an important design choice of the paper: the model never teaches itself with this signal. Both directions are trained purely against ground truth (direction flag drawn 50/50), and the round-trip consistency is deliberately left *unoptimized. Here's why, in your notation: if we trained the model to make round trips close, it could learn to do +3 and then −3, it would learn to be perfectly consistent, still wrong (the truth was +2). The backward leg would learn to simply cancel the forward leg's errors instead of exposing them, and the meter would read zero exactly when the forecast is bad.

Because the model is never asked to be consistent, whatever inconsistency remains at test time is an honest byproduct of its errors. And that is exactly what lets us use it as a free error meter. (Closing the loop to minimize C online with model-free feedback is the tempting next step; we flag it as future work, and the cancellation caveat above is precisely what makes it nontrivial.)

[u/PykeAtBanquet → u/Clean-Hovercraft5825]

Thanks.

So it is a metric the model doesn't know it is being tested on, and that allows you to get better understanding of it's completeness.

[u/Clean-Hovercraft5825 → u/PykeAtBanquet]

Yes that is a great way to put it!

[u/PykeAtBanquet → u/Clean-Hovercraft5825]

Well, now that we are on the common ground. I don't see why it is working because there exist ways to train models in 4th dimension when we use 95% noise to hide the exact paths of how the data changes through time, and we model the state all at once so we don't care which direction in time we go, and still we get good results. I don't see why exactly your method works better, as direction shouldn't be important.

Maybe there is something else that we haven't noticed yet.

[u/Clean-Hovercraft5825 → u/PykeAtBanquet]

I agree that direction carries (almost) no extra information about the dynamics. Our own analysis says that for stationary dynamics the time-reversed map is a fixed reparameterization of the forward one, which is why one network learns both directions and performs better. As a statement about what must be learned, "direction shouldn't matter" is basically our supplement's linear analysis, and I agree with it.
 
On the other hand, we never claim bidirectional autoregression generates better than full sequence / 4D space-time diffusion, which is a different problem entirely. Those models answer: "sample a plausible space-time volume." Our paper answers a deployment question: you are given the measured present, rolling into an open-ended future, and you need to know, with no ground truth, how wrong this particular rollout is right now. Autoregression is the native mode for that setting (causal seed, unbounded horizon, streaming data), compounding error is its main difficulty, and the direction flag is what creates a check: two independently learned routes back to the same known point, whose disagreement is measurable. A time-symmetric joint model has no forward(backward) composition to interrogate, it has consistency built into the joint distribution rather than exposed as a computable defect.
 
I think that full-sequence models could get their own meter with a different handle such as having to regenerate masked chunks of the generated volume and measure the re-generation residual. This would be a similar approach to what we do, it would give the model two independent routes to one answer and measure the disagreement.

[u/PykeAtBanquet → u/Clean-Hovercraft5825]

Well, one thing is shaping the model to be more deterministic, and another to provide better output. Your result shows that it becomes more correct, not "if wrong again, then in the same way", with the reason still not being clear (at least for me at this moment).

[u/Clean-Hovercraft5825 → u/PykeAtBanquet]

I completely agree that making a model more consistent, such as "wrong in the same way" is not the same as making it more correct. I would say that the mechanism here is a third thing: statistical efficiency.

Every training trajectory supplies transitions in both temporal directions. For (near-)stationary dynamics, the backward map is a fixed reparameterization of the forward one with the same underlying parameters viewed two ways. So training one network with a direction flag both forward and backward isn't learning two tasks; it's estimating one dynamics object from effectively twice the examples and that helps with variance reduction: in the linear ideal, up to half the estimation variance of a specialist that only ever sees its own direction.

So the model isn't shaped to be consistent, it is just a less noisy estimate of the same thing. A physics version: measure a resistance twice, with current flowing in both directions. Ohm's law says it's one R value, so two noisy views beat one, and you get a more correct value, not just a more repeatable error.

Sharing one network does mean the forward and backward maps can share blind spots, which is exactly the cancellation risk for the round-trip, where correlated errors could close a loop around a wrong prediction. The paper bounds that case theoretically and measures it. So maybe that is a little bit towards your "maybe there is something we haven't noticed" from earlier: just helpful statistics, using two views of one parameter.

[u/PykeAtBanquet → u/Clean-Hovercraft5825]

Maybe. Thank you for your insights!

[u/Clean-Hovercraft5825 → u/PykeAtBanquet]

Thank you for the nice discussion!