randomwalk
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
Comparison · Analytics
bagyo vs fect
A side-by-side editorial comparison of bagyo and fect — release velocity, themes, recent moves, and the top alternatives to consider.
bagyo vs fect: at a glance
What is bagyo?
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
A data package distributing Philippine Area of Responsibility tropical cyclone records, developed through 2024 pre-releases and accepted by CRAN in early 2026. The substantive release is v0.2.0: 2021 and 2022 typhoon data added, an unexported helper for downloading cyclone reports, CITATION.cff, an R 4.1 dependency for the base pipe, and a full pass over vignettes, tests and README. The v0.1.1 tag announcing the first CRAN release carries no content and is stamped two hours after v0.2.0.
What is fect?
A counterfactual estimator turning itself into a platform for multiple estimands
fect implements counterfactual estimators for panel data with treatment effects — imputation-based fixed effects, interactive fixed effects, matrix completion. The 2026 releases move fast and bundle heavily: 2.1.0 rewrote complex fixed effect handling, 2.2.0 unified cross-validation under a single cv.method parameter and replaced method='gsynth' with an explicit time.component.from switch, 2.4.1 introduced a post-hoc estimand API, and 2.4.5 added group.fe for coarsened fixed effects plus a $sample slot exposing which cells entered estimation.
bagyo vs fect: editorial side-by-side
bagyo
0.0ANALYTICS
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
◆ Current state
A data package distributing Philippine Area of Responsibility tropical cyclone records, developed through 2024 pre-releases and accepted by CRAN in early 2026. The substantive release is v0.2.0: 2021 and 2022 typhoon data added, an unexported helper for downloading cyclone reports, CITATION.cff, an R 4.1 dependency for the base pipe, and a full pass over vignettes, tests and README. The v0.1.1 tag announcing the first CRAN release carries no content and is stamped two hours after v0.2.0.
◆ Where it's heading
The package is establishing itself as a citable, yearly-updated dataset rather than a one-off scrape — the download helper and the '2022 data and general yearly upkeep' commit both point at a recurring refresh, and the CRAN DOI and CITATION file exist so the data can be cited in papers. It sits alongside the same maintainer's other public-health and survey data packages, which received matching repository upkeep in the same month.
◆ Prediction
Expect an annual data release adding the next typhoon season, since that is the only recurring change in the history and the download helper was written to support it.
fect
0.0ANALYTICS
A counterfactual estimator turning itself into a platform for multiple estimands
◆ Current state
fect implements counterfactual estimators for panel data with treatment effects — imputation-based fixed effects, interactive fixed effects, matrix completion. The 2026 releases move fast and bundle heavily: 2.1.0 rewrote complex fixed effect handling, 2.2.0 unified cross-validation under a single cv.method parameter and replaced method='gsynth' with an explicit time.component.from switch, 2.4.1 introduced a post-hoc estimand API, and 2.4.5 added group.fe for coarsened fixed effects plus a $sample slot exposing which cells entered estimation.
◆ Where it's heading
The direction is separation of estimation from interpretation. Where the package once returned one effect from one fit, estimand() now dispatches typed estimands — ATT, cumulative ATT, APTT, log ATT — from any imputation fit, with effect() and att.cumu() soft-deprecated but byte-identical pending 3.0.0. Alongside that runs a transparency thread: the $sample matrix, out-of-sample comparison via fect_mspe(), and named component sources instead of opaque method aliases. The release notes are unusually precise about which results change and which do not.
◆ Prediction
The soft-deprecation notice names 3.0.0 as the removal point for effect() and att.cumu(), so a major release consolidating on the estimand() dispatcher is the clearly signposted next step.
Alternatives to bagyo and fect
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 bagyo or fect.
fastml
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
churon
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
rainette
rainette rebuilt its Reinert clustering in 0.2.0, tuned it in 0.3.0, and has coasted since.
Recent activity from bagyo and fect
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agofectAdds group.fe for coarsened fixed effects and a $sample slot
- 3mo agofectPost-hoc estimand API decouples estimands from the fit ⚡
- 4mo agofectUnified cross-validation and explicit control of time components
- 7mo agobagyobagyo v0.1.1
- 7mo agobagyo2021 and 2022 typhoon data added
- 7mo agofectRewrites complex fixed effect handling and fixes speed
- 11mo agofectAdds heterogeneous treatment effect plots and caps default cores
- 2y agobagyoPre-release for Zenodo archiving
- 2y agobagyoInitial pre-release
Frequently asked questions
What is the difference between bagyo and fect?
They serve adjacent needs but don't currently overlap on shipped themes. bagyo and fect 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.
Is bagyo better than fect?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bagyo and fect 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.
What are the best alternatives to bagyo?
Top bagyo alternatives in Analytics are ranked by recent ship velocity. Browse the "bagyo alternatives" section above for the current picks, or visit /alternatives/bagyo for the full list with editorial commentary on each.
What are the best alternatives to fect?
Top fect alternatives in Analytics are ranked by recent ship velocity. Browse the "fect alternatives" section above for the current picks, or visit /alternatives/fect for the full list with editorial commentary on each.