Browse State-of-the-Art › Gesture Recognition

Gesture Recognition

149 papers with code · 13 benchmarks · 15 datasets archive 2025-07-28

Computer Vision

Gesture Recognition is an active field of research with applications such as automatic recognition of sign language, interaction of humans and robots or for new ways of controlling video games.

Source: Gesture Recognition in RGB Videos Using Human Body Keypoints and Dynamic Time Warping

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

13 leaderboard tables shown for this task, 13 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted. 10 shown of 13 until expanded.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
DVS128 Gesture (14 rows) TENNs-PLEIADES TENNs-PLEIADES: Building Temporal Kernels with Orthogonal Polynomials code — Compare
CapgMyo DB-a (1 row) 2SRNN Domain Adaptation for sEMG-based Gesture Recognition with... code — Compare
CapgMyo DB-b (1 row) 2SRNN Domain Adaptation for sEMG-based Gesture Recognition with... code — Compare
CapgMyo DB-c (1 row) 2SRNN Domain Adaptation for sEMG-based Gesture Recognition with... code — Compare
ChaLearn 2013 (1 row) 3S Net TTM Skeleton-based Gesture Recognition Using Several Fully Connected... code — Compare
Chalearn 2014 (1 row) 3D-CNN + LSTM Learning Deep and Compact Models for Gesture Recognition code — Compare
ChaLearn 2016 (1 row) 3S Net TTM Skeleton-based Gesture Recognition Using Several Fully Connected... code — Compare
GesturePod (1 row) GesturePod GesturePod: Enabling On-device Gesture-based Interaction for White... code — Compare
Montalbano (1 row) Temp Conv + LSTM Beyond Temporal Pooling: Recurrence and Temporal Convolutions for... code — Compare
MSRC-12 (1 row) 3S Net TTM Skeleton-based Gesture Recognition Using Several Fully Connected... code — Compare
Ninapro DB-1 12 gestures (1 row) 2SRNN Domain Adaptation for sEMG-based Gesture Recognition with... code — Compare
Ninapro DB-1 8 gestures (1 row) 2SRNN Domain Adaptation for sEMG-based Gesture Recognition with... code — Compare
SHREC 2017 track on 3D Hand Gesture Recognition (1 row) PointLSTM An Efficient PointLSTM for Point Clouds Based Gesture Recognition code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

15 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

3 subtasks in the archive's task tree.

Papers archive 2025-07-28

archive papers tagged: 572 · with a code link: 149 · where Syntology ran a sample: 13 (10 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran (13 of 572 tagged: 10 with a run with no instrument failure, 3 where every run was a failure of Syntology's instrument)

Page 1 of 6: papers 1 to 100 of 572, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from. The first sentence of the abstract is shown for the first 30 papers; every abstract is on its paper's page.

Syntology lines on 11 of the papers shown; no Syntology record for the others (a paper without an arXiv id cannot be joined to the graph, and absence from the graph layer is not a recorded non-run). “Ran” means the sample executed on a synthesized fixture, not that the paper's result was reproduced; each line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

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