Copyright © 2026 Saccadic LLC · Patent pending.

Browse chapters
  1. Release NotesChanges by version
  2. Chapter 1What IRIS Is and Is Not
  3. Chapter 2The IRIS Data Model
  4. Chapter 3How IRIS Measures
  5. Chapter 4Safe Interpretation and the First 15 Minutes
  6. Chapter 5Dashboard Overview
  7. Chapter 6Installation
  8. Chapter 7Configuration
  9. Chapter 8Build the Model Spec and Probe Set
  10. Chapter 9Minimal Tracker Integration
  11. Chapter 10Launch the Bench and Verify Capture
  12. Chapter 11Runtime Control, Signals, Metrics, and Logs
  13. Chapter 12Integration Patterns by Model Family
  14. Chapter 13Distributed Training
  15. Chapter 14Artifacts, Reports, Export, and Security
  16. Chapter 15Troubleshooting
  17. Chapter 16Whole Model and Layer Structure
  18. Chapter 17Domain Training and Affinity
  19. Chapter 18Attention-Head Diagnostics
  20. Chapter 19MoE Expert and Router Diagnostics
  21. Chapter 20Facets and Emergent Pathways
  22. Chapter 21Gradient Residuals, Stability, Curvature, and Update Efficiency
  23. Chapter 22Adaptive Cadence and Event Detection
  24. Chapter 23CLI Reference
  25. Chapter 24Configuration-Key Reference
  26. Chapter 25API Reference
  27. Chapter 26File and Schema Reference
  28. Chapter 27Glossary and Concept Index
  29. Chapter 28The Flow Map
  30. Appendix ADiagnostic Availability Matrix
  31. Appendix BLLM Prompt Library
On this page

Chapter 5 — Dashboard Overview

Bench — the live dashboard

Start the Bench on a run directory with iris /path/to/run-dir. It reads the diagnostic bundle while training continues or after training has ended. You can inspect the same captured run without loading its model again. For launch flags and remote access, see Chapter 10.

Find the view that answers your question

View What to inspect
Run Run identity, captured frames, credits, resource readings, and tracker controls.
Concept Space A projection of how labeled probes are organized in the recorded representations.
Whole Model Training outcomes and internal structure or motion across the run.
Domains Differences between the categories assigned to your probes.
Layers Spectra, effective dimensionality, orientation, and other layer-level readings.
Heads Per-head readings when the architecture and capture support them.
Experts Expert and routing readings on supported mixture-of-experts captures.
Facets Observed groupings of probes, with explicit evidence and identity limits.
Flow Map Layer-to-layer signal views, where the run recorded them.
Run Notes Your record of interventions and observations.
User Signals you reported and functions you define over available channels.
AI Review Prompts Prompts for integration, probes, and evidence-aware report reading.
Manuals Product documentation inside the Bench.

Not every model or bundle supports every view. Read the sentence explaining an unavailable panel before changing settings. An architecturally inapplicable measurement differs from one that was not captured, was shed, or is still being prepared.

Compare the same frame

The playback bar lets you inspect recorded training steps across views. Pause when reading exact values. A display animation does not create new measured frames between captures. Look at step labels and capture gaps, especially when comparing an internal change with loss or accuracy.

Keep observations with the run

Use Run Notes and chart observations to record what you saw and what changed in the training setup. Note checkpoint resumes, optimizer changes, data changes, and manual interventions. A timestamped observation helps you evaluate a proposed explanation later; it is not itself evidence of cause.

Your own signals and functions

Report a scalar with tracker.report_signal(index, value, label=..., unit=..., description=...). In the User tab, Reported signals remain distinguishable from IRIS™-derived measurements. Give each signal a clear definition and unit so another reader can interpret it.

Derived functions are evaluated in the Bench over data already in the run. Use the variable picker to choose available channels and save expressions you want to reuse. A function cannot manufacture an absent channel. If inputs have no jointly available samples, preserve that gap rather than interpolating a result and treating it as measured.

Check cost and resources

Review the run's license and credit state before training, and use the portal for current pricing and account requirements. Measure instrumentation overhead on your own model and hardware. Capture cadence, probe count, available diagnostics, and resource pressure affect the work performed; neither another run's overhead nor a resource badge predicts yours.