Skip to main content
Challenge

Build an Accelerator Chassis Thermal Incident Root-Cause Diagnoser

Analyze multi-sensor thermal logs during server shutdown events to reconstruct thermal runaway sequences. Generate hardware engineer post-mortem summaries and facility air-balance tasks using hosted Claude.

EngineeringHosted by Vera
Challenge brief

What you are building

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

Analyze multi-sensor thermal logs during server shutdown events to reconstruct thermal runaway sequences. Generate hardware engineer post-mortem summaries and facility air-balance tasks using hosted Claude.

Datacenter Hardware Reliability Specialist

Ingest high-frequency sensor streams tracking intake temperature, exhaust delta, and per-card junction temperatures.

Detect abnormal temperature gradient rates and identify the initial failing component.

Prompt hosted Claude to synthesize a formal hardware failure post-mortem and inspection steps.

Package diagnostic conclusions into a review dossier for facility HVAC and technician teams.

Interactive timeline viewer displaying thermal gradient curves, component failure markers, and an audit report preview.

Create synthetic CSV logs simulating an 8-GPU chassis thermal runaway scenario with exhaust and junction metrics. Starter examples below are synthetic. They are not downloaded records.

NVIDIA DCGM exporter Adopts DCGM junction temperature and memory temperature counters to trace localized thermal spikes.

anthropic, pydantic-ai, pandas. anthropic-claude excels at correlating disparate multi-sensor anomalies into concise post-mortem findings. Hosted Claude API for structured report compilation; pandas locally for metric gradients.

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.

Pinpoint the exact timestamp and GPU index of the initial thermal trip.

Produce actionable inspection recommendations targeting physical heatsinks and fans.

Ensure all output dossiers clearly delineate confirmed observations from suggested root causes.

```json [ { "input": { "chassis_id": "rack-12-u3", "incident_time": "2025-02-10T14:30:00Z", "sensor_readings": [ { "gpu_id": 0, "junction_temp": 81, "memory_temp": 75 }, { "gpu_id": 1, "junction_temp": 105, "memory_temp": 99 }, { "gpu_id": 2, "junction_temp": 82, "memory_temp": 76 } ] }, "expected_output": { "primary_fault_device": "GPU-1", "critical_threshold_exceeded": true, "hypothesized_cause": "Localized thermal paste degradation or liquid cooling plate blockage on GPU-1", "immediate_task": "Reseat GPU-1 cold plate and verify thermal interface material integrity." } }, { "input": { "chassis_id": "rack-12-u4", "incident_time": "2025-02-10T15:00:00Z", "sensor_readings": [ { "gpu_id": 0, "junction_temp": 70, "memory_temp": 68 }, { "gpu_id": 1, "junction_temp": 71, "memory_temp": 69 } ] }, "expected_output": { "primary_fault_device": null, "critical_threshold_exceeded": false, "hypothesized_cause": "Nominal operations, no thermal runaway detected", "immediate_task": "Continue standard telemetry monitoring." } } ] ```

Read-only telemetry analysis; does not interact with datacenter control loops or physical power switches. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Read-only telemetry analysis; does not interact with datacenter control loops or physical power switches. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Pinpoint the exact timestamp and GPU index of the initial thermal trip. Produce actionable inspection recommendations targeting physical heatsinks and fans. Ensure all output dossiers clearly delineate confirmed observations from suggested root causes.

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 high-frequency sensor streams tracking intake temperature, exhaust delta, and per-card junction temperatures. Detect abnormal temperature gradient rates and identify the initial failing component. Prompt hosted Claude to synthesize a formal hardware failure post-mortem and inspection steps. Package diagnostic conclusions into a review dossier for facility HVAC and technician teams.

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

Pinpoint the exact timestamp and GPU index of the initial thermal trip. Produce actionable inspection recommendations targeting physical heatsinks and fans. Ensure all output dossiers clearly delineate confirmed observations from suggested root causes.

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

Interactive timeline viewer displaying thermal gradient curves, component failure markers, and an audit report preview.

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

Read-only telemetry analysis; does not interact with datacenter control loops or physical power switches.

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 high-frequency sensor streams tracking intake temperature, exhaust delta, and per-card junction temperatures.

  • Detect abnormal temperature gradient rates and identify the initial failing component.

  • Prompt hosted Claude to synthesize a formal hardware failure post-mortem and inspection steps.

  • Package diagnostic conclusions into a review dossier for facility HVAC and technician teams.

Resources and assets

Reference links and supporting material

Dataset notes

Create synthetic CSV logs simulating an 8-GPU chassis thermal runaway scenario with exhaust and junction metrics. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Anthropic Claude

LLM for code generation & more

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest high-frequency sensor streams tracking intake temperature, exhaust delta, and per-card junction temp...
  • Pinpoint the exact timestamp and GPU index of the initial thermal trip. Produce actionable inspection recom...
  • Interactive timeline viewer displaying thermal gradient curves, component failure markers, and an audit rep...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 1 configured tool

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
  • Anthropic Claude · 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 Chassis Thermal Incident Root-Cause Diagnoser