Skip to main content
Challenge

Build an Accelerator Thermal Planning and Throttling Reviewer

Analyze multi-accelerator server chassis thermal logs and cooling sensor feeds to detect thermal throttling events. Formulate rack airflow rebalancing plans and workload evacuation proposals.

EngineeringHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Analyze multi-accelerator server chassis thermal logs and cooling sensor feeds to detect thermal throttling events. Formulate rack airflow rebalancing plans and workload evacuation proposals.

Data Center Facilities and Compute Engineer

Ingest time-series DCGM thermal readings and clock frequency records from physical accelerator nodes.

Identify sudden clock speed drops correlated with thermal limit breaches.

Map localized hot spots across server chassis fan zones and compute trays.

Invoke hosted Claude API to draft a mechanical thermal mitigation and load-shedding plan.

Chassis thermal heat-map dashboard with cooling fan status indicators and maintenance export.

Generate synthetic CSV files with 24-hour sensor telemetry representing 16 GPUs across two rack chassis. Starter examples below are synthetic. They are not downloaded records.

NVIDIA DCGM exporter Reference DCGM exporter metrics for accelerator die temperature, slowdown throttling flags, and fan speeds.

pydantic-ai, anthropic, matplotlib. pydantic-ai validates thermal reading schemas and bounds before initiating automated risk assessment. Hosted Claude API accessed via SDK for root-cause synthesis; no internal hardware measurements asserted.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Identifies GPU thermal throttling episodes where temperature exceeds 84C and clocks drop by over 20 percent.

Highlights chassis fan zone degradation where fan duty cycle is pinned at maximum with rising temps.

Synthesizes an incident ticket specifying failed fan modules and recommended job rescheduling.

```json [ { "input": { "chassis_id": "chassis-03", "gpu_index": 6, "temperature_c": 89, "throttle_flag_active": true, "clock_mhz": 1120, "nominal_clock_mhz": 1800, "fan_speed_pct": 100 }, "expected_output": { "thermal_state": "CRITICAL_THROTTLE", "clock_deficit_pct": 37.78, "chassis_risk": "local_airflow_restriction", "remedial_action": "evacuate_workload_and_inspect_chassis_fan_b" } }, { "input": { "chassis_id": "chassis-01", "gpu_index": 2, "temperature_c": 64, "throttle_flag_active": false, "clock_mhz": 1785, "nominal_clock_mhz": 1800, "fan_speed_pct": 55 }, "expected_output": { "thermal_state": "NOMINAL", "clock_deficit_pct": 0.83, "chassis_risk": "none", "remedial_action": "none" } } ] ```

Generates operational cooling recommendations without directly controlling data center building management systems or fan speeds. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Generates operational cooling recommendations without directly controlling data center building management systems or fan speeds. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Identifies GPU thermal throttling episodes where temperature exceeds 84C and clocks drop by over 20 percent. Highlights chassis fan zone degradation where fan duty cycle is pinned at maximum with rising temps. Synthesizes an incident ticket specifying failed fan modules and recommended job rescheduling.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest time-series DCGM thermal readings and clock frequency records from physical accelerator nodes. Identify sudden clock speed drops correlated with thermal limit breaches. Map localized hot spots across server chassis fan zones and compute trays. Invoke hosted Claude API to draft a mechanical thermal mitigation and load-shedding plan.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Identifies GPU thermal throttling episodes where temperature exceeds 84C and clocks drop by over 20 percent. Highlights chassis fan zone degradation where fan duty cycle is pinned at maximum with rising temps. Synthesizes an incident ticket specifying failed fan modules and recommended job rescheduling.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

Chassis thermal heat-map dashboard with cooling fan status indicators and maintenance export.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Generates operational cooling recommendations without directly controlling data center building management systems or fan speeds.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest time-series DCGM thermal readings and clock frequency records from physical accelerator nodes.

  • Identify sudden clock speed drops correlated with thermal limit breaches.

  • Map localized hot spots across server chassis fan zones and compute trays.

  • Invoke hosted Claude API to draft a mechanical thermal mitigation and load-shedding plan.

Resources and assets

Reference links and supporting material

Dataset notes

Generate synthetic CSV files with 24-hour sensor telemetry representing 16 GPUs across two rack chassis. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Pydantic AI

Typed Python agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest time-series DCGM thermal readings and clock frequency records from physical accelerator nodes. Ident...
  • Identifies GPU thermal throttling episodes where temperature exceeds 84C and clocks drop by over 20 percent...
  • Chassis thermal heat-map dashboard with cooling fan status indicators and maintenance export.
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Pydantic AI · Optional
Orchestration
  • Pydantic AI · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build an Accelerator Thermal Planning and Throttling Reviewer