mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of LightLogR and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
Wearable light-exposure data gets circular time and versioned device formats
LightLogR ingests recordings from wearable light loggers and optical radiation dosimeters, and its release notes are lopsided: four of the six most recent tags are one-line merge stubs while 0.10.0 carries several thousand words. That release is where the package sits — dataset-wide summary tables, a version argument on the importers, and time of day handled as a circular quantity.
Six months of releases and not one of them touched the scoring models
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
LightLogR ingests recordings from wearable light loggers and optical radiation dosimeters, and its release notes are lopsided: four of the six most recent tags are one-line merge stubs while 0.10.0 carries several thousand words. That release is where the package sits — dataset-wide summary tables, a version argument on the importers, and time of day handled as a circular quantity.
The arc runs from reading files off N devices toward modelling the awkward shapes of chronobiology data. Circular conversion lets bedtimes crossing midnight average correctly; remove_partial_data() can demand a minimum duration rather than a fraction of a known total; add_states() takes Interval objects so sleep-scoring output flows straight in. The device side hardens in parallel — supported_versions() exists because a VEET firmware release changed the file format mid-life.
The version switch currently covers VEET and a German-locale Actiwatch Spectrum; more device-format generations behind that same argument are the obvious continuation as manufacturers revise exports. The named milestones (Civil Dawn, then Sunrise) suggest the next substantive release will be another themed one rather than a steady drip.
writeAlizer generates predicted writing-quality scores from features produced by Coh-Metrix, ReaderBench and GAMET, downloading its trained scoring models on demand. Every release in this window — nine of them between September 2025 and February 2026 — is about that download path rather than the scoring: classed error conditions, checksum verification, an offline mode, a mockable artifact directory, and dependency reporting for the model families a user actually invokes.
The package is being made safe to distribute. CRAN's policy on packages that reach the internet drove the first wave — graceful failure, tests that preflight their URLs and skip, examples seeded from a local mock model — and 1.7.0 turned the accumulated fixes into structure with named error classes for each failure mode. Only 1.7.2 adds anything a user would ask for: filename handling for Coh-Metrix and GAMET outputs that arrive as paths.
With the artifact registry hardened and documented, the pressure that produced nine releases in six months should ease, and attention can return to the models themselves — the vignette on scoring-model development added in 1.7.2 hints at that. Nothing here promises new models.
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either LightLogR or writeAlizer.
mice can finally predict, not just estimate, from multiply imputed data.
A market-microstructure toolkit that keeps adding estimators as the papers land.
A vowel-analysis package trimming dependencies after an email address got it archived.
The R half of the EMU speech database system, fixing what was quietly broken.
A Bayesian model-averaging package spending its 2.0 on memory, not methods.
tidyplots keeps rebuilding its own foundations rather than layering around them.
See all LightLogR alternatives → · See all writeAlizer alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. LightLogR and writeAlizer are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LightLogR and writeAlizer are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top LightLogR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "LightLogR alternatives" section above for the current picks, or visit /alternatives/lightlogr for the full list with editorial commentary on each.
Top writeAlizer alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "writeAlizer alternatives" section above for the current picks, or visit /alternatives/writealizer for the full list with editorial commentary on each.