pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of JointFPM and Rmonize — 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.
Collapsed a pile of parameters into one object and renamed every report column
Rmonize supports data harmonization: taking heterogeneous input datasets, applying processing rules against a DataSchema, and producing a harmonized dossier with assessment, summary and visual reports. Version 2.0.0 reshaped how that is driven — the evaluate, summarize and visualize functions now take the dossier alone rather than six or seven parallel arguments — and renamed every column in the assessment and summary outputs into plain language. The package is closely coupled to madshapR, whose changes the notes warn may require updates to existing user code.
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.
Rmonize supports data harmonization: taking heterogeneous input datasets, applying processing rules against a DataSchema, and producing a harmonized dossier with assessment, summary and visual reports. Version 2.0.0 reshaped how that is driven — the evaluate, summarize and visualize functions now take the dossier alone rather than six or seven parallel arguments — and renamed every column in the assessment and summary outputs into plain language. The package is closely coupled to madshapR, whose changes the notes warn may require updates to existing user code.
The arc runs from correctness toward interface. Version 1.0.1 was bug fixes found on real data, 1.1.0 added a debug parameter so harmonization could be tested with incomplete inputs, and 2.0.0 is a deliberate simplification that breaks existing code in exchange for a smaller surface. Renaming outputs from expressions like 'Categories::missing' and 'Nb. non-valid values' to 'Non-valid categories' and 'Number of non-valid values' points at reports being read by people who are not the person who wrote the harmonization rules.
Expect the superseded parameters and the renamed demo object to be removed outright rather than left superseded, and continued work on the visual reports, which carry the largest volume of referenced issues across all three versions.
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 Rmonize.
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 Rmonize 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 Rmonize 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 Rmonize 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 Rmonize alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Rmonize alternatives" section above for the current picks, or visit /alternatives/rmonize for the full list with editorial commentary on each.