vcfR
A genomics workhorse whose visible release feed stops dead in mid-2020.
Comparison · Infra & APIs
trackeR vs TrendLSW
A side-by-side editorial comparison of trackeR and TrendLSW — release velocity, themes, recent moves, and the top alternatives to consider.
trackeR vs TrendLSW: at a glance
What is trackeR?
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.
What is TrendLSW?
Wavelet trend estimation tightens the defaults it shipped with.
TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.
trackeR vs TrendLSW: editorial side-by-side
trackeR
0.0INFRA · APIS
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
Expect the next release to be another compatibility or parsing fix rather than a new metric.
TrendLSW
0.0INFRA · APIS
Wavelet trend estimation tightens the defaults it shipped with.
◆ Current state
TrendLSW estimates trend and evolutionary wavelet spectrum for locally stationary time series through a single TLSW() entry point. Its history since the first CRAN appearance is short and centres on defaults and plotting around that function, plus one dataset addition. The latest entry carries both the 1.0.4 and 1.0.3 notes in one body.
◆ Where it's heading
The package has moved from getting onto CRAN to correcting the choices it launched with: the spectrum filter defaults were swapped to their trend counterparts, the plot.CI switch was removed in favour of inferring it from what was actually computed, and an example was shrunk to fit check timings. This is consolidation around a stable API rather than expansion.
◆ Prediction
Further releases most likely continue tuning TLSW() defaults and plot behaviour; the entries show no work toward new estimators.
Alternatives to trackeR and TrendLSW
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 trackeR or TrendLSW.
dialr
The R phone-number package stopped only parsing numbers and started asking them where they are.
ggVennDiagram
A Venn diagram package whose public release notes say almost nothing — including about its copyright cleanup.
ordinalsimr
A Shiny app for choosing the right ordinal test reached CRAN in a single 90-minute burst of tags.
transltr
A new R localization package that reached CRAN and immediately downgraded itself to experimental.
hereR
An R client for HERE's location APIs, shaped almost entirely by what the vendor exposes next.
See all trackeR alternatives → · See all TrendLSW alternatives →
Recent activity from trackeR and TrendLSW
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agoTrendLSWTrend filter defaults replace spectrum defaults; plot.CI dropped
- 11mo agotrackeRplot_route() fixed; plot layout moved to patchwork
- 2y agoTrendLSWNew z.acc and z.labels datasets shipped with the package
- 2y agoTrendLSWDescription field and plot.TLSW documentation fixes
- 2y agotrackeRTCX cadence bug fixed; m_per_min units and Stadia maps
- 7y agotrackeRCompressed file reading and correct GPX power extraction
- 7y agotrackeRvertical_noise threshold for elevation gain
- 7y agotrackeRCumulative elevation gain added as a derived metric
- 7y agotrackeRFortify and print bugs fixed in summary objects
Frequently asked questions
What is the difference between trackeR and TrendLSW?
They serve adjacent needs but don't currently overlap on shipped themes. trackeR and TrendLSW 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.
Is trackeR better than TrendLSW?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. trackeR and TrendLSW 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.
What are the best alternatives to trackeR?
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.
What are the best alternatives to TrendLSW?
Top TrendLSW alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "TrendLSW alternatives" section above for the current picks, or visit /alternatives/trendlsw for the full list with editorial commentary on each.