Papers › Learning Optimized Risk Scores

Learning Optimized Risk Scores

1 Oct 2016arXiv:1610.00168archive 2025-07-28

Berk Ustun, Cynthia Rudin

Risk scores are simple classification models that let users make quick risk predictions by adding and subtracting a few small numbers. These models are widely used in medicine and criminal justice, but are difficult to learn from data because they need to be calibrated, sparse, use small integer coefficients, and obey application-specific operational constraints. In this paper, we present a new machine learning approach to learn risk scores. We formulate the risk score problem as a mixed integer nonlinear program, and present a cutting plane algorithm for non-convex settings to efficiently recover its optimal solution. We improve our algorithm with specialized techniques to generate feasible solutions, narrow the optimality gap, and reduce data-related computation. Our approach can fit risk scores in a way that scales linearly in the number of samples, provides a certificate of optimality, and obeys real-world constraints without parameter tuning or post-processing. We benchmark the performance benefits of this approach through an extensive set of numerical experiments, comparing to risk scores built using heuristic approaches. We also discuss its practical benefits through a real-world application where we build a customized risk score for ICU seizure prediction in collaboration with the Massachusetts General Hospital.

PaperPDFCodeCode 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 17 code samples harvested from 1 repository linked to this paper: 13 ran (of which 0 constructed an object rather than computing a result; 13 with no instrument failure: 0 honoured, 0 violated, 13 with no contract checked; 0 where Syntology's instrument failed) · 4 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code; here there are none.

By repository: official repository: 17 samples from 1 repository, 13 ran (13 with no instrument failure; 0 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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

ustunb/risk-slim officialmentioned in paperBSD-3-ClauseSyntology: 17 samples, 13 ran (0 instrument-failed) · 4 unverified report
csinva/imodels MITSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to Hierarchical Shrinkage: improving the accuracy and interpretability of tree-based methods (arXiv:2202.00858; that paper's own run record: 2 ran (of which 0 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); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

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

13ran
4unverified

Licence: 0 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 ustunb/risk-slim. “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: 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. “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.

ustunb/risk-slim official repository 17 samples, 13 ran (0 instrument-failed) · 4 unverified
chained_updates riskslim/bound_tightening.py ran BSD-3-Clause (permissive) · 2a595781bb9b7383 · report fixture: signature bounds:dict/0/?, C_0_nnz:ndarray/1/float, new_objval_at_feasible:float/0/float, new_objval_at_relaxation:float/0/float, MAX_CHAIN_COUNT:int/0/int · returned dict · level recorded 2026-09-25
chained_updates_for_lp riskslim/bound_tightening.py ran BSD-3-Clause (permissive) · e1a24ddd1cf1f51d · report fixture: signature bounds:dict/0/?, C_0_nnz:ndarray/1/float, new_objval_at_feasible:float/0/float, new_objval_at_relaxation:float/0/float, MAX_CHAIN_COUNT:int/0/int · returned dict · level recorded 2026-09-25
get_score_bounds riskslim/coefficient_set.py ran BSD-3-Clause (permissive) · 22cbea24923d563c · report fixture: signature Z_min:ndarray/1/float, Z_max:ndarray/1/float, rho_lb:ndarray/1/float, rho_ub:ndarray/1/float, L0_reg_ind:ndarray/1/bool, L0_max:int/0/int · returned tuple · level recorded 2026-09-25
log_loss_value riskslim/loss_functions/log_loss.py ran BSD-3-Clause (permissive) · 5b43aab78c4d7aac · report fixture: signature Z:ndarray/2/float, rho:ndarray/1/float · returned float64 · level recorded 2026-09-25
log_loss_value riskslim/loss_functions/log_loss_weighted.py ran BSD-3-Clause (permissive) · 34890f80e9c65f94 · report fixture: signature Z:ndarray/2/float, weights:ndarray/1/float, total_weights:float/0/float, rho:ndarray/1/float · returned float64 · level recorded 2026-09-25
log_loss_value_and_slope riskslim/loss_functions/log_loss.py ran BSD-3-Clause (permissive) · 2f06cc1a465825fa · report fixture: signature Z:ndarray/2/float, rho:ndarray/1/float · returned tuple · level recorded 2026-09-25
log_loss_value_and_slope riskslim/loss_functions/log_loss_weighted.py ran BSD-3-Clause (permissive) · 90585cdae65d8b2d · report fixture: signature Z:ndarray/2/float, weights:ndarray/1/float, total_weights:float/0/float, rho:ndarray/1/float · returned tuple · level recorded 2026-09-25
log_loss_value_from_scores riskslim/loss_functions/log_loss.py ran fingerprinted BSD-3-Clause (permissive) · eaa3f193f86f279b · report fixture: signature scores:ndarray/1/float · returned float64 · level recorded 2026-09-25
log_loss_value_from_scores riskslim/loss_functions/log_loss_weighted.py ran BSD-3-Clause (permissive) · ff70d6112fe96426 · report fixture: signature weights:ndarray/1/float, total_weights:float/0/float, scores:ndarray/1/float · returned float64 · level recorded 2026-09-25
sequential_rounding riskslim/heuristics.py ran BSD-3-Clause (permissive) · 4ae4afee5bbdf03c · report fixture: signature rho:ndarray/1/float, Z:ndarray/2/float, C_0:ndarray/1/float, compute_loss_from_scores_real:callable/0/?, get_L0_penalty:callable/0/?, objval_cutoff:float/0/float · returned tuple · level recorded 2026-09-25
set_cplex_mip_parameters riskslim/mip.py ran BSD-3-Clause (permissive) · 5a8052ed4de8fb58 · report fixture: returned Mock · level recorded 2026-09-25
set_cpx_display_options riskslim/mip.py ran BSD-3-Clause (permissive) · 67f13b56be61d84a · report fixture: returned Mock · level recorded 2026-09-25
setup_objective_functions riskslim/setup_functions.py ran BSD-3-Clause (permissive) · 08def7f24ed6859a · report fixture: signature compute_loss:callable/0/?, L0_reg_ind:ndarray/1/int, C_0_nnz:ndarray/1/float · returned tuple · level recorded 2026-09-25
discrete_descent riskslim/heuristics.py unverified BSD-3-Clause (permissive) · 8b42b46879f2c9d1 · report
round_solution_pool riskslim/initialization.py unverified BSD-3-Clause (permissive) · e21287282a0837b1 · report
setup_loss_functions riskslim/setup_functions.py unverified BSD-3-Clause (permissive) · 99ac5b0cae0ef1ef · report
setup_penalty_parameters riskslim/setup_functions.py unverified BSD-3-Clause (permissive) · 8f27d034da26ad2e · report

Tasks

Seizure prediction

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