Context Navigation

Changes between Version 4 and Version 5 of GridEngine

-                      v4
+                      v5
 Then record the job ID as reported. Whatever output there will be from the script will be saved into a file named as your job file, but extended with `.oNNNN` where NNNN is your job ID. Once your job is run, check the file to ensure that the job succeeded. This is best done with the command `less` (e.g. `$ less my_job_file.job.oNNNN`). See below for how to get more information on if your job is running. You should check the mail you got from GridEngine regarding how the job was run (or use `qacct -j JOB_ID` to get the same information). First check that the exit_status is zero. If not, your job failed. Check how long time the job used ("wallclock"). If it is equal to the requested time, the job most likely failed due to insufficient run time (increase the runtime requested and try to rerun your job). Go on and check how much memory was used (max_vmem), if it is equal to the requested amount, your job most likely failed due to lack of memory (update your job file and request a few more GB). If none of these two factors seem to be the culprit, check the output of your job for error messages.
+=== Multithreading option ===
+If you need to run your job with multiple threads you can do so by using the following command:
+ -pe smp (int)
+ -pe openmpi (int)
 For more information on what you can do with qsub, check the man page (`$ man qsub`)