Papers › Deep Multi-Task Networks For Occluded Pedestrian Pose Estimation
Deep Multi-Task Networks For Occluded Pedestrian Pose Estimation
Arindam Das, Sudip Das, Ganesh Sistu, Jonathan Horgan, Ujjwal Bhattacharya, Edward Jones, Martin Glavin, Ciarán Eising
Most of the existing works on pedestrian pose estimation do not consider estimating the pose of an occluded pedestrian, as the annotations of the occluded parts are not available in relevant automotive datasets. For example, CityPersons, a well-known dataset for pedestrian detection in automotive scenes does not provide pose annotations, whereas MS-COCO, a non-automotive dataset, contains human pose estimation. In this work, we propose a multi-task framework to extract pedestrian features through detection and instance segmentation tasks performed separately on these two distributions. Thereafter, an encoder learns pose specific features using an unsupervised instance-level domain adaptation method for the pedestrian instances from both distributions. The proposed framework has improved state-of-the-art performances of pose estimation, pedestrian detection, and instance segmentation.
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
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Pose Estimation | COCO test-dev | PPE (ResNeXt-101) | AP | 75.7 | #20 of 47 | Archive leaderboard | report |
| Pose Estimation | COCO test-dev | PPE (ResNeXt-101) | AP50 | 90.3 | #20 of 47 | Archive leaderboard | report |
| Pose Estimation | COCO test-dev | PPE (ResNeXt-101) | AP75 | 76.3 | #20 of 47 | Archive leaderboard | report |
| Pose Estimation | COCO test-dev | PPE (ResNeXt-101) | APL | 79.5 | #20 of 47 | Archive leaderboard | report |
| Pose Estimation | COCO test-dev | PPE (ResNeXt-101) | APM | 80.7 | #20 of 47 | 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.
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