| Argonne Leadership Computing Facility | |
|
| an Office of Science user facility | ||
| DATA CATALOG | ||
| ALCF Public Data | |
| Data Set: COBALT_MACHINE_RESERVATION | |
| Source: Argonne Leadership Computing Facility |
| COLUMN | DATA TYPE | DESCRIPTION | EXAMPLE |
|---|---|---|---|
| TIME_START | TIMESTAMP | Reservation Start Time | |
| TIME_END | TIMESTAMP | Reservation End Time | |
| QUEUE_NAME_GENID | VARCHAR(64) | Queue Name. In some cases the queue name is a GENID, ie. a 12 digit number. This is done to protect projects and users from having their name published. | R.hw.R08-M0-N03-J16 |
| MACHINE_NAME | VARCHAR(64) | Machine Name | mira |
| RESERVATION_NAME | VARCHAR(128) | Reservation name | hw.IBM_Maintenance-R0C0D |
| CYCLE | INTEGER | ||
| CYCLEID | INTEGER | ||
| RESID | INTEGER | Cobalt reservation id, if the job was run within a reservation. This matches RESID in the DIM_JOB_COMPOSITE data source. | 1764 |
| RUNTIME | INTEGER | The elapsed seconds the job executed. | 35747 |
| WALLTIME | INTEGER | The seconds requested for a job, can be different than runtime | 100800 |
| NODES_COST | DECIMAL(24, 4) | Number of Nodes in the reservation | 49152 |
| CORE_HOURS_COST | DECIMAL(24, 4) | Number of Cores in the reservation multiplied by RUNTIME seconds divided by 3600 | 488065.7067 |
| CORE_SECONDS_COST | DECIMAL(24, 4) | Number of Cores in the reservation multiplied by RUNTIME seconds | 1757036544.0000 |
| LOCATION | VARCHAR(4096) | Location on machine, syntax will vary depending on machine | MIR-00000-7BFF1-49152 |
| MAJOR_PROJECT | VARCHAR(64) | ||
| INSTANCE_INDEX | INTEGER | When there are multiple records for the same resid, the index count increases by 1 for each record. Multiple records indicates the reservation changed. The last record, ie. highest index, is the last changed record for the reservation | 0 |
| DATA_LOAD_STATUS | VARCHAR(16) | complete | |
| RESERVATION_TYPE | VARCHAR(16) | RESERVATION: a reservation for a specific user or project to be used for regular jobs, ie. not any of the below categories. HARDWARE OUTAGE: A reservation was created due to a hardware outage to prevent jobs from using the nodes. SOFTWARE OUTAGE: A reservation was created due to a software outage to prevent jobs from using the nodes. SYSTEM OUTAGE: A reservation was created due to a full system outage to prevent jobs from using the nodes. FACILITY OUTAGE: A reservation was created due to a facility outage to prevent jobs from using the nodes. PREVENTATIVE MAINTENANCE: The nodes were unavailable to users due to a preventative maintenance (PM). TESTING ACCEPTANCE: The nodes were not available due to acceptance testing. TESTING ACCEPTANCE: The acceptance team is testing nodes. TESTING STORAGE: The storage team is testing nodes. TESTING: Other testing is being done using these nodes. UNKNOWN: The reservation does not fit any of the above categories. | RESERVATION |