rmems commited on
Commit
b85d5d1
·
verified ·
1 Parent(s): 6f22802

Upload hf_dataset_card.md

Browse files
origin_hardware_baselines/resident_evil_4/hf_dataset_card.md ADDED
@@ -0,0 +1,76 @@
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: gpl-3.0
3
+ task_categories:
4
+ - time-series-forecasting
5
+ tags:
6
+ - neuromorphic
7
+ - snn
8
+ - liquid-state-machines
9
+ - gaming
10
+ - hardware-telemetry
11
+ - gpu
12
+ pretty_name: Metis SMoE Latent Telemetry (Gaming)
13
+ ---
14
+
15
+ # Metis SMoE Latent Telemetry
16
+ ## Neuromorphic Hardware Telemetry from demanding Gaming Workloads
17
+
18
+ This dataset provides high-fidelity, high-frequency (5ms interval) hardware telemetry data captured from extreme PC gaming workloads. This dataset is optimized to simulate the biological responses of a nervous system to intense stimulus (excitatory input, action potentials/firing rates, and inhibitory responses).
19
+
20
+ ### Context
21
+ The telemetry data was recorded using a custom Rust-based data collector via the NVIDIA Management Library (NVML) on a Fedora 43 Linux system. Workloads represent highly transient rendering applications including:
22
+ - **Resident Evil 4 (Remake)** (with rendering complexities)
23
+ - **Cyberpunk 2077** (Path Tracing, DLSS 4.0)
24
+
25
+ This system provides the rich, high-frequency time-series data required to train **Spiking Neural Networks (SNNs)** and **Liquid State Machines (LSMs)**.
26
+
27
+ ### Neuromorphic Mapping (SNN Utility)
28
+ This data behaves as "sensorimotor" stimulus for neural networks:
29
+ - **Excitatory Inputs (Stimulus):** High surges in `pcie_rx_kbps` indicate asset floods (e.g., BVH structure updates for Path Tracing), mimicking sensory signals entering the system.
30
+ - **Action Potentials (Firing Rates):** `encoder_util_perc`, `decoder_util_perc`, and overall spatial `power_usage_mw` transients represent internal activity and network firing rates.
31
+ - **Inhibitory Inputs (Refractory/Limits):** Non-zero `throttle_reasons_bitmask` signals and thermal limits act as inhibitory governors, dynamically suppressing system activity.
32
+ - **State/Momentum:** Slow-moving environmental data like temperatures (`cpu_tctl_c`, `temperature_c`) and memory capacity.
33
+
34
+ ### Data Schema
35
+
36
+ The data is provided natively as Parquet files partitioned into train batches (`system_telemetry_v1_batch_*.parquet`).
37
+
38
+ | Feature | Type | Description |
39
+ | :--- | :--- | :--- |
40
+ | `timestamp_ms` | `Int64` | UNIX timestamp in milliseconds (5ms interval captures). |
41
+ | `power_usage_mw` | `UInt32` | Total GPU power usage in milliwatts. |
42
+ | `temperature_c` | `Float32` | GPU core temperature in Celsius. |
43
+ | `pcie_rx_kbps` | `UInt32` | Incoming PCIe throughput in Kilobytes per second (Excitatory). |
44
+ | `pcie_tx_kbps` | `UInt32` | Outgoing PCIe throughput in Kilobytes per second. |
45
+ | `encoder_util_perc` | `Float32` | NVIDIA Encoder (NVENC) utilization percentage. |
46
+ | `decoder_util_perc` | `Float32` | NVIDIA Decoder (NVDEC) utilization percentage. |
47
+ | `mangohud_active` | `Boolean` | Whether MangoHud overlay telemetry was active during the snapshot. |
48
+ | `cpu_tctl_c` | `Float32` | Primary CPU package temperature (Tctl). |
49
+ | `cpu_ccd1_c` | `Float32` | Temperature of CPU Core Complex Die 1. |
50
+ | `cpu_ccd2_c` | `Float32` | Temperature of CPU Core Complex Die 2. |
51
+ | `throttle_reasons_bitmask`| `UInt64` | Bitmask defining hardware throttling events (Power, Thermal, Sync) - acts as Inhibitory signals. |
52
+
53
+ ### Usage with Hugging Face `datasets`
54
+
55
+ You can seamlessly integrate this telemetry into your Neuromorphic modeling workflows using the Hugging Face `datasets` library.
56
+
57
+ ```python
58
+ from datasets import load_dataset
59
+ import pyarrow.parquet as pq
60
+
61
+ # Load the entire telemetry dataset as a single stream
62
+ dataset = load_dataset("rmems/Metis-SMoE-Latent-Telemetry", split="train")
63
+
64
+ print(dataset.features)
65
+ print(dataset[0])
66
+ ```
67
+
68
+ ### Export to Canonical CSV (For Corinth Canal Replay)
69
+ If you are using the Spikenaut `corinth-canal` framework, you can export a canonical CSV by grabbing a single dataset file:
70
+
71
+ ```bash
72
+ cargo run --bin export_csv data/train/system_telemetry_v1_batch_1.parquet canonical.csv
73
+ ```
74
+
75
+ ### License
76
+ This dataset is distributed under the GPL-3.0 License.