# Setup and Installation¶

This guide deal with the general setup and local installation of the xtb program.

## Getting the Program¶

The xtb program is now open source and available free of charge on GitHub.

At the release page you find the a compressed tarball (tar xf xtb*.tar.xz) usually containing the following content:

.
├── CHANGELOG.md
├── bin
│   └── xtb
├── include
│   └── xtb.h
├── lib
│   ├── libxtb.so -> libxtb.so.6
│   ├── libxtb.so.6 -> libxtb.so.6.2.1
│   └── libxtb.so.6.2.1
├── python
│   ├── setup.py
│   └── xtb
│       ├── __init__.py
│       ├── calculators.py
│       ├── interface.py
│       └── solvation.py
└── share
├── man
│   ├── man1
│   │   └── xtb.1
│   └── man7
│       └── xcontrol.7
└── xtb
├── .param_gfn0.xtb
├── .param_gfn2.xtb
└── .param_gfn.xtb


The binary is usually compiled with the Intel Fortran compiler and statically linked against Intel’s Math Kernel Library (Intel MKL). Newer versions of xtb (6.2 and newer) additionally include a shared library, the header specification of the C-API and a Python wrapper to use the API within the Atomic Simulation Environment (ASE).

First check the version by

> xtb --version
-----------------------------------------------------------
|                   =====================                   |
|                           x T B                           |
|                   =====================                   |
|                         S. Grimme                         |
|          Mulliken Center for Theoretical Chemistry        |
|                    University of Bonn                     |
-----------------------------------------------------------

* xtb version 6.2.1 (bf8695d) compiled by '[email protected]' on 2019-10-25

normal termination of xtb


This should print some fancy banner, the version number, say 6.2.1, the git commit hash, the user and host name of the programmer compiled the program and at date. Make sure the version is matching the version from the release page and the commit hash is the actual commit hash of the release, also the date of the compilation should match. We compile the program on our clusters in Bonn, so the host name is usually majestix (or hedy20 for the old-kernel version). You get also the user name of the programmer drafting the release, testing the binary and packing the tarball.

This line is very important when reporting a bug to us, because we can validate the binary you were using and easier reproduce it.

## Setting up xtb¶

This section will give you the basic information you need to know about the xtb program. Some of the steps are elemental for your calculation to succeed, so please consider to follow my instructions carefully.

Some part of the xtb program can be quite wasteful with stack memory, to avoid stack overflows when calculating large molecules, you should unlimit the system stack, e.g. with bash by

> ulimit -s unlimited


Note that the memory management of xtb is constantly improved to avoid using large amounts of stack memory, but to be on the save side include this option for production runs.

### Parallelisation¶

The xtb program uses OMP parallelisation, to calculate larger systems an appropriate OMP stacksize must be provided, chose a reasonable large number by

> export OMP_STACKSIZE=1G


To distribute the number of threads reasonable in the OMP section it is recommended to use

> export OMP_NUM_THREADS=<ncores>,1


You might want to deactivate nested OMP constructs by

> export OMP_MAX_ACTIVE_LEVELS=1


The default linear algebra backend of xtb is the Math Kernel Library, to make the linear algebra run in parallel export

> export MKL_NUM_THREADS=<ncores>


### Environment Variables for xtb¶

A number of environment variables is used by xtb to perform calculations. Please set the XTBPATH variable to include all locations were you store information relevant for your xtb calculation, like configuration files and parameter files. The present working directory is implicitly included for most files that are searched in the XTBPATH.

The old XTBHOME variable is used if you have not set the XTBPATH variable and is used in the same manner. xtb will print the values of XTBPATH and XTBHOME at the beginning of each calculation if set to verbose mode.

A configuration script to be sourced in your .bashrc is provided here

#!/usr/bin/env bash
# requirements: $XTBHOME is set to xtb root directory # otherwise the script will find the location of itself here: if [ -z "${XTBHOME}" ]; then
XTBHOME="$(cd -P "$(dirname "${BASH_SOURCE[0]}")" && pwd)" fi # set up path for xtb, using the xtb directory and the users home directory XTBPATH=${XTBHOME}/share/xtb:${XTBHOME}:${HOME}

# to include the documentation we include our man pages in the users manpath
MANPATH=${MANPATH}:${XTBHOME}/share/man

# finally we have to make the binaries and scripts accessable
PATH=${PATH}:${XTBHOME}/bin
LD_LIBRARY_PATH=${LD_LIBRARY_PATH}:${XTBHOME}/lib
PYTHONPATH=${PYTHONPATH}:${XTBHOME}/python

export PATH XTBPATH MANPATH LD_LIBRARY_PATH PYTHONPATH


It will set XTBHOME to the location of the script if you have not set it already and just assumes that XTBHOME contains the content of shipped tarball, then it will append the directories bin/ to your PATH variable, share/man/ to your MANPATH, lib/ to your LD_LIBRARY_PATH and python/ to your PYTHONPATH.

## Getting Help from xtb¶

Beside this manual you can check the in-program help by

> xtb --help


Unfortunately, this might be outdated, therefore, you should refer to the man-pages distributed with the xtb program. Please check for the man-pages of xtb(1) and xcontrol(7). There is also an online documentation, but you already now that one, of course.

### The Verbose Mode¶

If you think some information is missing in your calculation you can switch to the verbose mode by using --verbose in the command line arguments. This will increase the print level almost everywhere in the xtb program, also the input parser will print a lot of information that might be interesting for your current calculation.

Overall this can be an awful lot of information, so it is not recommended as a default option.

## Using xTB with Orca¶

Orca 4.2 implements support for xTB calculations using an IO based interface calling the xtb binary and parsing its output.

The binaries of Orca will call an executable called otool_xtb, which should be placed in the directory containing the Orca binaries. We recommend to create a symbolic link to your local xtb binary by

> ln -s \$(which xtb) otool_xtb


Important

xtb version 6.2.3 produces an energy printout which cannot be processes by the reader in Orca, to fix this issue, use the provided script to wrap the xtb binary instead of creating a symbolic link.

You can invoke xTB calculations in Orca by using one of the simple keywords

! XTB1 # for GFN1-xTB
! XTB2 # for GFN2-xTB


in your Orca input file, for more details refer to the Orca manual.

Orca will communicate with xtb mainly by using commandline arguments, requesting singlepoint calculations and parsing the total energy and gradient from the program output.

Of course you should setup the xtb related environment variables, such that xtb can find its parameter files and configuration files. The .xtbrc is still read if it is contained in XTBPATH and can be used to change the behaviour of xTB calculations in Orca, e.g. for setting the electronic temperature.