metatools
SDTM supplemental-qualifier merging got sturdier, then the package went quiet for two years.
Comparison · Analytics
cfr vs chromer
A side-by-side editorial comparison of cfr and chromer — release velocity, themes, recent moves, and the top alternatives to consider.
cfr vs chromer: at a glance
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.
What is chromer?
A chromosome-count database client that only ever ships when the upstream API moves.
chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.
cfr vs chromer: editorial side-by-side
cfr
0.0ANALYTICS
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.
chromer
0.0ANALYTICS
A chromosome-count database client that only ever ships when the upstream API moves.
◆ Current state
chromer is a thin R client for the Chromosome Counts Database. Every release in the past three years is maintenance: a new maintainer and licence change in 0.3, test-skipping when the upstream service is down in 0.4, and two separate releases whose entire content is that the database's URL changed again. The current 0.10 points at ccdb.tau.ac.il/services/.
◆ Where it's heading
The package is functionally complete and externally driven — its release cadence is a record of the CCDB's hosting history rather than of any development plan. The defensive work in 0.4, which added an internal check for whether the database is down and skips tests accordingly, shows the maintainer treating upstream instability as the permanent condition rather than an incident.
◆ Prediction
The next release will most likely be triggered by another CCDB endpoint or format change; nothing in the history suggests new functionality is planned.
Alternatives to cfr and chromer
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 chromer.
marquee
marquee is filling in the typographic details — outlines, border types, real font metrics for underlines.
logrx
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
lobstr
R's object inspector is losing its view of the internals as CRAN closes off the private C API.
GSODR
A weather-station data client that broke one return type to hand back distances instead of bare IDs.
giscoR
giscoR's 1.0 moved its dataset index into the cache, so new Eurostat releases arrive without a package update.
Recent activity from cfr and chromer
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agochromerChromosome Counts Database endpoint moved again
- 1y agocfrR-devel difftime patch and an individual-data vignette
- 2y agocfrSeverity estimator picks its own likelihood approximation
- 2y agochromerDatabase URL updated after upstream move
- 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN ⚡
- 2y agochromerAPI calls switched to https
- 2y agochromerDocumentation tweak for a CRAN check
- 3y agochromerTests skipped when the upstream database is down
- 3y agochromerNew maintainer; licence changes from CC0 to MIT
Frequently asked questions
What is the difference between cfr and chromer?
They serve adjacent needs but don't currently overlap on shipped themes. cfr and chromer 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 chromer?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cfr and chromer 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 chromer?
Top chromer alternatives in Analytics are ranked by recent ship velocity. Browse the "chromer alternatives" section above for the current picks, or visit /alternatives/chromer for the full list with editorial commentary on each.