Skip to main content

SEAMM xTB Plug-in

GitHub pull requests Build Status Code Coverage Code Quality Documentation Status PyPi VERSION

A SEAMM plug-in for the xTB family of extended tight-binding methods from the Grimme group.

Features

  • Single-point energies, geometry optimizations, and harmonic vibrational frequencies for molecular (non-periodic) systems.

  • The full set of xTB Hamiltonians and the GFN-FF force field:

    • GFN2-xTB (default) – self-consistent, multipole electrostatics, density-dependent dispersion. Recommended for general use.

    • GFN1-xTB – earlier self-consistent method.

    • GFN0-xTB – non-self-consistent, useful for robust screening.

    • GFN-FF – generic force field, automatically parameterized.

  • Implicit solvation with all three xTB-supported models:

    • ALPB – analytical linearized Poisson-Boltzmann (Ehlert et al., J. Chem. Theory Comput. 2021, 17, 4250).

    • GBSA – generalized-Born model.

    • CPCM-X – conductor-like polarizable continuum (Stahn et al., J. Phys. Chem. A 2023, 127, 7036).

    with the standard xTB solvent list (water, methanol, DMSO, acetonitrile, etc.).

  • Net charge and spin multiplicity are read from the configuration, so the same flowchart works unchanged across O2, triplet O2, and O2+ – a single loop can scan a list of systems with different charge/spin states.

  • Optimization with all eight xTB convergence levels (crude through extreme) and flexible structure handling: overwrite the current configuration in place, store the optimized structure as a new configuration, store it in a new system, or discard.

  • Vibrational analysis using xTB’s analytic Hessian, with the optimize-then-Hessian (--ohess) workflow recommended by xTB (or --hess alone if the geometry is already at a stationary point). Thermochemistry quantities (ZPE, H(T), T*S, S, G(T), total free energy) are reported in chemist-friendly units of kJ/mol and J/mol/K, not Eh.

  • Tabulated results in the local step.out and storage in the SEAMM property database using the standard <name>#xTB#{model} property-naming convention, so downstream plug-ins (Thermochemistry, Reaction Path, …) can pick up the values.

  • Automatic citation tracking. The principal xTB program reference, the active GFN method reference, the DFT-D4 dispersion references (for GFN2-xTB), and the implicit-solvation reference are all added to the run’s reference list automatically.

  • Automatic installation of the xtb executable into a dedicated seamm-xtb conda environment via the standard SEAMM Installer.

Acknowledgements

This package was created with the molssi-seamm/cookiecutter-seamm-plugin tool, which is based on the excellent Cookiecutter.

Developed by the Molecular Sciences Software Institute (MolSSI), which receives funding from the National Science Foundation under award CHE-2136142.

History

2026.11.5 – Tight convergence on request for finite differences
  • Steps that take finite differences of xTB’s gradients over its MDI engine, such as the new Vibrational Analysis step, can now ask for tight convergence: every calculation then runs at accuracy 1e-4. The engine starts each SCF from the previous structure’s, and at the default accuracy that left noise depending on the previous structure (water’s anharmonic force constants: 92 cm^-1 of noise, 0.12 with the tighter accuracy).

  • The MDI engine takes an --accuracy option.

2026.10.20 – Bugfix: an SCF that did not converge ended the MDI engine
  • In the tblite MDI engine (used e.g. by the Dimer Builder), one structure whose SCF did not converge ended the engine, and with it the whole step. A failed SCF is now retried from a fresh start, then with more iterations and stronger damping, then from another starting guess – none of which changes the converged energy. If none converges, the engine returns NaN for that structure and carries on, so the step can leave the point out. For Li+ with ethylene carbonate the failures were at large separations, 7-9 Å, and the retries converged them.

2026.10.9 – Bugfix: GFN2-xTB through tblite crashed
  • Any GFN2-xTB calculation through tblite (the MDI engine, as used by the Dimer Builder) crashed with a segmentation fault: tblite 0.6 and 0.7 need dftd4 4.2, and that combination fails in dftd4’s polarizabilities. The environment now pins tblite-python 0.5.0 (dftd4 3.7), which works; with it the xtb program is 6.4.1. GFN1-xTB was not affected.

  • Internal: requires Python 3.12; CI installs with uv from PyPI (no conda test environment); the unused Docker installation option was removed.

2026.5.2: Plug-in created using the SEAMM plug-in cookiecutter.

2026.5.12: Initial working version
  • Support for Energy, Optimization, and Frequencies

  • GFN0-xTB, GFN1-xTB, GFN2-xTB (the default), and GFN-FF supported

  • ALPB, GBSA, or CPCM-X implicit solvation

Metadata

Release files for xtb-step 2026.11.5

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for xtb-step 2026.11.5
File Size Uploaded Provenance Actions
xtb_step-2026.11.5.tar.gz 402.5 kB Without provenance Details for xtb_step-2026.11.5.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for xtb-step 2026.11.5
File Interpreter ABI Platform Actions
xtb_step-2026.11.5-py2.py3-none-any.whl Python 2, Python 3 none any Details for xtb_step-2026.11.5-py2.py3-none-any.whl

Total release size: 464.9 kB

Release files / xtb_step-2026.11.5.tar.gz

Download URL xtb_step-2026.11.5.tar.gz
Size 402.5 kB
Tags Source
SHA-256 checksum
How to use checksums
237b3b514aa1187820d5b3bc7b535f2569553d69466e2a69b3bf41b64d426c74
BLAKE2b-256 checksum
How to use checksums
c459202f46d33fe397fc0bc237be84c3cf74b929815efda5f07788131e83dbdd
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Release files / xtb_step-2026.11.5-py2.py3-none-any.whl

Download URL xtb_step-2026.11.5-py2.py3-none-any.whl
Size 62.4 kB
Tags Python 2 Python 3
SHA-256 checksum
How to use checksums
7283227f656497eba91cc572bf5b7abfdb57731e4071751aaba94350bfaae98b
BLAKE2b-256 checksum
How to use checksums
54d996ab12d3ab71c82872b1ef297d768c84f10944625b5d4e97a842adfc12c9
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.16

Security for xtb-step 2026.11.5

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page