MétaCan
Menu
Back to cohort
Record W2791685957 · doi:10.30577/jba.2018.v1n1.2

A Comparison of Various Data Reduction Procedures in a Multiple Sclerosis Sleep Study

2018· article· en· W2791685957 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.
fundA Canadian funder is recorded on the work.

Bibliographic record

VenueJournal of Biomedical Analytics · 2018
Typearticle
Languageen
FieldMedicine
TopicMultiple Sclerosis Research Studies
Canadian institutionsMcGill University Health CentreMontreal Neurological Institute and HospitalMcGill University
FundersMultiple Sclerosis SocietyMultiple Sclerosis Society of Canada
KeywordsMulticollinearityInterpretabilitySleep (system call)PolysomnographySleep qualityPittsburgh Sleep Quality IndexStatisticsQuality (philosophy)Computer scienceMedicineRegression analysisPsychologyInsomniaArtificial intelligenceMathematicsPsychiatry

Abstract

fetched live from OpenAlex

Clinical studies often deal with datasets with numerous variables. As a result of the similarities between the variables, we frequently observe the presence of multicollinearity in the data. This study aimed to apply different data reduction strategies to sleep study variables in multiple sclerosis (MS) patients. The main objective was to use various data reduction strategies to explain a subjective measure of sleep quality (Pittsburgh Sleep Quality Index: PSQI) by the objective measures of sleep quality obtained during complete in-laboratory overnight polysomnography. Overall, we found that few objective measures of sleep quality were important in explaining the subjective PSQI, based on the results of various well-accepted statistical methods. Total sleep time was found to be the most important feature of objective sleep quality for explaining subjective sleep quality among all other investigated objective sleep quality variables in most of the approaches investigated in this study. The LASSO method for estimation worked best in terms of interpretability among all the approaches considered.

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.002
metaresearch head score (Gemma)0.005
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Observational · Consensus signal: Observational
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.064
Threshold uncertainty score0.656

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.005
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.001
Scholarly communication0.0000.000
Open science0.0000.000
Research integrity0.0000.001
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.234
GPT teacher head0.423
Teacher spread0.189 · 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