Skip to content
#software testing Open access

Where Foundation Machine-Learning Potentials Fail for Iron-Sulfide Defect Kinetics: Failure Modes, Pre-Flight Checks, and a DFT Benchmark of Vacancy-Anchored Hydrogen Migration in Pyrite, Marcasite, Mackinawite, and Greigite

Sep 2026 · Zenodo (CERN European Organization for Nuclear Research)

Abstract

This dataset and code package accompanies the study of foundation machine-learning interatomic potentials (MLIPs) for vacancy-anchored hydrogen migration in pyrite, marcasite, mackinawite and greigite. Foundation MLIPs offer inexpensive migration-barrier calculations, but their reliability for hydrogen defects in magnetic iron sulfides remains uncertain. We establish plane-wave DFT references at PBE, U = 0 for these four minerals. The electronic barriers for sulfur-to-sulfur transfer around an Fe vacancy are 43, 208, 268 and 236 meV for mackinawite, marcasite, pyrite and the lower-barrier greigite path, respectively. A second greigite edge gives 567 meV: the shorter edge has the higher barrier, showing why path selection requires local coordination rather than distance alone. A separate pyrite sulfur-vacancy pocket supports Fe-to-Fe hydrogen transfer with a 94.6 meV reference barrier. The study distinguishes self-consistent MLIP pathways from energy evaluations on fixed DFT geometries. Nine foundation potentials evaluated on five DFT bands give barrier errors from −132 to +371 meV. The pyrite Fe-vacancy dimer reference is not part of this five-band comparison. The models identify the highest-energy image in 43 of 45 model–band comparisons, yet all nine overestimate the 43 meV mackinawite barrier by factors of 1.75–9.66. No consistent improvement with model generation is resolved in this small benchmark. Separate relaxation tests reveal pristine-greigite instability and endpoint-seeding sensitivity, which fixed-geometry energy tests cannot diagnose. Fine-tuning MACE-MP-0 on four bands from the other three sulfides reduces the held-out mackinawite error from 149 to 68 ± 23 meV (mean signed barrier error on the fixed DFT band ± standard deviation across eight training seeds). Fitting its own band alone permits a 4.6 meV mean absolute error, demonstrating representability without establishing transfer to unseen pathways. Harmonic zero-point corrections lower the four channel-reference barriers by 66–103 meV; mackinawite reaches the limit of harmonic barrier theory. Contents of this archive Repository documentation, DFT/NEB and dimer drivers, and instructions for reproducing analyses from stored results without new electronic-structure calculations. Structures and result data: extended-XYZ bands, endpoints and saddles, harvested energies and frequencies, selected production input/output records, and explicit unreliable-image and withdrawal flags. Nine-model benchmark records, including per-image profiles, forces and barrier comparisons, and the fine-tuning ladder, with dataset specifications, per-seed evaluations, schedule selection records and training logs. Figure generators with deposited plotting inputs and provenance hashes; TM-Spec records describe calculation settings, results and their stated limitations in machine-readable form. Scope and limitations These are local neutral-H defect calculations in dry bulk, with mineral-specific magnetic reference choices, not predictions of hydrated proton conductivity. The 45 model–band comparisons concern five pathways and are not independent observations. Target-band fitting controls are not validation on unseen paths, and a negative harmonic corrected barrier does not establish a barrierless quantum rate. Finite-iteration greigite Lanczos diagnostics do not certify the complete saddle index. Software manifests cover the three environments used for the nine-model evaluation. Older calculations have component-version records rather than complete contemporaneous package snapshots. A checkpoint checksum is supplied for MACE; model weights, immutable container images, and raw wavefunction/charge-density dumps are not included. Corrections and version 1.5 The historical greigite 1.86 eV trans-axis result is withdrawn as a migration barrier. Pentlandite diagnostics based on an incorrect crystal model are also withdrawn. Their marked records remain available for traceability and must not be treated as current reference results. Version 1.5 aligns documentation and structured metadata with these interpretations, corrects aggregation of the three available self-consistent NEB seed pairs, and strengthens analysis-input checks. It also supplies standalone figure inputs and selected method-provenance files. These changes preserve the existing numerical datasets and do not introduce new DFT or MLIP calculations.

View source

Similar papers

#computer vision Review Sep 2017

Agile Software Development Methods: Review and Analysis

This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.

P. Abrahamsson, O. Salo, Jussi Ronkainen et al. · 727 citations · ⚡54
#computer vision Jun 2008

The impact of agile practices on communication in software development

The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.

M. Pikkarainen, Jukka Haikara, O. Salo et al. · 401 citations · ⚡48
#machine learning Review Open access Oct 2014

Software development in startup companies: A systematic mapping study

The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.

Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al. · 394 citations · ⚡54
#computer vision Review Mar 2008

Agile methods in European embedded software development organisations: a survey on the actual use and usefulness of Extreme Programming and Scrum

The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.

O. Salo, P. Abrahamsson · 238 citations · ⚡9
#computer vision Open access Jul 2017

What happens when software developers are (un)happy

Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.

D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al. · 236 citations · ⚡13
#computer vision Open access Oct 2004

Mobile-D: an agile approach for mobile application development

The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.

P. Abrahamsson, Antti Hanhineva, H. Hulkko et al. · 225 citations · ⚡18

Related blog posts

MIT News · Artificial Intelligence Oct 2, 2026

Documenting the tech worker movement

Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.

GPT-Lab Sep 23, 2026

Requirements Don’t Live in Isolation: What We’re Exploring with Req-Space

Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…

GPT-Lab Sep 17, 2026

Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering

AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.

We use cookies to run the site and, with your consent, for analytics and to show ads. See our Cookie Policy.