Installing SOLPS-ITER on Marconi Gateway

Tip

Marconi/Gateway is a properly configured site and therefore the standard instructions on the Installation overview page should be sufficient. This page is a more detailed guide for those who are not familiar with the Gateway environment.

This tutorial is based in part on my and Aleš's experience and in part on $SOLPSTOP/docs/SOLPS-ITER_Download_and_installation.pdf. You may also refer to chapter 1.1 of the manual. Marconi Gateway is the goto machine for running SOLPS-ITER simulations. All the required libraries are available, so you can cheerfully avoid all the complicated hassle, which one is typically bound to run into when trying to install SOLPS-ITER.

Get into the Gateway command line, which can be done in two ways:
- local command line:
```
ssh -X username@login.eufus.eu
```
- set up an NX client (see Remote access)
- If you've forgotten your Gateway password, contact francesco.iannone@enea.it and ask him to reset it.
According to David Coster, you should not install SOLPS-ITER into your home folder. Use your folder in /pfs/work/ instead.:
```
cd /pfs/work/g2kjirak/
```
Download the source code of SOLPS-ITER into this folder:
```
git clone ssh://git@git.iter.org/bnd/solps-iter.git
```
If you get the error
```
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.
```
...you first need to set up SSH key authentication to identify your machine with your ITER user account. Go to https://git.iter.org/plugins/servlet/ssh/account/keys, log in and add a public key corresponding to a private key in your ~/.ssh/ folder. If you don't have any SSH keys generated yet, you can create them using
```
cd ~/.ssh
ssh-keygen -t rsa -C "your_email@example.com"
```
For added security, it is recommended to enter a non-empty private key passphrase. Once your keys are generated, upload (that is, copy-paste the inside of the id_rsa.pub file) your new public key to the public key list.
Get into the solps-iter folder:
```
cd solps-iter
```
Update the source code to the current master branch:
```
git submodule init
git submodule update
```
warning The manual also instructs to follow with these individual checkout calls below. However, they are not necessary (git submodule update does that already) and they are definitely not a good practice...
```
git checkout master
cd modules/B2.5
git checkout master
cd ../Eirene
git checkout master
cd ../DivGeo
git checkout master
cd ../Carre
git checkout master
cd ../adas
git checkout master
```
If you need any other branch than master, this is where you switch to it (after updating the submodules).
Switch to the tcsh shell:
```
tcsh
```
Set up SOLPS environment (basically tell the terminal where to look for special commands):
```
source setup.csh
```
If this is a clean new installation of SOLPS-ITER, run first_setup for good luck:

warning I believe that first_setup is intended only when setting up configuration of SOLPS-ITER on a completely new site. It generates default setup/config files if any are missing. But there is no harm in running it anyway.
```
first_setup
```
(There are several reasons why one might want several installations of SOLPS-ITER in their file space. The most benign one is that you're running several SOLPS-ITER versions for their respective quirks. The most common one is that a previous installation stopped working and you're making a fresh start.)
Compile SOLPS using 4 parallel processes:
```
gmake -j 4
```
- We're compiling in parallel so that it's faster, but this means that the compilation can crash because one process wants files which the other process has not created yet.
- The compilation always takes off where it crashed previously, so you can run gmake until it's done.
- Even after gmake exits and you see no error, run it again just to make sure that it's really done (my EIRENE once complained that it can't triangulate because it's missing the executable files - they had not compiled during gmake and I thought it was fine because there was no error message).
Alternative, slower way (doesn't have the issue off throwing errors because one process couldn't wait until another was finished, but takes a long time):
```
solps-iter_update
```
Congrats, your SOLPS-ITER is installed.

Minor alternatives to installing the entire SOLPS-ITER

Refer also to chapter 1.3 of the manual.

Compile parallelisation of EIRENE:

gmake b25eirene_mpi

Compile the debugging version of B2.5:

gmake listobj_debug; gmake depend_debug; gmake b25eirene_debug

Compile only B2.5:

gmake b25

Compile only EIRENE:

gmake eirene