Changes between Version 1 and Version 2 of MpiKernels
- Timestamp:
- 10/20/11 12:30:03 (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
MpiKernels
v1 v2 1 Since revision **67** in SVN branch **inst_procedure** it is possible to use MPI kernels with MUSCLE.1 Since revision **67** of SVN branch **inst_procedure** it is possible to use MPI kernels within MUSCLE framework. 2 2 3 4 == Limits & requirements == 3 == Limitation and Requirements == 5 4 6 5 … … 8 7 === MPI implementation === 9 8 10 Currently OpenMPI //does not support// binding with JNI (see [http://www.open-mpi.org/community/lists/devel/2005/09/0359.php this bug])9 Currently OpenMPI //does not support// applications that dynamically loads library (thus it does not work with JNI) - see [http://www.open-mpi.org/community/lists/devel/2005/09/0359.php this bug]). You need to use other MPI implementations: 11 10 12 11 The following implementation have been tested so far: … … 17 16 18 17 19 When using MPI in some kernel, this kernel must be run as the only in this muscle instance. Other kernels, as well as main, must be run fromother MUSCLE instances.18 When using MPI in the kernel, this kernel must be run as the only one in this muscle instance. Other kernels, as well as main, must be run from the other MUSCLE instances. 20 19 21 20 == Preparing source code == … … 31 30 As in Java, only process with Rank 0 may use MUSCLE routines, such as portals or the kernel.willStop() method. User is responsible for stopping all the processes once the kernel should stop. 32 31 33 MPI should be used in the naturalway, i.e. the program should start with MPI::Initialize() and finish with MPI::Finalize().32 MPI should be used in the standard way, i.e. the program should start with MPI::Initialize() and finish with MPI::Finalize(). 34 33 35 34 == Running MPI kernels == 36 35 37 36 To run a MPI kernel, one must distribute the processes with `mpirun`/`mpiexec` utility. One kernel per one MUSCLE instance allowed. 38 It is crucial to add the --mpi parameter for the muscle command - otherwise the simulation will fail, as multiple identical MUSCLE instances will arise.37 It is crucial to add the --mpi parameter for the muscle command - otherwise the simulation will fail, as multiple identical MUSCLE instances will be initialized. 39 38 40 39 `mpirun -n 5 muscle --mpi --cxa_file src/cxa/Test.cxa.rb mpi` 41 40 42 41 43 Of course, in another process the main must be started, as well as other kernels required by the cxa file, for example42 Of course, in another process the `--main` parameter must be given, as well as other kernels required, for example 44 43 45 44 `muscle --main plumber --cxa_file src/cxa/Test.cxa.rb --autoquit` 46 45 47 An example ( started with the commandsabove) has been added to the SVN in revision 68.46 An example (which can be started with the commands shown above) has been added to the SVN in revision 68.
