MétaCan
Menu
Back to cohort
Record W1971729061 · doi:10.4236/ajor.2014.44026

Using DEA and AHP for Ratio Analysis

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

VenueAmerican Journal of Operations Research · 2014
Typearticle
Languageen
FieldDecision Sciences
TopicEfficiency Analysis Using DEA
Canadian institutionsLaurentian University
Fundersnot available
KeywordsData envelopment analysisAnalytic hierarchy processRanking (information retrieval)Set (abstract data type)Measure (data warehouse)Computer scienceParametric statisticsRange (aeronautics)ClosenessEfficiencyMathematicsOperations researchMathematical optimizationStatisticsData miningEngineeringArtificial intelligence

Abstract

fetched live from OpenAlex

This research proposes an integrated approach to the Data Envelopment Analysis (DEA) and Analytic Hierarchy Process (AHP) methodologies for ratio analysis. According to this, we compute two sets of weights of ratios in the DEA framework. All ratios are treated as outputs without explicit inputs. The first set of weights represents the most attainable efficiency level for each Decision Making Unit (DMU) in comparison to the other DMUs. The second set of weights represents the relative priority of output-ratios using AHP. We assess the performance of each DMU in terms of the relative closeness to the priority weights of output-ratios. For this purpose, we develop a parametric goal programming model to measure the deviations between the two sets of weights. Increasing the value of a parameter in a defined range of efficiency loss, we explore how much the deviations can be improved to achieve the desired goals of the decision maker.This may result in various ranking positions for each DMU in comparison to the other DMUs. An illustrated example of eight listed companies in the steel industry of China is used to highlight the usefulness of the proposed approach.

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.018
metaresearch head score (Gemma)0.012
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: Empirical · Consensus signal: Empirical
Teacher disagreement score0.416
Threshold uncertainty score0.997

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0180.012
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0030.006
Science and technology studies0.0010.001
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.323
GPT teacher head0.564
Teacher spread0.241 · 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