Skip to content

Manual software installation

IGWN software is distributed through a variety of mechanisms, with principal support aimed at providing binary distributions for the LIGO Data Grid grid computing sites.

The following platforms have first-class support:

The following platforms have best-effort support:

The following platforms were supported in the past, but have now been dropped:

Conda (conda-forge)

A large number of IGWN software packages are available as Conda packages via the Conda-forge organisation.

More information

For full details see

Installing packages from conda-forge

To install a conda-forge package into an existing conda environment:

conda config --add channels conda-forge
conda install <package-name>

Scientific Linux 7

To configure yum to use the LSCSoft repositories:

Configuring the lscsoft-production repository

Download the configuration RPM for the production LSCSoft repository


Check that the SHA256 checksum matches the following:


Install the RPM:

rpm -ivh lscsoft-production-config-1.3-1.el7.noarch.rpm

Clear the yum cache and initialise the repository:

yum clean all
yum makecache

The system should now be configured to track the LSCSoft Production repository. The repository configuration itself is managed via packages in the LSCSoft repository so any updates will automatically be installed using the standard package update process.

Configuring other SL7 repositories

Now that the system is tracking the production repository it can be configured to track the other repositories required to install IGWN software:

yum install lscsoft-backports-config
yum install lscsoft-epel-config
yum install lscsoft-grid-config

If you want a newer git version then enable the WANdisco-git repository, add the following contents:

name=Wandisco GIT Repository

Update git

Whilst a newer version of git isn't technically required it is highly recommnded if you are going to be using any git-lfs enabled repositories, such as LALSuite.

Debian 9 (stretch)

No longer supported

Unfortunately we are no longer able to support the debian repositories documented in this section. If you require debian packages, please consider providing this support yourself (contact to enquire) or see the section Debian (alternative) section below.

Configuring the lscsoft Debian repository

To add the LSCSoft Debian repository to your system, create /etc/apt/sources.list.d/lscsoft.list with the following content:

deb stretch contrib
deb-src stretch contrib

Configuring the lscsoft-testing Debian repository

To add the LSCSoft testing Debian repository to your system, create /etc/apt/sources.list.d/lscsoft-testing.list with the following content:

deb stretch-proposed contrib
deb-src stretch-proposed contrib

Debian (alternative)

The group at AEI-Potsdam-Golm provide debian package builds, and provide access to those builds in a "flat" (and unsigned) repository, one directory per platform (architecture x distribution). These repositories also provide selected gridtools.

Debian users can configure that repository as an extra package source.

You might need to install ca-certificates and apt-transport-https before

In order to accept the certificate offered by you may need to install the ca-certificates package. Also, since hypatia insists on using https, the apt-transport-https package has to be installed:

apt-get install ca-certificates
apt-get install apt-transport-https

To use the alternative Debian package source, create /etc/apt/sources.list.d/lscdebian.list with the following content:

deb [trusted=yes]{arch}-{dist} ./

where {arch} can be one of

  • amd64,
  • arm64,
  • i386,
  • powerpc,
  • ppc64el,

and {dist} one of

  • jessie,
  • stretch,
  • buster.


Not all combinations are available, and some packages may be unavailable due to unaddressed build failures!

For example:

Source configuration for Buster on x86_64

deb [trusted=yes] ./

Source configuration for Stretch on x86 (32-bit)

deb [trusted=yes] ./

Once this is configured, run

apt-get update

to make the new package source available to APT.

To check that this configuration works, you should be able to search for IGWN-internal packages, e.g. python3-lal:

Verify Debian configuration

# apt-cache policy python3-lal
  Installed: (none)
  Candidate: 6.20.2-1+deb10u0
  Version table:
     6.20.2-1+deb10u0 500
        500 ./ Packages

Help is available

If running into problems with this approach, please contact