tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of geodist and TAF — release velocity, themes, recent moves, and the top alternatives to consider.
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.
TAF keeps turning ICES stock assessments into reproducible, dependency-pinned projects.
TAF is the R tooling behind the ICES Transparent Assessment Framework, which standardizes how fish stock assessments are laid out, sourced and rerun. The 4.3.0 release is the largest in years, adding roughly ten functions covering dependency installation and analysis, software version checks, directory inspection and README drafting. The package has carried zero non-base dependencies since 4.0.0, and the new work is careful not to break that.
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.
TAF is the R tooling behind the ICES Transparent Assessment Framework, which standardizes how fish stock assessments are laid out, sourced and rerun. The 4.3.0 release is the largest in years, adding roughly ten functions covering dependency installation and analysis, software version checks, directory inspection and README drafting. The package has carried zero non-base dependencies since 4.0.0, and the new work is careful not to break that.
The arc runs from analysis runner to project toolkit. Early 3.x releases built out the bootstrap and metadata machinery; 4.0.0 renamed the package and stripped every external dependency; 4.2.0 cleaned up vocabulary that confused users. 4.3.0 turns outward to the people running assessments — install.deps(), pdeps() and check.software() address reproducing someone else's environment, while draft.readme(), taf.example() and dir.tree() address understanding an unfamiliar project.
Expect the follow-up work to harden the new dependency functions rather than add more surface, since 4.3.1 arrived immediately to fix wide2long() compatibility with older R and that batch of ten functions has had little field exposure.
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 geodist or TAF.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — zero-dependency — within Analytics. geodist and TAF 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. geodist and TAF 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 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.
Top TAF alternatives in Analytics are ranked by recent ship velocity. Browse the "TAF alternatives" section above for the current picks, or visit /alternatives/taf-r for the full list with editorial commentary on each.