Papers › Diffusion Action Segmentation

Diffusion Action Segmentation

31 Mar 2023ICCV 2023 1arXiv:2303.17959archive 2025-07-28

Daochang Liu, Qiyue Li, AnhDung Dinh, Tingting Jiang, Mubarak Shah, Chang Xu

Temporal action segmentation is crucial for understanding long-form videos. Previous works on this task commonly adopt an iterative refinement paradigm by using multi-stage models. We propose a novel framework via denoising diffusion models, which nonetheless shares the same inherent spirit of such iterative refinement. In this framework, action predictions are iteratively generated from random noise with input video features as conditions. To enhance the modeling of three striking characteristics of human actions, including the position prior, the boundary ambiguity, and the relational dependency, we devise a unified masking strategy for the conditioning inputs in our framework. Extensive experiments on three benchmark datasets, i.e., GTEA, 50Salads, and Breakfast, are performed and the proposed method achieves superior or comparable results to state-of-the-art methods, showing the effectiveness of a generative approach for action segmentation.

PaperPDFConference PDFCodeCode Syntology ranMethod as code

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 9 code samples harvested from 1 repository linked to this paper: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 0 violated, 3 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

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

finspire13/diffact mentioned on GitHubpytorchSyntology: 9 samples, 5 ran (0 instrument-failed) · 4 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

9 samples harvested: 5 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 2 honoured, 0 violated, 3 with no contract checked; 0 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 · honoured contract
3ran
4unverified

Licence: 0 of the 9 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 finspire13/diffact. “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.

finspire13/diffact community (archive-listed) 9 samples, 5 ran (0 instrument-failed) · 4 unverified
MixedConvAttModule model.py ran MIT (permissive) · fd77486cce5e32ae · report fixture: signature x:Tensor/3/float, time_emb:Tensor/2/float, feature_layer_indices:list/1/int · returned tuple · level recorded 2026-09-24
MixedConvAttentionLayer model.py ran MIT (permissive) · ef74b7aaf3b39261 · report fixture: signature x:Tensor/3/float · returned Tensor · level recorded 2026-09-24
MixedConvAttentionLayerV2 model.py ran · metamorphic tier: invariant MIT (permissive) · 32b6836e0fb9fd26 · report fixture: signature x:Tensor/3/float, x_cross:Tensor/3/float · returned Tensor · level recorded 2026-09-22
denormalize in 64 papers
census: 9 implementations from 11 papers, 8 distinct outputs across 4 buckets, one shared input per bucket
model.py ran · honoured contract fingerprinted MIT (permissive) · a26089b06616104c · report fixture: signature x:Tensor/2/float, scale:Tensor/0/float · returned Tensor · level recorded 2026-09-24
normalize in 638 papers
census: 70 implementations from 82 papers, 51 distinct outputs across 11 buckets, one shared input per bucket
model.py ran · honoured contract fingerprinted MIT (permissive) · 2e8cfd3fd1d06402 · report fixture: signature x:Tensor/2/float, scale:float/0/float · returned Tensor · level recorded 2026-09-24
ASDiffusionModel model.py unverified MIT (permissive) · 17f4f458e497d756 · report
DecoderModel in 5 papers model.py unverified MIT (permissive) · d5e99d7e89351b01 · report
EncoderModel model.py unverified MIT (permissive) · e851843728ef46cd · report
MixedConvAttModuleV2 model.py unverified MIT (permissive) · eeea21116921cdb3 · report

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it.

1 assembly on this paper: 1 harvested, 0 generated.

harvested Assembly for Diffusion Action Segmentation (graph method: Diffusion Action Segmentation). 13 bricks; individually on a fixture: 8 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 3 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 5 unverified. The assembly has not been run end-to-end.

  1. ASDiffusionModel entry · level 0 · unverified · 17f4f458e497d756
  2. DecoderModel model · level 0 · unverified · d5e99d7e89351b01
  3. EncoderModel model · level 0 · unverified · e851843728ef46cd
  4. cosine_beta_schedule scheduler · level 1 · ran · honoured contract · 05e94467a0de94a4
  5. denormalize data_transform · level 1 · ran · honoured contract · a26089b06616104c
  6. extract helper · level 0 · unverified · 13c5bb713056a640
  7. normalize data_transform · level 1 · ran · honoured contract · 2e8cfd3fd1d06402
  8. MixedConvAttModuleV2 model · level 0 · unverified · eeea21116921cdb3
  9. get_timestep_embedding helper · level 1 · ran; the contract check could not run · cb49209c125de1b4
  10. swish helper · level 2 · ran · our draft was wrong · 0f786c407fb1ee4c
  11. MixedConvAttModule model · level 1 · ran · fd77486cce5e32ae
  12. MixedConvAttentionLayerV2 model · level 1 · ran · 32b6836e0fb9fd26
  13. MixedConvAttentionLayer model · level 1 · ran · ef74b7aaf3b39261

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2303.17959") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Action SegmentationDenoisingSegmentationTemporal Action Segmentation

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Action Segmentation 50 Salads DiffAct Acc 88.9 #4 of 28 Archive leaderboard report
Action Segmentation 50 Salads DiffAct Edit 85.0 #4 of 28 Archive leaderboard report
Action Segmentation 50 Salads DiffAct F1@10% 90.1 #4 of 28 Archive leaderboard report
Action Segmentation 50 Salads DiffAct F1@25% 89.2 #4 of 28 Archive leaderboard report
Action Segmentation 50 Salads DiffAct F1@50% 83.7 #4 of 28 Archive leaderboard report
Action Segmentation Breakfast DiffAct Acc 76.4 #5 of 37 Archive leaderboard report
Action Segmentation Breakfast DiffAct Average F1 73.6 #5 of 37 Archive leaderboard report
Action Segmentation Breakfast DiffAct Edit 78.4 #5 of 37 Archive leaderboard report
Action Segmentation Breakfast DiffAct F1@10% 80.3 #5 of 37 Archive leaderboard report
Action Segmentation Breakfast DiffAct F1@25% 75.9 #5 of 37 Archive leaderboard report
Action Segmentation Breakfast DiffAct F1@50% 64.6 #5 of 37 Archive leaderboard report
Action Segmentation GTEA DiffAct Acc 82.2 #3 of 28 Archive leaderboard report
Action Segmentation GTEA DiffAct Edit 89.6 #3 of 28 Archive leaderboard report
Action Segmentation GTEA DiffAct F1@10% 92.5 #3 of 28 Archive leaderboard report
Action Segmentation GTEA DiffAct F1@25% 91.5 #3 of 28 Archive leaderboard report
Action Segmentation GTEA DiffAct F1@50% 84.7 #3 of 28 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.

Methods

Diffusion

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