simlandr
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
A side-by-side editorial comparison of anyflights and slope — release velocity, themes, recent moves, and the top alternatives to consider.
A nycflights13 generator whose recent work is all about the data being right.
anyflights builds nycflights13-style datasets for any US airport and year, downloading flight, weather, airline, airport, and plane tables and optionally packaging them. The four visible releases span 2022 to 2025 and are dominated by keeping those downloads working. The most recent fixes a timezone leak and gaps in hourly weather data.
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
SLOPE fits sorted L-one penalized regression models. In July 2025 it replaced its entire solver with the external libslope C++ library, removing the ADMM solver, dropping debugging fields, changing alpha scaling and warning users directly that the breakage was extensive. The releases since have rebuilt convenience on top of that core: summary() and refit() methods for cross-validated objects, automatic refitting in cvSLOPE(), and a threading default reduced from half the available cores to one.
anyflights builds nycflights13-style datasets for any US airport and year, downloading flight, weather, airline, airport, and plane tables and optionally packaging them. The four visible releases span 2022 to 2025 and are dominated by keeping those downloads working. The most recent fixes a timezone leak and gaps in hourly weather data.
The function surface has been stable since 0.3; everything since concerns the fragility of the upstream sources. Broken URLs for airline data, download failures needing a session-timeout hint, planes data that stopped resolving, and weather values recorded only once an hour have each taken a release. Contributions come from teaching-adjacent users, which fits a package whose main use is generating course datasets.
Expect the next release to follow another upstream data-source change rather than to add a table or an argument.
SLOPE fits sorted L-one penalized regression models. In July 2025 it replaced its entire solver with the external libslope C++ library, removing the ADMM solver, dropping debugging fields, changing alpha scaling and warning users directly that the breakage was extensive. The releases since have rebuilt convenience on top of that core: summary() and refit() methods for cross-validated objects, automatic refitting in cvSLOPE(), and a threading default reduced from half the available cores to one.
The arc runs rewrite, then repair, then convenience. The 1.2.0 release is the repair phase — coefficients_scaled was returning unscaled values, which silently affected every coef.SLOPE() call — and 2.0.0 onward is convenience, with refit() now working without re-supplying training data. The tag timestamps are non-monotonic: 1.0.1 is stamped a minute after 1.1.0 despite the lower version, so ordering here reflects when tags were pushed, not what superseded what.
With the cross-validation workflow now closing itself out through automatic refitting, further work is more likely to extend the summary and plotting surface than to touch the solver again.
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 anyflights or slope.
Potential landscape tooling settling onto standard R generics after two rounds of renaming.
SEM reporting helpers converging on APA output, one CRAN resubmission at a time.
A raster-to-terra migration is the only readable change in a feed of merge notes.
Conditional density and log-likelihood fill out a vine copula regression package.
A drop-in string API for base R, kept alive by upstream check failures.
From a bundled hospital dataset to a live CMS API client.
See all anyflights alternatives → · See all slope alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. anyflights and slope 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. anyflights and slope 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 anyflights alternatives in Analytics are ranked by recent ship velocity. Browse the "anyflights alternatives" section above for the current picks, or visit /alternatives/anyflights for the full list with editorial commentary on each.
Top slope alternatives in Analytics are ranked by recent ship velocity. Browse the "slope alternatives" section above for the current picks, or visit /alternatives/slope for the full list with editorial commentary on each.