| 295 | | |
| 296 | | |
| 297 | | For psmpi versions ''before'' 5.4.6, the Module IDs (`PSP_MSA_MODULE_ID`) were not set automatically! |
| 298 | | This means that the user had to set and pass this variable explicitly, for example, via a bash script: |
| 299 | | {{{ |
| 300 | | #!/bin/bash |
| 301 | | # Script (script0.sh) for Module 0: (e.g. Cluster) |
| 302 | | APP="./IMB-MPI1 Bcast" |
| 303 | | export PSP_MSA_AWARENESS=1 |
| 304 | | export PSP_MSA_MODULE_ID=0 # <- set an arbitrary ID for this module! |
| 305 | | ./${APP} |
| 306 | | }}} |
| 307 | | {{{ |
| 308 | | #!/bin/bash |
| 309 | | # Script (script1.sh) for Module 1: (e.g. ESB) |
| 310 | | APP="./IMB-MPI1 Bcast" |
| 311 | | export PSP_MSA_AWARENESS=1 |
| 312 | | export PSP_MSA_MODULE_ID=1 # <- set a different ID for this module! |
| 313 | | ./${APP} |
| 314 | | }}} |
| 315 | | {{{ |
| 316 | | > srun ./script0 : ./script1 |
| 317 | | }}} |
| 318 | | |
| 319 | | In addition, this script approach can always be useful if one wants to set the Module IDs ''explicitly'', e.g. for debugging and/or emulating reasons. |
| | 295 | In addition, this script approach can always be useful if the user wants to set the Module IDs explicitly, e.g. for debugging and/or emulating reasons. |
