Backend
Fast Rates for Offline Contextual Bandits with Forward-KL Regularization under Single-Policy Concentrability
arXiv stat.TH0 views
arXiv:2605.09214v2 Announce Type: replace-cross Abstract: \emph{Kullback-Leibler} (KL) regularization is ubiquitous in reinforcement learning algorithms in the form of \emph{reverse} or \emph{forward} KL. Recent studies have demonstrated $\epsilon^{-1}$-type fast rates for decision making under reverse KL regularization, in contrast to the standard $\epsilon^{-2}$-type sample complexity. However, for forward-KL-regularized objectives, existing statistical analyses are either not applicable or result in $\tilde{O}(\epsilon^{-2})$ slow rates. We take the first step towards addressing this problem via a streamlined analysis of forward-KL-regularized offline CBs. We give the first $\tilde{O}(\epsilon^{-1})$ upper bounds in tabular and general function approximation settings, both under notions of \emph{single-policy concentrability}. In particular, our convex-analytical pipeline unifies these settings by exploiting the pessimism principle in a novel way and completely bypasses the proof routines in previous works based on the mean value theorem, which might be of independent interest. Moreover, we provide rate-optimal lower bounds, manifesting the tightness of our upper bounds in terms of statistical rates. Our lower bounds also demonstrate that the forward-KL-regularized sample complexity recovers the unregularized slow rate in the low-regularization regime, similarly to the reverse-KL regularization.
Source:https://arxiv.org/abs/2605.09214PreviousHyper Input Convex Neural Networks for Shape Constrained Learning and Optimal TransportNextHigher-Order Neyman Orthogonality in Moment-Condition Models
Related posts

Leaked AI API keys after a cloud platform incident: blast radius, rotation, and bill forensics
0dev.to

The Northflank AI Key Notice Sent Me Auditing My Own Setup. Here Is the Order That Worked
0dev.to
Containing cloud, package and AI keys after a GitHub Actions secret theft
0dev.to

Widening an Unleash rollout should keep the people already in
0dev.to
Before Your Team Standardizes on a Free AI Coding Stack, Run a Two-Endpoint Swap Test
0dev.to
Judge a Free AI Tier by Its Exit Cost, Not Its Entry Price
0dev.to