MétaCan
Menu
Back to cohort
Record W3036346356 · doi:10.1287/moor.2019.1043

On the Scenario-Tree Optimal-Value Error for Stochastic Programming Problems

2020· article· en· W3036346356 on OpenAlex

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

affAt least one author lists a Canadian institution in the pinned OpenAlex snapshot.

Bibliographic record

VenueMathematics of Operations Research · 2020
Typearticle
Languageen
FieldDecision Sciences
TopicRisk and Portfolio Optimization
Canadian institutionsPolytechnique Montréal
Fundersnot available
KeywordsMathematical optimizationTree (set theory)MathematicsStochastic programmingDiscretizationNode (physics)Bellman equationDynamic programmingComputer scienceExpected value

Abstract

fetched live from OpenAlex

Stochastic programming problems generally lead to large-scale programs if the number of random outcomes is large or if the problem has many stages. A way to tackle them is provided by scenario-tree generation methods, which construct approximate problems from a reduced subset of outcomes. However, it is well known that the number of scenarios required to keep the approximation error within a given tolerance grows rapidly with the number of random parameters and stages. For this reason, to limit the fast growth of complexity, scenario-tree generation methods tailored to problems must be developed. These will use more information about the problem than just the underlying probability distributions; namely, they will also take into account the objective function and the constraints. In this paper, we develop a general framework to build problem-driven scenario trees. We do so by studying how the optimal-value error arises as a sum of lower-level errors made at each node of the tree. We show how these small but numerous node errors depend on the specific features of the problem and how they can be controlled by designing scenario trees with appropriate branching structures and discretization points and weights. We illustrate our approach on two examples.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.006
metaresearch head score (Gemma)0.018
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: Simulation or modeling
GenreCandidate signal: Methods · Consensus signal: none
Teacher disagreement score0.781
Threshold uncertainty score0.990

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0060.018
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.001
Science and technology studies0.0010.000
Scholarly communication0.0010.000
Open science0.0010.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.407
GPT teacher head0.486
Teacher spread0.080 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it