qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of fossilsim and tidytransit — release velocity, themes, recent moves, and the top alternatives to consider.
A fossil-record simulator that quietly grew a trait-evolution engine.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
FossilSim is a mature R package for simulating fossil records on phylogenetic trees, and its release cadence reflects that: long gaps punctuated by a single capability addition. The last four releases span three years, with the most recent being a compatibility sync to its companion Shiny front-end rather than new functionality. The core simulation surface has been stable since 2022.
The arc runs from sampling mechanics toward simulating what the organisms actually were. Version 2.2.0 taught the package to handle occurrence data for occurrence birth-death models; 2.3.0 then added trait simulation under Mk, BM and OU, which is a different kind of output than fossil ages. Since then the work has been maintenance and keeping the FossilSimShiny GUI in step, suggesting the authors consider the current model set feature-complete.
The pairing of the 2.3.3 release with a FossilSimShiny version bump points to the GUI, not the library, as where the next visible work lands. The entries do not show enough activity to predict a specific new model family.
tidytransit reads GTFS transit feeds into tidy data frames and computes travel times using a RAPTOR implementation. Recent work splits between the reader keeping pace with the spec — locations.geojson in 1.7.0, empty strings parsed as NA in 1.8.0 — and the router gaining realism, most recently in-seat transfers. Feed specifications are now pulled from the automatically parsed GTFS reference rather than maintained by hand.
The package has settled into tracking an external standard, which is why the changelog reads as a sequence of spec conformance items rather than a roadmap. Parsing responsibility keeps shifting outward to gtfsio, and data sources have moved with the ecosystem, from the retired transitfeeds API to MobilityData. Router changes are rarer than reader changes but land in the same releases.
Further GTFS spec features are the safest expectation, with GTFS-Flex the likeliest area now that locations.geojson reading is in place.
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 fossilsim or tidytransit.
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.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
See all fossilsim alternatives → · See all tidytransit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. fossilsim and tidytransit 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. fossilsim and tidytransit 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 fossilsim alternatives in Analytics are ranked by recent ship velocity. Browse the "fossilsim alternatives" section above for the current picks, or visit /alternatives/fossilsim-r for the full list with editorial commentary on each.
Top tidytransit alternatives in Analytics are ranked by recent ship velocity. Browse the "tidytransit alternatives" section above for the current picks, or visit /alternatives/tidytransit-r for the full list with editorial commentary on each.