Across this series you've run simulation, lint, synthesis, STA, and PnR jobs one at a time. Learning Sessions is what ties them together into a single, trackable history of your work — and it's a PRO feature.
6 min read | Beginner Level
What You'll Learn
- How to start a Learning Session before running jobs
- What runs, the timer, and milestones track
- How to diff two runs against each other
- How to add notes and share a read-only session link
Starting a Session
Open the Learn menu in the navbar and select Sessions. On FREE, this menu item is visible but locked with an upgrade prompt; on PRO, it opens a dialog to name your session before you start. Start the session before running any jobs you want it to track — runs made before a session starts aren't logged into it retroactively.
Learning Sessions require the PRO tier. On FREE, the Sessions menu item is visible but locked.
Runs, Timer & Milestones
Once a session is running, a toolbar shows an elapsed-time timer alongside pause/resume/complete controls. Every simulation, synthesis, lint, or STA job you run while the session is active becomes a numbered, timestamped entry in the session's Run History, and certain milestones — like your first successful simulation — are flagged automatically.
Diffing Two Runs
Open Run History and select two runs from the session — for example, your first synthesis attempt and a later one after fixing a lint warning. The diff viewer shows what changed between them, both in code and in results.
Adding Notes & Sharing a Read-Only Link
You can attach a note to any run — useful for recording why you made a particular change. A session can also be shared as a read-only link, which supports comments; if you're working through this series as part of a class, that's a natural way for an instructor to leave feedback on your run history.
Common Mistakes
Mistake #1: Forgetting to start the session before running jobs
Runs made before a session starts aren't added to it after the fact. If you want your first simulation run tracked, start the session first.
Mistake #2: Assuming a shared link lets the viewer edit
A shared session link is read-only with comments — a viewer can leave feedback, but can't re-run jobs or modify your code through it.
Where Is This Used?
Session-style run logging mirrors how verification teams track regression history across a project's life — not just what the current state is, but how it got there, and why specific changes were made along the way.
Practice Exercise
Challenge: Build a Two-Run History
Start a session, then re-run the Chapter 2 simulation and the Chapter 3 synthesis you already completed earlier in this series. Open Run History and diff the two.
Hint
You're not looking for a "correct" diff here — just confirming both runs appear as separate, timestamped entries you can select.
Solution
Both jobs should appear in Run History in the order you ran them, each with its own timestamp; selecting both in the diff viewer shows the code and result differences between a simulation run and a synthesis run — a good first look at how the diff view behaves before using it on two runs of the same job type later.
Summary
In this tutorial, you learned:
- How to start a Learning Session before running jobs
- What the timer, Run History, and milestones track
- How to diff two runs against each other
- How to add notes and share a read-only session link