Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you need user interaction , or are only running something once , or don't have enough time to learn to write a batch file, then run `sinteractive`. This will ask you for the resources you require and then dump you into a screen session on a node. If you don't know what that entails, just try it. Be sure to exit from your sinteractive session when you're done, otherwise you're a terrible person for requesting resources you aren't using. See the full SLURM user documentation if you need to make batch jobs or want to learn about other cool commands like squeue, sbatch, scontrol, sacct, scancel, and smap.

Try to avoid requesting far more resources than you need on the cluster. Any resources that you tell SLURM you're going to use cannot be offered to other users regardless of whether you actually use those resources. If you fudge your numbers too much, you're eligible to have your allocation terminated by admins.

Sinteractive is not the best way to run jobs by any means.  For any sort of repeatable workflow, you need to write batch jobs.

Software

Basic interpreted languages are there (Python, Perl, BASH). If you can't find something you need, we might have it as a module. Run `module avail` to see what modules we have available for loading. From that list, you can run `module load <NAME>/<VERSION>` where <NAME>/<VERSION> is from that list. For example, you can run `module load R/3.1.1` and then you magically have access to that version of R.

...