Recent changes to installation_instructions

installation_instructions modified by André Offringa

André Offringa — Thu, 20 Feb 2020 09:23:19 -0000

--- v45
+++ v46
@@ -53,7 +53,7 @@

     :::bash
     apt-get install liblua5.3-dev libfftw3-dev libboost-dev libboost-date-time-dev \
-    libboost-filesystem-dev libboost-python-dev libboost-system-dev libboost-signals-dev \
+    libboost-filesystem-dev libboost-numpy-dev libboost-python-dev libboost-system-dev libboost-signals-dev \
     libboost-thread-dev libxml2-dev liblapack-dev libcfitsio-dev libgtkmm-3.0-dev \
     cmake g++ libpng-dev

installation_instructions modified by André Offringa

André Offringa — Thu, 20 Feb 2020 09:21:44 -0000

--- v44
+++ v45
@@ -53,7 +53,7 @@

     :::bash
     apt-get install liblua5.3-dev libfftw3-dev libboost-dev libboost-date-time-dev \
-    libboost-filesystem-dev libboost-system-dev libboost-signals-dev \
+    libboost-filesystem-dev libboost-python-dev libboost-system-dev libboost-signals-dev \
     libboost-thread-dev libxml2-dev liblapack-dev libcfitsio-dev libgtkmm-3.0-dev \
     cmake g++ libpng-dev

installation_instructions modified by André Offringa

André Offringa — Thu, 20 Feb 2020 09:14:08 -0000

--- v43
+++ v44
@@ -52,7 +52,7 @@
 I disencourage you to compile gtkmm yourself; it has many dependencies. Rather use your package manager (or ask your system administrator). Debian ships this library as "libgtkmm-3.0-dev". Here is an apt command for Debian / Ubuntu systems that installs everything except Casacore:

     :::bash
-    apt-get install libfftw3-dev libboost-dev libboost-date-time-dev \
+    apt-get install liblua5.3-dev libfftw3-dev libboost-dev libboost-date-time-dev \
     libboost-filesystem-dev libboost-system-dev libboost-signals-dev \
     libboost-thread-dev libxml2-dev liblapack-dev libcfitsio-dev libgtkmm-3.0-dev \
     cmake g++ libpng-dev

installation_instructions modified by André Offringa

André Offringa — Thu, 20 Feb 2020 09:12:43 -0000

--- v42
+++ v43
@@ -13,11 +13,11 @@

 ### On Red Hat

-The following document lists some instructions that can be helpful for instaling AOFlagger on Red Hat: [Installing AOFlagger on rhel 7.6](Installation instructions RHEL 7.6) (Thanks to Leonardo Saavedra from NRAO).
+The following document lists some instructions that can be helpful for installing AOFlagger on Red Hat: [Installing AOFlagger on rhel 7.6](Installation instructions RHEL 7.6) (Thanks to Leonardo Saavedra from NRAO).

 ### Help with installation

-If you are unsure about installing AOFlagger and you are doing it for the first time, take this into account:
+If you are unsure about installing AOFlagger and you are installing it for the first time, take this into account:

  * It is easiest to install AOFlagger on a Linux machine. Ubuntu, Debian and derived distributions are most easy to install to. Red Hat and derived distributions (e.g. CentOS) are harder if you want to have the graphical interface. This is mainly because Red Hat doesn't ship an up-to-date GTKMM package, which is required for the graphical interface.
  * It is easier when you can get root access to install distribution packages. This is particularly the case if you want the graphical interface. 
