webchem
Adding chemical databases with one hand while public ones close programmatic access with the other.
Comparison · Analytics
cfr vs logrx
A side-by-side editorial comparison of cfr and logrx — release velocity, themes, recent moves, and the top alternatives to consider.
cfr vs logrx: 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 logrx?
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
cfr vs logrx: 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.
logrx
0.0ANALYTICS
A clinical-script logger that stopped shipping after its 0.2 line, changelogs made of merged PRs.
◆ Current state
logrx produces execution logs for R scripts in regulated clinical work, recording what ran, what it returned, and which unapproved packages or functions were used. Its release notes are raw merged-PR lists rather than written changelogs, which makes the substance hard to read from the feed. The most recent release, 0.2.2 in June 2023, exists to track tidyselect and dplyr changes.
◆ Where it's heading
Feature work concentrated in the 0.1 line — return codes, a results writer, a to_report parameter, and logging of unapproved package and function use — and the 0.2 releases have been compatibility maintenance and hotfixes. Three years of silence in a pharmaverse that has otherwise kept shipping suggests the package reached the shape its users needed rather than that it was abandoned mid-design.
◆ Prediction
Nothing in these entries points to planned work; the likeliest trigger for a release is a breaking change in tidyverse dependencies, which is what produced the last one.
Alternatives to cfr and logrx
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 logrx.
sftime
The spatiotemporal companion to sf, moving at the pace of the packages around it.
ReLTER
An interface to Europe's long-term ecosystem research network that went quiet after 2.0.
waywiser
Spatial model assessment that spent the last year on cross-platform arithmetic and CRAN rules.
taxizedb
Stopped trusting the cloud to prepare its taxonomic databases and does the conversion locally.
fellingdater
Went from estimating felling dates to doing the crossdating that produces them.
Recent activity from cfr and logrx
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1y agocfrR-devel difftime patch and an individual-data vignette
- 2y agocfrSeverity estimator picks its own likelihood approximation
- 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN ⚡
- 3y agologrxAlignment with tidyselect and dplyr changes
- 3y agologrxRelease v0.2.1
- 3y agologrxFormatted log output plus CRAN readiness work
- 4y agologrxPackage renamed to logrx; return codes and results writer land
Frequently asked questions
What is the difference between cfr and logrx?
They serve adjacent needs but don't currently overlap on shipped themes. cfr and logrx 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 logrx?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. cfr and logrx 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 logrx?
Top logrx alternatives in Analytics are ranked by recent ship velocity. Browse the "logrx alternatives" section above for the current picks, or visit /alternatives/logrx for the full list with editorial commentary on each.