qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of gtfstools and r4ss — 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.
NOAA's Stock Synthesis toolkit renamed its columns and shook the packages built on it.
r4ss reads, writes, runs and plots Stock Synthesis fisheries models, and is the base layer for a set of NOAA assessment packages. The current release tracks SS3 3.30.23.1 with plot and reader fixes. The consequential recent change was structural: the SS_read* functions standardised their column names, which broke downstream packages and forced at least one to pin an older version.
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.
r4ss reads, writes, runs and plots Stock Synthesis fisheries models, and is the base layer for a set of NOAA assessment packages. The current release tracks SS3 3.30.23.1 with plot and reader fixes. The consequential recent change was structural: the SS_read* functions standardised their column names, which broke downstream packages and forced at least one to pin an older version.
The project explicitly de-emphasises releases — the notes tell users to install the latest development version and treat tags as anchors for dependent packages. That has produced a rhythm of long quiet stretches punctuated by a breaking cleanup: the run-function revamp in 1.46.1, then the column renaming in 1.50.0. Ordinary releases in between are SS3 version tracking.
Expect the next tagged release to follow the next SS3 version rather than a fixed schedule, with continued incremental plotting and reader fixes.
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 r4ss.
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 r4ss alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. gtfstools and r4ss 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 r4ss 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 r4ss alternatives in Analytics are ranked by recent ship velocity. Browse the "r4ss alternatives" section above for the current picks, or visit /alternatives/r4ss for the full list with editorial commentary on each.