EdgeFirst Studio Integration
The profiler is always operated against an EdgeFirst Studio validation session — the mechanism that joins an on-target run to Studio's metrics dashboard and trace viewer.
This section covers:
- Connecting to Studio — interactive login and headless credential handling.
- Validation from Studio — create a validation session in Studio, then point the profiler at the session ID.
- Validation from the Profiler — browse projects and training sessions in the profiler's F2 Studio screen and create the validation session in place.
Validation sessions, end to end
A validation session is the unit of work that links the device, the model, the dataset, and the Studio results. Every session has a short ID like v-abc123. The session ID is the only piece of state you need to remember.
sequenceDiagram
participant Dev as You
participant Pro as edgefirst-profiler<br/>(on target)
participant St as EdgeFirst Studio
Dev->>Pro: validate --session-id v-abc123
Pro->>St: pull model + dataset
Pro->>Pro: run pipeline,<br/>write predictions.parquet + trace.pftrace
Pro->>St: upload predictions + trace
St->>St: compute mAP / mIoU,<br/>render charts and trace view
Dev->>St: view charts, compare runs,<br/>open trace
The on-target side is the profiler. Studio receives the published artifacts and produces the accuracy charts, the per-operator timing visualizations, and the comparison views. The on-device dependency footprint is small — no Python, no pycocotools — and the binary uses edgefirst-hal, multiple inference engines, and the EdgeFirst DMA optimizations for high on-target performance.
What you see in Studio
When the validation session finishes, the session card surfaces accuracy charts, a per-frame timing summary, and the trace viewer.
See Object Detection Metrics and Segmentation Metrics for the metrics reference.