1. Qube
2. Job Submission Dialog

Job Submission Dialog

...

• Set Defaults: Store as defaults in the User Preferences for that Jobtype, the values listed in the current submission dialog. The interface will use those values the next time the dialog is opened. This allows you to specify common fields like Priority or Executable that should always be the same value.
• Clear Defaults: Remove any stored defaults for that Jobtype submission dialog
• Expert Mode: Toggle button to display or hide export and non-default values from the submission dialog to reduce clutter when there are a lot of parameters. The current state of this toggle is stored in the Preferences Dialog.
• Save [Disk Icon]: Store the current properties of the job from the dialog as a file (by default an XML file). This can be used to submit through the WranglerView at a later time with "Submit->File…" or from the command line with the qbsub command, or via the API.
• Cancel: Cancel the job submission and close the dialog.
• Submit: Submit the job with the specified parameters to the Qube! Supervisor.

Basic Parameters

Basic Parameters for all Jobs

...

• Name: name used for the job, usually artist specified.
• Priority: priority of the job. A number between 1 and 9999. Lower numbers mean higher priority.
• CPUsInstances: The number of processes (or subjobs/instances) to run the job with at the same time. When rendering, this equates to the number of frames being rendered at the same time.

Render Thread and Job Reservation Controls

This section is located near the top of the submission UI, and is collapsed when 'Expert Mode' is not selected.  For applications that do not support setting the number of threads, this section is not visible at all.

...

Thread Control Behavior

...

Checking Use All Cores for applications or renderers that support auto-detection of the number of cores installed on a worker host will set the renderer's appropriate control to enable this feature. In the case of a Maya job, it sets renderThreads=0; for the Mentalray renderer, it sets autoRenderThreads=True.  It will try to "do the right thing" for each application where this control is visible.

...

As you change the Specific Thread Count control the reservations value will automatically update.

Parameters for Cmdline Jobs

...

• Command: The command to run on the Worker. Paths and syntax should be what the Worker's OS expects, not the submitting machine.
• Shell (Linux/OS X): Specify the shell to use when executing the command line on the Worker. Only visible in Expert Mode.

Parameters for Cmdrange Jobs

...

• Command: Same as the Cmdline Job, though it will substitute the following strings based on the frame being executed for the given task.
  • QB_FRAME_NUMBER
  • QB_FRAME_START
  • QB_FRAME_END
  • QB_FRAME_STEP
  • QB_FRAME_RANGE
• Range: The frame range to execute.
• Execution
  • Individual Frames
  • Chunks with n Frames
  • Split into n Partitions
• Ordering: Specify whether tasks should be executed in ascending, descending, or binary sort (first, last, middle, split the middle values, …) order.

...

Parameters for SimpleCmd Jobs

...

• All the fields for either Cmdline or Cmdrange jobs (see above), plus
  
• Cmd Template: String used to construct the command line along with the rest of the job parameters. Python string representations are used, e.g. %(val)s to represent the string value from "val". If listed, %(argv)s places all optional arguments at that location instead of at the end. This constructs a command line that is then used by the Cmdline or Cmdrange jobtypes on the Workers. See above for the string replace values for CmdRange.
• Executable – path to the renderer or executable to run. Unless it is in the path on the Worker's environment, this needs to be set to an absolute path (to where the executable is located on the Worker)

...