GEX levels history: walls and exposures through the day
The history panel records one point per minute and plots the call wall, zero gamma and the put wall against spot through the session, either as prices or as distances from spot. A second track below carries net GEX, vanna or charm over the same timeline.
Senzoukria · Documentation · Updated September 2026
Where to find it
- Where
- GEX workspace → History page
- Cadence
- One point per minute, capped at 480 points — roughly an extended session
- Reading modes
- By price (default) and Distance, remembered locally
- Exposure track
- NET GEX (default), VANNA, CHARM
- Sanity filter
- A level more than 20% away from spot is dropped rather than plotted
What it does
On a quiet underlying the walls do not move all day: three perfectly flat lines, with spot the only living trace. The screen then suggests nothing is happening, when what is happening is that price is closing in on a wall that has not moved.
That is why the panel offers two readings of the same data. By price plots the three levels and spot on a price axis. Distance replots them as their percentage gap from spot, so a motionless wall being approached becomes a line diving toward the axis — and it is the movement, not the position, that decides a session.
Both the full-chain levels and the 0DTE levels are recorded at every point, so switching the workspace expiry mode changes what is drawn without needing anything to be recorded again.
Settings
| Setting | Default | What it changes |
|---|---|---|
| Reading mode | By price | Switches between price levels and percentage distance from spot |
| Exposure track | NET GEX | Plots net GEX, vanna or charm on the lower track |
| Series drawn | CW, ZG, PW | Call wall, zero gamma and put wall, each in its workspace colour |
| Corridor | Shown when both walls exist | The gap between the put wall and the call wall, whose width is an item in itself |
| Retention | 480 points at one per minute | The oldest point is dropped once the buffer is full |
| Panel height | Floor of 320 px, exposure track 110 px | Below the floor the lines stop being separable |
How to use it
Use By price to situate the levels, then switch to Distance whenever the price lines look static. The corridor readout tells you whether the space between the walls is closing on price — a narrowing corridor describes a short session, a widening one describes room.
The exposure track is where sign changes show. Vanna and charm matter less for their value at a given minute than for the moment they change sign during the day, which a snapshot never shows. Points recorded before a field existed, or where the backend could not compute it, are skipped rather than filled with a zero: a zero is an assertion, an absence is not.
Per-level drift is reported alongside: not recorded when nothing usable exists, held when the level has not moved, or a signed percentage when it has.
Limits and pitfalls
The history is intraday and session-scoped: it starts filling when the workspace is open, so there is no morning in an application launched at noon. The panel prints how many points it holds while it fills.
A recorded zero gamma may come from the price profile rather than from the backend when the backend could not place one; the two are both flips but not the same measurement, and the point records which it was. Levels more than 20% away from spot are treated as outliers and dropped, because a single aberrant value would flatten the whole scale.
Related pages
This page in other languages
Frequently asked questions
- How far back does the history go?
- Up to 480 points at one per minute, which covers roughly an extended session. It is recorded while the workspace is open and does not backfill a morning you were not connected for.
- What does the Distance mode show that By price does not?
- The same levels measured from spot. A wall that never moves but is being approached becomes a line diving toward the axis, which the price view draws as a flat line.
- Why does the vanna track have gaps?
- Points recorded before the field existed, or points where the backend could not compute it, carry no value. They are skipped rather than drawn at zero, because a zero vanna would be a claim the data does not support.