vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
A side-by-side editorial comparison of ordinalsimr and trackeR — release velocity, themes, recent moves, and the top alternatives to consider.
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
ordinalsimr compares ordinal endpoints by simulation — you specify probability distributions, sample sizes and iterations, and it runs the candidate statistical tests against them so you can see which behaves best. It is delivered as a Shiny application with a data-entry grid, and its entire release history spans six days in January 2025: three tags inside 90 minutes on the 20th, then a CRAN-compliance release on the 26th.
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.
ordinalsimr compares ordinal endpoints by simulation — you specify probability distributions, sample sizes and iterations, and it runs the candidate statistical tests against them so you can see which behaves best. It is delivered as a Shiny application with a data-entry grid, and its entire release history spans six days in January 2025: three tags inside 90 minutes on the 20th, then a CRAN-compliance release on the 26th.
The release bodies are auto-generated pull-request lists covering the repository's whole history, so they read as a build log rather than a changelog: data entry UI, an rhandsontable statistics module, iteration and sample-size modules, binomial confidence intervals, plot tests, and a rename to the current package name late in development. What that log shows is a single-author project built to completion privately and then published all at once, with the public version history existing mainly to satisfy CRAN.
With the CRAN submission accepted and no post-release entries in the feed, the next move is most likely a maintenance release; the PR log gives no signal of planned work beyond the tests already implemented.
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 ordinalsimr or trackeR.
A genomics workhorse whose visible release feed stops dead in mid-2020.
The R phone-number package stopped only parsing numbers and started asking them where they are.
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
One paper, one release: the functional control chart package ships methods as they get published.
See all ordinalsimr 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. ordinalsimr 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. ordinalsimr 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 ordinalsimr alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ordinalsimr alternatives" section above for the current picks, or visit /alternatives/ordinalsimr 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.