What about MonolixSuite running on a cluster ?

MonolixSuite can run on a cluster.

Monolix installation

To run MonolixSuite on a cluster, each cluster node must have access to the MonolixSuite directory and to the user home directory. Thus, there are two possibilities.

  1. MonolixSuite is installed on each node. In that case, each node has a MonolixSuite installation.
  2. MonolixSuite installation is shared. MonolixSuite is installed on a master server. Each cluster node accesses to MonolixSuite through a shared directory (via CIFS, Network drive, NFS, …).

License management

On a cluster, we are managing the usage of our applications with the license management system described here.
The license management server is on a physical machine and manage the application through its license file. The associated license file has to be put in the folder {MonolixSuite install path}/config/system/access (and also {MonolixSuite install path}/bin/Monolix_mcr/runtime/config/system/access for MonolixSuite2016R1). So either on all nodes in the installation case 1, or only on the master server in the configuration 2.

Running Monolix on a cluster

To run Monolix with the command line: in the lib folder (typically $HOME/Lixoft/MonolixSuite2018R1/lib/)

monolix -p mlxtran_project_path

where mlxtran_project_path is a Monolix project with a .mlxtran extension. Notice that a typical project from the demo can be found here $HOME/Lixoft/MonolixSuite2018R1/resources/demos/monolix/1.creating_and_using_models/1.1.libraries_of_models/theophylline_project.mlxtran

Generally, a task is submitted to the cluster using a specific command, e.g. qsub in the case of Torque, PBS or GridEngine (former SGE). This command runs a script, provided as parameter, on a cluster node chosen by the cluster scheduler.To run Monolix on a cluster: in the lib folder (typically $HOME/Lixoft/MonolixSuite2018R1/lib/)

qsub qSubOptions monolix -p mlxtran_project_path

where qSubOptions corresponds to your cluster options.
To run using mpi with the command line: in the lib folder (typically $HOME/Lixoft/MonolixSuite2018R1/lib/)

mpirun mpiOptions distMonolix -p mlxtran_project_path

where mpiOptions corresponds to your mpi options. Notice that the mpirun call another program that requires another license.
In addition, the package was done with openmpi 1.6. If you have a more recent version (1.8, 1.10 or 2.0) version, you just have to create a symbolic link from your installation

  • from your installation of libmpi.so (usually in /usr/lib64/openmi/lib/libmpi.so.XX) to libmpi.so.1 (in our lib folder).
     sudo  ln -s your_installation_of_openmi/lib/libmpi.so.XX  installation_of_MonolixSuite2018R1/lib/libmpi.so.1
  • from your installation of libmpi.so (usually in /usr/lib64/openmi/lib/libmpi_cxx.so.XX ) to libmpi_cxx.so.1
    (in our lib folder).

     sudo  ln -s your_installation_of_openmi/lib/libmpi_cxx.so.XX   installation_of_MonolixSuite2018R1/lib/libmpi_cxx.so.1
    

For further assistance, contact us.

Jonathan CHAUVINWhat about MonolixSuite running on a cluster ?