vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
Comparison · Infra & APIs
JointFPM vs multimark
A side-by-side editorial comparison of JointFPM and multimark — release velocity, themes, recent moves, and the top alternatives to consider.
JointFPM vs multimark: at a glance
What is JointFPM?
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.
What is multimark?
Five years of compiler and CRAN fixes on a capture-recapture package.
multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.
JointFPM vs multimark: editorial side-by-side
JointFPM
0.0INFRA · APIS
Recurrent-event modelling settles, with mean_no() promoted to stable.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.
multimark
0.0INFRA · APIS
Five years of compiler and CRAN fixes on a capture-recapture package.
◆ Current state
multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.
◆ Where it's heading
This is preservation rather than development. The one substantive entry, in 2021, corrected an MCMC error in multimarkClosedSCR() serious enough that the author told users to revisit past analyses; everything since has been keeping the C code compiling across platforms. Release intervals now stretch to years.
◆ Prediction
Expect the pattern to hold, with a release whenever a toolchain or upstream dependency forces one and no change to the samplers.
Alternatives to JointFPM and multimark
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 multimark.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
ordinalsimr
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
transltr
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
hereR
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all JointFPM alternatives → · See all multimark alternatives →
Recent activity from JointFPM and multimark
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agomultimarkBrobdingnag sum import dropped after upstream removal
- 1y agoJointFPMmean_no() promoted to a stable interface
- 2y agoJointFPMsummary() method and control arguments passed to rstpm2
- 2y agoJointFPMGaussian quadrature option for the mean-events integration
- 2y agoJointFPMStandardized marginal estimates plus input validation
- 2y agoJointFPMBug fixes for differences between mean-event functions
- 3y agomultimarkr-devel error fixed at CRAN's request
- 3y agomultimarkLinux compilation warnings cleared
- 4y agomultimarkFedora build error fixed at CRAN's request
- 4y agomultimarkMCMC detection-probability bug fixed in multimarkClosedSCR()
- 4y agomultimarkUnused parallelism dependencies removed
Frequently asked questions
What is the difference between JointFPM and multimark?
They serve adjacent needs but don't currently overlap on shipped themes. JointFPM and multimark 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 JointFPM better than multimark?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. JointFPM and multimark 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 JointFPM?
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.
What are the best alternatives to multimark?
Top multimark alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "multimark alternatives" section above for the current picks, or visit /alternatives/multimark for the full list with editorial commentary on each.