MPI4py: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 187: Line 187:
</tab>
</tab>
</tabs>
</tabs>
<!--T:35-->
2. Submit your job to the scheduler.


<!--T:36-->
<!--T:36-->
2.1 Test your script.
2. Test your script.


<!--T:37-->
<!--T:37-->
Before submitting your job, it is important to test that your submission script will start without errors.
Before submitting your job, it is important to test that your submission script will start without errors. You can do a quick test in an [[Running_jobs#Interactive_jobs|interactive job]].
You can do a quick test in an [[Running_jobs#Interactive_jobs|interactive job]].


<!--T:38-->
<!--T:38-->
2.2 Submit your job
3. Submit your job to the scheduler.
{{Command|sbatch submit-mpi4py-distributed.sh}}
{{Command|sbatch submit-mpi4py-distributed.sh}}


Line 239: Line 235:
<!--T:45-->
<!--T:45-->
srun python use_cupy.py;
srun python use_cupy.py;
}}


<!--T:46-->
<!--T:47-->
2. Submit your job to the scheduler.
2. Test your script.


<!--T:47-->
2.1 Test your script.


<!--T:48-->
<!--T:48-->
Before submitting your job, it is important to test that your submission script will start without errors.
Before submitting your job, it is important to test that your submission script will start without errors. You can do a quick test in an [[Running_jobs#Interactive_jobs|interactive job]].
You can do a quick test in an [[Running_jobs#Interactive_jobs|interactive job]].


<!--T:49-->
<!--T:49-->
2.2 Submit your job
3. Submit your job to the scheduler.
{{Command|sbatch submit-mpi4py-gpu.sh}}
{{Command|sbatch submit-mpi4py-gpu.sh}}


rsnt_translations
56,420

edits

Navigation menu