monitOS
monitOS relicenses to MIT, the clearest signal in a sparse Novartis release feed.
Comparison · Analytics
clinify vs EpiNow2
A side-by-side editorial comparison of clinify and EpiNow2 — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
clinify vs EpiNow2: at a glance
What is clinify?
Clinical-table typesetting for R, closing the gap between R output and regulatory Word documents
clinify renders clinical trial tables into Word documents through {officer}, aiming at the layout conventions regulatory submissions expect. 0.4.0 is the current CRAN release and folds in an unreleased 0.3.1. The recent work is almost entirely about header and spacing control: which adjacent header cells merge, where the rule under a spanner starts and stops, and how much vertical space sits above, below and between header rows and the table body.
What is EpiNow2?
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
clinify vs EpiNow2: editorial side-by-side
clinify
2.5ANALYTICS
Clinical-table typesetting for R, closing the gap between R output and regulatory Word documents
◆ Current state
clinify renders clinical trial tables into Word documents through {officer}, aiming at the layout conventions regulatory submissions expect. 0.4.0 is the current CRAN release and folds in an unreleased 0.3.1. The recent work is almost entirely about header and spacing control: which adjacent header cells merge, where the rule under a spanner starts and stops, and how much vertical space sits above, below and between header rows and the table body.
◆ Where it's heading
The package is moving from producing a correct table toward producing one that survives an organisation's house style. 0.4.0's additions are all written to hold under a customised `clinify_table_default()` — `clin_spanner_rule()` draws after the default styling function so it persists when a house style clears the borders it started from, and takes an `officer::fp_border()` or `FALSE` so a style can decline the rule entirely. The earlier 0.3.0 line did the structural work, introducing `clindoc()` document objects that accept multiple tables plus automatic pagination.
◆ Prediction
Expect continued refinement of layout primitives that follow the table rather than fixed column numbers, since both new 0.4.0 functions were built specifically to track spanners and headers as a layout changes. The entries do not indicate a move beyond Word output.
EpiNow2
0.0ANALYTICS
EpiNow2 unified its model interface, then went back to deepen the estimators behind it
◆ Current state
EpiNow2 estimates reproduction numbers, infections and delay distributions from incomplete epidemiological reporting data. 1.8.0 was the structural turning point: every main modelling function now returns a consistent S3 object with `fit`, `args` and `observations`, reachable through shared accessors. The releases either side of it work on estimator quality — accumulation of irregularly reported data in 1.7.0, and a substantial expansion of `estimate_truncation()` in 1.9.0.
◆ Where it's heading
The package spent this window paying down interface debt and is now extending from the tidier base. Options that existed only for `estimate_infections()` have been propagated outward: `estimate_truncation()` gained the full `dist_spec` delay families, `obs_opts()` observation model selection between Poisson and negative binomial, and the `likelihood` and `return_likelihood` settings that make prior-only fits and loo-compatible output possible. Hardcoded assumptions are being replaced by specifiable ones in the same motion — the truncation model's additive noise term was a fixed `sigma ~ normal(0, 1)` prior and is now a `dist_spec` argument.
◆ Prediction
Expect the remaining modelling functions to keep converging on the shared options interface, since the last two releases have each moved another function onto it. A new `estimate_dist()` for interval-censored linelist data suggests delay estimation is the area still gaining surface.
Alternatives to clinify and EpiNow2
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 clinify or EpiNow2.
kernelshap
kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.
filtro
filtro moves to S7 and multiplies its feature-scoring methods in a single release.
modeltime.resample
modeltime.resample exists to keep backtesting working as tidymodels shifts underneath it.
modeltime.ensemble
modeltime.ensemble wakes after four years, and the work is all tune 2.0 compatibility.
shapviz
shapviz refines its SHAP plots release by release while chasing ggplot2's moving target.
See all clinify alternatives → · See all EpiNow2 alternatives →
Recent activity from clinify and EpiNow2
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 13d agoclinifyFiner header merging, spanner rules and header padding
- 1mo agoEpiNow2estimate_truncation gains full delay and observation options
- 6mo agoEpiNow2Unified return objects and shared accessors across all models ⚡
- 1y agoclinifyclindoc document objects and automatic pagination
- 1y agoEpiNow2Patch for an upstream rstan issue
- 1y agoEpiNow2Accumulation for irregularly reported data; unified priors
- 1y agoEpiNow2Matern kernel spectral density fix and GP prior revert
- 1y agoEpiNow2Gaussian Process model improvements and explicit defaults
Frequently asked questions
What is the difference between clinify and EpiNow2?
Both compete on the same themes — r-package — within Analytics. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 clinify better than EpiNow2?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 clinify?
Top clinify alternatives in Analytics are ranked by recent ship velocity. Browse the "clinify alternatives" section above for the current picks, or visit /alternatives/clinify-r for the full list with editorial commentary on each.
What are the best alternatives to EpiNow2?
Top EpiNow2 alternatives in Analytics are ranked by recent ship velocity. Browse the "EpiNow2 alternatives" section above for the current picks, or visit /alternatives/epinow2 for the full list with editorial commentary on each.