qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of fossilsim and lpjmlkit — release velocity, themes, recent moves, and the top alternatives to consider.
A fossil-record simulator that quietly grew a trait-evolution engine.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
The LPJmL toolkit finally reads NetCDF, closing a gap against the format its field uses.
lpjmlkit is the R toolkit for running the LPJmL dynamic global vegetation model and reading its output. The 1.8.0 release adds direct NetCDF reading, either straight or via .nc.json metafiles, alongside the package's own binary formats. Before that, 1.7.3 sped up read_io(), reworked the LPJmLGridData implementation and added reservoir input support. Releases are infrequent, roughly one every 12 to 18 months.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
The arc runs from sampling mechanics toward simulating what the organisms actually were. Version 2.2.0 taught the package to handle occurrence data for occurrence birth-death models; 2.3.0 then added trait simulation under Mk, BM and OU, which is a different kind of output than fossil ages. Since then the work has been maintenance and keeping the FossilSimShiny GUI in step, suggesting the authors consider the current model set feature-complete.
The pairing of the 2.3.3 release with a FossilSimShiny version bump points to the GUI, not the library, as where the next visible work lands. The entries do not show enough activity to predict a specific new model family.
lpjmlkit is the R toolkit for running the LPJmL dynamic global vegetation model and reading its output. The 1.8.0 release adds direct NetCDF reading, either straight or via .nc.json metafiles, alongside the package's own binary formats. Before that, 1.7.3 sped up read_io(), reworked the LPJmLGridData implementation and added reservoir input support. Releases are infrequent, roughly one every 12 to 18 months.
The work concentrates on the I/O layer rather than the modeling interface, and it is moving toward the formats the wider earth-system community already exchanges. The gap between 1.7.3 and 1.8.0 is over a year, so this is a research-group package released when the science requires it, not on a schedule. The changelog itself is thin — several entries are merge-commit text or CRAN resubmissions.
Further I/O breadth is the likeliest direction now that NetCDF is supported, though the entries give no schedule; the release cadence has not been regular enough to predict timing.
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 fossilsim or lpjmlkit.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all fossilsim alternatives → · See all lpjmlkit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fossilsim and lpjmlkit 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. fossilsim and lpjmlkit 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 fossilsim alternatives in Analytics are ranked by recent ship velocity. Browse the "fossilsim alternatives" section above for the current picks, or visit /alternatives/fossilsim-r for the full list with editorial commentary on each.
Top lpjmlkit alternatives in Analytics are ranked by recent ship velocity. Browse the "lpjmlkit alternatives" section above for the current picks, or visit /alternatives/lpjmlkit-r for the full list with editorial commentary on each.