Papers › Efficient Human Pose Estimation via 3D Event Point Cloud

Efficient Human Pose Estimation via 3D Event Point Cloud

9 Jun 2022arXiv:2206.04511archive 2025-07-28

Jiaan Chen, Hao Shi, Yaozu Ye, Kailun Yang, Lei Sun, Kaiwei Wang

Human Pose Estimation (HPE) based on RGB images has experienced a rapid development benefiting from deep learning. However, event-based HPE has not been fully studied, which remains great potential for applications in extreme scenes and efficiency-critical conditions. In this paper, we are the first to estimate 2D human pose directly from 3D event point cloud. We propose a novel representation of events, the rasterized event point cloud, aggregating events on the same position of a small time slice. It maintains the 3D features from multiple statistical cues and significantly reduces memory consumption and computation complexity, proved to be efficient in our work. We then leverage the rasterized event point cloud as input to three different backbones, PointNet, DGCNN, and Point Transformer, with two linear layer decoders to predict the location of human keypoints. We find that based on our method, PointNet achieves promising results with much faster speed, whereas Point Transfomer reaches much higher accuracy, even close to previous event-frame-based methods. A comprehensive set of results demonstrates that our proposed method is consistently effective for these 3D backbone models in event-driven human pose estimation. Our method based on PointNet with 2048 points input achieves 82.46mm in MPJPE3D on the DHP19 dataset, while only has a latency of 12.29ms on an NVIDIA Jetson Xavier NX edge computing platform, which is ideally suitable for real-time detection with event cameras. Code is available at https://github.com/MasterHow/EventPointPose.

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

Syntology 8 code samples harvested from 1 repository linked to this paper: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 4 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 1 repository, 7 ran (3 with no instrument failure; 4 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.

masterhow/eventpointpose officialmentioned in papermentioned on GitHubpytorchMITSyntology: 8 samples, 7 ran (4 instrument-failed) · 1 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

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 0 violated, 3 with no contract checked; 4 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 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 · our draft was wrong
2ran; the contract check could not run
3ran
1unverified

Licence: 3 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. For 3 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 masterhow/eventpointpose. “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.

masterhow/eventpointpose official repository 8 samples, 7 ran (4 instrument-failed) · 1 unverified
adjust_target_weight dataset/DHP19EPC.py ran MIT (permissive) · a21b18dcf8ea0abf · report fixture: signature joint:list/1/float, target_weight:float/0/float, tmp_size:int/0/int, sx:int/0/int, sy:int/0/int · returned float · level recorded 2026-09-24
farthest_point_sample in 64 papers models/PointTrans_tools.py ran; the contract check could not run (RAISES) fingerprinted MIT (permissive) here; the stored copy is pointer only · 295c8424ac32f9cf · report fixture: signature xyz:Tensor/3/float, npoint:int/0/int · returned Tensor · level recorded 2026-09-22
generate_sa_simdr dataset/DHP19EPC.py ran MIT (permissive) · 7abde57071cd0268 · report fixture: signature joints:ndarray/2/float, joints_vis:ndarray/2/float, sigma:int/0/int, sx:int/0/int, sy:int/0/int, num_joints:int/0/int · returned tuple · level recorded 2026-09-24
get_graph_feature in 51 papers
census: 6 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
models/DGCNN.py ran MIT (permissive) · ed56c753ee0b0cf9 · report fixture: signature x:Tensor/3/float, k:int/0/int, idx:NoneType/0/?, cudanum:int/0/int · returned Tensor · level recorded 2026-09-24
index_points in 49 papers models/PointTrans_tools.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 5547bda8a763a5f4 · report fixture: signature points:Tensor/3/float, idx:Tensor/3/int · returned Tensor · level recorded 2026-09-22
knn in 87 papers
census: 12 implementations from 17 papers, 6 distinct outputs across 4 buckets, one shared input per bucket this sample: bucket 1 of 4, arg 1: rank 3, kind float, dtype float32
models/DGCNN.py ran; the contract check could not run (RAISES) · metamorphic tier: invariant fingerprinted MIT (permissive) · cdd0141594039dcb · report fixture: signature x:Tensor/3/float, k:int/0/int · returned Tensor · level recorded 2026-09-22
square_distance in 89 papers
census: 11 implementations from 18 papers, 4 distinct outputs across 2 buckets, one shared input per bucket this sample: bucket 1 of 2, arg 1: rank 3, kind float, dtype float32 · arg 2: rank 3, kind float, dtype float32
models/PointTrans_tools.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 74c3fe06cea2f553 · report fixture: signature src:Tensor/3/float, dst:Tensor/3/float · returned Tensor · level recorded 2026-09-22
generate_label in 8 papers dataset/DHP19EPC.py unverified MIT (permissive) · 4a5bd96c473d7a4d · report

Tasks

3D Human Pose EstimationEdge-computingPlaying the Game of 2048Pose Estimation

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
3D Human Pose Estimation DHP19 Point Transformer GFLOPs 10.06 #1 of 2 Archive leaderboard report
3D Human Pose Estimation DHP19 Point Transformer MPJPE2D 6.46 #1 of 2 Archive leaderboard report
3D Human Pose Estimation DHP19 Point Transformer MPJPE3D 73.37 #1 of 2 Archive leaderboard report
3D Human Pose Estimation DHP19 Point Transformer Params (M) 3.65 #1 of 2 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

Absolute Position EncodingsAdamAttentionBPEDGCNNDense ConnectionsDropoutLabel SmoothingLayer NormalizationLinear LayerMulti-Head AttentionPosition-Wise Feed-Forward LayerResidual ConnectionSoftmaxTransformer

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