Dataset Viewer
The dataset viewer is not available for this dataset.
Unexpected token '<', "<html> <h"... is not valid JSON

Need help to make the dataset viewer work? Make sure to review how to configure the dataset viewer, and open a discussion for direct support.

YAML Metadata Warning:The task_categories "time-series-classification" is not in the official list: text-classification, token-classification, table-question-answering, question-answering, zero-shot-classification, translation, summarization, feature-extraction, text-generation, fill-mask, sentence-similarity, text-to-speech, text-to-audio, automatic-speech-recognition, audio-to-audio, audio-classification, audio-text-to-text, voice-activity-detection, depth-estimation, image-classification, object-detection, image-segmentation, text-to-image, image-to-text, image-to-image, image-to-video, unconditional-image-generation, video-classification, reinforcement-learning, robotics, tabular-classification, tabular-regression, tabular-to-text, table-to-text, multiple-choice, text-ranking, text-retrieval, time-series-forecasting, text-to-video, image-text-to-text, image-text-to-image, image-text-to-video, visual-question-answering, document-question-answering, zero-shot-image-classification, graph-ml, mask-generation, zero-shot-object-detection, text-to-3d, image-to-3d, image-feature-extraction, video-text-to-text, keypoint-detection, visual-document-retrieval, any-to-any, video-to-video, other

GPT-OSS-20B LMSYS Layer-2 Expert Power Traces — 600k tokens at 10 MSPS

This dataset contains real power/current traces captured from an NVIDIA H100 PCIe system while running GPT-OSS-20B decode on LMSYS prompts. The capture target is layer 2 MoE expert execution only; earlier/later transformer work is executed off-trace to avoid wasting acquisition time.

Capture summary

  • Model: openai/gpt-oss-20b
  • Target layer: 2
  • Captured region: target_layer_experts_only
  • Prompts: LMSYS Chat, English-filtered prompt plan
  • Accepted decode tokens: 600,000
  • Prompts touched: 9,375
  • Experts per token: 4
  • Total expert windows: 2,400,000
  • Unique experts observed: 32 / 32
  • Trace sample rate: 10 MSPS
  • Samples per capture: 100,000
  • Capture duration: 10 ms
  • Trace dtype: float16
  • Trace shape: (100000,)
  • Approximate trace payload size: 120.08 GB

Layout

traces/shard_XXXXXX/step_YYYYYY.npy      # float16 power trace, shape (100000,)
records/shard_XXXXXX/step_YYYYYY.json    # per-token metadata and expert window bounds
timelines/shard_XXXXXX/...               # periodic timing/timeline artifacts
prompt_plan.jsonl                        # deterministic prompt plan used by the run
capture_meta.json                        # capture summary and expert counts
run_state.json                           # final committed run state
layer_windows.rebuilt.jsonl              # flattened expert-window index from audit

Each record contains:

  • global_step
  • prompt_plan_index
  • token_in_prompt
  • hit_experts
  • trace_file
  • trace_stats
  • layer_windows, with expert_idx, sample_start, sample_end, and millisecond boundaries
  • scope configuration including adc_freq_effective, adc_decimate, and adc_samples

Health/audit status

Final audit status:

  • committed records: 600,000
  • missing trace files: 0
  • trace dtypes: float16: 600000
  • trace shapes: (100000,): 600000
  • loaded trace sample count during audit: 1,000
  • audit warnings: 0
  • audit errors: 0

A separate visual spot check sampled early, middle, and late captures and confirmed that the annotated expert windows are inside the traces and visually aligned.

Notes

The analog chain is AC-coupled/high-pass and the installed current clamp is outside its specified flat bandwidth for MHz-scale components. Treat absolute current calibration cautiously; the main intended use is comparative classification/analysis of expert-conditioned trace structure.

Downloads last month
194