MétaCan
Menu
Back to cohort
Record W3104895535 · doi:10.1002/nav.21528

Partial input to output impacts in DEA: Production considerations and resource sharing among business subunits

2013· article· en· W3104895535 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

VenueNaval Research Logistics (NRL) · 2013
Typearticle
Languageen
FieldDecision Sciences
TopicEfficiency Analysis Using DEA
Canadian institutionsYork University
Fundersnot available
KeywordsData envelopment analysisComputer scienceSet (abstract data type)Production (economics)Variable (mathematics)Operations researchResource (disambiguation)Mathematical optimizationEconomicsMathematicsMicroeconomics

Abstract

fetched live from OpenAlex

Abstract Data envelopment analysis (DEA) is a methodology for evaluating the relative efficiencies of peer decision‐making units (DMUs), in a multiple input/output setting. Although it is generally assumed that all outputs are impacted by all inputs, there are many situations where this may not be the case. This article extends the conventional DEA methodology to allow for the measurement of technical efficiency in situations where only partial input‐to‐output impacts exist. The new methodology involves viewing the DMU as a business unit, consisting of a set of mutually exclusive subunits, each of which can be treated in the conventional DEA sense. A further consideration involves the imposition of constraints in the form of assurance regions (AR) on pairs of multipliers. These AR constraints often arise at the level of the subunit, and as a result, there can be multiple and often inconsistent AR constraints on any given variable pair. We present a methodology for resolving such inconsistencies. To demonstrate the overall methodology, we apply it to the problem of evaluating the efficiencies of a set of steel fabrication plants. © 2013 Wiley Periodicals, Inc. Naval Research Logistics, 2013

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.013
metaresearch head score (Gemma)0.196
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Scholarly communication
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.183
Threshold uncertainty score0.999

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0130.196
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.005
Science and technology studies0.0010.001
Scholarly communication0.0020.001
Open science0.0010.001
Research integrity0.0000.001
Insufficient payload (model declined to judge)0.0000.001

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.329
GPT teacher head0.464
Teacher spread0.135 · 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