The hierarchy
Core terms
tenant / visibility boundary
The organization you belong to. Everything you can see in Braven is scoped to a company you’re a member of. There’s no cross-company visibility — “shared” always means “shared with your company,” never public.
grouping of experiments
A named bucket of Experiments inside a Company — typically one measurement campaign, product line, or workstream. Every company member can see every project; there’s no separate project membership to manage.
one unit of lab work
Uploaded data files plus everything derived from them — metadata, pipeline runs, plots, notes. Named from the uploaded file (or folder) at ingestion. This is the page you open to look at one piece of work.
one execution of a Pipeline
A single time a Pipeline processed an Experiment. A Run writes its Config, Summary, Series, and Figures all at once, at the end — nothing streams in while it’s still running. Re-running a pipeline replaces the previous Run’s output for that experiment; it doesn’t append to it.
a Python script Braven runs for you
A script you write once (or generate) that runs automatically against every new Experiment’s files. See Write a pipeline script.
input metadata
Small key–value settings a Run was given (temperature, voltage, sample ID, …). Shown as columns/filters in the Experiments list.
output metadata
Small key–value results a Run produced (slope, gain, threshold, …). Same shape as Config, opposite direction — inputs vs. outputs.
plottable measurement data
A named set of numeric traces (x/y arrays) an Experiment produces — the thing that ends up as an interactive chart. See Series vs. Figures for how this differs from a Figure.
an uploaded matplotlib plot
A matplotlib figure your pipeline script uploaded with
braven.upload(fig, name). Braven keeps the rendered PNG and tries to auto-extract an interactive version of its line/scatter data — see Series vs. Figures.the physical thing being measured
A sensor, board, or setup identified by a stable key (serial number, MAC address, or anything unique you choose). An Experiment can be tagged to one or more Devices. See Devices.
the desktop/OneDrive sync agent
A background agent that watches a folder and uploads new files as Experiments automatically — no code required. See Ingest data.
cross-experiment comparison view
The project tab where you combine Series and Figures from multiple experiments onto shared charts — the place you go to compare runs. See Analyze and compare.
a saved analysis, made shareable
An Analysis arrangement you’ve saved and can share with teammates or export. See Reports.