Papers › 3D Human Pose Estimation using Spatio-Temporal Networks with Explicit Occlusion Training
3D Human Pose Estimation using Spatio-Temporal Networks with Explicit Occlusion Training
Yu Cheng, Bo Yang, Bo wang, Robby T. Tan
Estimating 3D poses from a monocular video is still a challenging task, despite the significant progress that has been made in recent years. Generally, the performance of existing methods drops when the target person is too small/large, or the motion is too fast/slow relative to the scale and speed of the training data. Moreover, to our knowledge, many of these methods are not designed or trained under severe occlusion explicitly, making their performance on handling occlusion compromised. Addressing these problems, we introduce a spatio-temporal network for robust 3D human pose estimation. As humans in videos may appear in different scales and have various motion speeds, we apply multi-scale spatial features for 2D joints or keypoints prediction in each individual frame, and multi-stride temporal convolutional net-works (TCNs) to estimate 3D joints or keypoints. Furthermore, we design a spatio-temporal discriminator based on body structures as well as limb motions to assess whether the predicted pose forms a valid pose and a valid movement. During training, we explicitly mask out some keypoints to simulate various occlusion cases, from minor to severe occlusion, so that our network can learn better and becomes robust to various degrees of occlusion. As there are limited 3D ground-truth data, we further utilize 2D video data to inject a semi-supervised learning capability to our network. Experiments on public datasets validate the effectiveness of our method, and our ablation studies show the strengths of our network\'s individual submodules.
In Syntology Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.
Code
No code repository is listed for this paper in the archive or in Syntology's graph.
Code Syntology ran Syntology
Not run by Syntology. Nothing on this page verifies that the listed code works.
Tasks
1 archive task tag without a task page not shown.
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| 3D Human Pose Estimation | 3DPW | Spatio-Temporal Network (T=128) | PA-MPJPE | 71.8 | #104 of 119 | Archive leaderboard | report |
| 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Average MPJPE (mm) | 40.1 | #18 of 88 | Archive leaderboard | report |
| 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Multi-View or Monocular | Monocular | #18 of 88 | Archive leaderboard | report |
| 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | PA-MPJPE | 30.7 | #18 of 88 | Archive leaderboard | report |
| 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Using 2D ground-truth joints | No | #18 of 88 | Archive leaderboard | report |
| 3D Human Pose Estimation | HumanEva-I | Spatio-Temporal Network (T=128) | Mean Reconstruction Error (mm) | 13.5 | #3 of 31 | Archive leaderboard | report |
| 3D Human Pose Estimation | MPI-INF-3DHP | Spatio-Temporal Network (T=128) | PCK | 84.1 | #105 of 108 | Archive leaderboard | report |
| Monocular 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Average MPJPE (mm) | 40.1 | #9 of 52 | Archive leaderboard | report |
| Monocular 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Frames Needed | 128 | #9 of 52 | Archive leaderboard | report |
| Monocular 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Need Ground Truth 2D Pose | No | #9 of 52 | Archive leaderboard | report |
| Monocular 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | PA-MPJPE | 30.7 | #9 of 52 | Archive leaderboard | report |
| Monocular 3D Human Pose Estimation | Human3.6M | Spatio-Temporal Network (T=128) | Use Video Sequence | Yes | #9 of 52 | 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
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