← Back to home
Comparison · Analytics

datefixR vs simulist

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

datefixR vs simulist: at a glance

FeaturedatefixRsimulist
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesdate-parsing, rust, data-cleaning, localizationepiverse-trace, outbreak-simulation, line-list, data-realism
Last editorial update53m ago4h ago
WebsiteVisit →Visit →

What is datefixR?

The messy-date parser rewrote its core in Rust and came out 300x faster.

datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.

Read the full datefixR 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 →

datefixR vs simulist: editorial side-by-side

D
datefixR
ANALYTICS
0.0

The messy-date parser rewrote its core in Rust and came out 300x faster.

◆ Current state

datefixR standardizes inconsistently formatted dates — the kind that arrive from spreadsheets and hand-entered clinical or survey data, with mixed separators, ambiguous orders, missing components, and month names in whatever language the source used. Version 2.0.0 rewrote the parsing core in Rust, reporting over 300x throughput against previous versions through fastpath handling of common formats and parallel column processing via a cores argument. Version 2.0.1 then spent itself cleaning up after that rewrite, restoring ordinal indicator support, stopping malformed dates from being silently cast to NA, and reinstating error messages that had gone missing.

◆ Where it's heading

Two long arcs meet here. The first is localization: Russian, Indonesian, German, Spanish month abbreviations, and experimental Roman numeral months accumulated release by release, with full translation of user-facing messages treated as a goal rather than a bonus. The second is the migration off R for the parsing hot path — internals began moving to C++ around 1.3.1 before the Rust rewrite replaced that work entirely. The 2.0.1 regressions show the cost of that move, since behavior that was implicit in the R implementation had to be re-specified.

◆ Prediction

The Rust core is one release into stabilization and 2.0.1 was entirely regression repair, so expect further correctness fixes against pre-2.0.0 behavior before any new format support lands.

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

See all datefixR alternatives → · See all simulist alternatives →

Recent activity from datefixR and simulist

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

  1. 3mo agodatefixRRust rewrite regressions repaired, silent NA casting stopped
  2. 6mo agosimulistJOSS paper corrections
  3. 6mo agosimulistWeighted sex sampling and epiparameter objects for reporting delays
  4. 11mo agosimulistcensor_linelist() adds interval censoring and a weekend effect
  5. 11mo agodatefixRParsing core rewritten in Rust for a 300x speedup
  6. 1y agosimulistPost-processing arrives: truncated snapshots and deliberately messy line lists
  7. 1y agosimulistEvery sim_*() argument gains a default
  8. 1y agodatefixRIndonesian month names and translations added
  9. 2y agosimulistInfectious period replaces contact interval; time-varying fatality risk added
  10. 2y agodatefixR'ene' and 'ener' recognized as January
  11. 3y agodatefixRRussian localization, Roman numeral months, Windows freeze fix
  12. 3y agodatefixRExcel leap-year offset and single-digit day fixes

Frequently asked questions

What is the difference between datefixR and simulist?

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

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

Top datefixR alternatives in Analytics are ranked by recent ship velocity. Browse the "datefixR alternatives" section above for the current picks, or visit /alternatives/datefixr 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.