SYNTOLOGY HomeExplorerAtlasCodeMethodologyAboutDevelopersFeedPricing
Paper · 1708.02696 · 2017

What Actions are Needed for Understanding Human Actions in Videos?

arXiv · PDF · Open in the Atlas

Code that ran

5 of 5 samples (functions and classes) lifted from this paper's linked repositories executed on a synthesized input in Syntology's jail (0 of them constructed an object rather than computing a result; 2 honoured the contract we drafted, 1 violated it and 0 have no contract verdict; 2 failures of our instrument; 0 no recorded run), measured 2026-11-22; repository links from the Papers with Code archive attributed under CC BY-SA, no affiliation; bodies inline only under a permissive licence as GitHub detects it. Not a reproduction of the paper's results.

"Ran" means the function executed on a synthesized input and returned a value. It is not a reproduction of the paper's results. This record, dated, as JSON: /api/ran/1708.02696.json · badge: /api/ran/1708.02696.svg

Each repository's role is a label: a classifier's output recorded on the link, or, where no role is recorded, what the Papers with Code archive marked. The line under it names its basis. Neither says who wrote the code.

RepositoryRoleRan
gsig/actions-for-actions canonical (classifier label)
classifier basis: classifier_2025
5 ran · 0 no recorded run
FunctionStatusWhere it lives
loadfile Ran
ran; our contract draft was wrong, not the code
gsig/actions-for-actions/oracles/combine_submissions.py
pointer only (licence: GPL-3.0) · get_code("98baafdbed557c1b")
How it ran

The body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, gsig/actions-for-actions, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

loadfile Ran
ran; our contract draft was wrong, not the code
gsig/actions-for-actions/error_analysis/errorplot.py
pointer only (licence: GPL-3.0) · get_code("c36fd0b89b23c0b1")
How it ran

The body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, gsig/actions-for-actions, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

lookup Ran
ran, honoured the contract we drafted
gsig/actions-for-actions/oracles/combine_submissions.py
pointer only (licence: GPL-3.0) · get_code("5d3d7d25f0d43d38")
How it ran

The body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, gsig/actions-for-actions, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

normme Ran
ran, violated the contract we drafted
gsig/actions-for-actions/oracles/combine_submissions.py
pointer only (licence: GPL-3.0) · get_code("9124fe8c17636a61")
How it ran

The body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, gsig/actions-for-actions, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

parse_actions Ran
ran, honoured the contract we drafted
gsig/actions-for-actions/error_analysis/errorplot.py
pointer only (licence: GPL-3.0) · get_code("23bba5c34cef8ef6")
How it ran

The body of this sample is withheld: GPL-3.0, as GitHub detects it on this paper's repository, gsig/actions-for-actions, is not in the permissive set Syntology serves inline. The setup block that called it is withheld with it, because it is written against that body. source_path and origin say where the code lives, to read under the repository's own terms. A run is recorded.

Also present in other papers' code

Of 5 samples lifted from this paper's linked repositories, 5 carry a function identity and 0 do not. Of the 5 distinct functions with an identity, 0 are also present in other papers whose code we hold (0 with at least one paper dated earlier, 0 the same month, 0 later) and 5 are only here among the 52,977 papers whose code Syntology holds (as of 2026-09-26).

Only here means: among the 52,977 papers whose code Syntology holds (51,887 with lifted samples, 1,090 through their assemblies only), as of 2026-09-26, no other paper's lifted samples or current assembly bricks contain an identical function body after normalisation.

Presence, not direction: an identical function body in two papers' repositories does not say who wrote it, which came from which, or that either paper's method rests on it. Matching is exact after normalisation, so a renamed or edited function is not matched. Dates are when papers appeared, not when code was written. Only .py files the harvester lifted are covered; notebooks are not read. A new-style arXiv id YYMM.NNNN dates a paper to the month 20YY-MM; otherwise Paper.year dates it to the year; otherwise it is undated. Dates are when the paper appeared, not when the code was written. Read 2026-11-22.

Repositories linked to this paper

Some links come from the archived Papers with Code dataset (CC BY-SA 4.0): attribution and licence.

Abstract

What is the right way to reason about human activities? What directions forward are most promising? In this work, we analyze the current state of human activity understanding in videos. The goal of this paper is to examine datasets, evaluation metrics, algorithms, and potential future directions. We look at the qualitative attributes that define activities such as pose variability, brevity, and density. The experiments consider multiple state-of-the-art algorithms and multiple datasets. The results demonstrate that while there is inherent ambiguity in the temporal extent of activities, current datasets still permit effective benchmarking. We discover that fine-grained understanding of objects and pose when combined with temporal reasoning is likely to yield substantial improvements in algorithmic accuracy. We present the many kinds of information that will be needed to achieve substantial gains in activity understanding: objects, verbs, intent, and sequential reasoning. The software and additional information will be made available to provide other researchers detailed diagnostics to understand their own algorithms.

For agents

The same record, over MCP at https://syntology.ai/mcp:

get_harvested_code_for_paper("1708.02696")
get_code_for_paper("1708.02696")
have("1708.02696")

The run record, dated, one paper per request, free:

curl https://syntology.ai/api/ran/1708.02696.json

A badge for a README (the split and the date, never a ratio):

[![Syntology run record](https://syntology.ai/api/ran/1708.02696.svg)](https://syntology.ai/paper/1708.02696)

Connect an agent — have() is free.