Skip to content

03 / Analyze · Calculation Lineage & Provenance

Follow the value back to the method.

Metric Inspector turns a calculated value into an inspectable method path. Iriscope also packages the relevant analysis state into a readable methodology report and a machine-readable provenance file.

Explore the workflow

Back to Iriscope

Iriscope Metric Inspector for an IVT-robust AOI transition count, showing its definition, export field, available and missing values, calculation path and actual project results.
From value to method: inspect the metric definition, calculation basis, availability and ordered path from source data to result.

The capability

What you can inspect and control.

Use this workflow for the part of the research question it addresses.

01

Concrete metric path

See inputs, preprocessing, event source, AOI mapping and aggregation in order.

02

Project-aware

Definitions, units, availability and actual values reflect the selected project scope.

03

Methodology bundle

Export a readable Markdown report and machine-readable JSON provenance.

04

Auditable review

Quality rules, corrections, event review and robustness status remain part of the record.

In the application

A workflow you can follow.

Keep the relevant material, definitions and review decisions connected at each step.

Iriscope Robustness Lab listing the detection thresholds, minimum durations, merge settings and provenance signatures actually stored for four methods.
Inspect the settings actually stored with each method: thresholds, minimum duration, merge settings and provenance signatures.
  1. Select a metric in the active export scope or open it from its context menu.
  2. Inspect its name, definition, export field, group, unit, calculation basis, availability and visible values.
  3. Follow the ordered path: samples, preprocessing, event source, AOI or pairwise construction, and metric aggregation.
  4. Export the methodology bundle when the project needs a transparent handoff, archive or methods record.

Method context

Keep the scope of the result visible.

The relevant settings, prerequisites and interpretation stay attached to the workflow.

Method settings, scope and interpretation

Validation, correction and calculation are related — but not silently merged.
Iriscope retains the difference between raw and cleaned samples, stored events, non-destructive review state and documented correction layers. A result can therefore be inspected without presenting one hidden preprocessing state as unquestionable fact.

Connect the workflow

Bring this capability into your study.

Tell us about the material, recording and result you need to inspect. We can identify the appropriate product and method scope.

Discuss Iriscope

Explore the workflow