rollupTree
The recursive-computation engine under massProps grows the accessors its consumer needed
A side-by-side editorial comparison of campsismod and PEIMAN2 — release velocity, themes, recent moves, and the top alternatives to consider.
The model layer under Campsis, renamed in step with it and increasingly JSON-addressable.
Campsismod holds the model object layer for the Campsis pharmacometric simulation suite: reading, editing and writing model definitions that Campsis then simulates. Its recent releases track a single programme, adding a JSON route into model objects and then renaming the whole API to snake_case in 1.4.0, a week before Campsis 1.9.0 did the same. Release notes are terse issue lists, so the reasoning behind each change has to be read from the sibling package.
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.
Campsismod holds the model object layer for the Campsis pharmacometric simulation suite: reading, editing and writing model definitions that Campsis then simulates. Its recent releases track a single programme, adding a JSON route into model objects and then renaming the whole API to snake_case in 1.4.0, a week before Campsis 1.9.0 did the same. Release notes are terse issue lists, so the reasoning behind each change has to be read from the sibling package.
This package moves when Campsis needs it to move. The JSON constructor landed here in 1.3.0 and reached Campsis datasets a day later; parameter uncertainty generation was handed down from Campsis in that package's 1.6.0; and the snake_case migration started here before propagating up. That ordering makes Campsismod the place where suite-wide interface decisions are taken first, even though the visible payoff shows up in Campsis.
Expect Campsismod to keep absorbing model-level responsibilities that Campsis currently handles, and to extend the JSON mapping to whatever parts of the model object it does not yet cover. The entries give no signal on a 2.0, and with the rename already spent there is little reason to expect one soon.
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 campsismod or PEIMAN2.
The recursive-computation engine under massProps grows the accessors its consumer needed
A mass-properties rollup spends a year on documentation and follows its sibling's API
Six months of releases and not one of them touched the scoring models
A cognitive-science sampling package ships once, then goes quiet for eighteen months
A Bayesian volatility sampler in its maintenance decade, paying for its own speed
A black-box interpreter reaches CRAN, then learns multi-class and survival responses
See all campsismod alternatives → · See all PEIMAN2 alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. campsismod is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. campsismod is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
Top campsismod alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "campsismod alternatives" section above for the current picks, or visit /alternatives/campsismod 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.