Papers › Deep Reinforcement Learning for Unsupervised Video Summarization with...

Deep Reinforcement Learning for Unsupervised Video Summarization with Diversity-Representativeness Reward

29 Dec 2017arXiv:1801.00054archive 2025-07-28

Kaiyang Zhou, Yu Qiao, Tao Xiang

Video summarization aims to facilitate large-scale video browsing by producing short, concise summaries that are diverse and representative of original videos. In this paper, we formulate video summarization as a sequential decision-making process and develop a deep summarization network (DSN) to summarize videos. DSN predicts for each video frame a probability, which indicates how likely a frame is selected, and then takes actions based on the probability distributions to select frames, forming video summaries. To train our DSN, we propose an end-to-end, reinforcement learning-based framework, where we design a novel reward function that jointly accounts for diversity and representativeness of generated summaries and does not rely on labels or user interactions at all. During training, the reward function judges how diverse and representative the generated summaries are, while DSN strives for earning higher rewards by learning to produce more diverse and more representative summaries. Since labels are not required, our method can be fully unsupervised. Extensive experiments on two benchmark datasets show that our unsupervised method not only outperforms other state-of-the-art unsupervised methods, but also is comparable to or even superior than most of published supervised approaches.

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

The archive's official repository (KaiyangZhou/vsumm-reinforce) was not harvested; the 1 sample below comes from 1 community repository.

Syntology 1 code sample harvested from 1 repository linked to this paper: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code. Every run on this page is a failure of Syntology's instrument, not of the code.

By repository: community (archive-listed): 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

KaiyangZhou/vsumm-reinforce officialmentioned in papermentioned on GitHubpytorchSyntology: not harvested report
HoganZhang/pytorch-vsumm-reinforce mentioned on GitHubpytorchSyntology: not harvested report
KaiyangZhou/pytorch-vsumm-reinforce mentioned on GitHubpytorchSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
n9839950/EGH400-2-DSN mentioned on GitHubpytorchSyntology: not harvested report
neda60/video-summarization-using-FCSN mentioned on GitHubpytorchSyntology: not harvested report
ymlwww/rlproject mentioned on GitHubpytorchSyntology: not harvested 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

1 sample harvested: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Every run on this page is a failure 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.

1ran · our draft was wrong

Licence: 0 of the 1 sample 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 KaiyangZhou/pytorch-vsumm-reinforce. “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.

KaiyangZhou/pytorch-vsumm-reinforce community (archive-listed) 1 sample, 1 ran (1 instrument-failed) · 0 unverified
split_random create_split.py ran · our draft was wrong fingerprinted MIT (permissive) · c8b52d13ddb9702b · report fixture: signature keys:list/1/str, num_videos:int/0/int, num_train:int/0/int · returned tuple · level recorded 2026-09-22

Tasks

Decision MakingDeep Reinforcement LearningDiversityReinforcement LearningReinforcement Learning (RL)Sequential Decision MakingSupervised Video SummarizationUnsupervised Video SummarizationVideo Summarizationreinforcement-learning

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Supervised Video Summarization SumMe DR-DSN F1-score (Augmented) 43.9 #20 of 21 Archive leaderboard report
Supervised Video Summarization SumMe DR-DSN F1-score (Canonical) 42.1 #20 of 21 Archive leaderboard report
Supervised Video Summarization TvSum DR-DSN F1-score (Augmented) 59.8 #20 of 21 Archive leaderboard report
Supervised Video Summarization TvSum DR-DSN F1-score (Canonical) 58.1 #20 of 21 Archive leaderboard report
Unsupervised Video Summarization SumMe DR-DSN F1-score 41.4 #10 of 10 Archive leaderboard report
Unsupervised Video Summarization SumMe DR-DSN Parameters (M) 2.63 #10 of 10 Archive leaderboard report
Unsupervised Video Summarization SumMe DR-DSN training time (s) 19.8 #10 of 10 Archive leaderboard report
Unsupervised Video Summarization TvSum DR-DSN F1-score 57.6 #7 of 8 Archive leaderboard report
Unsupervised Video Summarization TvSum DR-DSN Kendall's Tau 0.020 #7 of 8 Archive leaderboard report
Unsupervised Video Summarization TvSum DR-DSN Parameters (M) 2.63 #7 of 8 Archive leaderboard report
Unsupervised Video Summarization TvSum DR-DSN Spearman's Rho 0.026 #7 of 8 Archive leaderboard report
Unsupervised Video Summarization TvSum DR-DSN training time (s) 58.8 #7 of 8 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

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