Browse State-of-the-Art › Occluded Face Detection

Occluded Face Detection

5 papers with code · 4 benchmarks · 2 datasets archive 2025-07-28

Computer Vision

Benchmarks archive 2025-07-28

4 leaderboard tables shown for this task, 4 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.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
MAFA (2 rows) FAN Face Attention Network: An Effective Face Detector for the Occluded Faces code — Compare
WIDER Face (Easy) (1 row) TinaFace(ResNet-50) TinaFace: Strong but Simple Baseline for Face Detection code — Compare
WIDER Face (Hard) (1 row) TinaFace(ResNet-50) TinaFace: Strong but Simple Baseline for Face Detection code — Compare
WIDER Face (Medium) (1 row) TinaFace(ResNet-50) TinaFace: Strong but Simple Baseline for Face Detection 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

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

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 7 · with a code link: 5 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 7 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 7 of 7, 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.

  • 24 Oct 2018 4 repositories listed
    In this paper, we propose a novel face detection network with three novel contributions that address three key aspects of face detection, including better feature learning, progressive loss design and anchor assign…
  • 26 Nov 2020 2 repositories listed
    Face detection has received intensive attention in recent years.
  • 28 Jun 2015 2 repositories listed
    The presence of occluders significantly impacts object recognition accuracy.
  • 20 Nov 2017 1 repository listed
    The performance of face detection has been largely improved with the development of convolutional neural network.
  • 15 Sep 2017 1 repository listed
    This paper introduces an Adversarial Occlusion-aware Face Detector (AOFD) by simultaneously detecting occluded faces and segmenting occluded areas.
  • Face mask detection project report.
    2 Jul 2025 0 repositories listed
    Recognition from faces is a popular and significant technology in recent years.
  • A Comparative Study of Face Detection Algorithms for Masked Face Detection
    18 May 2023 0 repositories listed
    Contemporary face detection algorithms have to deal with many challenges such as variations in pose, illumination, and scale.

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