STACAS
Single-cell batch correction that learned to use cell labels, then spent three releases chasing Seurat.
Comparison · Analytics
bagyo vs incase
A side-by-side editorial comparison of bagyo and incase — release velocity, themes, recent moves, and the top alternatives to consider.
bagyo vs incase: 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 incase?
A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.
incase supplies in_case(), switch_case(), grep_case() and fn_case() as vectorised recoding functions in the dplyr::case_when idiom, with _fct and _list variants that return factors or lists instead of forcing atomic type conversion. The 0.4.0 release deprecates the undotted preserve, default and ordered arguments in favour of dotted forms, starting a removal clock, and adds .exhaustive to error on unmatched inputs.
bagyo vs incase: 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.
incase
0.0ANALYTICS
A safer case_when that keeps hardening its guarantees while realigning to tidyverse naming.
◆ Current state
incase supplies in_case(), switch_case(), grep_case() and fn_case() as vectorised recoding functions in the dplyr::case_when idiom, with _fct and _list variants that return factors or lists instead of forcing atomic type conversion. The 0.4.0 release deprecates the undotted preserve, default and ordered arguments in favour of dotted forms, starting a removal clock, and adds .exhaustive to error on unmatched inputs.
◆ Where it's heading
The arc is consistently toward catching recoding mistakes at the call site rather than letting them pass silently. Early releases broadened how a match can be expressed — pattern matching, function application, factor and list returns. Recent work has shifted to guarantees about the result: correct factor level ordering relative to .default, and now an exhaustiveness check. Notably 0.4.0 reverses the 0.3.2 decision to accept arguments with or without dots, trading that flexibility for namespace safety against user-supplied case names.
◆ Prediction
The deprecation warnings introduced in 0.4.0 point to a follow-up release that removes the undotted arguments outright. Whether .exhaustive eventually becomes the default is unclear from these entries.
Alternatives to bagyo and incase
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 incase.
ggtrace
A debugger for ggplot2's internals, hardening its grip as the internals it traces keep moving.
kde1d
A univariate density estimator that added zero-inflated data and reopened its C++ API to do it.
svines
Stationary vine copulas for time series, released in lockstep with the rest of Nagler's vine stack.
gghighlight
A single-purpose ggplot2 extension that has spent six years tracking ggplot2 instead of growing.
rtrek
A Star Trek data package that became a Memory Alpha web client and has been patching scrapers ever since.
See all bagyo alternatives → · See all incase alternatives →
Recent activity from bagyo and incase
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 7mo agobagyobagyo v0.1.1
- 7mo agobagyo2021 and 2022 typhoon data added
- 11mo agoincaseDotted arguments and an .exhaustive matching check
- 2y agobagyoPre-release for Zenodo archiving
- 2y agobagyoInitial pre-release
- 2y agoincaseDotted and undotted arguments both accepted
- 5y agoincaseFix NULL return when no condition matches
- 5y agoincaseFactor and list return families arrive
- 5y agoincaseDrop unused stats import to clear a check NOTE
- 5y agoincasePattern and function-based matching families added
Frequently asked questions
What is the difference between bagyo and incase?
They serve adjacent needs but don't currently overlap on shipped themes. bagyo and incase 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 incase?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bagyo and incase 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 incase?
Top incase alternatives in Analytics are ranked by recent ship velocity. Browse the "incase alternatives" section above for the current picks, or visit /alternatives/incase for the full list with editorial commentary on each.