...
You should see the test jobs or other jobs that you have submitted. Notice that they are color coded - if you are lucky, they will all be blue, which is the color of a successfully completed job. Jobs which failed are colored red. The jobs also have a status, such as "complete", "failed" or "running." Running jobs are shown in green. There are other colors for other statuses, which you will become familiar with as you submit and monitor jobs.
Let's have a look at some simple tasks you can do from this UI. First, click on one of your test jobs in the Jobs pane.
...
Notice that in the panel below the Jobs panel, you can look at the Job Properties on one tab, and the Output on the next two tabs (Output Log & Error Log). This is the Job Details panel - we'll cover that in a second.
<image of Properties panel>
...
If you want to rerun the job, but change some of the submission parameters - maybe the frame range was wrong, or you want to send the output to a different location - then you want to resubmit. Again right-mouse on the job line in the Jobs panel, and choose Resubmit. In this case you will get a Qube submission dialog, and you can modify any of the parameters before hitting "Submit". Note that when you resubmit, you are creating a new job with a new job ID. This is different from retrying an existing job.
Finally, you may want to kill a job. If you have a long running job and you know the results are going to be wrong, or you want to stop it for some other reason, you can kill the job. This is also a right-mouse button menu entry.
...
Note that asking the Supervisor for an update every few seconds puts more load on it, and if there are many artists all doing the same thing, you could be slowing down the overall farm just for the sake of convenience. Think twice before asking for lots of updates you aren't going to be noticing anyway.
Looking at Job
...
Details
The Job Details panel has a number of tabs. The first one, Job Properties, lists a number of attributes of the job, including the frame range and the command and/or scene file used.
The next two are useful for finding out what went wrong with jobs that fail (or getting logging information from jobs that succeed). Most output will go to the first tab, Output Log. Some programs will send error messages and other information to a separate stream, which goes to the Error Log. Scroll to the bottom of either of these - error messages are coded in red, warnings in yellow and info (as determined by the program being run) in green. All of the tabs and their uses are explained in more detail in the User's Guide.