rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
Comparison · Infra & APIs
modsem vs PEIMAN2
A side-by-side editorial comparison of modsem and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-packages
modsem vs PEIMAN2: at a glance
| Feature | modsem | PEIMAN2 |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 0.0 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | structural-equation-modeling, latent-interactions, lms-estimator, mplus-interop | proteomics, post-translational-modification, enrichment-analysis, reproducibility |
| Last editorial update | 1h ago | 1h ago |
| Website | Visit → | Visit → |
What is modsem?
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.
What is PEIMAN2?
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
modsem vs PEIMAN2: editorial side-by-side
modsem
0.0INFRA · APIS
modsem is grinding latent interaction models toward Mplus parity, one estimator at a time.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
PEIMAN2
0.0INFRA · APIS
PEIMAN2 cut its annotation database loose from its release cycle without breaking CRAN.
◆ Current state
PEIMAN2 does enrichment analysis over post-translational modifications, testing whether a protein list is enriched for particular PTMs against UniProt-derived annotations, with translation functions bridging to mass spectrometry workflows. Its answers are only as current as its bundled database, and until June that database could only be refreshed by releasing a new package version. Version 1.1.0 changes that.
◆ Where it's heading
The package has been moving from a fixed snapshot toward versioned, user-selectable data. Earlier releases updated the bundled database in place — 1.0.0 shipped the March 2025 version and said little else — which meant the annotation vintage was whatever the package version implied. Now update_peiman_database() downloads and caches external database files and UniProt PTM lists, enrichment workflows take a database_version argument, and the mass-spec translators take a ptmlist_version, so an analysis can pin a dated database rather than a package release. The CRAN-safe default is preserved deliberately: loading, examples and checks still use the bundled internal data and need no network.
◆ Prediction
Version pinning is now expressible but the release notes do not describe how a chosen version is recorded in output, so surfacing the active database version in results is the natural companion. The database and the UniProt PTM list are versioned separately, which leaves room for a combined manifest.
Alternatives to modsem and PEIMAN2
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 PEIMAN2.
massProps
A mass-properties rollup spends a year on documentation and follows its sibling's API
writeAlizer
Six months of releases and not one of them touched the scoring models
samplr
A cognitive-science sampling package ships once, then goes quiet for eighteen months
stochvol
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
midr
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all modsem alternatives → · See all PEIMAN2 alternatives →
Recent activity from modsem and PEIMAN2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1mo agomodsemUnique Mplus file IDs, cleanup argument, LMS gradient refactor
- 2mo agoPEIMAN2Database updates decouple from package releases ⚡
- 2mo agomodsemComposite constructs for LMS, plus MC-LMS-CAT and MC-QML-CAT
- 3mo agomodsemPrint spacing and a partial-match fix in getSortedEtas()
- 4mo agomodsemCategorical argument for Mplus; partial support for the <~ operator
- 5mo agomodsemConsistent three-way interaction estimates with rcs=TRUE
- 6mo agomodsemSecondary pruning and a forward-difference Hessian mode
- 1y agoPEIMAN2Bundled database refreshed to the March 2025 UniProt vintage
- 1y agoPEIMAN2Documentation fix for the second example dataset
- 2y agoPEIMAN2Background lists for SEA and PSEA; tidyverse dependency dropped
Frequently asked questions
What is the difference between modsem and PEIMAN2?
Both compete on the same themes — r-packages — within Infra & APIs. modsem and PEIMAN2 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.
Is modsem better than PEIMAN2?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. modsem and PEIMAN2 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.
What are the best alternatives to modsem?
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.
What are the best alternatives to PEIMAN2?
Top PEIMAN2 alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "PEIMAN2 alternatives" section above for the current picks, or visit /alternatives/peiman2 for the full list with editorial commentary on each.