qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of gtfstools and ss3diags — release velocity, themes, recent moves, and the top alternatives to consider.
gtfstools stopped guarding its own object model and started accepting everyone else's.
gtfstools reads, edits, filters and validates GTFS public transport feeds in R on a data.table backend. Since 1.3.0 it accepts GTFS objects produced by other packages such as gtfsio and tidytransit, converting them through an as_dt_gtfs() generic. Validation runs MobilityData's canonical validator, now supported through v6.0.0.
A fisheries diagnostics package that lives and dies by one upstream dependency.
ss3diags provides residual, retrospective and hindcast cross-validation diagnostics for Stock Synthesis models, sitting directly on top of r4ss. Its recent history is dominated by that dependency: when r4ss 1.50.0 renamed columns across its read and write functions, ss3diags pinned itself to 1.49.3 only, then spent the following release adapting. It now requires r4ss 1.50.0 and above and has moved to native R pipes.
gtfstools reads, edits, filters and validates GTFS public transport feeds in R on a data.table backend. Since 1.3.0 it accepts GTFS objects produced by other packages such as gtfsio and tidytransit, converting them through an as_dt_gtfs() generic. Validation runs MobilityData's canonical validator, now supported through v6.0.0.
The package built out a wide function surface first — filters, geometry conversion, speed and duration calculations — then turned outward. Delegating validation to MobilityData's validator and accepting other packages' objects both trade self-sufficiency for a position inside the wider GTFS ecosystem. Deprecations are handled slowly, with old behaviour left as the default for a release or more.
Expect continued validator version tracking and further completion of the deprecation cycle around filter_by_stop_id()'s full_trips behaviour.
ss3diags provides residual, retrospective and hindcast cross-validation diagnostics for Stock Synthesis models, sitting directly on top of r4ss. Its recent history is dominated by that dependency: when r4ss 1.50.0 renamed columns across its read and write functions, ss3diags pinned itself to 1.49.3 only, then spent the following release adapting. It now requires r4ss 1.50.0 and above and has moved to native R pipes.
The package is a downstream consumer whose release schedule is largely dictated by NOAA's r4ss. Between compatibility passes it has been shifting documentation from loose cookbook scripts into proper vignettes and shedding bundled Rdata in favour of objects generated at build time. Note that 2.0.3 and 2.1.0 were published the same day, so version order in this feed does not track chronology.
The next release most likely follows the next breaking r4ss change; between those, expect continued vignette and parameter-validation work.
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 gtfstools or ss3diags.
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
The R package for CODATA constants rebuilt its symbol table on NIST's naming so future updates stop being hand work.
The R client for AusTraits spends its releases chasing the dataset it reads.
A ggplot2 layer for seasonal adjustment output, filling in one plot type at a time.
A fossil-record simulator that quietly grew a trait-evolution engine.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
See all gtfstools alternatives → · See all ss3diags alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. gtfstools and ss3diags 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. gtfstools and ss3diags 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 gtfstools alternatives in Analytics are ranked by recent ship velocity. Browse the "gtfstools alternatives" section above for the current picks, or visit /alternatives/gtfstools-r for the full list with editorial commentary on each.
Top ss3diags alternatives in Analytics are ranked by recent ship velocity. Browse the "ss3diags alternatives" section above for the current picks, or visit /alternatives/ss3diags for the full list with editorial commentary on each.