Both sides previous revision Previous revision Next revision | Previous revision |
doku:forge [2024/07/05 07:48] – grokyta | doku:forge [2024/07/05 07:51] (current) – [ddt (semi-interactive via sbatch):] grokyta |
---|
... click OK twice to close the dialogues | ... click OK twice to close the dialogues |
... click Close to exit from the Configure menu | ... click Close to exit from the Configure menu |
... next really select 'Remote Launch' by clicking the name tag that was auto-assigned # (will again ask for a Password/OTP, then the licence label should come up ok in the lower left corner and the connecting client should appear in the lower right corner ) | ... next really select 'Remote Launch' by clicking the name tag that was auto-assigned # (will again ask for a Password/OTP, |
| then the licence label should come up ok in the lower left corner and the connecting client should appear in the lower right corner ) |
</code> | </code> |
<code> | <code> |
... don't forget to include 'module load allinea/18.2_FORGE' and '#SBATCH -L allinea@vsc' | ... don't forget to include 'module load allinea/18.2_FORGE' and '#SBATCH -L allinea@vsc' |
... the actual program execution should be prefixed with 'ddt --connect --np=32 ...' we better avoid express launch style | ... the actual program execution should be prefixed with 'ddt --connect --np=32 ...' we better avoid express launch style |
my_uid@l35$ sbatch ./run.ddt.slrm.scrpt # (in the other ddt-window sent into the background initially, a separate window pops up saying 'Reverse Connect Request' which needs to be accepted, then the usual ddt options will become available and the actual session may be launched by clicking 'Run') | my_uid@l35$ sbatch ./run.ddt.slrm.scrpt # (in the other ddt-window sent into the background initially, a separate window pops up saying 'Reverse Connect Request' |
| which needs to be accepted, then the usual ddt options will become available and the actual session may be launched by clicking 'Run') |
</code> | </code> |
| |
... click OK twice to close the dialogues | ... click OK twice to close the dialogues |
... click Close to exit from the Configure menu | ... click Close to exit from the Configure menu |
... next really select 'Remote Launch' by clicking the name tag that was auto-assigned above # ( licence label should be ok in the lower left corner and the hostname of the connecting client should appear in the lower right corner ) | ... next really select 'Remote Launch' by clicking the name tag that was auto-assigned above # ( licence label should be ok in the lower left corner |
| and the hostname of the connecting client should appear in the lower right corner ) |
| |
ssh vsc3.vsc.ac.at -l my_uid # a second terminal will be needed to actually start the debug session | ssh vsc3.vsc.ac.at -l my_uid # a second terminal will be needed to actually start the debug session |
my_uid@n305-044$ cd wherever/my/app/may/be | my_uid@n305-044$ cd wherever/my/app/may/be |
my_uid@n305-044$ srun --jobid 8909346 -n 16 hostname # just a dummy check to see whether all is set up and working correctly | my_uid@n305-044$ srun --jobid 8909346 -n 16 hostname # just a dummy check to see whether all is set up and working correctly |
my_uid@n305-044$ ddt --connect srun --jobid 8909346 --mpi=pmi2 -n 64 ./a.out -arg1 -arg2 # (in the initial ddt-window a dialogue will pop up prompting for a Reverse Connection request; accept it and click Run and the usual debug session will start ) | my_uid@n305-044$ ddt --connect srun --jobid 8909346 --mpi=pmi2 -n 64 ./a.out -arg1 -arg2 # (in the initial ddt-window a dialogue will pop up prompting |
| for a Reverse Connection request; accept it and click Run and the usual debug session will start ) |
</code> | </code> |
| |