

Projects¶

Jobs are organized into Projects for convenience, which represent a particular type of Set exclusive to Jobs only. One can thus think about projects as collections of jobs, in the same manner as a file system directory is a collection of files.

Projects can only be present at the top-level, with no possibility of creating nested projects one inside the other. In the user interface they are labelled with their distinctive "folder" icon .

Slug¶

Also referred to as "Accounting Slug".

The Slug offers a computer-friendly representation of the name of the Project. This is relevant in the context of Account Charges and is used to identify a project inside each charge entry.

Accounting¶

We isolate job sets in this manner in order to facilitate the accounting per project separately. For example, when Accounts are working on multiple problems (eg. multiple classes of materials, or multiple internal customers), these problems can be isolated in their own projects to better organize the data and further understand the balance spent on each.

View Accounting Information per Project¶

There are two ways to track charges on each project, as explained in what follows.

From Charges Page¶

We describe how to access and navigate the main "Charges and Payments" page here.

In Command Line¶

Alternatively, the charges incurred as part of each Project can be inspected directly on the Command Line Interface, as outlined in this page.

CLI Path¶

The path of the Project inside the cluster infrastructure is formed utilizing the slug field explained above.

Question marks "???" might be present within this path instead of the actual cluster number label (eg. "001" for "cluster-001"), because different clusters are employed for executing the Project's Jobs with each cluster having a dedicated directory for the project. See explanation in directory structure for more information on this.

Status¶

Similarly to the status of individual Jobs, each Project also has a general status assigned to it, according to the following conventions.

Active: at least one job is present with an Active status inside the Project.
Stand-by: at least one job in the Project is pending execution, but has been submitted to the queue already (Submitted status).
Idle: all other possibilities, whereby all jobs contained in the project have statuses other than Active and Submitted.

The Project Status is indicated in Project Explorer, under the corresponding column.

Default Project¶

Each new Account is initialized with a default project named "Default". It is initially set to be shared publicly with all platform users. Higher levels of privacy for this and all subsequently created Projects can be set when an appropriate service level is attributed to the account.

"External" Project¶

Jobs created through External Uploads are placed into the corresponding project.

Project Page¶

Each Project has its own dedicated page, listing all the contained Jobs among other properties. We review Projects Pages here.

Projects Explorer¶

The list of projects created under an account can be viewed under the Projects Explorer interface.

Create / Delete¶

The procedure for creating or deleting Projects under Explorer is explained separately.