TRV-2026-2242Version 1 · Certified
Reason for this version
Certified into the record
Canonical text (the exact bytes fingerprinted)
TRUVACE RECORD VERSION record: TRV-2026-2242 version: 1 kind: certified reason: Certified into the record timestamp: 2026-10-24T18:34:41.286047Z status: published lens: g_space sector: science headline: Comparative evaluation of machine learning algorithms for Maize Lethal Necrosis Disease detection under class imbalance dek: Maize Lethal Necrosis Disease (MLND) remains a major threat to maize production in sub-Saharan Africa, creating a need for accurate, interpretable, and computationally efficient diagnostic tools. This study presents a comprehensive comparative evaluation of nine machine learning algorithms for MLND detection using a structured feature-based dataset comprising 7,892 maize leaf observations obtained from the Kenya Agricultural and Livestock Research Organization (KALRO). The extracted features captured color, text… gain_title: Structured leaf-feature models can detect maize lethal necrosis with consistent, interpretable and computationally light performance, with LightGBM offering the best balance for low-resource settings. problem_title: (none) trace_subject: (none) gain_reading: Structured leaf-feature models can detect maize lethal necrosis with consistent, interpretable and computationally light performance, with LightGBM offering the best balance for low-resource settings. gain_evidence: LightGBM provided the most favorable balance for resource-constrained environments problem_reading: (none) problem_evidence: (none) quick_read: Researchers compared nine machine learning algorithms for identifying Maize Lethal Necrosis Disease using 7,892 leaf observations from the Kenya Agricultural and Livestock Research Organization. Inputs were extracted color, texture, lesion and morphological features, and the pipeline used SMOTE and class weighting to handle moderate class imbalance. The work matters because the disease threatens maize production in sub-Saharan Africa and the region needs diagnostic tools that are accurate, interpretable and cheap to run. The results are still preliminary: the best models were broadly comparable and misclassification remained notable, so field-ready use depends on external validation. limitation: The achieved performance means about one in four samples may be misclassified, and the models need further external validation before operational deployment. tag: Evidence-backed gain key_points: CatBoost had the highest mean accuracy at 0.753, while Logistic Regression had the highest mean AUC at 0.808. | Overlapping confidence intervals among the best models suggest broadly comparable performance, so criteria beyond accuracy matter. | Explainable AI identified Chlorosis Intensity, Green-Yellow Ratio and Necrotic Area as the most influential predictors. | Post-hoc probability calibration substantially improved the reliability of predicted probabilities, as measured by Expected Calibration Error. rundown: The evaluation used repeated stratified 5-fold cross-validation, an independent 80/20 test set and leave-one-county-out cross-validation to test geographic generalisability. An ablation study quantified how much SMOTE and class weighting contributed. Beyond predictive scores, the authors weighed computational efficiency, model size and inference latency. LightGBM was judged the most favorable balance for resource-constrained environments, while Logistic Regression was an interpretable option with minimal computational needs. The authors frame the results as a foundation for future field-based decision-support systems rather than a deployed tool, noting that external validation is still required. sources: - peer_reviewed | PLOS One | https://doi.org/10.1371/journal.pone.0349738 | 2026-10-23 prev: 0000000000000000000000000000000000000000000000000000000000000000
- sha256
- 09e938b7a353f9eb413e5a0a73324fcb3ba287d5d5a0e01013b58867354047b0
- previous
- 0000000000000000000000000000000000000000000000000000000000000000
Verify this record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-2242 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace