Inputs & Outputs
Before using the tool, it would be helpful to define all the input arguments available to the user to enrich their estimations and the final outputs (columns of the returned datasets).
Input Arguments
Argument |
Description |
|---|---|
|
The first date of the range to process jobs for, in |
|
The final date of the range to process jobs for, in |
|
Comma-separated list of all the HPC job IDs to filter on (e.g |
|
UK region of the HPC cluster you are using, needed for carbon intensity data. |
|
Option to include scope 3 (embodied) emissions estimates as well as scope 2 in the output. |
|
Save the final datasets to CSV file for further analysis elsewhere. |
Output Data
Below are the columns returned in the outputted datasets once the tool has been run. These are not stored if you are using the command-line interface, unless the user has specified the data to be saved to CSV. The following pages describe how to use the tool and store outputs for each user mode:
SLURM-Extracted Job Data columns
Column Name |
Description |
|---|---|
|
Unique identifier for your job ran on the HPC system. |
|
Unique numerical ID of the job submitter. |
|
Username of the person who submitted the job. |
|
Name of the partition the job was submitted to. |
|
Processor type of the partition ( |
|
Job name given by the user when submitted. |
|
Date and time the job was submitted in |
|
Numeric code representing the job status (1 = completed/successful, 0 = failed). |
|
Total number of nodes allocated to the job(s). |
|
Total number of CPU cores allocated to the job(s). |
|
Total number of GPUs allocated to the job(s). |
|
Total wallclock runtime of the job(s). |
|
The actual CPU time consumed by the job(s), summed across all CPUs |
|
Estimated CPU time (NCPUs * |
|
Estimated GPU usage time ( |
|
Amount of memory requested by the user at job submissions (in GB). |
|
Amount of memory actually used by the job(s) (in GB). |
|
The estimated minimum amount of memory required for the job(s) to run (in GB). |
|
Calculated total node-hour usage (in hours). |
|
File system path where the job was run from. |
Energy Data
Column Name |
Description |
|---|---|
|
Total energy consumed (kWh) by the job(s) measured by hardware energy/power counters |
|
Total energy consumed (kWh) by the job(s) including the datacenter overhead (PUE factor). |
|
Total energy consumed by the job(s) without the datacenter overhead (PUE) applied (usage-based estimate) |
|
Energy consumed by CPUs (usage-based estimate). |
|
Energy consumed by GPUs (usage-based estimate). |
|
Energy consumed by memory (usage-based estimate). |
|
Energy consumed by memory if only the required memory was allocated (usage-based estimate). |
|
Total energy consumed (kWh) by the job(s) if only the required memory was allocated. |
|
Energy consumed by failed jobs only. |
Carbon Emissions Data
Column Name |
Description |
|---|---|
|
Carbon Intensity at the time of job submission for the selected |
|
Scope 2 (operational) emissions calculated using estimated energy (in gCO2e). |
|
Scope 2 (operational) emissions calculated using measured energy (energy counters). |
|
Scope 3 (embodied) emissions estimated for the job(s). |
|
Scope 2 emissions produced if only the required memory had been allocated. |
|
Scope 2 emissions associated with the failed jobs only. |
|
Total carbon emissions in gCO2e (scope 2 + scope 3). |
Equivalents for User Interest
These data are provided as approximate values intended to help contextualise the impact of the user’s computational carbon footprint. See the Methodology for sources and assumptions for these calculations.
Column Name |
Description |
|---|---|
|
The approximate electricity cost (in British pounds) of running the job(s) |
|
The equivalent number of miles driven by an average UK car (miles). |
|
The months for one tree to absorb the total amount of CO2e produced (months). |
|
Equivalent number of UK household’s daily emissions from electricity use. |
|
Equivalent number of flights from Bristol to Paris. |