Papers › ROSE: A Retinal OCT-Angiography Vessel Segmentation Dataset and New Model

ROSE: A Retinal OCT-Angiography Vessel Segmentation Dataset and New Model

10 Jul 2020arXiv:2007.05201archive 2025-07-28

Yuhui Ma, Huaying Hao, Huazhu Fu, Jiong Zhang, Jianlong Yang, Jiang Liu, Yalin Zheng, Yitian Zhao

Optical Coherence Tomography Angiography (OCT-A) is a non-invasive imaging technique, and has been increasingly used to image the retinal vasculature at capillary level resolution. However, automated segmentation of retinal vessels in OCT-A has been under-studied due to various challenges such as low capillary visibility and high vessel complexity, despite its significance in understanding many eye-related diseases. In addition, there is no publicly available OCT-A dataset with manually graded vessels for training and validation. To address these issues, for the first time in the field of retinal image analysis we construct a dedicated Retinal OCT-A SEgmentation dataset (ROSE), which consists of 229 OCT-A images with vessel annotations at either centerline-level or pixel level. This dataset has been released for public access to assist researchers in the community in undertaking research in related topics. Secondly, we propose a novel Split-based Coarse-to-Fine vessel segmentation network (SCF-Net), with the ability to detect thick and thin vessels separately. In the SCF-Net, a split-based coarse segmentation (SCS) module is first introduced to produce a preliminary confidence map of vessels, and a split-based refinement (SRN) module is then used to optimize the shape/contour of the retinal microvasculature. Thirdly, we perform a thorough evaluation of the state-of-the-art vessel segmentation models and our SCF-Net on the proposed ROSE dataset. The experimental results demonstrate that our SCF-Net yields better vessel segmentation performance in OCT-A than both traditional methods and other deep learning methods.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 11 code samples harvested from 1 repository linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 2 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 11 samples from 1 repository, 10 ran (8 with no instrument failure; 2 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 10 samples that ran has no recorded date.

iMED-Lab/OCTA-Net-OCTA-Vessel-Segmentation-Network mentioned on GitHubpytorchApache-2.0Syntology: 11 samples, 10 ran (2 instrument-failed) · 1 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

11 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 8 with no instrument failure: 0 honoured, 0 violated, 8 with no contract checked; 2 where Syntology's instrument failed) · 1 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

2ran · our draft was wrong
8ran
1unverified

Licence: 1 of the 11 samples is pointer only, meaning Syntology does not serve that copy's text. For that sample, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from iMED-Lab/OCTA-Net-OCTA-Vessel-Segmentation-Network. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

iMED-Lab/OCTA-Net-OCTA-Vessel-Segmentation-Network community (archive-listed) 11 samples, 10 ran (2 instrument-failed) · 1 unverified
Crop code/OCTA-Net/fundus_dataset.py ran Apache-2.0 (permissive) · bca69db90e38dc43 · report fixture: signature image:Image/0/?, label:Image/0/?, mask:Image/0/?, max_attempts:int/0/int, crop_size:tuple/1/int · returned tuple · level recorded 2026-09-24
build_loss in 8 papers code/OCTA-Net/losses.py ran Apache-2.0 (permissive) · 70bab76a9adb7f32 · report fixture: signature loss:str/0/str · returned focal_loss · level recorded 2026-09-24
calc_auc in 5 papers code/OCTA-Net/evaluation.py ran Apache-2.0 (permissive) · f1a1dc397cac1ca3 · report fixture: signature pred_arr:ndarray/2/float, gt_arr:ndarray/2/int, mask_arr:ndarray/2/int · returned float · level recorded 2026-09-24
clip_by_tensor in 6 papers code/OCTA-Net/losses.py ran fingerprinted Apache-2.0 (permissive) · a6980e3ba0fcef1c · report fixture: signature t:Tensor/2/float, t_min:Tensor/0/float, t_max:Tensor/0/float · returned Tensor · level recorded 2026-09-24
deconv in 48 papers code/OCTA-Net/imed_models.py ran · our draft was wrong Apache-2.0 (permissive) · b528298ef3ced2c0 · report fixture: signature in_channels:int/0/int, out_channels:int/0/int · returned ConvTranspose2d · level recorded 2026-09-22
extract_mask in 6 papers code/OCTA-Net/evaluation.py ran Apache-2.0 (permissive) · 32bab0b40aa74387 · report fixture: signature pred_arr:ndarray/2/float, gt_arr:ndarray/2/int, mask_arr:ndarray/2/int · returned tuple · level recorded 2026-09-24
linear_stretch code/OCTA-Net/fundus_dataset.py ran fingerprinted Apache-2.0 (permissive) · f65d403bcfc1c4b1 · report fixture: signature img_arr:ndarray/2/float · returned ndarray · level recorded 2026-09-24
paint_border_overlap code/OCTA-Net/fundus_dataset.py ran Apache-2.0 (permissive) · d44fedcfc25f202f · report fixture: signature full_img:ndarray/2/float, crop_size:tuple/1/int, stride:tuple/1/int · returned ndarray · level recorded 2026-09-24
random_crop in 59 papers code/OCTA-Net/octa_dataset.py ran Apache-2.0 (permissive) · 42834384f9d9373b · report fixture: signature image:Image/0/?, label:Image/0/?, crop_size:tuple/1/int · returned tuple · level recorded 2026-09-24
short_hash in 15 papers code/OCTA-Net/resnest.py ran · our draft was wrong Apache-2.0 (permissive) here; the stored copy is pointer only · 979123ace229d553 · report fixture: signature name:str/0/str · returned str · level recorded, date not recorded
numeric_score code/OCTA-Net/evaluation.py unverified Apache-2.0 (permissive) · 3abdf9144e7b2061 · report

Tasks

Retinal Vessel SegmentationSegmentation

Datasets

Introduced by this paper, per the archive.

ROSE

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Retinal Vessel Segmentation ROSE-1 DVC OCTA-Net Dice Score 70.74 #1 of 5 Archive leaderboard report
Retinal Vessel Segmentation ROSE-1 SVC OCTA-Net Dice Score 76.97 #2 of 5 Archive leaderboard report
Retinal Vessel Segmentation ROSE-1 SVC-DVC OCTA-Net Dice Score 75.76 #2 of 5 Archive leaderboard report
Retinal Vessel Segmentation ROSE-2 OCTA-Net Dice Score 70.77 #2 of 5 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