Papers › A Machine Learning Benchmark for Facies Classification

A Machine Learning Benchmark for Facies Classification

12 Jan 2019arXiv:1901.07659archive 2025-07-28

Yazeed Alaudah, Patrycja Michalowicz, Motaz Alfarraj, Ghassan AlRegib

The recent interest in using deep learning for seismic interpretation tasks, such as facies classification, has been facing a significant obstacle, namely the absence of large publicly available annotated datasets for training and testing models. As a result, researchers have often resorted to annotating their own training and testing data. However, different researchers may annotate different classes, or use different train and test splits. In addition, it is common for papers that apply machine learning for facies classification to not contain quantitative results, and rather rely solely on visual inspection of the results. All of these practices have lead to subjective results and have greatly hindered the ability to compare different machine learning models against each other and understand the advantages and disadvantages of each approach. To address these issues, we open-source a fully-annotated 3D geological model of the Netherlands F3 Block. This model is based on the study of the 3D seismic data in addition to 26 well logs, and is grounded on the careful study of the geology of the region. Furthermore, we propose two baseline models for facies classification based on a deconvolution network architecture and make their codes publicly available. Finally, we propose a scheme for evaluating different models on this dataset, and we share the results of our baseline models. In addition to making the dataset and the code publicly available, this work helps advance research in this area by creating an objective benchmark for comparing the results of different machine learning approaches for facies classification.

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 12 code samples harvested from 3 repositories linked to this paper: 6 ran (of which 0 constructed an object rather than computing a result; 5 with no instrument failure: 0 honoured, 0 violated, 5 with no contract checked; 1 where Syntology's instrument failed) · 6 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: community (archive-listed): 12 samples from 3 repositories, 6 ran (5 with no instrument failure; 1 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 on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

ADharaUTEXAS123007/FaciesClassificationSEG mentioned on GitHubpytorchMITSyntology: 2 samples, 2 ran (0 instrument-failed) · 0 unverified report
deepkapha/EarthAdaptNet mentioned on GitHubpytorchMITSyntology: 5 samples, 3 ran (0 instrument-failed) · 2 unverified report
olivesgatech/image-2022-volumetric-contrastive mentioned on GitHubpytorchBSD-2-ClauseSyntology: 5 samples, 1 ran (1 instrument-failed) · 4 unverified report
olivesgatech/man-recon mentioned on GitHubpytorchSyntology: not harvested report
yalaudah/facies_classification_benchmark mentioned on GitHubpytorchMITSyntology: not harvested 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

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

1ran · our draft was wrong
5ran
6unverified

Licence: 2 of the 12 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.

ADharaUTEXAS123007/FaciesClassificationSEG community (archive-listed) 2 samples, 2 ran (0 instrument-failed) · 0 unverified
cross_entropy in 92 papers
census: 6 implementations from 8 papers, 5 distinct outputs across 2 buckets, one shared input per bucket
core/loss.py ran MIT (permissive) · 69bbbd5738c7bb71 · report fixture: signature input:Tensor/4/float, target:Tensor/4/int, weight:Tensor/1/float, ignore_index:int/0/int · returned Tensor · level recorded 2026-09-24
np_to_tb core/utils.py ran fingerprinted MIT (permissive) · 5be33a4b7c072ed7 · report fixture: signature array:ndarray/3/float · returned Tensor · level recorded 2026-09-24
deepkapha/EarthAdaptNet community (archive-listed) 5 samples, 3 ran (0 instrument-failed) · 2 unverified
ce_unflat core/losses_metrics.py ran fingerprinted MIT (permissive) · 26b9ad36cc24cfa7 · report fixture: signature inp:Tensor/4/float, tar:Tensor/4/float · returned Tensor · level recorded 2026-09-24
dice_loss in 193 papers
census: 10 implementations from 16 papers, 7 distinct outputs across 4 buckets, one shared input per bucket
core/losses_metrics.py ran MIT (permissive) · 66fac178bc30d0be · report fixture: signature true:Tensor/4/int, logits:Tensor/4/float, eps:float/0/float, ignore_index:int/0/int · returned Tensor · level recorded 2026-09-24
jaccard_loss core/losses_metrics.py ran MIT (permissive) · 399b66aec1defd1f · report fixture: signature true:Tensor/3/int, logits:Tensor/4/float, eps:float/0/float, ignore_index:int/0/int · returned Tensor · level recorded 2026-09-24
get_model_instance_segmentation core/lr_scheduler.py unverified MIT (permissive) · f6600daba8b96379 · report
to_3_channels train_SeismicNet.py unverified MIT (permissive) · f329bc18a7d30845 · report
olivesgatech/image-2022-volumetric-contrastive community (archive-listed) 5 samples, 1 ran (1 instrument-failed) · 4 unverified
set_optimizer in 24 papers util.py ran · our draft was wrong BSD-2-Clause (permissive) here; the stored copy is pointer only · a44a1925c2c778ba · report fixture: signature opt:Options/0/?, model:callable/0/? · returned SGD · level recorded 2026-09-24
accuracy in 872 papers
census: 8 implementations from 7 papers, 7 distinct outputs across 6 buckets, one shared input per bucket
util.py unverified BSD-2-Clause (permissive) here; the stored copy is pointer only · 913d82af53065418 · report
check_accuracy main_seismic_semantic.py unverified BSD-2-Clause (permissive) · a9052bbb3339ce5a · report
generate_images_labels dataset_analysis.py unverified BSD-2-Clause (permissive) · 161b350d944c1319 · report
set_model main_seismic_semantic.py unverified BSD-2-Clause (permissive) · 6da83d609bf6d61e · report

Tasks

BIG-bench Machine LearningClassificationFacies ClassificationGeneral ClassificationSeismic Interpretation

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