Difference between revisions of "Development and Testing"
m |
m |
||
| Line 11: | Line 11: | ||
$ srundev --time=01:00:00 | $ srundev --time=01:00:00 | ||
| − | The srundev command is a wrapper around the | + | The srundev command is a wrapper around the <code>srun --partition=hpg2-dev --pty bash -i</code> command. |
;Note: | ;Note: | ||
Revision as of 13:02, 19 July 2016
If you need to develop code (i.e., the standard edit, build, test cycle) or test your workflows and scripts before submitting batch jobs, you should do it within an interactive developmental session under SLURM. The software environment on the nodes within the dev partition is kept consistent with that of the compute servers so you can run jobs and get an accurate idea of what resources are used.
Please remember that you are not allowed to run user applications on the login servers. Interactive work of any kind must be performed in a developmental SLURM session.
Access
Connect to the cluster (ssh user@hpg2.rc.ufl.edu) and use SLURM to start a developmental session.
For example, to get a one-hour session with the default 1 processor core and 2gb of memory:
$ module load ufrc $ srundev --time=01:00:00
The srundev command is a wrapper around the srun --partition=hpg2-dev --pty bash -i command.
- Note
- The default time limit for the hpg2-dev partition is 00:10:00 (10 minutes). The maximum time limit in the dev partition is 12 hours.
- At this time, you will not be able to access a development session if your invested resources are fully engaged.