Installation instructions

In order to understand the informatic organisation of the coupling, you can read this pdf.

Step I / Get the sources

Once the codes you want to couple are installed (AVBP/AVTP/PRISSMA, see Requirements), you have get the PrePALM canevas of the coupled different coupled applications.
On the NFS (on your home or wkdir), type the following commands to clone the Git archive:

You end up with the directory OPALM_AVBP_AVTP_PRISSMA that contains:

Step II / Link to the standalone codes

Go in the directory UNITS/, be sure that the variables AVBP_HOME (the path to the 1st level directory of AVBP, if you use it in the coupled application), AVTP_HOME (the path to the 1st level directory of AVTP, if you use it in the coupled application) and DOMHOME (the path to the 1st level directory of PRISSMA, if you use it in the coupled application) are well setted.
Type sh and check in the directories corresponding to the codes you want to couple that the link created by the tool ( are pointing on the good libraries of your codes.

Then, come back in the main directory (OPALM_AVBP_AVTP_PRISSMA/) and go to the directory corresponding to the case you want to treate (AVBP_AVTP/, AVBP_PRISSMA/, AVTP_PRISSMA/, AVBP_AVTP_PRISSMA/).
Be sure that the following files are up to date respectivly to the version of the code your are using:

Step III / Compilation

You are now ready to compile the application in order to create the executables that will be launched for the coupled simulation. First, you have to generate the PALM files either by loading the graphical interface PrePALM or direclty with the command prepalm --c [avbp_avtp][avbp_prissma][avtp_prissma][3codescoupling].ppl (where prepalm is your alias for PrePALM).
Then, you have to fill the Make.include file with the path where OpenPALM is installed as well as compilation option of the machine on which you are running. The directory OPALM_AVBP_AVTP_PRISSMA/HOST contains exemple of machine (CURIE, JADE, NEPTUNE, CORAIL).
Finally, type make to compile and generate the executable of the coupled application.