In this section we review the concept of computational "Jobs", which consist in the application of a Workflow (or simulation) on a Material to produce one or more Properties.
Job is a "container" entity that is used to organize the data and track resource allocation. The terminology and naming is commonly used for distributed resource allocation management. A job, in the computational sense, represents the simplest entity that has accounting set up for, and can have one or more Material and a single Workflow associated with it.
We implement Jobs as another entity type. As such, they have the same user interface components (with some distinct features) as other entities, as explained here.
The data convention applied for Jobs including, for example, their database representation is explained in this page.
Jobs have different statuses attributed to them depending on the level of progress of the simulation. We explain the list of possible statuses here.
Jobs can collectively be grouped together into Sets, which in this context are referred to as Projects.
Jobs Explorer is another specific implementation of the Explorer component and is explained in this page.
Jobs Designer is another specific implementation of the Designer component described in more detail here.
This page explains how the Viewer differs from Designer component in the context of Jobs.
Some actions pertain specifically to Jobs, and are introduced in this page.