← Back to home
Comparison · Analytics

cfr vs gigs

A side-by-side editorial comparison of cfr and gigs — release velocity, themes, recent moves, and the top alternatives to consider.

cfr vs gigs: at a glance

Featurecfrgigs
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, severity-estimation, outbreak-analytics, epiversegrowth-standards, neonatal-health, r-package, ropensci
Last editorial update6h ago57m ago
WebsiteVisit →Visit →

What is cfr?

cfr packaged delay-corrected severity estimation, then went quiet on maintenance.

The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.

Read the full cfr trajectory →

What is gigs?

gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.

gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.

Read the full gigs trajectory →

cfr vs gigs: editorial side-by-side

C
cfr
ANALYTICS
0.0

cfr packaged delay-corrected severity estimation, then went quiet on maintenance.

◆ Current state

The package estimates disease severity and case ascertainment while correcting for the delay between a case being reported and its outcome being known. After the 0.1.1 rework of the estimation internals and a maintainer handover to Adam Kucharski, activity dropped to a vignette and an R-devel compatibility patch in February 2025.

◆ Where it's heading

The methodological work is done and consolidated: likelihood approximation is now selected automatically from outbreak size and an initial severity estimate, and the internals were renamed with a dot prefix to close the public surface down to cfr_static(), cfr_rolling() and the data-preparation generic. Releases since have been documentation and compatibility only.

◆ Prediction

The 0.1.0 notes flagged time-varying ascertainment as future work and it has not appeared in the two releases since; nothing in these entries indicates when or whether it lands.

G
gigs
ANALYTICS
0.0

gigs redesigned its whole conversion API for rOpenSci, then spent three releases getting the docs to build.

◆ Current state

gigs implements international newborn and infant growth standards — INTERGROWTH-21st, WHO — converting anthropometric measurements to z-scores and centiles and classifying growth outcomes. The 0.5.0 release rewrote the public API around rOpenSci review feedback; the two releases after it change no code at all, existing purely to get the documentation site building.

◆ Where it's heading

The package has moved from vector-in, vector-out conversion helpers to a data.frame-oriented interface with a single classify_growth() entry point that computes whatever outcomes the supplied columns allow. That is a shift from library to tool — the user describes their data rather than picking the right function. The trailing releases suggest the code is settled and the remaining work is packaging and discoverability.

◆ Prediction

With the API rewrite absorbed and hosting moved to rOpenSci, the next substantive release should add growth standards or outcomes rather than reshape the interface again.

Alternatives to cfr and gigs

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 cfr or gigs.

See all cfr alternatives → · See all gigs alternatives →

Recent activity from cfr and gigs

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1y agocfrR-devel difftime patch and an individual-data vignette
  2. 1y agogigsDocs and Zenodo archiving
  3. 1y agogigsDocs-only release; nothing changed internally
  4. 1y agogigsConversion API rewritten around data frames and classify_growth()
  5. 2y agocfrSeverity estimator picks its own likelihood approximation
  6. 2y agogigsDocumentation fixes for autotest compliance
  7. 2y agogigsINTERGROWTH-21st fetal standards and input validation
  8. 2y agogigsPatch release with documentation update
  9. 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN

Frequently asked questions

What is the difference between cfr and gigs?

They serve adjacent needs but don't currently overlap on shipped themes. cfr and gigs 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 cfr better than gigs?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cfr and gigs 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 cfr?

Top cfr alternatives in Analytics are ranked by recent ship velocity. Browse the "cfr alternatives" section above for the current picks, or visit /alternatives/cfr for the full list with editorial commentary on each.

What are the best alternatives to gigs?

Top gigs alternatives in Analytics are ranked by recent ship velocity. Browse the "gigs alternatives" section above for the current picks, or visit /alternatives/gigs for the full list with editorial commentary on each.