Hugging Face's logo

Datasets:
callensxavier
/
cpugym-v9-scientific-dataset

Tasks:
Text Classification
Tags:
reinforcement-learning
compiler-optimization
cpugym
telemetry
scientific-dataset
Dataset card Files
xet
 Community
cpugym-v9-scientific-dataset / SCIENTIFIC_REPORT.md
callensxavier's picture
callensxavier
Publish CPUGym V9 dataset 20260604T085100Z
3a6b635 verified
preview code
|
Raw
History Blame Contribute Delete
2.6 kB

CPUGym V9 Freeze Report

Generated: 2026-06-04T08:51:20.931560+00:00 Release tag: 20260604T085100Z

Executive Summary

The public V9 dashboard is stale and should not be used as the authoritative source for current training progress. Its bound SQLite database remains at a single snapshot with timestep 56 and zero recorded checkpoints or evaluations. In contrast, the live V9 storage lineage continues to emit fresh checkpoints and fresh run-scoped telemetry under v9/p3/ and v9/p2r-20260603T074706Z/.

The freeze selected the latest modified checkpoint from the active p3 lineage:

  • Latest modified checkpoint: v9/p3/v8_step12728_20260604_081300.zip
  • Latest modified timestamp: 2026-06-04T08:13:00+00:00
  • Highest observed step in p3: v9/p3/v8_step15768_20260603_220156.zip

Current Training Status

Public Dashboard Status

  • Dashboard timestep: 56
  • Dashboard progress: 0.01%
  • Dashboard snapshots: 1
  • Dashboard evaluations: 0
  • Dashboard checkpoints: 0

Live Promotion Pipeline Status

  • Promotion compactor consumed: 21960
  • Promotion true count: 21960
  • Promotion false count: 0
  • Promotion true ratio: 1.0

SQLite Telemetry Comparison

  • Root dashboard DB snapshot count: 1
  • Root dashboard latest snapshot timestep: 56
  • p3 DB snapshot count: 59
  • p3 DB latest snapshot timestep: 13552
  • p3 DB latest elapsed seconds: 38189.986297369
  • p3 DB latest reward mean: -1.1798117704123474
  • p3 DB latest checksum OK rate: 0.8400357462019661
  • p2r DB snapshot count: 7
  • p2r DB latest snapshot timestep: 680

Interpretation

  1. Training is active in storage even though the dashboard surface is stale.
  2. The p3 lineage is the strongest active candidate because it has the freshest telemetry, the deepest snapshot history, and a validated latest checkpoint.
  3. The p2r lineage is active but materially behind in telemetry depth.
  4. The day1 frozen archive remains the earlier validation anchor, while this release preserves the latest live p3 checkpoint as the final reusable serialization.

Limitations

  1. ContainerApp live log streaming is blocked locally by an intercepted SSL chain, so this report relies on durable storage artifacts rather than direct tail logs.
  2. The generic production inference storage account gemtstmlstorage was not reachable from this environment, so the reusable inference artifact was published into the reachable V9 artifact store instead.
  3. The public V9 dashboard needs rebinding to the active p3 database before it can be trusted again as an operational surface.