Learn
Data clocks and model limits
A WebApp screen can combine a moving spot price, periodically refreshed options analytics, daily open interest, and a saved session range. To understand a change—or an apparent mismatch—check which of those observations you are comparing.
Different data, different clocks
A price tick can arrive between analytics refreshes.
The calculation uses the inputs available to that refresh.
Normally unchanged within the trading session.
Accumulated activity; it is not a count of open positions.
Its own anchor and boundaries stay fixed after capture.
Patterns are schematic. Read the actual status, session date, and timestamp in your view; a fresh spot tick does not make the other observations equally recent.
Outside the update window, or when the service reports updates paused, the latest saved analytics can remain visible. On a full U.S. market holiday, check the pause notice and next update. All times on this page are Eastern Time, not your browser’s local time.
A refresh timestamp is not the age of every input. It identifies an analytics update; it does not mean OI has just been cleared again or every option quote changed at that instant. Check Last Refresh together with the price badge and any pause or previous-session label.
The badge can show a live derived price or a ~1 min delayed spot price fallback. A live badge does not establish a direct exchange quote: index and futures prices use the product’s CFD/proprietary mapping. For instrument-specific interpretation, see the price badge and futures mapping.
Open interest and volume answer different questions
OI counts outstanding contracts
Reported OI reflects contracts still open after the clearing/reporting process. The WebApp’s OI columns normally stay fixed during the session. On weekends and holidays, the relevant report may be from an earlier trading day—not simply yesterday’s calendar date.
Volume measures session activity
A contract can trade repeatedly, and trades can open or close positions. Volume therefore cannot be added to OI to reconstruct the live position book. Before 9:30 AM ET, the WebApp’s volume columns refer to the previous session; check the session label.
Why a gamma wall can move without new OI
GEX and DEX weight contract counts by option sensitivities. Those sensitivities can change with spot, implied volatility, and time. At the next analytics calculation, the exposure distribution and the ranking of its peaks can therefore change even if the reported OI inputs are identical.
A new C1 label is not, by itself, evidence that traders just opened calls at that strike. Separately, a spot move relative to unchanged profile levels can change the displayed state without relocating the levels themselves. Distinguish a changed exposure calculation from a changed position of price within the map.
Also keep sign and change separate: a hypothetical move from +40M to +30M Net GEX is a decrease of 10M, while the resulting exposure remains positive. A negative change is not the same as negative exposure.
Saved ranges and live calculations
Adaptive Expected Move follows the live spot reference and recalculates with refreshed options inputs. Its printed boundaries can move with spot between chain refreshes. A saved EOD, PRE, or OPEN band keeps its captured anchor and boundaries.
To isolate that distinction, hold the illustrative Adaptive distances at −4 / +3 points while its reference rises from 100 to 101. Keep a separate PRE snapshot anchored at 99, with a saved ±3-point width.
Dots mark each reference price. Both Adaptive boundaries shift by one point in this example, while their distances and total span stay fixed. The PRE band does not move. This isolates the anchor effect; actual refreshed distances can also change.
The 6:30 AM PRE capture is separate from the normal 6:40 AM start of minute analytics updates. They serve different purposes. For the EOD/PRE/OPEN definitions and dates, see Expected Move Box; for updated ranges, see Adaptive Expected Move.
Comparing TradingView and the WebApp
Minute analytics + separate spot stream
A current price and the latest options snapshot can have different timestamps on the same screen.
About five scheduled updates
A new candle or a moving TradingView price does not mean a new TanukiTrade analytics package has arrived.
Check the scheduled delivery windows and compare matching symbols, calendar expirations, aggregation modes and timestamps. Mapped futures also require the same underlying-to-display mapping. Different snapshot times can explain different values without either view being defective.
Copy Levels supplies a manual snapshot to GEX Profile PRO through Manual Override. It checks compatible context and uses the newer matching data. Pasting does not turn it into a continuous WebApp feed; copy again when you need to supply a newer snapshot.
Record enough context to compare like with like
| Observation | Record with the value |
|---|---|
| GEX / DEX profile | Symbol, exact expiration, standalone or cumulative scope, analytics timestamp, and units. |
| Reported OI / session volume | The reporting or trading-session date. Keep position counts separate from traded activity. |
| Adaptive range | Expiration, method or delta setting, spot reference, both distances, boundaries, and analytics time. |
| Saved session band | Target session date, EOD/PRE/OPEN label, captured anchor, and saved boundaries. |
| History / Replay | Recorded day, selected playback time, and available snapshot time. Historical sampling need not match the live refresh cadence. |
In Replay, use the recorded context rather than today’s clock. A future price overlay is later price action for review; it is not information that was available at the playback moment. See GEX History/Replay.
Freshness does not establish ownership or intent
Reported OI counts outstanding contracts, and volume counts trading activity. Neither alone identifies who owns each side, a complete dealer inventory, or the hedges already executed elsewhere. Recalculating more frequently does not supply that missing information. Read dealer hedging for the model assumptions.
For the underlying market-data concepts, see OIC on open interest and the clearing process and changing option gamma.
TanukiTrade documentation. Levels are context, not a recommendation. tanukitrade.com