Papers › Active learning of reactive Bayesian force fields: Application to heterogeneous...

Active learning of reactive Bayesian force fields: Application to heterogeneous hydrogen-platinum catalysis dynamics

3 Jun 2021arXiv:2106.01949links table onlyarchive 2025-07-28

Jonathan Vandermause, Yu Xie, Jin Soo Lim, Cameron J. Owen, Boris Kozinsky

The archive published only this paper's code-link row. Authors, date and abstract are from arXiv's metadata (CC0), read from the Kaggle arXiv metadata snapshot of 2026-09-12 where its title matched the archive's; the title is the archive's.

Accurate modeling of chemically reactive systems has traditionally relied on either expensive ab initio approaches or flexible bond-order force fields such as ReaxFF that require considerable time, effort, and expertise to parameterize. Here, we introduce FLARE++, a Bayesian active learning method for training reactive many-body force fields on the fly during molecular dynamics (MD) simulations. During the automated training loop, the predictive uncertainties of a sparse Gaussian process (SGP) force field are evaluated at each timestep of an MD simulation to determine whether additional ab initio data are needed. Once trained, the SGP is mapped onto an equivalent and much faster model that is polynomial in the local environment descriptors and whose prediction cost is independent of the training set size. We apply our method to a canonical reactive system in the field of heterogeneous catalysis, hydrogen splitting and recombination on a platinum (111) surface, obtaining a trained model within three days of wall time that is twice as fast as a recent Pt/H ReaxFF force field and considerably more accurate. Our method is fully open source and is expected to reduce the time and effort required to train fast and accurate reactive force fields for complex systems.

Code

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; 1 ran; 0 honoured the contract we drafted; 7 have no recorded run. Read from Syntology's graph 2026-09-24; that is when this build read the record, not when the samples ran.

Licence: 0 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 2 repositories linked to this paper, official or community; each sample names its own and says which. “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. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself; “our draft was wrong” and “fixture could not drive it” are failures of Syntology's instrument, not of the code.

Each sample ends with its code_sha256, Syntology's identity for that exact code. An agent fetches the stored sample with Syntology's MCP tool get_code(code_sha256="…") (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 from a repository marked official are listed first. 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 four 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; or the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar). 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.

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