Browse State-of-the-Art › Fovea Detection
Fovea Detection
3 papers with code · 4 benchmarks · 3 datasets archive 2025-07-28
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.
| Dataset | Best model (first row in archive order) | Paper | Code | Syntology | Compare |
|---|---|---|---|---|---|
| ADAM (1 row) | HBA-U-Net | U-Net with Hierarchical Bottleneck Attention for Landmark... | code | — | Compare |
| IDRiD (1 row) | HBA-U-Net | U-Net with Hierarchical Bottleneck Attention for Landmark... | code | — | Compare |
| REFUGE (1 row) | HBA-U-Net | U-Net with Hierarchical Bottleneck Attention for Landmark... | code | — | Compare |
| REFUGE Challenge (1 row) | EfficientNet+U-Net++ | Optic Disc, Cup and Fovea Detection from Retinal Images Using... | — | — | 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
3 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.
Papers archive 2025-07-28
archive papers tagged: 8 · with a code link: 3 · 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 8 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 8 of 8, 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.
-
1 Mar 2022 1 repository listedAt the coarse stage, we obtain the OD/OC coarse segmentation and the heatmap localization of fovea through a joint segmentation and detection module.
-
9 Jul 2021 1 repository listedThe network consists of a novel bottleneck attention block that combines and refines self-attention, channel attention, and relative-position attention to highlight retinal abnormalities that may be important for fovea…
-
1 Jul 2018 1 repository listedDiabetic Macular Edema (DME) is an advanced symptom of diabetic retinopathy that affects central vision of diabetes patients.
-
JOINEDTrans: Prior Guided Multi-task Transformer for Joint Optic Disc/Cup Segmentation and Fovea Detection19 May 2023 0 repositories listedDeep learning-based image segmentation and detection models have largely improved the efficiency of analyzing retinal landmarks such as optic disc (OD), optic cup (OC), and fovea.
-
EyeLoveGAN: Exploiting domain-shifts to boost network learning with cycleGANs10 Mar 2022 0 repositories listedThis paper presents our contribution to the REFUGE challenge 2020.
-
20 Nov 2020 0 repositories listedThe accurate detection of retinal structures like an optic disc (OD), cup, and fovea is crucial for the analysis of Age-related Macular Degeneration (AMD), Glaucoma, and other retinal conditions.
-
Fundus Image Analysis for Age Related Macular Degeneration: ADAM-2020 Challenge Report3 Sep 2020 0 repositories listedAge related macular degeneration (AMD) is one of the major causes for blindness in the elderly population.
-
UOLO - automatic object detection and segmentation in biomedical images9 Oct 2018 0 repositories listedWe propose UOLO, a novel framework for the simultaneous detection and segmentation of structures of interest in medical images.
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