datefixR
The messy-date parser rewrote its core in Rust and came out 300x faster.
A side-by-side editorial comparison of serofoi and sftime — release velocity, themes, recent moves, and the top alternatives to consider.
serofoi grew a serosurvey simulator alongside the force-of-infection models it was built to fit.
serofoi estimates the force of infection from serological survey data using Bayesian serocatalytic models fitted through Stan. Beyond fitting it now simulates serosurveys — specifying a model and a survey design and generating the data such a survey would produce. The most recent release is visualisation and naming work.
The spatiotemporal companion to sf, moving at the pace of the packages around it.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
serofoi estimates the force of infection from serological survey data using Bayesian serocatalytic models fitted through Stan. Beyond fitting it now simulates serosurveys — specifying a model and a survey design and generating the data such a survey would produce. The most recent release is visualisation and naming work.
The package moved from fitting-only to a fit-and-simulate pair. 0.1.0 added simulation from time- or age-varying force-of-infection trends and simplified the fitted object down to a Stan fit; 1.0.2 broadened simulation into full serosurvey generation with its own vignette. 1.0.3 then spent its effort on naming consistency and plotting options, which is what a package does once its scope is set.
With simulation and fitting both in place, the natural next step is tooling that closes the loop between them — recovery checks or study-design guidance built on simulated surveys.
sftime extends sf with an active time column, giving R a data frame class for data that is both spatial and temporal. Its recent history is almost entirely integration work: 0.3.0 added conversion methods from spatstat point patterns, sftrack and sftraj movement objects and cubble data frames, plus dedicated tidyr::drop_na() and dplyr::dplyr_reconstruct() methods. The two releases since are a namespace version-check correction and a switch from the magrittr pipe to the native pipe in examples.
The package's job is to be interoperable, so its releases follow whatever the surrounding spatial and tidyverse packages do. The dplyr_reconstruct() work is the clearest example of why that matters: inheriting sf's method caused column binding to silently return an sf object where an sftime object was expected, which is the kind of class-preservation bug that only surfaces two steps downstream. Development is sparse, roughly one release a year.
Expect further conversion methods as new spatiotemporal classes appear in the R spatial ecosystem, and continued tracking of dplyr and tidyr generics. The entries do not indicate any planned change to the sftime class itself.
Other Analytics 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 serofoi or sftime.
The messy-date parser rewrote its core in Rust and came out 300x faster.
The legend engine mapsf spun out, now covering legend types the parent map package can draw.
R help pages translated on demand by whichever LLM you point it at.
Thematic mapping in base R that finally got a theming system, then spent two years polishing legends.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
The tidyverts forecasting core rebuilt model combination on full residual covariance.
See all serofoi alternatives → · See all sftime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. serofoi and sftime 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. serofoi and sftime 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 Analytics products to evaluate alongside.
Top serofoi alternatives in Analytics are ranked by recent ship velocity. Browse the "serofoi alternatives" section above for the current picks, or visit /alternatives/serofoi for the full list with editorial commentary on each.
Top sftime alternatives in Analytics are ranked by recent ship velocity. Browse the "sftime alternatives" section above for the current picks, or visit /alternatives/sftime for the full list with editorial commentary on each.