mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of modsem and writeAlizer — release velocity, themes, recent moves, and the top alternatives to consider.
modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.
modsem fits interaction and quadratic effects between latent variables in R, offering both product-indicator approaches (modsem_pi) and distribution-analytic ones (modsem_da, covering LMS and QML). Releases land roughly monthly and are dense pull-request lists. The recent line is dominated by the LMS approach: gradient refactors, parallel E-steps, composite construct support, and careful handling of residual covariances between latent variables.
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.
modsem fits interaction and quadratic effects between latent variables in R, offering both product-indicator approaches (modsem_pi) and distribution-analytic ones (modsem_da, covering LMS and QML). Releases land roughly monthly and are dense pull-request lists. The recent line is dominated by the LMS approach: gradient refactors, parallel E-steps, composite construct support, and careful handling of residual covariances between latent variables.
Two things are being closed at once. The modelling gap — composites and formative constructs, categorical estimators, residual covariances in every direction, multigroup and clustered designs — brings modsem toward what commercial Mplus users expect, and the package's Mplus bridge is maintained alongside it, now with unique file IDs and a cleanup argument. The performance gap is the other: memoised H0, parallel E-step, optimized gradients and Hessians for both LMS and QML, all aimed at the distribution-analytic estimators that are expensive by construction. Convention borrowing from lavaan continues in message formatting and standard-error defaults.
The 1.0.20 and 1.0.21 releases both spent effort on residual covariances between endogenous and exogenous latent variables across estimation, prediction and standardization, and that thread has not obviously closed. The arrival of a second contributor moving MplusAutomation to Suggests suggests dependency trimming continues.
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 modsem 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 modsem 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. modsem 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. modsem 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 modsem alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "modsem alternatives" section above for the current picks, or visit /alternatives/modsem 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.