qqman
The Manhattan-plot package for GWAS results, finished and dormant since 2017.
A side-by-side editorial comparison of biocro and gtfstools — release velocity, themes, recent moves, and the top alternatives to consider.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
BioCro is a C++ crop growth simulator with an R interface, built from swappable modules for photosynthesis, respiration and development. Version 3.3.0 added multidimensional and one-dimensional root finders to the C++ source and put them to work immediately, replacing the fixed-point iteration used for intercellular CO2 with a Dekker root finder on the grounds that fixed-point iteration is known to be unstable there. Getting to that release also required moving from C++11 to C++17 and updating the bundled boost from 1.71 to 1.89.
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.
BioCro is a C++ crop growth simulator with an R interface, built from swappable modules for photosynthesis, respiration and development. Version 3.3.0 added multidimensional and one-dimensional root finders to the C++ source and put them to work immediately, replacing the fixed-point iteration used for intercellular CO2 with a Dekker root finder on the grounds that fixed-point iteration is known to be unstable there. Getting to that release also required moving from C++11 to C++17 and updating the bundled boost from 1.71 to 1.89.
Two threads run together: the biology is being broken into finer interchangeable modules — separate maintenance respiration, alternative linear and logistic SLA methods, a direct development-index module — while the numerics underneath are being made solvable in general. The root finders are explicitly staged to move into the shared biocro/framework repository, so this is groundwork for other models rather than for this package alone.
More module-level alternatives that depend on simultaneous-equation solutions are the natural follow-on, and the root finders should migrate out to biocro/framework as the notes state.
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 biocro 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 biocro alternatives → · See all gtfstools alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. biocro 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. biocro 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 biocro alternatives in Analytics are ranked by recent ship velocity. Browse the "biocro alternatives" section above for the current picks, or visit /alternatives/biocro-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.