Papers › Deep multi-scale video prediction beyond mean square error

Deep multi-scale video prediction beyond mean square error

17 Nov 2015arXiv:1511.05440archive 2025-07-28

Michael Mathieu, Camille Couprie, Yann Lecun

Learning to predict future images from a video sequence involves the construction of an internal representation that models the image evolution accurately, and therefore, to some degree, its content and dynamics. This is why pixel-space video prediction may be viewed as a promising avenue for unsupervised feature learning. In addition, while optical flow has been a very studied problem in computer vision for a long time, future frame prediction is rarely approached. Still, many vision applications could benefit from the knowledge of the next frames of videos, that does not require the complexity of tracking every pixel trajectories. In this work, we train a convolutional network to generate future frames given an input sequence. To deal with the inherently blurry predictions obtained from the standard Mean Squared Error (MSE) loss function, we propose three different and complementary feature learning strategies: a multi-scale architecture, an adversarial training method, and an image gradient difference loss function. We compare our predictions to different published results based on recurrent neural networks on the UCF101 dataset

PaperPDFCodeCode Syntology ran

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.

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

Code

Syntology 10 code samples harvested from 2 repositories linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 10 samples from 2 repositories, 6 ran (4 with no instrument failure; 2 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 between 2026-09-22 and 2026-09-26 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

AdarshMJ/PredGAN mentioned on GitHubtfSyntology: not harvested report
coupriec/VideoPredictionICLR2016 mentioned on GitHubtorchGPL-3.0Syntology: not harvested report
dyelax/Adversarial_Video_Generation mentioned on GitHubtfMITSyntology: 7 samples, 4 ran (0 instrument-failed) · 3 unverified report
liuem607/DYAN mentioned on GitHubpytorchSyntology: not harvested report
wileyw/VideoGAN mentioned on GitHubpytorchSyntology: 3 samples, 2 ran (2 instrument-failed) · 1 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

10 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 0 honoured, 0 violated, 4 with no contract checked; 2 where Syntology's instrument failed) · 4 unverified. “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.

2ran · our draft was wrong
4ran
4unverified

Licence: 0 of the 10 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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”. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

dyelax/Adversarial_Video_Generation community (archive-listed) 7 samples, 4 ran (0 instrument-failed) · 3 unverified
b in 5 papers Code/tfutils.py ran MIT (permissive) · ea03a354040c8006 · report fixture: signature shape:tuple/1/int, const:float/0/float · returned ResourceVariable · level recorded 2026-09-26
conv_out_size Code/tfutils.py ran MIT (permissive) · 7fbb509ee32c4723 · report fixture: signature i:int/0/int, p:str/0/str, k:int/0/int, s:int/0/int · returned int · level recorded 2026-09-26
denormalize_frames Code/utils.py ran fingerprinted MIT (permissive) · 9f8a9b1faf0c144f · report fixture: signature frames:ndarray/3/float · returned ndarray · level recorded 2026-09-26
get_dir in 14 papers Code/constants.py ran MIT (permissive) · e83222ab4f55b7ad · report fixture: signature directory:str/0/str · returned str · level recorded 2026-09-26
normalize_frames Code/utils.py unverified MIT (permissive) · 1aa2d1529a141acb · report
w Code/tfutils.py unverified MIT (permissive) · 77fde3d5c103dd8c · report
wileyw/VideoGAN community (archive-listed) 3 samples, 2 ran (2 instrument-failed) · 1 unverified
clip_l2_diff process_data.py ran · our draft was wrong fingerprinted MIT (permissive) · 6058e7d6ba3bf3ef · report fixture: signature clip:ndarray/3/float, hist_len:int/0/int · returned float32 · level recorded 2026-09-22
crop_batch inference.py ran · our draft was wrong MIT (permissive) · be76e24e497297f1 · report fixture: signature images:list/1/ndarray, fw:int/0/int, fh:int/0/int, cw:int/0/int, ch:int/0/int · returned ndarray · level recorded 2026-09-22
reconstruct_frame inference.py unverified MIT (permissive) · cc7ac26dfc006739 · report

Tasks

Optical Flow EstimationPredictionVideo Prediction

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