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.
name: pcl-data-profile description: The instrument inventory, file formats, and data-rate estimates for the Adom Industries NSF PCL Test Bed node in Fort Worth. Use when asked what data the node produces, what formats an instrument writes, how much data the lab generates per day, or when planning storage, transport, or deposition for Adom datasets.
Adom PCL Node Data Profile
Adom Industries is the NSF PCL Test Bed node in Fort Worth, Texas, focused on electronics prototyping. This skill is the authoritative answer to "what data does that node produce, in what format, and how fast."
Site uplink: 28 Gbps.
Instruments → formats
| Instrument | Native / exported formats | Interface rate |
|---|---|---|
| High-resolution live cameras | .mkv, .ts (H.264/AVC) |
record 4K60; stream 1080p/1440p60 |
| Oscilloscopes (MXR series) | .csv, .wav, .png |
1 Gbps |
| FLIR thermal cameras | .jpg (radiometric) |
per-experiment frame rate |
| Spectrum analyzers | .bin (custom); exports .csv, .sta |
5 Gbps |
| Microphones | .wav |
44.1 kHz / 176.4 kB/s |
| Power sensors | .wav |
audio-rate |
| BME690 (pressure/temp/humidity) | .csv, .txt, .bin, .json, .jsonl |
low rate |
| BMI270 (6-DOF IMU) | .csv, .txt, .bin, .json, .jsonl |
up to 1.6 kHz ODR |
| µV/µA voltage + current sensing | .csv, .bin, .json, .jsonl, .wav |
sample-rate dependent |
| Custom user sensors | user-defined (same format menu) | unbounded |
Rate estimates
All figures are estimates pending measured numbers after InstaPCB goes live in January 2027. "Active" = 8 h/day of workcell operation.
- 4K60 camera: ~50–80 Mbps → ~200–290 GB/day active, ~650 GB/day continuous, per camera.
- Spectrum analyzer: 5 Gbps peak → burst-limited; tens of GB/day typical, TB/day if streamed.
- Oscilloscope: 1 Gbps peak → burst-limited; single-GB to tens of GB/day typical.
- FLIR: ~0.5–1.5 MB/frame → MB/day for single shots, up to ~40 GB/day continuous.
- Microphone: 176.4 kB/s → ~15 GB/day continuous, per mic.
- Power sensor: ~15–50 GB/day continuous, per channel.
- µV/µA sensing: sub-GB/day logging to ~70 GB/day at 100 kHz.
- BMI270: ~140 MB/day at 100 Hz to ~2.2 GB/day at 1.6 kHz (binary); ~10× as JSONL.
- BME690: ~1 MB/day at 1 Hz binary; ~90 MB/day at 10 Hz JSONL.
Node totals: ~1–3 TB/day typical, 10+ TB/day heavy. The 28 Gbps uplink is ~302 TB/day saturated, so the network is not the binding constraint on a typical day; one sustained 5 Gbps spectrum capture uses about a fifth of it.
Publication
Every dataset is published on the Adom Wiki with a persistent identifier, named authors, a per-page license, git-backed history, captured provenance, and machine-readable metadata behind a REST API — and ships with the skill that explains how to read its format. Browse: https://wiki.adom.inc/skills
Not yet in place: DOI minting, Zenodo/protocols.io/The Stacks deposition, funder and ROR fields, an output register, CC0/CC BY licensing for data and protocols, and experiments packaged as publishable units.
---
name: pcl-data-profile
description: The instrument inventory, file formats, and data-rate estimates for the Adom Industries NSF PCL Test Bed node in Fort Worth. Use when asked what data the node produces, what formats an instrument writes, how much data the lab generates per day, or when planning storage, transport, or deposition for Adom datasets.
---
# Adom PCL Node Data Profile
Adom Industries is the NSF PCL Test Bed node in Fort Worth, Texas, focused on
electronics prototyping. This skill is the authoritative answer to "what data
does that node produce, in what format, and how fast."
Site uplink: **28 Gbps**.
## Instruments → formats
| Instrument | Native / exported formats | Interface rate |
|---|---|---|
| High-resolution live cameras | `.mkv`, `.ts` (H.264/AVC) | record 4K60; stream 1080p/1440p60 |
| Oscilloscopes (MXR series) | `.csv`, `.wav`, `.png` | 1 Gbps |
| FLIR thermal cameras | `.jpg` (radiometric) | per-experiment frame rate |
| Spectrum analyzers | `.bin` (custom); exports `.csv`, `.sta` | 5 Gbps |
| Microphones | `.wav` | 44.1 kHz / 176.4 kB/s |
| Power sensors | `.wav` | audio-rate |
| BME690 (pressure/temp/humidity) | `.csv`, `.txt`, `.bin`, `.json`, `.jsonl` | low rate |
| BMI270 (6-DOF IMU) | `.csv`, `.txt`, `.bin`, `.json`, `.jsonl` | up to 1.6 kHz ODR |
| µV/µA voltage + current sensing | `.csv`, `.bin`, `.json`, `.jsonl`, `.wav` | sample-rate dependent |
| Custom user sensors | user-defined (same format menu) | unbounded |
## Rate estimates
All figures are estimates pending measured numbers after InstaPCB goes live in
January 2027. "Active" = 8 h/day of workcell operation.
- 4K60 camera: ~50–80 Mbps → ~200–290 GB/day active, ~650 GB/day continuous, per camera.
- Spectrum analyzer: 5 Gbps peak → burst-limited; tens of GB/day typical, TB/day if streamed.
- Oscilloscope: 1 Gbps peak → burst-limited; single-GB to tens of GB/day typical.
- FLIR: ~0.5–1.5 MB/frame → MB/day for single shots, up to ~40 GB/day continuous.
- Microphone: 176.4 kB/s → ~15 GB/day continuous, per mic.
- Power sensor: ~15–50 GB/day continuous, per channel.
- µV/µA sensing: sub-GB/day logging to ~70 GB/day at 100 kHz.
- BMI270: ~140 MB/day at 100 Hz to ~2.2 GB/day at 1.6 kHz (binary); ~10× as JSONL.
- BME690: ~1 MB/day at 1 Hz binary; ~90 MB/day at 10 Hz JSONL.
**Node totals:** ~1–3 TB/day typical, 10+ TB/day heavy. The 28 Gbps uplink is
~302 TB/day saturated, so the network is not the binding constraint on a typical
day; one sustained 5 Gbps spectrum capture uses about a fifth of it.
## Publication
Every dataset is published on the Adom Wiki with a persistent identifier, named
authors, a per-page license, git-backed history, captured provenance, and
machine-readable metadata behind a REST API — and ships with the skill that
explains how to read its format. Browse: https://wiki.adom.inc/skills
Not yet in place: DOI minting, Zenodo/protocols.io/The Stacks deposition, funder
and ROR fields, an output register, CC0/CC BY licensing for data and protocols,
and experiments packaged as publishable units.