← Back to home
Comparison · Analytics

cfr vs nanoparquet

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

cfr vs nanoparquet: at a glance

Featurecfrnanoparquet
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesepidemiology, severity-estimation, outbreak-analytics, epiverseparquet, r-language, interoperability, data-formats
Last editorial update4h ago46m 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 nanoparquet?

nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.

nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.

Read the full nanoparquet trajectory →

cfr vs nanoparquet: 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.

N
nanoparquet
ANALYTICS
0.0

nanoparquet is chasing byte-level agreement with the Java and Rust Parquet readers, not feature count.

◆ Current state

nanoparquet reads and writes Parquet from R with no Arrow dependency, which is its entire reason to exist. The 0.4.0 line renamed the reader API and added schema authoring plus `append_parquet()`, and the 0.5.x releases have gone after interoperability: definition and repetition level encodings the Apache Parquet Java library expects, flatbuffer alignment the Rust arrow-rs reader expects, 128-bit decimals, and Polars-written files that omit the dictionary page offset. The newest release adds `bit64::integer64` columns and writing to stdout.

◆ Where it's heading

Almost every entry since 0.4.0 names another engine — Java, arrow-rs, Polars, Arrow schema metadata — which tells you the maintainers are treating cross-reader fidelity as the product rather than R-side ergonomics. The type system is filling in from the edges: DECIMAL beyond 8 bytes, UUID, FLOAT16 and INTERVAL as raw lists, and now 64-bit integers with an explicit read-type option instead of a silent cast to double. Writing to `:stdout:` points at a second audience, shell pipelines rather than interactive R.

◆ Prediction

The remaining unmapped Parquet types the changelog has been parking in raw-vector lists — FLOAT16 and INTERVAL — are the obvious next targets, following the same pattern by which DECIMAL and UUID graduated to real R types.

Alternatives to cfr and nanoparquet

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 nanoparquet.

See all cfr alternatives → · See all nanoparquet alternatives →

Recent activity from cfr and nanoparquet

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

  1. 3mo agonanoparquet64-bit integer columns and writing Parquet to stdout
  2. 4mo agonanoparquetFiles now readable by the Java and Rust Parquet libraries
  3. 1y agocfrR-devel difftime patch and an individual-data vignette
  4. 1y agonanoparquetReads Polars files that omit the dictionary page offset
  5. 1y agonanoparquetDate, FLOAT, and mixed-encoding read fixes
  6. 1y agonanoparquetSchema authoring and append_parquet arrive with a renamed API
  7. 1y agonanoparquetFixes a write_parquet crash
  8. 2y agocfrSeverity estimator picks its own likelihood approximation
  9. 2y agocfrDelay-corrected severity and ascertainment estimation on CRAN

Frequently asked questions

What is the difference between cfr and nanoparquet?

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

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

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