TRV-2026-2267Certified recordPeer-reviewed

The Sleep-Wake Classification Performance of Pediatric-Trained Machine Learning Algorithms for Raw Accelerometer Data

Study objectives Actigraphy sleep-wake classification methods increasingly seek to leverage raw acceleration data and machine-learning-based classification, but performance evaluation in pediatrics is limited. We trained machine-learning models using pediatric data and compared their sleep-wake classification performance with existing algorithms for children. Methods Sixty-five children (46% female, ages 5.3-17.7 years) completed in-lab overnight polysomnography and wore a GENEActiv device on their non-dominant…

Health · The Trace — both readings · certified 2026-10-26 · v1 · article view · machine-readable

Current reading — gain

A machine-learning classifier trained on children's data scored sleep and wake more accurately than an adult-trained random forest and GGIR algorithms when checked against lab sleep recordings.

Current reading — problem

The best-performing pediatric classifier still underestimated total sleep duration by an average of 25 minutes per night.

What this doesn’t fix

The evaluation involved only 65 children, one wrist-worn device model and in-lab overnight recordings, so performance in other devices, settings or populations is not shown by the study.

Evidence

  • Peer-reviewedSLEEP2026-10-24
Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2267, v1: “The Sleep-Wake Classification Performance of Pediatric-Trained Machine Learning Algorithms for Raw Accelerometer Data.” Truvace, 2026-10-26. /record/TRV-2026-2267 (accessed at citation time). sha256 0dc51b835d8debd9…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv10dc51b835d8d…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-2267 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.