Papers › Skin Lesion Analysis Toward Melanoma Detection 2018: A Challenge Hosted by the...

Skin Lesion Analysis Toward Melanoma Detection 2018: A Challenge Hosted by the International Skin Imaging Collaboration (ISIC)

9 Feb 2019arXiv:1902.03368archive 2025-07-28

Noel Codella, Veronica Rotemberg, Philipp Tschandl, M. Emre Celebi, Stephen Dusza, David Gutman, Brian Helba, Aadi Kalloo, Konstantinos Liopyris, Michael Marchetti, Harald Kittler, Allan Halpern

This work summarizes the results of the largest skin image analysis challenge in the world, hosted by the International Skin Imaging Collaboration (ISIC), a global partnership that has organized the world's largest public repository of dermoscopic images of skin. The challenge was hosted in 2018 at the Medical Image Computing and Computer Assisted Intervention (MICCAI) conference in Granada, Spain. The dataset included over 12,500 images across 3 tasks. 900 users registered for data download, 115 submitted to the lesion segmentation task, 25 submitted to the lesion attribute detection task, and 159 submitted to the disease classification task. Novel evaluation protocols were established, including a new test for segmentation algorithm performance, and a test for algorithm ability to generalize. Results show that top segmentation algorithms still fail on over 10% of images on average, and algorithms with equal performance on test data can have different abilities to generalize. This is an important consideration for agencies regulating the growing set of machine learning tools in the healthcare domain, and sets a new standard for future public challenges in healthcare.

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 17 code samples harvested from 3 repositories linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 11 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): 17 samples from 3 repositories, 6 ran (4 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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. 2 of the 6 samples that ran have no recorded date.

18 repositories listed; official and paper-mentioned ones first.

MiguelC23/XAI-Skin-Cancer-Detection-A-Prototype-Based-Deep-Learning-Architecture-with-Non-Expert-Supervision mentioned on GitHubpytorchMITSyntology: 6 samples, 2 ran (2 instrument-failed) · 4 unverified report
NoelleI/Melanoma mentioned on GitHubtfSyntology: not harvested report
NoelleI/Pigmentation mentioned on GitHubSyntology: not harvested report
Woodman718/FixCaps mentioned on GitHubpytorchMITSyntology: 9 samples, 3 ran (0 instrument-failed) · 6 unverified report
XtraHamster/SKCAN mentioned on GitHubtfSyntology: not harvested report
adityathakurxd/shades mentioned on GitHubtfApache-2.0Syntology: not harvested report
datascisteven/Melanoma-Detector mentioned on GitHubtfMITSyntology: 2 samples, 1 ran (0 instrument-failed) · 1 unverified report
datascisteven/Melanoma-Image-Classification mentioned on GitHubtfMITSyntology: not harvested report
datawithgladys/skin_lesion_diagnosis_classification mentioned on GitHubtfSyntology: not harvested report
examsherpa/Melanoma-Image-Classification mentioned on GitHubtfMITSyntology: not harvested report
kianoush/Skin_Cancer_CNN mentioned on GitHubSyntology: not harvested report
leona-ha/Skin-Screening_Web-App mentioned on GitHubtfSyntology: not harvested report
lucasgb2/skinlession mentioned on GitHubSyntology: not harvested report
marinbenc/medical-polar-training mentioned on GitHubpytorchSyntology: not harvested report
mxn170019/Skin-Cancer-Identification-Tensorflow-CNN mentioned on GitHubtfSyntology: not harvested report
richmondvan/melanoma-detection mentioned on GitHubApache-2.0Syntology: not harvested report
samirsalman/SkinCancer-Machine_Learning_Project mentioned on GitHubSyntology: not harvested report
sauravmishra1710/EXPLAINABLE-AI---Skin-Cancer-Detection-explained-with-GRADCAM mentioned on GitHubtfSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Grad-CAM: Visual Explanations from Deep Networks via Gradient-based Localization (arXiv:1610.02391; that paper's own run record: 90 ran (of which 32 constructed an object rather than computing a result; 62 with no instrument failure: 6 honoured, 4 violated, 52 with no contract checked; 28 where Syntology's instrument failed) · 51 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

17 samples harvested: 6 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 1 honoured, 0 violated, 3 with no contract checked; 2 where Syntology's instrument failed) · 11 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.

1ran · honoured contract
2ran · our draft was wrong
3ran
11unverified

Licence: 2 of the 17 samples are pointer only, meaning Syntology does not serve that copy's text. For 2 of them, 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 3 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

MiguelC23/XAI-Skin-Cancer-Detection-A-Prototype-Based-Deep-Learning-Architecture-with-Non-Expert-Supervision community (archive-listed) 6 samples, 2 ran (2 instrument-failed) · 4 unverified
conv1x1 in 691 papers 1CP_BinaryProblem/resnet_features.py ran · our draft was wrong MIT (permissive) · d9def42110729a85 · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded, date not recorded
conv3x3 in 1,376 papers 1CP_BinaryProblem/resnet_features.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · fac5364e2f53c6db · report fixture: signature in_planes:int/0/int, out_planes:int/0/int, stride:int/0/int · returned Conv2d · level recorded, date not recorded
densenet121_features in 5 papers 1CP_BinaryProblem/densenet_features.py unverified MIT (permissive) · d5149ec5f0e567e9 · report
densenet169_features in 5 papers 1CP_BinaryProblem/densenet_features.py unverified MIT (permissive) · cf20cbc234ba341a · report
densenet201_features in 5 papers 1CP_BinaryProblem/densenet_features.py unverified MIT (permissive) · 3803a12204298d72 · report
resnet18_features in 5 papers 1CP_BinaryProblem/resnet_features.py unverified MIT (permissive) · 94b612209067f3e5 · report
Woodman718/FixCaps community (archive-listed) 9 samples, 3 ran (0 instrument-failed) · 6 unverified
autopad in 36 papers Module/model410.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · 988a3c854b1b13d0 · report fixture: signature k:int/0/int, p:NoneType/0/? · returned int · level recorded 2026-09-22
one_hot in 150 papers
census: 18 implementations from 25 papers, 10 distinct outputs across 6 buckets, one shared input per bucket
Module/HAM10000/utils.py ran MIT (permissive) · f613c916edc5a87c · report fixture: signature x:Tensor/1/int, length:int/0/int · returned Tensor · level recorded 2026-09-24
squash in 30 papers
census: 8 implementations from 5 papers, 4 distinct outputs across 2 buckets, one shared input per bucket
Module/model410.py ran fingerprinted MIT (permissive) · b4eecff210748e3b · report fixture: signature s:Tensor/3/float · returned Tensor · level recorded 2026-09-24
make_features Module/model410.py unverified MIT (permissive) · f9c9e4fe5c1a8fcd · report
make_features Module/model501.py unverified MIT (permissive) · ff3bba7a352a6b09 · report
make_features Module/COVID-19/model611.py unverified MIT (permissive) · c43d325c73c349a2 · report
make_features Module/HAM10000/model.py unverified MIT (permissive) · 0f2733da4d03102f · report
make_features Module/HAM10000/model_1028.py unverified MIT (permissive) · 07c104644e1a6805 · report
make_features Module/NCT-CRC-HE-100K-NONORM/model.py unverified MIT (permissive) · 04b48f22fb99a49a · report
datascisteven/Melanoma-Detector community (archive-listed) 2 samples, 1 ran (0 instrument-failed) · 1 unverified
stratified_sample_report utils.py ran MIT (permissive) · ea4c68fb7406e3dd · report fixture: signature df:DataFrame/0/?, strata:list/1/str, size:NoneType/0/? · returned DataFrame · level recorded 2026-09-24
stratified_sample in 10 papers utils.py unverified MIT (permissive) · 9b0434206a958b83 · report

Tasks

AttributeLesion SegmentationSegmentation

Datasets

Introduced by this paper, per the archive.

ISIC 2018 Task 1ISIC 2018 Task 2ISIC 2018 Task 3Lesion Boundary Segmentation Dataset

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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