pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of JointFPM and remap — release velocity, themes, recent moves, and the top alternatives to consider.
Recurrent-event modelling settles, with mean_no() promoted to stable.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
A regional-model smoother in long-term maintenance, four years past its last real feature.
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.
The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.
With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.
remap fits separate models to geographic regions and blends their predictions into a continuous surface, using the min_n nearest observations so region boundaries do not show as discontinuities. The methodological work is finished — the last behavioural change landed in 2022, and everything since has been unit handling, compiler warnings, dependency compatibility and citation updates. The July release is one such patch.
This is a stable academic package tracking its ecosystem rather than growing. The visible pattern is reactive maintenance: sf's 1.0.0 transition, ggplot2's size-to-linewidth rename, a gcc-UBSAN error on zero-point distance calculations, and now a check that distance matrices passed to remap() and predict() are converted to kilometres. Note that the feed's timestamps invert the version order — 0.3.1 is stamped seconds after 0.3.2 despite being the earlier release, so recency in this feed is not a reliable guide to sequence.
Nothing in these entries points to new capability. The realistic expectation is more of the same: a patch whenever sf, ggplot2 or a CRAN check surfaces an incompatibility, at roughly the observed cadence of one release every year or two.
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 JointFPM or remap.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all JointFPM alternatives → · See all remap alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. JointFPM and remap 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. JointFPM and remap 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 JointFPM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "JointFPM alternatives" section above for the current picks, or visit /alternatives/jointfpm for the full list with editorial commentary on each.
Top remap alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "remap alternatives" section above for the current picks, or visit /alternatives/remap for the full list with editorial commentary on each.