Where does activity concentrate?
Compare effective rank across layers and frames. Inspect how broadly measured variation is distributed.
IRIS · SACCADIC’s flagship product
Measure how
AI knowledge
develops.
Loss tells you how a model scored. IRIS lets you watch its internal representations develop while it trains, then compare those changes with validation evidence.
An inspection instrument for research teams · Pre-alpha
Inside the instrumentLayer structure
The score is only
part of the picture.
Keep loss, accuracy, and held-out evaluation. Add an internal view that helps you locate a change and choose what to inspect next.
When do patterns reorganize?
Follow basis rotation and representation motion over time. Place internal changes beside your outcome curves.
How do domains interact?
Inspect representation overlap and measured agreement or opposition between probe gradients.
One loss curve.
Two internal stories.
Two invented internal patterns share the same loss curve. First compare the definitions below, then switch patterns and move through training.
Distributed structure
Several layers retain higher effective rank: measured variation uses more independent directions within each of those layers.
Concentrated structure
Effective rank rises in one layer while falling in others. The measured pattern becomes more uneven across layers.
These names describe the two patterns in this illustration. Here, effective rank is k95: the whole-number count of leading eigenvalues needed to capture 95% of measured activation variance. Neither pattern alone establishes better learning.
Interactive illustration · Synthetic data
Illustrative loss curve
The same improving loss. It cannot tell you which internal pattern is unfolding.
What an internal view adds
A slow, 10-second sweep across an illustrative 20,000-step run. Drag to explore; release to continue. Pause to hold a frame.
Invented values for teaching, not a captured run. Higher or lower rank is not a quality grade. Check the pattern against your task, probes, and validation.
See the evidence
in context.
Real screenshots from the IRIS bench. Inspect a view, read what it measures, and keep the next question attached to the evidence.
Structure evolves differently by layer.
Effective rank describes how many directions carry most measured activation variation. Compare trajectories to see which layers changed.
Next question: how do those changes line up with domain-level evaluation?
Inspect during
training.
New diagnostic frames appear automatically in the Bench web interface as training runs, so your team can examine changes without waiting for the run to finish.
Choose when to measure.
Set a fixed extraction interval in training steps, or use adaptive cadence to capture more often when the model is changing and less often when it is quiet. During a live run, adjust the schedule in the Bench or tune adaptive sensitivity.
Explore and export.
Use the visual Bench to compare layers, domains, and training frames. Export chart data as Excel workbooks or JSON, or use the optional Butler to relay scalar measurements to W&B, TensorBoard, MLflow, or Aim.
Ask your own questions.
IRIS offers more than 100 built-in views; availability depends on your model and captured data. For another measure, compute it in your training code and report it as a User Defined Signal, as in the MIT-inspired flow-complexity example. You can also combine signals and IRIS measurements in a User Defined Function in the Bench.
Capture cadence, analysis latency, and available diagnostics determine what you can see and when. Measure capture overhead on your workload. Earlier evidence is an opportunity to review; it is not a promise of time or compute savings.
Get started
with IRIS.
Download, install, add credits, and connect the tracker to a familiar training script.
Download IRIS.
Sign in or create an account, complete the account setup, and choose the download for your computer.
Open download dashboard ↗Install on your training machine.
Follow the Install IRIS instructions in your dashboard. They guide you through installing the package and saving your run key.
Add credits.
Choose a credit pack in the portal. The smallest pack is 1 credit. Check the quoted run price and your available balance before training.
Add credits ↗Let your LLM connect the tracker.
In the Bench, open AI Review Prompts → Add IRIS to Training. Give the copied prompt and your training script to your coding assistant.
The four essential calls are: create
Explore the Bench example →IrisTracker, checkshould_extract(step)and callextract(model, step=step)inside the training loop, then callflush()afterward. Addreport_loss(loss)if you want a loss curve in the Bench. The prompt can add other available measurements while preserving your model and training logic.
A penny for your thoughts.
Small experiments start at 0.01 credits per run. Through 10 million parameters, the rate is 0.05 credits per million parameters.
- 1M parameters
- 0.05 credits
- 5M parameters
- 0.25 credits
- 10M parameters
- 0.50 credits
$1 = 1 credit
Pricing counts all model parameters, including frozen ones. Run duration does not set the charge. Prices are rounded down to 0.01-credit steps, with a 0.01-credit minimum.
Add credits ↗Purchased credits expire twelve months after purchase. Check the portal for current pricing and account requirements before you buy or begin a run.
A few practical answers.
Does IRIS replace validation?
No. IRIS complements performance measurements with internal observations. A structural change does not by itself establish better quality, generalization, or a cause.
Does IRIS decide how to change training?
No. IRIS reports measurements. It does not prescribe optimizer settings, change model weights, or decide whether a run should stop.
Will every view be available?
Availability depends on the model, captured channels, probes, and configuration. Some diagnostics require additional measurements; expert views require a mixture-of-experts model.
Where does the inspection happen?
The tracker runs in your environment. The bench reads captured diagnostic artifacts without reloading the model. Licensing requires a network connection at the start of a run. Review diagnostic artifacts before sharing them.