First Step Instructions

This documentation briefly summarizes the first steps on how to install and compile the PAWIAN PWA software and how to run a test application.

Software Repository and Access to the Source Code

Navigate to
You should be greeted by the “Sign In” page of our Gitlab server. As an external user, please select the “Register” tab right above the User/Password fields.
By supplying your name, user name and an eMail address you can now create a user account for this Gitlab. After having done so, you should be able to browse the PAWIAN sources by navigating to Explore public projects -> All -> EP1/Pawian - or, even easier, by clicking this link:
You can view the code in the browser, or use the link at the top of the PAWIAN project page to clone the repository to your local machine. Try a “git clone ” on your machine; it should ask you for your credentials. Supply the username/PWD for the newly created gitlab account and it should start cloning.

After having done this, make sure you have all the external packages installed (Minuit2, log4cpp, boost-build, root). You may want to have a look at one of the SetEnv_* files, modify one of them to fit your needs and source it.

Some useful information and instructions about git can be found here.

External Packages

Before you can compile and link the code the following external packages must be installed: You can download the source code or the relevant tar-files for For Boost the packages in the distribution repository should work fine too.

NOTE: As PAWIAN parallelizes intensity calculations on the event level, all parallelization done by any minimizer has to be turned off. To compile Minuit2 with OpenMP disabled, run the corresponding configuration script with the --disable-openmp option:

./configure --disable-openmp

Compilation and Linking

To compile and run PAWIAN some environment variables have to be set. An example is given in the file "SetEnv_rub" in the top directory. The "Jamroot" file most likely has to be modified to let the paths (libraries, includes) match your local environment. Used path constants like ${ROOTSYS} or ${extern} are best defined in the site-config.jam configuration file in the boost-build directory, e.g:

/usr/share/boost-build/site-config.jam : (example directory, create file if not existing:)

path-constant ROOTSYS : <path to rootsys>

path-constant extern : <path to folder with external libraries>


Then you are ready for compiling and linking the code. By typing
  • "bjam" executables with debugging options will be created. These executables and the relevant libraries are then located at "subdirectory"/bin/<compile-version>/debug/link-static/
  • "bjam release" executables with optimized performance will be created (recommended for the actual PWA). Here you can find the relevant executables in "subdirectory"/bin/<compile-version>/release/link-static/
By typing "bjam clean" or "bjam release clean" you clean up your created executables and libraries and you can start to compile the code from scratch.

Starting an Example PWA

To test your PAWIAN installation, please have a look at the the example PWA tutorial.
Topic revision: r7 - 20 May 2020, MalteAlbrecht
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding PANDA Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)