Adom PCL Node Data Profile
Public Made by Adomby adom
The physical shape of the data produced by the Adom Industries NSF PCL Test Bed node: every instrument that generates data, the file types each writes, and the rate it writes them at.
Install?
The physical shape of the data produced by the Adom Industries NSF PCL Test Bed node: every instrument that generates data, the file types each writes, and the rate it writes them at.
adom-wiki pkg install adom/pcl-data-profileLatest: v0.1.3, published
Contents
README
markdownData Generation at the Adom PCL Node
Adom Industries, NSF PCL Test Bed node, Fort Worth, Texas.
The instruments at our node that generate data, the file types each produces, and the rate at which they produce it today and projected as we scale.
Our node is an electronics-prototyping cloud lab. Instruments fall into two groups, and the distinction is what drives every number below:
- Per-workcell instruments: one of each per workcell. These scale linearly with workcell count, and they dominate our volume.
- Bench instruments: shared across the lab. These are bursty, not continuous, and they do not scale with workcell count.
We run 20 workcells today, each with one camera. We anticipate thousands, plausibly tens of thousands.
Instruments and file types
Per-workcell instruments
| Instrument | File types | Rate |
|---|---|---|
| High-resolution live camera | .mkv, .ts (H.264/AVC) |
records 4K (3840×2160) at 60 fps, ~50–80 Mbps; simultaneously streams 1080p or 1440p at 60 fps to users |
| Microphone | .wav |
44.1 kHz, 176.4 kB/s |
| Power sensor | .wav |
audio-rate waveform stream |
| BME690 — barometric pressure, temperature, humidity | .csv, .txt, .bin, .json, .jsonl |
low rate, typically 1–10 Hz |
| BMI270 — 6-DOF IMU (accelerometer + gyroscope) | .csv, .txt, .bin, .json, .jsonl |
up to 1.6 kHz ODR |
The camera stream is a live view for remote users and is not retained; the 4K60 record is the archived artifact.
Bench instruments
| Instrument | File types | Rate |
|---|---|---|
| Oscilloscopes — MXR series | .csv, .wav, .png |
1 Gbps streaming |
| Spectrum analyzers | custom binary (.bin); exports .csv, .sta |
5 Gbps streaming |
| FLIR thermal cameras | .jpg (radiometric) |
frame rate set per experiment |
| µV/µA voltage and current sensing | .csv, .bin, .json, .jsonl, .wav |
sample-rate dependent |
These are our highest-rate instruments by interface speed, but they capture in short bursts around a device under test rather than streaming continuously, so their contribution to daily volume is far smaller than the camera fleet's.
Custom user sensors
Our node exists to let other labs prototype electronics, so a user can put any
component on a board we fabricate and read it back through our stack. The lists
above are our fixed inventory; the sensors a user brings are open-ended. Their
formats follow the same menu: .csv, .bin, .json, .jsonl, .wav, and
images.
Rates
Per-unit, per-day estimates for each instrument. Assumes 8 active hours per day.
| Instrument | Per unit, per active day |
|---|---|
| 4K60 camera | ~216 GB (~650 GB if run continuously) |
| Power sensor | ~17 GB |
| Microphone | ~5 GB |
| BMI270 IMU | ~46 MB at 100 Hz, ~740 MB at 1.6 kHz (binary; ~10× as JSONL) |
| BME690 | under 30 MB |
| Per-workcell subtotal | ~240 GB |
| Oscilloscope (MXR) | burst-limited; single-GB to tens of GB |
| Spectrum analyzer | burst-limited; tens of GB, TB-scale if streamed |
| FLIR thermal | MB for single shots, up to ~40 GB continuous |
| µV/µA sensing | sub-GB logging to ~70 GB at 100 kHz |
| Custom user sensors | user-defined; unbounded |
Current vs. projected
Per-workcell instruments dominate, so total volume tracks workcell count almost linearly.
| Today | 1,000 workcells | 10,000 workcells | |
|---|---|---|---|
| Workcells | 20 | 1,000 | 10,000 |
| Cameras | 20 | 1,000 | 10,000 |
| Mics / power / BME690 / BMI270 | 20 each | 1,000 each | 10,000 each |
| Per-workcell volume | ~4.8 TB/day | ~240 TB/day | ~2.4 PB/day |
| Bench instruments | ~0.05–0.5 TB/day | ~0.05–0.5 TB/day | ~0.05–0.5 TB/day |
| Total | ~5 TB/day | ~240 TB/day | ~2.4 PB/day |
| Sustained average | ~0.5 Gbps | ~22 Gbps | ~222 Gbps |
Uplink
28 Gbps is our potential uplink once the factory is fully built out, not what is installed today.
That number is worth holding next to the table above. A 28 Gbps uplink is ~302 TB/day if saturated, which covers roughly 1,000 workcells — our projected volume there is ~22 Gbps sustained, comfortably inside it. At 10,000 workcells we would need on the order of 222 Gbps, roughly eight times the fully-built-out figure. Somewhere past a few thousand workcells, egress becomes the binding constraint rather than the instruments, and the question shifts from "how much can we generate" to "what do we keep, what do we reduce at the edge, and what do we ship."
On these numbers
The instrument inventory, the file types, and the native interface rates are firm. The daily volumes are estimates: they assume 8 active hours per day and one of each per-workcell instrument per workcell. Actual volume depends on real duty cycles, which we will have once InstaPCB goes live in January. This page is versioned and will be updated in place with measured figures then.
Contact: Kyle Bergstedt (co-PI, AI lead) — [email protected] · John Lauer (PI) — [email protected]