Papers › Hyperparameter Optimization Can Even be Harmful in Off-Policy Learning and How to Deal with It

Hyperparameter Optimization Can Even be Harmful in Off-Policy Learning and How to Deal with It

23 Apr 2024arXiv:2404.15084archive 2025-07-28

Yuta Saito, Masahiro Nomura

There has been a growing interest in off-policy evaluation in the literature such as recommender systems and personalized medicine. We have so far seen significant progress in developing estimators aimed at accurately estimating the effectiveness of counterfactual policies based on biased logged data. However, there are many cases where those estimators are used not only to evaluate the value of decision making policies but also to search for the best hyperparameters from a large candidate space. This work explores the latter hyperparameter optimization (HPO) task for off-policy learning. We empirically show that naively applying an unbiased estimator of the generalization performance as a surrogate objective in HPO can cause an unexpected failure, merely pursuing hyperparameters whose generalization performance is greatly overestimated. We then propose simple and computationally efficient corrections to the typical HPO procedure to deal with the aforementioned issues simultaneously. Empirical investigations demonstrate the effectiveness of our proposed HPO algorithm in situations where the typical procedure fails severely.

PaperPDFCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 9 code samples harvested from 1 repository linked to this paper: 4 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; 2 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: found in paper text by Syntology: 9 samples from 1 repository, 4 ran (1 with no instrument failure; 3 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

st-tech/zr-obp found in paper text by SyntologyApache-2.0Syntology: 9 samples, 4 ran (3 instrument-failed) · 5 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

9 samples harvested: 4 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 0 honoured, 0 violated, 1 with no contract checked; 3 where Syntology's instrument failed) · 5 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · our draft was wrong
2ran; the contract check could not run
1ran
5unverified

Licence: 0 of the 9 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from st-tech/zr-obp. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

st-tech/zr-obp found in paper text by Syntology 9 samples, 4 ran (3 instrument-failed) · 5 unverified
convert_to_action_dist obp/utils.py ran · our draft was wrong Apache-2.0 (permissive) · c923dce25aad53dd · report fixture: signature n_actions:int/0/int, selected_actions:ndarray/2/int · returned ndarray · level recorded 2026-09-24
estimate_confidence_interval_by_bootstrap obp/utils.py ran; the contract check could not run (RAISES) Apache-2.0 (permissive) · a1f2bd7d1acda181 · report fixture: signature samples:ndarray/1/float, alpha:float/0/float, n_bootstrap_samples:int/0/int, random_state:int/0/int · returned dict · level recorded 2026-09-24
sample_action_fast obp/utils.py ran; the contract check could not run (RAISES) fingerprinted Apache-2.0 (permissive) · 5ae885b38baf7e63 · report fixture: signature action_dist:ndarray/2/float, random_state:int/0/int · returned ndarray · level recorded 2026-09-24
sample_random_uniform_coefficients obp/dataset/synthetic.py ran Apache-2.0 (permissive) · 4fa7b27a8c130446 · report fixture: signature effective_dim_action_context:int/0/int, effective_dim_context:int/0/int, random_:RandomState/0/? · returned tuple · level recorded 2026-09-24
linear_behavior_policy_continuous obp/dataset/synthetic_continuous.py unverified Apache-2.0 (permissive) · 0b2a873bf9ce492b · report
linear_reward_funcion_continuous obp/dataset/synthetic_continuous.py unverified Apache-2.0 (permissive) · 8030be7b385db03a · report
logistic_polynomial_reward_function obp/dataset/synthetic.py unverified Apache-2.0 (permissive) · 628f213ec1c901a2 · report
logistic_reward_function obp/dataset/synthetic.py unverified Apache-2.0 (permissive) · 99116d6ac9c6fa92 · report
quadratic_reward_funcion_continuous obp/dataset/synthetic_continuous.py unverified Apache-2.0 (permissive) · ad68c45f6b6ffe98 · report

Tasks

Decision MakingHyperparameter OptimizationOff-policy evaluationRecommendation Systems

1 archive task tag without a task page not shown.

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

HPO

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections