Papers › Offline Model-Based Optimization by Learning to Rank

Offline Model-Based Optimization by Learning to Rank

15 Oct 2024arXiv:2410.11502archive 2025-07-28

Rong-Xi Tan, Ke Xue, Shen-Huan Lyu, Haopu Shang, Yao Wang, Yaoyuan Wang, Sheng Fu, Chao Qian

Offline model-based optimization (MBO) aims to identify a design that maximizes a black-box function using only a fixed, pre-collected dataset of designs and their corresponding scores. A common approach in offline MBO is to train a regression-based surrogate model by minimizing mean squared error (MSE) and then find the best design within this surrogate model by different optimizers (e.g., gradient ascent). However, a critical challenge is the risk of out-of-distribution errors, i.e., the surrogate model may typically overestimate the scores and mislead the optimizers into suboptimal regions. Prior works have attempted to address this issue in various ways, such as using regularization techniques and ensemble learning to enhance the robustness of the model, but it still remains. In this paper, we argue that regression models trained with MSE are not well-aligned with the primary goal of offline MBO, which is to select promising designs rather than to predict their scores precisely. Notably, if a surrogate model can maintain the order of candidate designs based on their relative score relationships, it can produce the best designs even without precise predictions. To validate it, we conduct experiments to compare the relationship between the quality of the final designs and MSE, finding that the correlation is really very weak. In contrast, a metric that measures order-maintaining quality shows a significantly stronger correlation. Based on this observation, we propose learning a ranking-based model that leverages learning to rank techniques to prioritize promising designs based on their relative scores. We show that the generalization error on ranking loss can be well bounded. Empirical results across diverse tasks demonstrate the superior performance of our proposed ranking-based models than twenty existing methods.

PaperPDFCodeCode Syntology ranMethod as code

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 17 code samples harvested from 4 repositories linked to this paper: 15 ran (of which 1 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 3 violated, 6 with no contract checked; 6 where Syntology's instrument failed) · 2 unverified. Where Syntology's instrument failed: 6 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 8 samples from 2 repositories, 8 ran (6 with no instrument failure; 2 where Syntology's instrument failed); found in paper text by Syntology: 8 samples from 1 repository, 6 ran (3 with no instrument failure; 3 where Syntology's instrument failed); community: 1 sample from 1 repository, 1 ran (0 with no instrument failure; 1 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 between 2026-09-22 and 2026-09-24 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed. 1 of the 15 samples that ran has no recorded date.

ggchen1997/bdi officialmentioned in paperjaxSyntology: 1 sample, 1 ran (1 instrument-failed) · 0 unverified report
lamda-bbo/offline-ram officialmentioned in paperpytorchSyntology: 7 samples, 7 ran (1 instrument-failed) · 0 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

17 samples harvested: 15 ran (of which 1 constructed an object rather than computing a result; 9 with no instrument failure: 0 honoured, 3 violated, 6 with no contract checked; 6 where Syntology's instrument failed) · 2 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.

3ran · violated contract
6ran · our draft was wrong
6ran
2unverified

Licence: 9 of the 17 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 4 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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”. For 2 samples that ran, the graph records a signature this page does not show, each row saying why in its tooltip: for 1, an argument's recorded type or element kind is a printout of an object in Syntology's harness (such as a mock object, a class or a pandas printout), not the type of an input, so it does not describe the call's shape; for 1, for a class the fixture built without calling, the harness called the object with inputs it made up itself, so the recorded signature is the harness's probe, not the fixture's arguments. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

ggchen1997/bdi official repository 1 sample, 1 ran (1 instrument-failed) · 0 unverified
make_loss_fn utils.py ran · our draft was wrong no licence file found · pointer only · 3f6fcd223948503e · report fixture: signature kernel_fn:callable/0/?, mode:str/0/str · returned PjitFunction · level recorded 2026-09-22
lamda-bbo/offline-ram official repository 7 samples, 7 ran (1 instrument-failed) · 0 unverified
LambdaRankLossFunction losses/lambdaRank.py ran · metamorphic tier: deterministic fingerprinted no licence file found · pointer only · 878f7feaba547fb6 · report fixture: returned LambdaRankLossFunction · level recorded 2026-09-22
LossFunction in 8 papers losses/lambdaRank.py ran fingerprinted no licence file found · pointer only · f39d3df3ce16b87c · report fixture: signature y_pred:Tensor/2/float, y_true:Tensor/2/float · returned NoneType · level recorded 2026-09-24
dcg in 14 papers losses/neuralNDCG.py ran no licence file found · pointer only · f40a7926c73e49c1 · report fixture: signature y_true:Tensor/2/float, y_pred:Tensor/2/float, ats:list/1/int, gain_function:callable/0/? · returned Tensor · level recorded 2026-09-24
deterministic_neural_sort losses/loss_utils.py ran · our draft was wrong no licence file found · pointer only · fd1924a6479e1fa4 · report fixture: signature s:Tensor/3/float, tau:Tensor/0/float · returned Tensor · level recorded 2026-09-24
lambdaRank_scheme losses/lambdaRank.py ran fingerprinted no licence file found · pointer only · 9c71991dafef6c40 · report fixture: signature G:Tensor/2/float, D:Tensor/2/float · returned Tensor · level recorded 2026-09-24
sample_gumbel in 62 papers losses/loss_utils.py ran no licence file found · pointer only · c754deebeb9906bf · report fixture: signature samples_shape:tuple/1/int, device:str/0/str, eps:float/0/float · returned Tensor · level recorded 2026-09-24
sinkhorn_scaling losses/loss_utils.py ran no licence file found · pointer only · 089fa157d43247ba · report fixture: signature mat:Tensor/3/float, tol:float/0/float, max_iter:int/0/int · returned Tensor · level recorded 2026-09-24
brandontrabucco/design-bench found in paper text by Syntology 8 samples, 6 ran (3 instrument-failed) · 2 unverified
default_linear_distribution design_bench/datasets/dataset_builder.py ran · violated contract fingerprinted MIT (permissive) · 97d1dadc0092cddc · report fixture: signature ranks:ndarray/1/int · returned ndarray · level recorded 2026-09-24
default_quadratic_distribution design_bench/datasets/dataset_builder.py ran · violated contract fingerprinted MIT (permissive) · cd881bdf30de1f0a · report fixture: signature ranks:ndarray/1/int · returned ndarray · level recorded 2026-09-24
default_uniform_distribution design_bench/datasets/dataset_builder.py ran · violated contract fingerprinted MIT (permissive) · 7dbee57a564eced6 · report fixture: signature ranks:ndarray/1/int · returned ndarray · level recorded 2026-09-24
get_confirm_token in 41 papers design_bench/disk_resource.py ran · our draft was wrong MIT (permissive) · fb3792dae3b52c70 · report fixture: returned str · level recorded 2026-09-24
import_name design_bench/task.py ran · our draft was wrong MIT (permissive) · 9bdda179859c7e1c · report fixture: signature name:str/0/str · returned type · level recorded 2026-09-24
one_hot in 150 papers
census: 18 implementations from 25 papers, 10 distinct outputs across 6 buckets, one shared input per bucket
design_bench/datasets/discrete_dataset.py ran · our draft was wrong MIT (permissive) · 9254b9a1999e5ab9 · report fixture: signature a:ndarray/2/int, num_classes:int/0/int · returned ndarray · level recorded 2026-09-24
direct_download design_bench/disk_resource.py unverified MIT (permissive) · bee40bc7b8e40002 · report
google_drive_download design_bench/disk_resource.py unverified MIT (permissive) · 0508c25f44e088dc · report
jiangnanboy/learning_to_rank community 1 sample, 1 ran (1 instrument-failed) · 0 unverified
load_data in 700 papers src/trees/lgb_ltr.py ran · our draft was wrong no licence file found · pointer only · 3006c520eff7c841 · report fixture: signature feats:str/0/str, group:str/0/str · returned tuple · level recorded, date not recorded

Method as code Syntology

What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.

2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).

2 sibling assemblies for learning to rank (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.

harvested Assembly for learning to rank (graph method: learning to rank). 2 bricks; individually on a fixture: 2 ran (of which 1 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 0 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. LambdaRankLossFunction entry · level 1 · ran · 878f7feaba547fb6
  2. LossFunction helper · level 1 · ran · f39d3df3ce16b87c

harvested Assembly for learning to rank (graph method: learning to rank). 1 brick; individually on a fixture: 1 ran (of which 0 constructed an object rather than computing a result; 0 with no instrument failure: 0 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. The assembly has not been run end-to-end.

one of 2 siblings

  1. make_loss_fn entry · level 1 · ran · our draft was wrong · 3f6fcd223948503e

Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2410.11502") returns these assemblies with each brick's role and wiring (how to connect).

Tasks

Ensemble LearningLearning-To-Rankmodel

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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