Papers › Spatial-Temporal Transformer for Dynamic Scene Graph Generation

Spatial-Temporal Transformer for Dynamic Scene Graph Generation

26 Jul 2021ICCV 2021 10arXiv:2107.12309archive 2025-07-28

Yuren Cong, Wentong Liao, Hanno Ackermann, Bodo Rosenhahn, Michael Ying Yang

Dynamic scene graph generation aims at generating a scene graph of the given video. Compared to the task of scene graph generation from images, it is more challenging because of the dynamic relationships between objects and the temporal dependencies between frames allowing for a richer semantic interpretation. In this paper, we propose Spatial-temporal Transformer (STTran), a neural network that consists of two core modules: (1) a spatial encoder that takes an input frame to extract spatial context and reason about the visual relationships within a frame, and (2) a temporal decoder which takes the output of the spatial encoder as input in order to capture the temporal dependencies between frames and infer the dynamic relationships. Furthermore, STTran is flexible to take varying lengths of videos as input without clipping, which is especially important for long videos. Our method is validated on the benchmark dataset Action Genome (AG). The experimental results demonstrate the superior performance of our method in terms of dynamic scene graphs. Moreover, a set of ablative studies is conducted and the effect of each proposed module is justified. Code available at: https://github.com/yrcong/STTran.

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 14 code samples harvested from 2 repositories linked to this paper: 13 ran (of which 4 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

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

yrcong/sttran officialmentioned in papermentioned on GitHubpytorchMITSyntology: 9 samples, 8 ran (1 instrument-failed) · 1 unverified report
lunaproject22/aar mentioned on GitHubpytorchSyntology: 5 samples, 5 ran (0 instrument-failed) · 0 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

14 samples harvested: 13 ran (of which 4 constructed an object rather than computing a result; 12 with no instrument failure: 0 honoured, 0 violated, 12 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; 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
12ran
1unverified

Licence: 6 of the 14 samples are pointer only, meaning Syntology does not serve that copy's text. For 1 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. 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”. For 1 sample that ran, the graph records a signature this page does not show: for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

yrcong/sttran official repository 9 samples, 8 ran (1 instrument-failed) · 1 unverified
cuda_collate_fn dataloader/action_genome.py ran MIT (permissive) · 3b53b8b24f740103 · report fixture: signature batch:list/1/Tensor · returned Tensor · level recorded 2026-09-25
get_ranking in 11 papers lib/pytorch_misc.py ran MIT (permissive) here; the stored copy is pointer only · a1e587129dd2dfaf · report fixture: signature predictions:Tensor/2/float, labels:Tensor/1/int, num_guesses:int/0/int · returned tuple · level recorded 2026-09-24
im_list_to_blob in 5 papers lib/funcs.py ran MIT (permissive) · d614ca29b05d68ec · report fixture: signature ims:list/1/ndarray · returned ndarray · level recorded 2026-09-25
obj_edge_vectors lib/word_vectors.py ran MIT (permissive) · 3b52f8f6c24ea8da · report fixture: returned Tensor · level recorded 2026-09-25
optimistic_restore in 6 papers lib/pytorch_misc.py ran MIT (permissive) · 6d0daf87a6ec7e39 · report fixture: signature network:callable/0/?, state_dict:dict/0/? · returned bool · level recorded 2026-09-25
pairwise in 27 papers lib/pytorch_misc.py ran · our draft was wrong MIT (permissive) · fef49730c9e9a2b8 · report fixture: signature iterable:list/1/int · returned zip · level recorded 2026-09-24
reporthook in 5 papers lib/word_vectors.py ran MIT (permissive) · e31361e8a2fbb396 · report fixture: signature t:tqdm/0/? · returned function · level recorded 2026-09-25
transpose_packed_sequence_inds lib/funcs.py ran MIT (permissive) · bbdc9c82250ba50d · report fixture: signature lengths:list/1/int · returned tuple · level recorded 2026-09-25
load_word_vectors in 5 papers lib/word_vectors.py unverified MIT (permissive) · 7fee693dfb2f64b5 · report
lunaproject22/aar community (archive-listed) 5 samples, 5 ran (0 instrument-failed) · 0 unverified
TransformerDecoder in 49 papers lib/transformer.py ran · metamorphic tier: deterministic no licence file found · pointer only · 22fd84f6ef1eaa10 · report fixture: returned TransformerDecoder · level recorded 2026-09-22
TransformerDecoderLayer in 45 papers lib/transformer.py ran no licence file found · pointer only · 65aa79798bcd2990 · report fixture: signature query:Tensor/3/float, key:Tensor/3/float, value:Tensor/3/float, key_padding_mask:Tensor/2/bool · returned tuple · level recorded 2026-09-24
TransformerEncoder in 96 papers lib/transformer.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 040179c6bd8eb32f · report fixture: returned TransformerEncoder · level recorded 2026-09-22
TransformerEncoderLayer in 90 papers lib/transformer.py ran · metamorphic tier: deterministic no licence file found · pointer only · cf0d96423bcfe244 · report fixture: returned TransformerEncoderLayer · level recorded 2026-09-22
transformer in 16 papers lib/transformer.py ran · metamorphic tier: deterministic no licence file found · pointer only · 1e8a7993eb1f6599 · report fixture: returned transformer · level recorded 2026-09-22

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 Spatial-Temporal Transformer (STTran) (graph method: Spatial-Temporal Transformer (STTran)). 6 bricks; individually on a fixture: 6 ran (of which 4 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

  1. transformer entry · level 1 · ran · 1e8a7993eb1f6599
  2. TransformerDecoder model · level 1 · ran · 22fd84f6ef1eaa10
  3. TransformerDecoderLayer model · level 1 · ran · 65aa79798bcd2990
  4. TransformerEncoder model · level 1 · ran · 040179c6bd8eb32f
  5. TransformerEncoderLayer model · level 1 · ran · cf0d96423bcfe244
  6. _get_clones helper · level 1 · ran · our draft was wrong · a8f1bbeb369e1829

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="2107.12309") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

DecoderScene Graph GenerationVideo UnderstandingVideo Visual Relation DetectionVisual Relationship Detection

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Absolute Position EncodingsAttentionDense ConnectionsLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionTransformer

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