In this tutorial, we provide the commands to install ScalFMM and the needed tools in order to compute parallel efficiencies.
We first show how to obtain the homogeneous efficencies and then the heterogeneous ones (not done yet).
## Installing the libraries
For some installation steps, we provide a "valid-if" command which provide a basic test to ensure it should work.
For some installation steps, we provide a "valid-if" test which shows if the previous command has been done correctly or not.
In case of success `STEP-OK` will be print-out.
In addition, if a library is already installed on the system, it is possible to set the output variables directly and test with the "valid-if" command if it should work.
In addition, if a library is already installed on the system, it is possible to set the output variables directly and test with the "valid-if" command if it will work.
The installation and configuration to have the execution traces and executions times are marked as __Optional__ but higly recommended since they let have the efficiencies.
However, if one wants to execute without any overhead, it might need to remove the usage of FXT.
It is possible to follow these steps only to compile ScalFMM above StarPU and so we marked the installation of execution-trace tools as __Optional__.
However, we higly recommended to install them and to follow all the steps since they let have the efficiencies.
But if one wants to execute without any overhead, it might need to remove the usage of FXT.
### Pre-requiste:
In order to follow this tutorial, it is needed to have the following applications installed:
...
...
@@ -23,35 +27,33 @@ In order to follow this tutorial, it is needed to have the following application
* __Optional__ Vite (from `sudo apt-get install vite` or see [http://vite.gforge.inria.fr/download.php](http://vite.gforge.inria.fr/download.php))
* __Optional__ Qt5 library to be able to change the colors of the execution traces in order to visualize the different FMM operators
> Some installations of CUDA does not have libcuda file.
> [Remark] Some installations of CUDA does not have libcuda file.
> In this case, one needs to create a link : `sudo ln /usr/local/cuda-7.5/lib64/libcudart.so /usr/local/cuda-7.5/lib64/libcuda.so`
> We have run this tutorial with the modules : `module load compiler/gcc/4.9.2 cuda75/toolkit/7.5.18 intel/mkl/64/11.2/2016.0.0 build/cmake/3.2.1`
### Working directory
The variable `SCALFMM_TEST_DIR` is used to specify the working directory:
The variable `SCALFMM_TEST_DIR` is used to specify the working directory where all the tools are going to be installed:
```bash
export SCALFMM_TEST_DIR=~/scalfmm_test
if[[!-d$SCALFMM_TEST_DIR]];then
mkdir$SCALFMM_TEST_DIR
fi
export SCALFMM_TEST_DIR=~/scalfmm_test
cd$SCALFMM_TEST_DIR
```
In order to be able to stop the tutorial in the middle and restart later, we will keep the register variables in a file that should be source to restart.
In order to be able to stop the tutorial in the middle and restart later, we will register the variables in a file that should be source to restart later:
```bash
function scalfmmRegisterVariable(){echo"export $1=${!1}">>"$SCALFMM_TEST_DIR/environment.source";}
@@ -61,10 +63,21 @@ if [[ -n $SCALFMM_TEST_DIR ]] && [[ -d $SCALFMM_TEST_DIR ]] ; then
fi
```
### Downloading Packages
- Restarting the tutorial
To restart the tutorial, one needs to re-define the working directory and to source the save file before to resume:
```
export SCALFMM_TEST_DIR=~/scalfmm_test
if [[ ! -d $SCALFMM_TEST_DIR ]] ; then
mkdir $SCALFMM_TEST_DIR
fi
cd $SCALFMM_TEST_DIR
source "$SCALFMM_TEST_DIR/environment.source"
```
In case the node used for compiling/testing do not have access to internet, then download the following packages first.
### Downloading Packages
If the computational node does not have access to internet, we provide a command to download the needed packages (otherwise the next commands still include just in time download):
