pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
A side-by-side editorial comparison of gofedf and trackeR — release velocity, themes, recent moves, and the top alternatives to consider.
A two-test goodness-of-fit package opens itself up to any weight function
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.
gofedf runs goodness-of-fit tests built on the empirical distribution function. Its three releases trace a short, clean arc: existence in 2023, then p-values computed from an analytical solution of the integral equation in 2024, then in 2026 a user-supplied weight function that replaces the fixed menu. Cramer-von Mises and Anderson-Darling are now two points in a family rather than the two options.
The package is generalising rather than accumulating. Each release removed a hard-coded decision: first how eigenvalues are computed, offering both the analytical route and a matrix approximation; then which weight function defines the statistic at all. The maintainer's own framing in 1.1.0 is a contrast against what earlier versions would not let you do, which is the shape of a package aiming to become a framework.
An arbitrary weight function is the extensibility point that matters for EDF tests; what it lacks is calibration guidance, since Type I error behaviour was the argued benefit of the analytical eigenvalue route. Documented recommendations or diagnostics for user-chosen weights are the natural follow-up, though the entries do not announce one.
trackeR reads GPS and fitness-tracker files in TCX, GPX and JSON form and turns them into session data, distribution and concentration profiles, and route plots. Feature work concentrated in the 1.5 series in 2019; the two releases since are corrective. The latest swaps the plot layout dependencies for patchwork and fixes plot_route() returning nothing.
Recent releases track other people's changes: ggmap moving to Stadia maps, gridExtra giving way to patchwork, a cadence field being read into the wrong column. The 2019 entries are where the analysis surface was built out, with cumulative elevation gain, compressed file reading and elevation-noise thresholds, and it has not moved much since.
Expect the next release to be another compatibility or parsing fix rather than a new metric.
Other Infra & APIs 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 gofedf or trackeR.
The protist reference database keeps widening past the rRNA gene it was built on.
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
Conservation planning absorbs the literature's target-setting rules as code.
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
An ecosystem model starts tracking carbon isotopes and land-use change.
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
See all gofedf alternatives → · See all trackeR alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. gofedf and trackeR 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. gofedf and trackeR 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 Infra & APIs products to evaluate alongside.
Top gofedf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "gofedf alternatives" section above for the current picks, or visit /alternatives/gofedf for the full list with editorial commentary on each.
Top trackeR alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "trackeR alternatives" section above for the current picks, or visit /alternatives/tracker for the full list with editorial commentary on each.