mice
mice can finally predict, not just estimate, from multiply imputed data.
A side-by-side editorial comparison of formr and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
formr's R client reached CRAN and moved its recommended path to the v1 REST API.
formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.
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.
formr is the R-side client for formr.org, the open study framework used to run longitudinal and experience-sampling questionnaires. In May it reached CRAN for the first time, released in step with formr.org server v1.0.0, and the formr_api_* family built on the server's RESTful surface became the supported entry point. The three releases since have been repair work on the paths that move rendered output and API results.
The direction is consolidation around the v1 API while the legacy Classic path is left running but demoted in the vignette. The complication is that CRAN's requirements and the OpenCPU server's requirements pull against each other: CRAN review pushed rendering into tempdir() with random filenames, which broke rforms.org because the server fetches a fixed knit.html, and 1.1.2 had to put it back. The 1.2.0 note describes the same write-directory problem being solved in an OpenCPU-aware way rather than reverted, alongside making dependencies installable under WASM.
Two of the last three releases were regressions in the render path, so the OpenCPU-aware write directory in 1.2.0 is the change most likely to need follow-up. The Classic formr_results() path remains in the package with no removal date announced, and nothing in these entries indicates when that ends.
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.
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.
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.
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 formr or PEIMAN2.
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 formr alternatives → · See all PEIMAN2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-packages — within Infra & APIs. formr 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. formr 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.
Top formr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "formr alternatives" section above for the current picks, or visit /alternatives/formr for the full list with editorial commentary on each.
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.