Papers › Formalizing Atom-typing and the Dissemination of Force Fields with Foyer

Formalizing Atom-typing and the Dissemination of Force Fields with Foyer

7 Dec 2018arXiv:1812.06779links table onlyarchive 2025-07-28

Christoph Klein, Andrew Z. Summers, Matthew W. Thompson, Justin Gilmer, Clare McCabe, Peter T. Cummings, Janos Sallai, Christopher R. Iacovella

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.

A key component to enhancing reproducibility in the molecular simulation community is reducing ambiguity in the parameterization of molecular models. Ambiguity in molecular models often stems from the dissemination of molecular force fields in a format that is not directly usable or is ambiguously documented via a non-machine readable mechanism. Specifically, the lack of a general tool for performing automated atom-typing under the rules of a particular force field facilitates errors in model parameterization that may go unnoticed if other researchers are unable reproduce this process. Here, we present Foyer, a Python tool that enables users to define force field atom-typing rules in a format that is both machine- and human-readable thus eliminating ambiguity in atom-typing and additionally providing a framework for force field dissemination. Foyer defines force fields in an XML format, where SMARTS strings are used to define the chemical context of a particular atom type. Herein we describe the underlying methodology of the Foyer package, highlighting its advantages over typical atom-typing approaches and demonstrate is application in several use-cases.

PaperPDFCode

Code

mosdef-hub/foyer officialmentioned in papermentioned on GitHub report
bc118/foyer mentioned on GitHub report
dcardenasv/foyer mentioned on GitHub report
jrdcasa/foyer_cj mentioned on GitHub 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

Not run by Syntology. Nothing on this page verifies that the listed code works.

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