← Back to home
Comparison · Analytics

nanoparquet vs simulist

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

nanoparquet vs simulist: at a glance

Featurenanoparquetsimulist
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesparquet, r-language, interoperability, data-formatsepiverse-trace, outbreak-simulation, line-list, data-realism
Last editorial update46m ago5h ago
WebsiteVisit →Visit →

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 →

What is simulist?

simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.

simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.

Read the full simulist trajectory →

nanoparquet vs simulist: editorial side-by-side

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.

S
simulist
ANALYTICS
0.0

simulist stopped simulating clean outbreaks and started simulating the mess real surveillance data arrives in.

◆ Current state

simulist generates synthetic line list and contact-tracing data for outbreak analytics as part of the Epiverse-TRACE stack. It reached stable status in 0.6.0 and was published in JOSS alongside 0.7.0 in February 2026. Its distinguishing feature is no longer the epidemic simulation itself but the post-processing layer that degrades the output into realistic data.

◆ Where it's heading

The scope moved outward in two steps. 0.5.0 added truncate_linelist() and messy_linelist() to produce right-truncated snapshots and data with missingness and inconsistencies; 0.6.0 added censor_linelist() for grouping dates into intervals with a weekend-reporting effect. The simulation core has meanwhile settled — 0.7.0's changes are interface polish: weighted sex sampling and <epiparameter> objects accepted for reporting_delay.

◆ Prediction

Post-processing is where the recent work is, so further realism controls — additional reporting artefacts or interval schemes — are a likelier next step than new epidemic model structures.

Alternatives to nanoparquet and simulist

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

See all nanoparquet alternatives → · See all simulist alternatives →

Recent activity from nanoparquet and simulist

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. 6mo agosimulistJOSS paper corrections
  4. 6mo agosimulistWeighted sex sampling and epiparameter objects for reporting delays
  5. 11mo agosimulistcensor_linelist() adds interval censoring and a weekend effect
  6. 1y agosimulistPost-processing arrives: truncated snapshots and deliberately messy line lists
  7. 1y agonanoparquetReads Polars files that omit the dictionary page offset
  8. 1y agonanoparquetDate, FLOAT, and mixed-encoding read fixes
  9. 1y agonanoparquetSchema authoring and append_parquet arrive with a renamed API
  10. 1y agosimulistEvery sim_*() argument gains a default
  11. 1y agonanoparquetFixes a write_parquet crash
  12. 2y agosimulistInfectious period replaces contact interval; time-varying fatality risk added

Frequently asked questions

What is the difference between nanoparquet and simulist?

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

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

What are the best alternatives to simulist?

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