Bureaucrats, cc_docs_admin, cc_staff
2,306
edits
Chapel: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 45: | Line 45: | ||
Installing multi-locale (distributed-memory) Chapel requires fine-tuning its launcher for the specific physical interconnect on the cluster. Since Compute Canada clusters Cedar and Graham employ two different physical interconnects, we do not have one multi-locale Chapel module for both machines. Instead, multi-locale Chapel has been compiled in a separate directory as an experimental setup on each system. You can test this setup with the following Chapel code printing basic information about the nodes available inside your job: | Installing multi-locale (distributed-memory) Chapel requires fine-tuning its launcher for the specific physical interconnect on the cluster. Since Compute Canada clusters Cedar and Graham employ two different physical interconnects, we do not have one multi-locale Chapel module for both machines. Instead, multi-locale Chapel has been compiled in a separate directory as an experimental setup on each system. You can test this setup with the following Chapel code printing basic information about the nodes available inside your job: | ||
< | </translate> | ||
{{ | {{ | ||
File | File | ||
| Line 61: | Line 61: | ||
} | } | ||
}} | }} | ||
<translate> | |||
Load Chapel and start an interactive job requesting four nodes and three cores on each node: | Load Chapel and start an interactive job requesting four nodes and three cores on each node: | ||
{{Command |module unload chapel-single}} | |||
Once the interactive job starts, you can compile and run your code from the prompt on the first allocated compute node: | Once the interactive job starts, you can compile and run your code from the prompt on the first allocated compute node: | ||
chpl probeLocales.chpl -o probeLocales | chpl probeLocales.chpl -o probeLocales | ||
./probeLocales -nl 4 | ./probeLocales -nl 4 | ||
For production jobs, please write a Slurm submission script and submit your job with <code>sbatch</code> instead. | For production jobs, please write a Slurm submission script and submit your job with <code>sbatch</code> instead. | ||
</translate> | </translate> | ||