Tasks and Jobs

Introduction

Tasks and Jobs are entities used for data processing. With them it is possible to write custom programs to process existing data or gather additional data from other resources. A task is the element containing code, files and definition of parameters. A task itself can't be run. For code execution a creation of a job is required. The job specifies all the required parameters and allows to setup execution related options.

Task

Each task has a type (e.g. Python). Based on its type it is handled accordingly. Generally tasks with different programming languages will have different type. Task can also have a subtype. For example two different subtypes may have different libraries available. As IVIS currently supports only Python for tasks this categorizations may change with incoming requirements.

Job

A job holds configuration for a task. There can be multiple jobs for the same task each with their own settings and parameters. A job can be run and we can set trigger conditions to automate execution.

Triggers

The framework provides UI for coding and mechanism for running jobs when given conditions are met. Such conditions include:

• Periodic trigger - run job once every set period of time
• Signal set trigger - run if new data are added to selected signal set
• Minimal interval - on execution command job runs only if set interval has passed since the last run
• Delay - on execution command job waits given period of time before running

API

The API for task developers is described in Tasks API.

Troubleshooting tasks

If the task environment doesn't build correctly, it might sometimes help to modify it manually. This is intended only for IVIS instance admins with direct access to the server. See details in Troubleshooting tasks.