MétaCan
Menu
Back to cohort
Record W7117357636 · doi:10.1016/j.metip.2025.100225

Group-based trajectory modeling under non-random attrition: A sensitivity analysis and application to frailty trajectories

2025· article· en· W7117357636 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.
aboutThe title or abstract carries a Canadian signal from the geographic lexicon.

Bibliographic record

VenueMethods in Psychology · 2025
Typearticle
Languageen
FieldComputer Science
TopicAnomaly Detection Techniques and Applications
Canadian institutionsUniversity of Manitoba
Fundersnot available
KeywordsAttritionTrajectoryDropout (neural networks)Monte Carlo methodSensitivity (control systems)Constant (computer programming)

Abstract

fetched live from OpenAlex

Group-based trajectory modeling (GBTM) is used to identify trajectories but suffers from attrition bias when dropout is nonrandom. We evaluate an extended GBTM that models attrition as a latent-class process. Monte Carlo simulations compare the extended model with conventional GBTM across trajectory separation and missing-data mechanisms, and test a parsimonious version with a constant dropout rate within classes. conventional GBTM is adequate for separated trajectories but biased when they overlap and attrition is nonrandom. The extended GBTM remains unbiased, as shown in Manitoba frailty data. Implications: modeling attrition improves robustness; the parsimonious extension remains reliable under complex dropout. • Compared extended GBTM with conventional GBTM under simulated non-random attrition. • Conventional GBTM bias emerged when trajectory classes overlapped and attrition was non-random; robust only under well-separated trajectories. • Parsimonious extended GBTM (constant dropout rate within classes) consistently produced unbiased estimates of class proportions and trajectory shapes across all scenarios. • Empirical application to frailty data reclassified 11% of the sample into a high-risk worsening group, illustrating the practical impact of accounting for attrition.

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.001
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Simulation or modeling · Consensus signal: none
GenreCandidate signal: Methods · Consensus signal: Methods
Teacher disagreement score0.884
Threshold uncertainty score0.561

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0010.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0000.000
Bibliometrics0.0010.003
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.044
GPT teacher head0.428
Teacher spread0.384 · 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