Run job

Run a test query

In the job configuration window, select the job type Test Query, scroll down and click on Run Job.

This job type queries available geospatial datasets for your configured job parameters and generates image quicklooks and metadata associated with the available datasets (see table below).

A test query does not consume credits.

Test query results	Description
Preview	Metadata in JSON format (acquisition date, cloud cover, incidence angle, scene identifier, processing level etc.).
Quicklooks	A low-resolution version of the image. The original resolution of the image can only be purchased and retrieved by running a live job.
Results	Metadata delivered in the file `data.json`. Usage information delivered in the file `usage.json` (optional).

Run live job

In the job configuration window, select the job type Live Job, scroll down and click on Run Job.

A new window appears and informs you about the minimum amount of credits that will be held from the beginning until the completion of the job run. This amount of credits will be deducted from your account. If you agree, click Confirm & Job Run.

You will be redirected to the job dashboard, where the job is currently running.

A live job consumes the credits displayed in the job estimation.

The job dashboard parameters are explained in the table below.

Job progress	Description	Example
Step	The order of the blocks added to the workflow defines the steps. Steps are associated with each individual output generated by the job run. Steps are also defined as tasks. A job consists of one or more tasks. Each run task contains a log message.	`1` `2` `3`
Name	The Docker name of the blocks added to the workflow.	`oneatlas-pleiades-fullscene`
Status	The progress of the task or job.	`Not started` `Pending` `Running` `Cancelling` `Failed` `Cancelled` `Successful`
Processing time	The duration for each block and the total job duration.	`00:03:55`
Credits	The credits consumed for each block and the total job credit consumption. The credit costs are divided as follows: - Infrastructure Costs - Data Costs - Processing Costs	`1` `320` `0`
Download result	The outputs generated by each task or job run. Outputs can be downloaded in two ways: 1. To download the final output (of the last block), click on Download. 2. To download the individual outputs from each block, click on Results.	`Download` `Results`

Credit consumption

According to the job estimation, the credit costs of the job will be deducted from your account balance. Please note that the credit costs are broken down into infrastructure costs, data and processing costs. Even if you download free geospatial datasets (e.g. Sentinel-2) or apply free algorithms, the credit costs will include the infrastructure. This happens because you are using the UP42 platform as a service to perform data downloads and computations.

Good to know

The credit costs for infrastructure are usually negligible (e.g. 1-2 credits).

Download outputs

Currently, UP42 does not support the direct visualization of geospatial outputs and users need to download and save the outputs separately for further rendering in third-party GIS software. After successfully running the job, you can download the outputs by following the steps below:

You can download either the output of the last block (final output) or the outputs of each block (individual outputs).
In this case, we will download the individual output of the data block Pléiades Reflectance (Download), which is the first line of the results panel (see screenshot below). On the left side, the corresponding Docker name is oneatlas-pleiades-fullscene.
The output is downloaded as a TAR archive (TGZ) that needs to be unpacked. To perform this action on Windows OS, please refer to the tutorial How to unpack a tar file in Windows.

Troubleshooting

If the job fails, you can contact support and provide the universally unique identifier (UUID) of the failed job, in order to investigate the problem properly.

A job UUID is always generated after running a job (live job or test query). This UUID is also called a job ID and is very useful for troubleshooting job failures, viewing the job parameters or viewing the generated outputs. There are two ways to find the job ID:

Go to the URL where your job was run and extract the job ID after jobs/ and before ?workspace.

URL format: https://console.up42.com/projects/{project-id}/jobs/{job-id}?workspace={workspace-id}
job ID example: 6d7c1025-2915-40e9-88a1-264763b22a7e

Go to the job dashboard and get the job ID which appears below the workflow title (see screenshot below).