Queues

A queue within ADFjobs is just a short-cut to set all job details for some selected job. In the Queue menu you see a list of defined queues. Selecting one of them means changing the job details from all selected jobs as defined in this particular queue.

You can define a queue in several ways: new (based on one of the included example queues), new (based on the job details settings from the selected job), or by editing an existing queue. One of the queues is the default queue: if you are going to run a job without setting the job details (either by specifying a queue, or by filling out the details by hand), ADFjobs will suggest to run the job in the default queue.

The simples queue is a local interactive queue. This is just called 'interactive' in the supplied examples. Normally, you will not need to make any changes to this. When you run ADFjobs for the first time, and it does not find any queues, it will automatically create one such queue for you.

Next is a remote interactive queue. Use the same settings as for the Interactive queue, except that you specify some remote machine (and optionally a remote user).

Finally, a queue might be configured such that your job ends up in some batch queue. For this to work, you need to use some submit command. Details for these commands differ very much depending on your batch system and its configuration. ADFjobs comes with some examples for LSF, PBE and SGE batch systems. You will need to change the commands to match the submit command you are supposed with your batch system.

When running a job, ADFjobs uses the information specified with Job Details to figure out the run command. Part of this might be the '$options' variable. This will be replaced by whatever the user puts in the input field to the right of the queue name (just before the job status). Thus, you can define one queue and use this field to specify a time limit, or the number of CPUs to use, or whatever else you wish.