Jobs FAQs
I used the module command but it still can't find the application that I am trying to use
If you want your job to access an application via the module command you will need to modify your
.bashrcso that it is automatically loaded by your job script. An easy way to check is to submit an interactive job (usinginteractivecommand) and then run module list to see what modules are available to your job.
- Once it has been assigned to a node the intricacies of the scheduling policy means that it becomes impossible for anyone including the administrator to make any further changes.
- The best way to determine what the resource requirements of your job is to run it for the first time whilst being generous with the resource requirements and then refine the requirements based on what the job actually used.
- The queues are set up to be first-in-first-out. The scheduler runs jobs and whose resourse requirements can be currently satisfied. Otherwise the job is queued until resources are available.
If your job uses more memory than you requested then it may cause issues on the active node. For example the extra memory you use becomes unavailable to another job that thinks that it is there to use so active memory will be swapped to the local disk and the node will slow to a crawl. To avoid this any job that uses more memory than requested will be terminated by the scheduler.
- Currently there is no limit (walltime) on the amount of time any job can run.