MétaCan
Menu
Back to cohort
Record W2021035803 · doi:10.1287/opre.1110.0937

Multiple Variable Proportionality in Data Envelopment Analysis

2011· article· en· W2021035803 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

VenueOperations Research · 2011
Typearticle
Languageen
FieldDecision Sciences
TopicEfficiency Analysis Using DEA
Canadian institutionsYork University
Fundersnot available
KeywordsData envelopment analysisProportionality (law)BundleReturns to scaleVariable (mathematics)EnvelopmentComputer scienceEconometricsSet (abstract data type)Operations researchMathematicsMathematical optimizationEconomicsMicroeconomics

Abstract

fetched live from OpenAlex

Data envelopment analysis (DEA) provides an optimization methodology for deriving an efficiency score for each member of a set of peer decision-making units. Under the original DEA model it was assumed that there is constant returns to scale (CRS). This idea was later extended to the more general case that allowed for variable returns to scale (VRS). In both of these structures, it is assumed that the returns to scale (RTS) classification, consistent with the classical definition, applies to the entire (input, output) bundle. In many settings it can be the case that the output bundle can be separated into distinct subsets or business units wherein an RTS-type behavior may be different for one subgroup than for another. We refer to such situations as involving multiple variable proportionality (MVP). Examples of MVP can occur when there are different product subgroupings in a company, different wards in hospitals, different programs in a university, and so on. Identification of such differential behavior can provide management with important insights regarding the most productive proportionality size (MPPS) in each of those subgroups. In the current paper we introduce DEA-based tools that address those situations where MVP exists.

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.030
metaresearch head score (Gemma)0.014
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesMetaresearch, Insufficient payload (model declined to judge)
Consensus categoriesMetaresearch, Insufficient payload (model declined to judge)
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.660
Threshold uncertainty score1.000

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0300.014
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0020.014
Science and technology studies0.0010.000
Scholarly communication0.0000.001
Open science0.0020.001
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0050.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.679
GPT teacher head0.548
Teacher spread0.130 · 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