Pipeline 1—The Job Perspective
The Job Perspective is the main window of the DAISY Pipeline GUI, containing three main views. Here, you can create and add jobs, run them, and monitor their progress. Jobs can be added via the New Job Wizard.
The Jobs View can be thought of as a job queue. Each Job that is created is available as an entry in this view. You can expand the Job to review details of its configuration. Depending on the state of a job, the status column of the Jobs view will flag the status as:
- completed or
If you are creating a queue of Jobs, you can reorder the queue via the arrow buttons in the top right corner of the Jobs view.
The Run menu item contains entries for running all of the currently selected job. The same applies to the cancel command. You can also use the Run and Cancel buttons at the top left part of the Jobs View.
To delete one or several jobs in the queue, select the job(s), and use the delete key on your keyboard, or the delete button at the top right part of the Jobs View. You can also clear all finished jobs by using the clear all finished jobs button at the at the top right part of the Jobs View.
While a job is running, you can monitor its progress in the Progress View. The Progress View contains one entry for each Transformer that the script contains.
The Messages View lists messages generated by the DAISY Pipeline while jobs are running. Some of these messages are for information only, for example, confirming that parts of the Job have been successful. However, other messages are critically important, and notice should be taken. For example, if a job fails, the reason for the failure will be provided here. Similarly, when a job includes validation, the result of the validation will be reported here.
There are four main types of messages:
- Info—for information only; giving you progress and context information.
- Warning—indicates that a possible problem has occurred; the Job may complete as intended, but extra caution should be taken to assure the result is ok.
- Error—indicates that an error has occurred that either caused the job to abort prematurely, or caused the output to be erroneous or incomplete.
- Debug—for running the Pipeline in Debug mode, something which you may be asked to do if you encounter a bug, and the developer or support technician requests more information. Note: this message type is filtered out by default, meaning that in order to see these messages, you need to turn off the DEBUG message filter.
The message type is listed for each message in the right column of the Messages table view.
Given the wide variety of functionality within the Pipeline, there are a vast amount of messages that can be emitted. For this reason, it is not possible to explain all of the in this manual.
Below are explanations for 2 types of message:
- Failed deleting temporary resource. The Pipeline uses temporary directories to store data during job execution. Usually, this temporary directory can be found in the Paths section of the Preferences dialog. However, some scripts use a temporary subdirectory of your output directory to store temporary data. In some instances (such as when this directory is in use by another application), the Pipeline can not delete these files.The files are typically stored in a subdirectory of your output directory called pipeline__temp. You can manually delete this folder after the job has finished.
- null. An admittedly nihilistic message that, if it is of type ERROR, indicates that you have encountered a bug. If that is the case, you should open the Error Log, save the information there to a log file, and report the bug, providing the log file as an attachment.
Messages can be filtered and grouped by type and job. The filtering and grouping options are available in the right top corner of the Messages View. and there is a dedicated icon for filtering each message type.
You can also access this functionality via the View menu in the Messages Tool Bar (a downwards white triangle icon). Alternatively, in the Window menu’s Navigation entry, select the Show View Menu command while the Messages View has focus.
By selecting the export messages option in the top right corner of the Messages View, you can save messages as a log file.Tags: Pipeline 1