MétaCan
Menu
Back to cohort
Record W4220879730 · doi:10.1002/qre.3094

Monitoring multivariate coefficient of variation for high‐dimensional processes

2022· article· en· W4220879730 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

VenueQuality and Reliability Engineering International · 2022
Typearticle
Languageen
FieldDecision Sciences
TopicAdvanced Statistical Process Monitoring
Canadian institutionsUniversity of Manitoba
Fundersnot available
KeywordsStatisticsLasso (programming language)Multivariate statisticsControl chartMathematicsCovariance matrixCovarianceStatisticCoefficient of variationComputer scienceProcess (computing)

Abstract

fetched live from OpenAlex

Abstract Multivariate coefficient of variation (MCV) charts are effective tools for monitoring process relative variability. They are developed on the assumption that the process subgroup size available for monitoring the MCV parameter is larger than the number of process characteristics. In such a case, the unbiased estimates of the in‐control mean vector and covariance matrix are used to calculate the chart monitoring statistic. Here, we study the performance of MCV control charts when only a small subgroup size is available for estimating the in‐control mean vector and covariance matrix. We examine the use of a shrinkage estimate of the covariance matrix and propose two one‐sided upward and downward least absolute shrinkage and selection operator (LASSO)‐based MCV charts for detecting upward and downward shifts in the process MCV parameter, respectively. Our simulation study shows that the LASSO‐based MCV charts outperform the classical two one‐sided MCV charts when small subgroup sizes are available for monitoring. The improved performance of the proposed LASSO‐based MCV charts in monitoring shifts in the MCV parameter is demonstrated via an illustrative case study of carbon fiber tube application, where changes are detected earlier than the classical two one‐sided MCV charts.

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.016
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: none
Teacher disagreement score0.590
Threshold uncertainty score0.992

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0030.016
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0000.000
Science and technology studies0.0000.000
Scholarly communication0.0000.000
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.080
GPT teacher head0.407
Teacher spread0.328 · 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