@@ -34,6 +34,8 @@
 * [FFTW](http://www.fftw.org/), used to perform Fourier transformations.

 * [Boost](http://www.boost.org/), used for date and time calculations, python connections and some other general functionalities.
+
+* [Lua](https://www.lua.org/download.html), the language used by AOFlagger for defining flagging strategies (since AOFlagger 2.15).

 * [libxml](http://xmlsoft.org/), used for saving scripts / configurations.

installation_instructions modified by André Offringa

André Offringa — Thu, 12 Sep 2019 07:50:17 -0000

--- v41
+++ v42
@@ -93,7 +93,7 @@
     cmake ../ -DCMAKE_INSTALL_PREFIX=/home/esmeralda/

 ### Using the Python interface
-The Python libs are build by default, but currently there's no direct way to have the python aoflagger lib installed in your path. After compilation, the python library is called `aoflagger.so` and placed in aoflagger/build/src. If one makes sure the lib is in the python path, it is then possible to do `import aoflagger` in Python.
+The Python lib that is necessary to use the [Python interface](python_interface), are build by default, but currently there's no direct way to have the python aoflagger lib installed in your Python path. After compilation, the python library is called `aoflagger.so` and placed in aoflagger/build/src. It is possible to use the interface (e.g. do `import aoflagger`) in Python as long as the lib is manually put in the python path. (I hope this get fixed soon, but the Python 2 to 3 transition + state of debian boost python made this rather hard).

 As of yet (2019-09-21; aoflagger 2.14.1) only trunk has good support for interfacing with Python. As long as 2.15 has not been released, make sure to use the latest master version of aoflagger (from git), as the Python interface is much more complete in master.

installation_instructions modified by André Offringa

André Offringa — Thu, 12 Sep 2019 07:46:27 -0000

--- v40
+++ v41
@@ -7,7 +7,7 @@

 ### Debian/Ubuntu package

-Since december 2016, AOFlagger is available in Debian and Ubuntu. All one need to do to install it there is:
+Since december 2016, AOFlagger is available in Debian and Ubuntu. All one need to do to install it on Debian/Ubuntu system is:

     sudo apt-get install aoflagger

@@ -33,7 +33,7 @@

 * [FFTW](http://www.fftw.org/), used to perform Fourier transformations.

-* [Boost](http://www.boost.org/), used for date and time calculations and some other general functionalities.
+* [Boost](http://www.boost.org/), used for date and time calculations, python connections and some other general functionalities.

 * [libxml](http://xmlsoft.org/), used for saving scripts / configurations.

@@ -92,6 +92,11 @@
     :::bash
     cmake ../ -DCMAKE_INSTALL_PREFIX=/home/esmeralda/

+### Using the Python interface
+The Python libs are build by default, but currently there's no direct way to have the python aoflagger lib installed in your path. After compilation, the python library is called `aoflagger.so` and placed in aoflagger/build/src. If one makes sure the lib is in the python path, it is then possible to do `import aoflagger` in Python.
+
+As of yet (2019-09-21; aoflagger 2.14.1) only trunk has good support for interfacing with Python. As long as 2.15 has not been released, make sure to use the latest master version of aoflagger (from git), as the Python interface is much more complete in master.
+
 ### Building with NDPPP

 To build AOFlagger so that it can be linked with NDPPP, it is necessary to make shared libraries. This is in most cases not the default. The normal way to build shared libraries is by specifying "-DBUILD_SHARED_LIBS=ON" to cmake, for example:

installation_instructions modified by André Offringa

André Offringa — Mon, 24 Jun 2019 20:56:37 -0000

--- v39
+++ v40
@@ -11,6 +11,9 @@

     sudo apt-get install aoflagger

+### On Red Hat
+
+The following document lists some instructions that can be helpful for instaling AOFlagger on Red Hat: [Installing AOFlagger on rhel 7.6](Installation instructions RHEL 7.6) (Thanks to Leonardo Saavedra from NRAO).

 ### Help with installation

installation_instructions modified by André Offringa

André Offringa — Tue, 11 Jun 2019 06:17:30 -0000

--- v38
+++ v39
@@ -9,7 +9,7 @@

 Since december 2016, AOFlagger is available in Debian and Ubuntu. All one need to do to install it there is:

-    apt-get install aoflagger
+    sudo apt-get install aoflagger

 ### Help with installation

installation_instructions modified by André Offringa

André Offringa — Thu, 14 Feb 2019 22:28:48 -0000

--- v37
+++ v38
@@ -30,7 +30,7 @@

 * [FFTW](http://www.fftw.org/), used to perform Fourier transformations.

-* [Boost](http://www.boost.org/), used for threading, date and time calculations and some other general functionalities.
+* [Boost](http://www.boost.org/), used for date and time calculations and some other general functionalities.

 * [libxml](http://xmlsoft.org/), used for saving scripts / configurations.

installation_instructions modified by André Offringa

André Offringa — Thu, 06 Apr 2017 14:10:54 -0000

--- v36
+++ v37
@@ -97,3 +97,11 @@
     cmake ../ -DBUILD_SHARED_LIBS=ON

 Once you have installed AOFlagger (with make install), NDPPP should now automatically find the library.
+
+### Building a machine independent binary
+
+To build AOFlagger so that it can run on any machine, add -DPORTABLE=True to the cmake command line:
+
+     :::bash
+     cmake ../ -DPORTABLE=True
+