Identification of injured elements in computational models of spinal cord injury using machine learning <sup>*</sup>
Bibliographic record
Abstract
The purpose of this study was to use machine learning (ML) algorithms to identify tissue damage based on the mechanical outputs of computational models of spinal cord injury (SCI). Three datasets corresponding to gray matter, white matter, and the combination of gray and white matter tissues were used to train the models. These datasets were built from the comparison of histological images taken from SCI experiments in non-human primates and corresponding subject-specific finite element (FE) models. Four ML algorithms were evaluated and compared using cross-validation and the area under the receiver operating characteristic curve (AUC). After hyperparameter tuning, the AUC mean values for the algorithms ranged between 0.79 and 0.82, with a standard deviation no greater than 0.02. The findings of this study also showed that k-nearest neighbors and logistic regression algorithms were better at identifying injured elements than support vector machines and decision trees. Additionally, depending on the evaluated dataset, the mean values of other performance metrics, such as precision and recall, varied between algorithms. These initial results suggest that different algorithms might be more sensitive to the skewed distribution of classes in the studied datasets, and that identifying damage independently or simultaneously in the gray and white matter tissues might require a better definition of relevant features and the use of different ML algorithms. These approaches will contribute to improving the current understanding of the relationship between mechanical loading and tissue damage during SCI and will have implications for the development of prevention strategies for this condition.Clinical Relevance- Linking FE model predictions of mechanical loading to tissue damage is an essential step for FE models to provide clinically relevant information. Combined with imaging technologies, these models can provide useful insights to predict the extent of damage in animal subjects and guide the decision-making process during treatment planning.
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.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.001 | 0.006 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.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.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".