paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of lpjmlkit and parallelDist — release velocity, themes, recent moves, and the top alternatives to consider.
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.
parallelDist is in pure preservation mode — one build fix every few years.
parallelDist computes distance matrices across threads in C++ via RcppParallel and Armadillo. The feature set has been settled since 0.2.3 in 2018, which added hamming distance and cosine similarity; everything after that is compatibility work. The most recent release, 0.2.7, exists only to drop a C++11 pin that newer Armadillo versions no longer tolerate.
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.
parallelDist computes distance matrices across threads in C++ via RcppParallel and Armadillo. The feature set has been settled since 0.2.3 in 2018, which added hamming distance and cosine similarity; everything after that is compatibility work. The most recent release, 0.2.7, exists only to drop a C++11 pin that newer Armadillo versions no longer tolerate.
The package is being kept installable, not developed. The three most recent releases are a toolchain pin removal, a DESCRIPTION field removal, and a coercion change inherited from proxy — none originate from user-facing intent. Gaps of three to four years between releases are the norm now, and each one is triggered by something upstream breaking rather than by a roadmap.
The next release will almost certainly be another compatibility fix timed to whatever Armadillo, Rcpp or CRAN check policy changes next. Nothing in the entries points to new distance measures or API work.
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 lpjmlkit or parallelDist.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
errors keeps making uncertainty print the way each scientific field expects.
CMAQ went global in v5.5, and has been patching that surface ever since.
enpls has not changed its statistics since 2016 — only its website, twice.
grex is a lookup table with a version number — it ships when the annotation moves.
See all lpjmlkit alternatives → · See all parallelDist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lpjmlkit and parallelDist 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. lpjmlkit and parallelDist 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 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.
Top parallelDist alternatives in Analytics are ranked by recent ship velocity. Browse the "parallelDist alternatives" section above for the current picks, or visit /alternatives/paralleldist for the full list with editorial commentary on each.