PEPS Software: Difference between revisions
No edit summary |
|||
| Line 41: | Line 41: | ||
git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps | git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps | ||
to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch. | to clone the repository into the ''offline-=peps' directory and switch to the ''peps' branch. This step takes some time due to the size of the repository. | ||
Revision as of 00:08, 26 May 2026
Software download
You need two steps to use the auger software:
- Download and install the externals
- Clone the auger offline repository, build and enjoy (test, modify, install, run)
Getting externals: ape
The PEPS enabled ape distribution is available form the Auger Ape Distribution page. To compile the externals, you have to make sure that your system has a number of packages installed. They are listed in the Manifest List for PEPS. The one-letter shorthand for key distributions are: a: Alma Linux, u: Ubuntu, d: Debian, r: Rocky Linux, f: Fedora.
You have to configure where you want to install the package to using typically ~/.aperc:
[DEFAULT] base = %(home)s/auger/software/ApePeps build = /tmp/ape-lukas [ape] jobs = 32 # Number of cores on your machine mirrors = mx de
You can then run
./ape install externals
and go for a coffee (depends on your machine).
Note: we currently cannot build the externals on MacOS, but this will be fixed soon (for some suitable definition of soon).
Getting offline from gitlab
The Auger Offline software is available from the offline project at the IAP-KIT gitlab server. You need
- An account at https://gitlab.iap.kit.edu
- Configure your account to have ssh keys for cloning. Provides a much more efficient workflow, using git over ssh and not https.
You then run
git clone -b peps git@gitlab.iap.kit.edu:auger-observatory/offline/offline.git offline-peps
to clone the repository into the offline-=peps' directory and switch to the peps' branch. This step takes some time due to the size of the repository.
