paleobuddy
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
A side-by-side editorial comparison of citeme and geodist — release velocity, themes, recent moves, and the top alternatives to consider.
Citation metadata machinery breaks out of INBO's checklist package to stand on its own.
citeme handles citation metadata for research software and organisations — building citation files, validating ORCIDs, RORs, licenses and URLs, and prompting for the pieces interactively. It was extracted from the checklist package in 0.1.0 and has spent the four releases since fleshing out organisational roles, most visibly publishers.
geodist stays dependency-free and fast, and warns you when 'cheap' distances stop being honest.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
citeme handles citation metadata for research software and organisations — building citation files, validating ORCIDs, RORs, licenses and URLs, and prompting for the pieces interactively. It was extracted from the checklist package in 0.1.0 and has spent the four releases since fleshing out organisational roles, most visibly publishers.
Development is running in tight monthly increments along two tracks: modelling who is attached to a piece of research software, and smoothing the interactive prompts that collect it. The publisher role added in 0.1.1 propagated through validation, community detection and YAML handling over the next two releases, which is how this package tends to land a concept — introduce the class field, then follow it everywhere it needs to reach.
Expect the interactive ask_* family to keep growing alongside whatever metadata field is being modelled next, and further alignment with the checklist package it was carved out of.
geodist computes geodesic distances between coordinate pairs in C with no dependencies, offering several measures that trade accuracy for speed — including a 'cheap' approximation used by default. The API is small and largely finished; 0.1.0 added geodist_min() for nearest-match lookups and 0.1.1 is a compiler warning fix.
Development has been about making the speed-accuracy trade visible rather than hiding it. The 0.0.6 release added messages telling users to pick a different measure once the default cheap approximation is applied beyond 100km, where its error stops being negligible. Around that, the work is input handling — tibble support, better lon/lat column matching, vector inputs — and hardening the C code. It is a package that treats being small and correct as the feature.
Expect continued low-frequency maintenance: compiler warnings and geodesic source updates account for three of the last six releases, and the function surface has grown by only two entries in five years.
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 citeme or geodist.
paleobuddy can now simulate trait-dependent diversification, not just birth-death.
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.
protr's feature set is finished; the work now is surviving Bioconductor's churn.
See all citeme alternatives → · See all geodist alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. citeme and geodist 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. citeme and geodist 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 citeme alternatives in Analytics are ranked by recent ship velocity. Browse the "citeme alternatives" section above for the current picks, or visit /alternatives/citeme-r for the full list with editorial commentary on each.
Top geodist alternatives in Analytics are ranked by recent ship velocity. Browse the "geodist alternatives" section above for the current picks, or visit /alternatives/geodist-r for the full list with editorial commentary on each.