Read OI by Strike, Expiration and Time

Choose a grouping for the same dated input

Map → Open Interest offers OI by Strike, OI by Expiration, OI Change and OI / Time. Each organizes dated outstanding-contract observations differently. By Strike locates concentrations across prices; By Expiration compares maturities; Time follows stored eligible dates; Change compares compatible observations across dates. Start by reading the OI date before expecting any of these views to react like a live execution tape.

Build a like-for-like comparison

Use the same root/family and expiration/right scope when checking totals across tools.

1. Open Open Interest and choose the source symbol.
2. Confirm the stated OI date and current session/date selection.
3. Inspect calls and puts by strike.
4. Switch to expiration grouping without changing the intended scope.
5. Use OI / Time to inspect available historical dates.
6. Open OI Change and verify the two dates/contracts being compared.

Listings affect change eligibility

OI Change concerns contracts alive at both relevant closes. A new listing or an expired contract does not have the same comparable population as a surviving one. Missing dates can leave a sparse time series; the application should not invent a daily point by carrying the last observation forward. Percentage change also depends on a usable prior denominator, so an undefined prior value should not become an ordinary finite growth rate.

Worked example: volume rises while OI stays fixed

During a busy session, the tape can show increasing executed contracts while OI by Strike remains unchanged on its stated daily date. That is expected when no new daily OI snapshot exists. The activity could include repeated turnover, openings and closings, which tape alone cannot separate completely. Compare the next eligible dated OI observation when available, keeping exact identities fixed. Do not infer the number of newly opened positions from intraday volume minus yesterday's OI.

Troubleshoot mismatched totals and missing dates

Check whether one view includes all expirations while another uses a strike neighborhood or side filter. Confirm the root rather than assuming a family and a single root are identical. If one historical date is absent, record the availability state instead of filling it yourself. A useful ticket includes OI dates, exact selection and hovered values from both groupings so support can distinguish scope from storage coverage.

Open interest is a dated position input

Open interest reports outstanding contracts as of its stated OI date. It is distinct from current-session contract volume, which counts executed activity in the admitted print set. A contract can trade repeatedly without producing the same change in open interest. Comparing volume with OI can help screen activity, but it does not identify how many trades opened positions or which participants hold them. Always retain the root, expiration, right and strike when matching records across dates.

A historical OI series contains stored eligible dates, not an automatically complete daily archive. Missing dates remain absent. OI Change compares compatible contracts alive at both relevant closes; a new listing or expired contract cannot be treated as an ordinary like-for-like row. Model calculations based on OI, including exposure and max pain, inherit that date and coverage. If a result appears unchanged during an active session, check whether its daily OI input has actually changed before treating the stable number as a failed live update.

Reconcile strike totals and expiration totals

For a numerical cross-check, choose one root/family, the same OI date, the same call/put scope and compatible strike/expiry bounds. Sum a bounded strike view only if it actually includes the same population as the expiration view. A broad headline total can intentionally exceed the visible neighborhood. If related roots are aggregated at family level, moving to one exact-root chain narrows the population and need not reproduce the family total. Keep those source choices visible in any exported notes.

For Change, compare the two actual stored OI dates rather than assuming adjacent calendar days. Weekend or unavailable dates can make them farther apart. Read absolute and percentage differences separately, and inspect the prior denominator before treating a very large percentage as large absolute activity. New or expired contracts are not ordinary matched pairs. In Time, missing dates should remain holes rather than being silently forward-filled. A stable OI series can still be correct during active trading because the source is dated positions, not the current execution counter shown on the tape.