osmapiR
osmapiR is the rare API client that tracks its server's wiki revision numbers in the changelog.
Comparison · Analytics
epidemics vs nanoparquet
A side-by-side editorial comparison of epidemics and nanoparquet — release velocity, themes, recent moves, and the top alternatives to consider.
epidemics vs nanoparquet: at a glance
What is epidemics?
epidemics swapped its C++ engine for odin — and quietly inverted how contact matrices must be passed.
epidemics ships composable compartmental model structures — default SEIR-V, Vacamole, diphtheria and Ebola — with classes for populations, interventions and vaccination campaigns. After more than two years without a release, 0.5.0 landed in July 2026 carrying both an engine migration and a breaking input-convention change. Maintainership moved to a new lead back in 0.4.0.
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.
epidemics vs nanoparquet: editorial side-by-side
epidemics
3.8ANALYTICS
epidemics swapped its C++ engine for odin — and quietly inverted how contact matrices must be passed.
◆ Current state
epidemics ships composable compartmental model structures — default SEIR-V, Vacamole, diphtheria and Ebola — with classes for populations, interventions and vaccination campaigns. After more than two years without a release, 0.5.0 landed in July 2026 carrying both an engine migration and a breaking input-convention change. Maintainership moved to a new lead back in 0.4.0.
◆ Where it's heading
The package's history is a sequence of deliberate breaking releases: 0.2.0 renamed every model function and vectorised the ODE models, 0.3.0 restructured the Ebola model into two levels and made replicates the default, and 0.5.0 rewrites the compiled core. The direction is toward a smaller, more declarative model definition layer with the numerical work delegated to a dedicated tool.
◆ Prediction
With the default, Vacamole and diphtheria systems now declared in odin, the Ebola model is the obvious remaining candidate for the same treatment.
nanoparquet
0.0ANALYTICS
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 epidemics 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 epidemics or nanoparquet.
ymlthis
ymlthis retired itself, naming Quarto as the reason it no longer needs to exist.
forestly
forestly built an interactive safety review tool, then taught it to produce submission-ready RTF.
pharmaverseadam
pharmaverseadam is the pharmaverse's test-data mirror, and it now covers neurology.
pkglite
pkglite's whole job is knowing which files in an R package are text — and it keeps getting better at guessing.
gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
See all epidemics alternatives → · See all nanoparquet alternatives →
Recent activity from epidemics and nanoparquet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 25d agoepidemicsODE models migrate to odin; contact matrices must no longer be transposed ⚡
- 3mo agonanoparquet64-bit integer columns and writing Parquet to stdout
- 4mo agonanoparquetFiles now readable by the Java and Rust Parquet libraries
- 1y agonanoparquetReads Polars files that omit the dictionary page offset
- 1y agonanoparquetDate, FLOAT, and mixed-encoding read fixes
- 1y agonanoparquetSchema authoring and append_parquet arrive with a renamed API ⚡
- 1y agonanoparquetFixes a write_parquet crash
- 2y agoepidemicsPeak timing and scenario comparison helpers; negative-susceptible bug fixed
- 2y agoepidemicsEbola model accepts vector inputs and defaults to 100 replicates
- 2y agoepidemicsODE models vectorised; every model function renamed
- 2y agoepidemicsFirst release: four composable compartmental model structures
Frequently asked questions
What is the difference between epidemics and nanoparquet?
They serve adjacent needs but don't currently overlap on shipped themes. epidemics is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is epidemics better than nanoparquet?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. epidemics is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to epidemics?
Top epidemics alternatives in Analytics are ranked by recent ship velocity. Browse the "epidemics alternatives" section above for the current picks, or visit /alternatives/epidemics 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.