Task List

The Task List is the main point of control for a system.

The Task List is a grid comprising of columns and rows.

The Task List contains tasks, which are defined by selecting a specific method to perform (for example): Instrument Calibrations, Stability Runs, Linearity Runs, Auto Tuning, Blanks, Standards and Sample Runs.

The Task List can be thought of as a "Sample List", as found in other software packages. We prefer to refer to it as a Task List because it is not just used to run samples.

A benefit of running routine operations such as Auto-Tunes and Stabilities in the Task list is that the task is automatically audited and can retrospectively be reviewed. This also allows the full features of the Task List to be used during instrument setup and not just for Sample runs. For example Scheduling, Delaying and Parametrization.

Although there is no limit to the number of tasks within a task list, it is recommended that you do not let task lists grow too big as it may affect the performance of lyticOS. For example, when starting lyticOS it may take some time to load a large task list.

It is recommended that you regularly create a new task list (e.g. every day, week or per project, etc.) depending on the number of samples that you are running.

As a rule of thumb, a task list should not contain more than several hundred tasks and ideally no more than 1000 tasks (although lyticOS does not enforce this limit).

Note: Only 1 task list can be open at any time.

Tasks

A Task can be thought of as an individual bit of "work".

To add a task click the "Add" button within the "Tasks" Ribbon Tab. This will either add an empty task to the task list (with no parameters set) or automatically create a quick copy of the most recently selected task in the Task List.

Every task has a common set of parameters that are editable within the Task List.

List of common fields that are available for all tasks within the task list

Column Name	Description
Id	An Id that is unique for the installation of lyticOS. Not editable by the user. Automatically populated when the task starts. If the task is exported and imported into another lyticOS installation, the Id is not changed (it is therefore, possible to have multiple tasks with the same Id. To Aid in validating uniqueness, the System Description can be used)
Name	Editable text field. Not required.
Method	The lyticOS method that will be run when the task starts. Required.
Sample Type	If the task is a sample, then the type of sample run can be specified. e.g. Blank, Sample, Standard, Sample with Internal Standard. Supported standards are configurable within lyticOS and therefore selectable by name. The default value is "None", which should be used for tasks that are not samples (e.g. Stability, Linearity, Auto-Tune, etc.). Setting the Sample Type simplifies the process of performing batch processing.
Row Number	Automatically populated to indicate the row number within the Task List.
Sample Id	Editable text field. Not required. Can be used to aid in the integration with LIMS systems.
Notes	Editable text field. Not required.
Batch	Used to define which batch a task should be automatically put into once the task is complete. Also indicates retrospectively what batches a task is in (e.g. if the task is in multiple batches).
Duration	Read-only field which displays the current running duration and predicted duration for a task. Once the task is complete, it will show how long the task took to complete.
Created Date	The date and time that the task was created.
Start Date	The date and time that the task was started.
Finish Date	The date and time that the task finished.
System Description	Automatically populated with the name of the system that the task was in when the task started.

A tasks common columns do not (under normal circumstances) affect the running of a task. The running of the task is solely influenced by the method that is chosen for each task and the associated method parameters.

The Method

The selected method for any task defines exactly what that particular task will do.

The method that is chosen for a Task governs what other columns become editable within the Task List. For example, if running a Sample Acquisition, you may want to input a vial number or sample weight. Through this mechanism, it is possible to customize how a method will run by setting method specific parameter values within the Task List. For example, a particular method may expose a "Delay" or "Duration" parameter to the Task List.

It is possible to customize which method parameters are editable within the task list. For more information see Methods.