qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of ArchR and gtfstools — release velocity, themes, recent moves, and the top alternatives to consider.
ArchR returns after three years, mostly to catch up with the ecosystem around it.
ArchR analyses single-cell chromatin accessibility data, and until early 2025 its last release was from 2022. Release 1.0.3 collects roughly three years of accumulated pull requests: ggplot2 3.5 compatibility, Seurat v5 object creation, large-matrix handling via ARMA_64BIT_WORD, trajectory and module-score work, and a published Docker image. The release candidate before it did nothing but lift a 500 MB import ceiling.
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.
ArchR analyses single-cell chromatin accessibility data, and until early 2025 its last release was from 2022. Release 1.0.3 collects roughly three years of accumulated pull requests: ggplot2 3.5 compatibility, Seurat v5 object creation, large-matrix handling via ARMA_64BIT_WORD, trajectory and module-score work, and a published Docker image. The release candidate before it did nothing but lift a 500 MB import ceiling.
This is a maintenance restart rather than a new direction. The contributor list shifts visibly from the original authors toward newer maintainers handling compatibility work, and the Docker image suggests an acknowledgement that reproducing the environment had become the harder problem. Whether the cadence recovers is not something these entries answer.
The entries do not support a confident call on future direction; the immediate question is whether releases resume at a normal interval or 1.0.3 was a one-off catch-up.
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.
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 ArchR or gtfstools.
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 ArchR alternatives → · See all gtfstools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. ArchR and gtfstools 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. ArchR and gtfstools 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 ArchR alternatives in Analytics are ranked by recent ship velocity. Browse the "ArchR alternatives" section above for the current picks, or visit /alternatives/archr-r for the full list with editorial commentary on each.
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.