Architecture / UML

Edge I/O measurement

A campus question needs measurements that do not require shipping student identities to a cloud.

Accepted source f357b4c0fcfa · ACCEPTED_MAIN · simulation-and-privacy-transform

The accepted UML is software structure. It is not a calibrated RF chain or a field campaign. measured_topology is not recorded as true.

Current is shown first. Future and legacy stay labeled. A rendered SVG is used when accepted main already committed one. Otherwise the Mermaid or Markdown source is shown and is not executed in the browser.

Current

Component — current

current mermaid

What this diagram shows

EXP[research_export + exporters.seven_gc_export]

What this diagram does NOT prove

This diagram does not prove a physical sensor was built or that radio measurements were collected.

Open full sizeDownload

Source path docs/uml/current/component.md @ f357b4c0fcfa

Sequence — sensing (current)

current mermaid

What this diagram shows

participant E as Emulator or Physical collector

What this diagram does NOT prove

This diagram does not prove a physical sensor was built or that radio measurements were collected.

Open full sizeDownload

Source path docs/uml/current/sequence_sensing.md @ f357b4c0fcfa

Future

Future — physical campaign

future mermaid

What this diagram shows

P6[Pixel 6a accepted sessions] --> TWIN[7gc-digital-twin ingest]

What this diagram does NOT prove

This diagram does not prove a physical sensor was built or that radio measurements were collected.

Open full sizeDownload

Source path docs/uml/future/physical_campaign.md @ f357b4c0fcfa

Legacy

Legacy UML index — edge-io-measurement-node

legacy markdown

What this diagram shows

Legacy UML index — edge-io-measurement-node

What this diagram does NOT prove

This diagram does not prove a physical sensor was built or that radio measurements were collected.

Open full sizeDownload

Source path docs/uml/legacy/index.md @ f357b4c0fcfa

Architecture library