MétaCan
Menu
Back to cohort
Record W1991303080 · doi:10.1142/s0217595914500420

A Variant of L<sup>♮</sup>-Convexity and its Application to Inventory Models with Batch Ordering

2014· article· en· W1991303080 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

VenueAsia Pacific Journal of Operational Research · 2014
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicSupply Chain and Inventory Management
Canadian institutionsUniversity of Toronto
FundersNational Natural Science Foundation of China
KeywordsConvexityInventory controlComputer scienceMathematical optimizationPerpetual inventoryInventory theoryOperations researchSensitivity (control systems)Mathematical economicsEconomicsMathematicsFinancial economicsEngineering

Abstract

fetched live from OpenAlex

Previous studies show that the concept of L ♮ -convexity is helpful in characterizing the optimal policy for some inventory models with positive leadtimes. Such examples include the lost-sales inventory model by Zipkin (2008). On the structure of lost-sales inventory models. Operations Research, 56(4) 937–944. and the inventory-pricing model by Pang et al. (2012). A note on the structure of joint inventory-pricing control with leadtimes. Operations Research, 60(3), 581–587. However, when taking batch ordering into account, L ♮ -convexity does not work anymore. In this paper, we extend L ♮ -convexity to a more general concept termed as Q-jump-L ♮ -convexity and apply it to batch ordering inventory models including a lost-sales inventory model and an inventory-pricing model with batch ordering and positive leadtimes. By utilizing this new concept, we can partially characterize the structure of the optimal policies for both the models. Moreover, we are able to evaluate the sensitivity of the optimal decisions with respect to system states. Our results can also be applied to the serial and the assembly inventory systems with lost-sales and batch ordering.

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.003
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.866
Threshold uncertainty score0.384

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.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.053
GPT teacher head0.291
Teacher spread0.237 · 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