The Interoperability Challenge in DFT Workflows Across Implementations

Simon Krarup Steensen, Tejender S. Thakur, Manuel Dillenz, Johan M. Carlsson, Celso R. C. Rêgo, Eibar Flores, Hamidreza Hajiyani, Felix Hanke, J. M. García‐Lastra, Wolfgang Wenzel, Nicola Marzari, Tejs Vegge, Giovanni Pizzi, Ivano E. CastelliarXiv 2025 · DOI · arXiv

TL;DR

Researchers have developed a "universal translator" for battery simulations, creating a standardized input/output schema that allows different Density Functional Theory (DFT) codes and workflow managers to speak the same language. While average battery voltages align remarkably well across different software implementations, the study reveals that "non-pristine" structures—like those in a partially charged battery—are highly sensitive to subtle technical settings, highlighting a major hurdle for fully autonomous materials discovery.

What Problem Does This Paper Address?

In the world of computational materials science, Density Functional Theory (DFT) is the gold standard for predicting material properties. However, the field suffers from a "Tower of Babel" problem: dozens of different DFT codes (like VASP, Quantum ESPRESSO, or CASTEP) each use their own idiosyncratic input formats, unit systems, and parameter conventions.

This fragmentation makes it incredibly difficult to cross-validate results. If Code A predicts a battery voltage of 4.0V and Code B predicts 3.8V, is the difference due to the physics, or just a subtle difference in how the two codes handle numerical "smearing" or structural relaxation? As we move toward self-driving laboratories and high-throughput screening, we need workflows that are engine-agnostic—meaning the scientific intent remains the same regardless of which software "engine" is under the hood.

Methods

The authors introduced a unified I/O schema based on JSON/YAML, designed to be human-readable and machine-actionable. This schema acts as a common interface for four different workflow managers: AiiDA, PerQueue, Pipeline Pilot, and SimStack.

Key methodological features include:

  • Standardized Protocols: They defined "fast," "moderate," and "precise" levels of accuracy that map to specific internal parameters across different DFT engines.
  • Intercalation Workflow: They implemented a specific workflow to calculate the Open-Circuit Voltage (OCV) of battery cathodes. This involves relaxing a fully discharged structure, removing ions to create a charged state, and calculating the energy difference.
  • Semantic Layer: To ensure the data is truly FAIR (Findable, Accessible, Interoperable, and Reusable), they used JSON-LD and domain-specific ontologies (like EMMO and BattINFO) to describe the metadata of the simulations.

Datasets

The study focused on five representative battery electrode materials sourced from the Materials Project:

  • Li₂Mn₃NiO₈ (High-voltage spinel)
  • LiFePO₄ (Olivine phosphate)
  • LiTiS₂ (Layered sulfide)
  • LiCoO₂ (Standard layered oxide)
  • MgMo₃S₄ (Chevrel phase for multivalent batteries)

These materials were chosen to span a broad range of transition metal chemistries and structural complexities.

Key Insights and Ideas

  • The "Pristine" Illusion: For perfect, fully discharged crystals, different DFT codes agree almost perfectly (discrepancies < 0.03 V). The real challenge arises when you introduce vacancies (charging the battery). These "non-pristine" structures are where the codes begin to diverge.
  • Smearing is a Silent Killer: "Smearing" is a mathematical trick used to help simulations converge. The authors found that for certain materials (like Li₂Mn₃NiO₈), the choice of smearing width can trigger artificial electronic gaps, leading to abrupt, non-physical jumps in predicted voltage.
  • Local Minima Traps: Different optimization algorithms can lead to different "relaxed" structures. In some cases, one code might find a cubic structure while another finds a slightly distorted non-cubic version that is lower in energy by 2 eV—a massive difference in the world of quantum chemistry.
  • Cross-Code Validation as a Debugger: The authors argue that interoperability isn't just a convenience; it's a validation tool. Running the same simulation in two different codes is the best way to catch "bad" pseudopotentials or insufficient convergence settings that would otherwise go unnoticed.

Key Results

  • High Alignment: Across all five implementations, the average OCV values showed excellent agreement, often within a few hundredths of a volt.
  • Low-SOC Sensitivity: Discrepancies were significantly higher at low states of charge (SOC). For example, in Li₂Mn₃NiO₈, metastable states led to a spread of about 0.2 V between different implementations at low SOC.
  • Successful Translation: The team successfully demonstrated that a single scientific intent (an OCV calculation) could be automatically translated and executed across four distinct workflow managers and four different DFT engines (VASP, GPAW, QE, and CASTEP) using their unified schema.

Limitations and Future Work

The current study intentionally simplified the physics to establish a baseline. The authors acknowledge several areas for expansion:

  • Magnetism and +U Corrections: The study was limited to non-spin-polarized calculations without Hubbard (+U) corrections. In real battery materials, transition metals are magnetic, and aligning these complex "plus-U" parameters across different codes is a notorious challenge.
  • Autonomous Convergence: Future workflows need to be "smarter"—automatically detecting when a specific structure (like a vacancy-rich supercell) requires higher k-point density or different smearing than the pristine bulk material.
  • Scaling: While the schema works for OCV, it needs to be tested on more complex properties like ion migration barriers or thermal stability.

Summary updated

Abstract

Interoperability and cross-validation remains a significant challenge in the computational materials discovery community. In this context, we introduce a common input/output standard designed for internal translation by various workflow managers (AiiDA, PerQueue, Pipeline Pilot, and SimStack) to produce results in a unified schema. This standard aims to enable engine-agnostic workflow execution across multiple density functional theory (DFT) codes, including CASTEP, GPAW, Quantum ESPRESSO, and VASP. As a demonstration, we have implemented a workflow to calculate the open-circuit voltage across several battery cathode materials using the proposed universal input/output schema. We analyze and resolve the challenges of reconciling energetics computed by different DFT engines and document the code-specific idiosyncrasies that make straightforward comparisons difficult. Motivated by these challenges, we outline general design principles for robust automated DFT workflows. This work represents a practical step towards more reproducible and interoperable workflows for high-throughput materials screening, while highlighting challenges of aligning electronic properties, especially for non-pristine structures.
BibTeX
@misc{steensen2025interoperability,
  author = {Simon Krarup Steensen and Tejender S. Thakur and Manuel Dillenz and Johan M. Carlsson and Celso R. C. Rêgo and Eibar Flores and Hamidreza Hajiyani and Felix Hanke and J. M. García‐Lastra and Wolfgang Wenzel and Nicola Marzari and Tejs Vegge and Giovanni Pizzi and Ivano E. Castelli},
  title = {{The Interoperability Challenge in DFT Workflows Across Implementations}},
  year = {2025},
  eprint = {2511.11524},
  archivePrefix = {arXiv},
  url = {https://arxiv.org/abs/2511.11524},
  howpublished = {arXiv},
}

Loading related content...

Figure