Browse State-of-the-Art › Artery/Veins Retinal Vessel Segmentation
Artery/Veins Retinal Vessel Segmentation
3 papers with code · 5 benchmarks · 4 datasets archive 2025-07-28
Artery/Veins (A/V) Retinal vessel segmentation is the task of segmenting vessels in retinal images, while distinguishing between arterioles and venules.
Description from the archive archive 2025-07-28.
Benchmarks archive 2025-07-28
5 leaderboard tables shown for this task, 5 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 |
|---|---|---|---|---|---|
| UZLF (5 rows) | LUNet | LUNet: Deep Learning for the Segmentation of Arterioles and... | code | — | Compare |
| INSPIRE-AVR (LUNet subset) (1 row) | LUNet | LUNet: Deep Learning for the Segmentation of Arterioles and... | code | — | Compare |
| LES-AV (1 row) | RRWNet | RRWNet: Recursive Refinement Network for effective retinal... | code | — | Compare |
| RITE/DRIVE (1 row) | RRWNet | RRWNet: Recursive Refinement Network for effective retinal... | code | — | Compare |
| HRF (1 row) | RRWNet | RRWNet: Recursive Refinement Network for effective retinal... | 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
4 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: 3 · 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 3 tagged papers has a Syntology run on record
Page 1 of 1: papers 1 to 3 of 3, 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 Sep 2024 1 repository listedAdditional CFIs, mainly from the population-based Rotterdam Study were annotated by graders for arteries and veins at pixel level, resulting in a dataset diverse in patient demographics and imaging conditions.
-
5 Feb 2024 1 repository listedThe framework consists of a fully convolutional neural network that recursively refines semantic segmentation maps, correcting manifest classification errors and thus improving topological consistency.
-
LUNet: Deep Learning for the Segmentation of Arterioles and Venules in High Resolution Fundus Images11 Sep 2023 1 repository listedUsing active learning, we created a new DFI dataset containing 240 crowd-sourced manual A/V segmentations performed by fifteen medical students and reviewed by an ophthalmologist, and developed LUNet, a novel deep…
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