Release notes and instructions LOFAR Offline release 2.15.0

In order to build the LOFAR source code for release 2.15, you will first need to install the AOFlagger. Download and installation instructions for the AOFlagger can be found here:

Please note the following:

  1. To be able to use AOFlagger with LOFAR build, set the AOFlagger build flag: “-DBUILD_SHARED_LIBS=ON”
  2. In LOFAR build, use the Cmake flag “-DAOFLAGGER_ROOT_DIR=<your aoflagger install dir>” to link to your local AOFlagger install directory.
  3. If you have an older system (like our CEP2), you may not be able to build the graphical tools with AOFlagger. The LOFAR build will by default build them for you. If you want to make use of the tools provided by the AOFlagger build, you will need to explicitly NOT build these in the LOFAR build using the Cmake flag “-DBUILD_AOFlagger=OFF”

Further build instruction for building the LOFAR release can be found here:


  • #9020 - PyBDSM island masks are incorrect when two islands are very close together


  • #8859 - Add option to pyparameterset to remove quotes



  • #8912 - Show IO statistics in DPPP
  • #8820 - Initialize DPPP logger properly
  • #8967 - Segfault in GainCal
  • #8989 - GainCal leaves some data uncalibrated dependent on minblperant. WARNING: Calibrating flagged data will now mark a solution as 'Flagged', where previously it would write a solution with value 1.0. If you apply the flagged solution (with DPPP gaincal or BBS), your data will now be replaced with NaN and flagged. Please do not flag stations if you want to leave them out in a calibration run. Instead, filter them out using msin.baseline or a DPPP filter step.

Pipeline Framework

  • #7812 - External AOFlagger :!: Note: Should be installed to build Offline module!
  • #9014 - Update HBA/LBA flagging strategies

Further questions can be sent to (build/obtain), (policies, usage) or Tammo Jan Dijkema (; inner workings).

  • Last modified: 2017-03-08 15:27
  • (external edit)