À suivreGuide suivant
Comment créer des graphiques à partir de vos données avec l'IA
Applications
GUIDE Technique
Off-policy evaluation estimates how a new decision policy might perform using data logged by an older policy, without deploying the new policy first.
Inverse propensity scoring reweights outcomes by action probabilities, but reliable estimates require adequate policy overlap, correct propensities and careful handling of high variance and selective feedback.
A policy maps context, such as a user and current page, to an action such as which item to display. Off-policy evaluation (OPE) estimates a target policy's expected outcomes using logs generated by a different behavior or logging policy. It can help screen a candidate before deployment, especially in recommendation, advertising and contextual bandits. Inverse propensity scoring (IPS) weights each logged reward by the ratio between the target policy's probability of choosing that action and the logging policy's probability. For deterministic policies, only records where the logged action matches the target contribute, scaled by the inverse logging propensity. This corrects selection under assumptions, but small logging propensities create large weights and high variance. Clipping weights can stabilize estimates while introducing bias. Self-normalized IPS divides by the sum of weights, and doubly robust methods combine propensity and reward models, each with distinct assumptions. Support or overlap is crucial. If the logging policy never chose an action in a context, the log contains no direct evidence of its outcome there. No weighting formula can recover that missing counterfactual without additional assumptions. Propensities must be logged accurately, and the reward outcome must be observed. Selective labels, delayed outcomes and interference can also undermine estimates. Use OPE as evidence, not a guarantee. Report effective sample size, weight distribution, overlap diagnostics and sensitivity to estimators. A large estimate driven by a few extreme weights should be treated cautiously. Candidate policy changes that move far outside historical support may require randomized exploration or a controlled online experiment. OPE complements offline predictive metrics but does not replace experimentation for every decision. Evaluation assumptions should be documented with the logging policy version, context features, action set and reward definition.
Les décisions en matière d'architecture déterminent les performances et les coûts d'exploitation pendant des années.
La formation technique aide les équipes à choisir la bonne pile, pas seulement la plus récente.
De meilleurs choix d’ingénierie réduisent les incidents de fiabilité en production.
OPE can help teams reduce risk by screening policies within the support of existing logs and identifying where evidence is too weak. Future data collection should record action propensities, exposure, context and outcomes with stable policy versions. Teams can combine OPE with small randomized experiments to improve support and validate estimates. Dashboards should show weight tails and effective sample size alongside policy value. When a candidate changes behavior substantially, the appropriate response may be to gather new evidence rather than extrapolate beyond the logs.
A recommender logged which item it showed, the context, click outcome and probability of selecting that item. An analyst uses those propensities to estimate a candidate policy's expected reward from the old log.
A target policy chooses actions that the logging policy almost never selected. The few matching outcomes receive large inverse weights, producing a noisy and potentially unstable estimate.
A team compares raw IPS with a self-normalized estimator and a doubly robust estimator, reporting assumptions and sensitivity rather than selecting whichever number is most favorable.
A policy evaluation lacks logged action probabilities. The analyst does not claim unbiased IPS results and instead collects better randomized logs or runs a controlled experiment.
L’optimisation d’un benchmark peut masquer des faiblesses plus larges du système.
Les coûts d’infrastructure et de maintenance sont souvent sous-estimés.
Les lacunes en matière de sécurité et d’observabilité peuvent se creuser à mesure que les systèmes deviennent plus complexes.
Définissez les objectifs de latence, de qualité et de coût avant la mise en œuvre.
Benchmark dans des conditions de charge et de données réalistes.
Surveillance des instruments pour détecter les erreurs, la dérive et l'impact sur l'utilisateur.
Préparez les chemins de restauration et de réponse aux incidents avant la mise à l’échelle.
Free newsletter
Three verified AI stories every weekday morning, written in plain English. Free forever, no ads.
One email each weekday. Unsubscribe in one click. We never sell or share your address.
Test yourself
Instant feedback on every answer, and a shareable certificate with a verifiable ID once you pass a course.
Support free AI education. AI Understanding is a 501(c)(3) nonprofit — no ads, no paywall, ever. Make a donation
Off-policy evaluation estimates how a new decision policy might perform using data logged by an older policy, without deploying the new policy first. Inverse propensity scoring reweights outcomes by action probabilities, but reliable estimates require adequate policy overlap, correct propensities and careful handling of high variance and selective feedback.
OPE uses logged behavior and outcomes to estimate performance under a different policy.
Inverse propensity weighting compensates for the logging policy's action selection under assumptions.
Small propensities lead to large inverse weights, making estimates unstable.
If the logger never took an action in a context, OPE cannot directly learn its outcome there from those logs.
Weight concentration can make a large raw dataset behave like a much smaller effective sample.
Continuez à apprendre
Plus de guides sélectionnés pour ce sujet
À suivreGuide suivant
Comment créer des graphiques à partir de vos données avec l'IA
Applications