Papers › Fast and interpretable classification of small X-ray diffraction datasets using data...

Fast and interpretable classification of small X-ray diffraction datasets using data augmentation and deep neural networks

20 Nov 2018arXiv:1811.08425archive 2025-07-28

Felipe Oviedo, Zekun Ren, Shijing Sun, Charlie Settens, Zhe Liu, Noor Titan Putri Hartono, Ramasamy Savitha, Brian L. DeCost, Siyu I. P. Tian, Giuseppe Romano, Aaron Gilad Kusne, Tonio Buonassisi

X-ray diffraction (XRD) data acquisition and analysis is among the most time-consuming steps in the development cycle of novel thin-film materials. We propose a machine-learning-enabled approach to predict crystallographic dimensionality and space group from a limited number of thin-film XRD patterns. We overcome the scarce-data problem intrinsic to novel materials development by coupling a supervised machine learning approach with a model agnostic, physics-informed data augmentation strategy using simulated data from the Inorganic Crystal Structure Database (ICSD) and experimental data. As a test case, 115 thin-film metal halides spanning 3 dimensionalities and 7 space-groups are synthesized and classified. After testing various algorithms, we develop and implement an all convolutional neural network, with cross validated accuracies for dimensionality and space-group classification of 93% and 89%, respectively. We propose average class activation maps, computed from a global average pooling layer, to allow high model interpretability by human experimentalists, elucidating the root causes of misclassification. Finally, we systematically evaluate the maximum XRD pattern step size (data acquisition rate) before loss of predictive accuracy occurs, and determine it to be 0.16°, which enables an XRD pattern to be obtained and classified in 5.5 minutes or less.

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

By repository: official repository: 2 samples from 1 repository, 1 ran (1 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 6 samples from 2 repositories, 6 ran (3 with no instrument failure; 3 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-25 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

PV-Lab/AUTO-XRD officialmentioned in papermentioned on GitHubtfApache-2.0Syntology: 2 samples, 1 ran (0 instrument-failed) · 1 unverified report
PV-Lab/autoXRD mentioned on GitHubtfSyntology: 3 samples, 3 ran (1 instrument-failed) · 0 unverified report
ma921/XRDidentifier mentioned on GitHubpytorchSyntology: 3 samples, 3 ran (2 instrument-failed) · 0 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

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 2 honoured, 1 violated, 1 with no contract checked; 3 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 · honoured contract
1ran · violated contract
2ran · our draft was wrong
1ran; the contract check could not run
1ran
1unverified

Licence: 3 of the 8 samples are pointer only, meaning Syntology does not serve that copy's text. 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.

PV-Lab/AUTO-XRD official repository 2 samples, 1 ran (0 instrument-failed) · 1 unverified
find_incorrects autoXRD_vis.py ran Apache-2.0 (permissive) · 3da6e7f77ed77400 · report fixture: signature ground_truth:list/1/ndarray, predictions_ord:list/1/list · returned tuple · level recorded 2026-09-25
get_cam autoXRD_vis.py unverified Apache-2.0 (permissive) · 9e44f4085bfb81d5 · report
PV-Lab/autoXRD community (archive-listed) 3 samples, 3 ran (1 instrument-failed) · 0 unverified
augdata autoXRD.py ran · our draft was wrong fingerprinted Apache-2.0 (permissive) · 00c7a4306c2ec79e · report fixture: signature data:ndarray/2/float, num:int/0/int, par1:list/1/float, minn:int/0/int, maxn:int/0/int · returned tuple · level recorded 2026-09-22
normdata autoXRD.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · 20dce98251942490 · report fixture: signature data:ndarray/2/float · returned ndarray · level recorded 2026-09-22
normdatasingle autoXRD.py ran · honoured contract fingerprinted Apache-2.0 (permissive) · ef94397398cdacec · report fixture: signature data:ndarray/2/float · returned ndarray · level recorded 2026-09-22
ma921/XRDidentifier community (archive-listed) 3 samples, 3 ran (2 instrument-failed) · 0 unverified
normalise in 26 papers train_expert.py ran · violated contract fingerprinted no licence file found · pointer only · f1a7af06566be3ed · report fixture: signature spectra:ndarray/1/float · returned ndarray · level recorded 2026-09-22
random_data_split train_expert.py ran; the contract check could not run (RAISES) · metamorphic tier: deterministic no licence file found · pointer only · bd71181156fd6add · report fixture: signature spectra:ndarray/2/float, labels:ndarray/1/int, settings:list/1/int · returned tuple · level recorded 2026-09-22
spectra_loader train_expert.py ran · our draft was wrong no licence file found · pointer only · 285d3f873a799a13 · report fixture: signature pickle_path:str/0/str · returned dict · level recorded 2026-09-22

Tasks

BIG-bench Machine LearningData AugmentationGeneral ClassificationSpace group classificationX-Ray Diffraction (XRD)

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

Average PoolingGlobal Average PoolingInterpretability

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