rjd3highfreq
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
A side-by-side editorial comparison of gtsummary and n1qn1c — release velocity, themes, recent moves, and the top alternatives to consider.
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
n1qn1c is a quasi-Newton optimization routine translated from Fortran to C, used as a solver backend by the nlmixr2 modeling stack rather than called directly by most users. Its two 2026 releases are a concentrated safety pass: global state converted to thread_local, static removed from local variables in the translated code, integer overflow guards added, and memory leaks closed in the R callback wrappers — plus the gcc-asan and valgrind fixes CRAN asked for.
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
The ARD work is the through-line. Table IDs exist so gather_ard() can return a named list; hierarchical tables gained per-level sorting and targeted filtering; ARD inputs are pre-processed so sorting applies to non-standard shapes. The package is becoming a structured-results engine that happens to render tables, rather than a renderer alone. Alongside that, 2.2.0 restored data pre-processing that 2.0 had removed after the reduced functionality hurt users — a maintainer willing to reverse a major-version decision.
Expect the hierarchical and ARD functions, introduced as a preview without a full deprecation cycle, to keep stabilizing toward a settled API rather than new table types appearing.
n1qn1c is a quasi-Newton optimization routine translated from Fortran to C, used as a solver backend by the nlmixr2 modeling stack rather than called directly by most users. Its two 2026 releases are a concentrated safety pass: global state converted to thread_local, static removed from local variables in the translated code, integer overflow guards added, and memory leaks closed in the R callback wrappers — plus the gcc-asan and valgrind fixes CRAN asked for.
The package is being hardened for use inside a parallel modeling framework rather than extended. The audit that produced the thread-safety work also surfaced two plain bugs in features users would have assumed worked: restart = TRUE left the mode at 2 instead of 3 because of a typo, and assign = TRUE referenced the wrong field name so the compressed Hessian was never written to the supplied environment. Earlier work points the same direction — the 6.0.1-12 function-pointer interface exists so nlmixr2est does not need resubmission when this package changes.
Expect further memory-safety and sanitizer work rather than algorithmic change; a Fortran-translated numerical core under CRAN's checking regime generates that kind of release indefinitely.
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 gtsummary or n1qn1c.
rjd3highfreq ships whatever the Java side ships, and only occasionally says what that was.
audubon's release feed is almost entirely Renovate bumping the JavaScript toolchain behind its Japanese text splitter.
affiner is quietly turning a grid transformation helper into a small computational geometry library.
ageproR spent two years chasing a moving file format, then added the recruitment models that justify the effort.
ledger adds a Rust toolchain fallback, so beancount imports work whether or not the Python tooling is installed.
gridpattern keeps widening its catalogue, and the newest patterns finally use the device's own line rendering.
See all gtsummary alternatives → · See all n1qn1c alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. gtsummary and n1qn1c 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. gtsummary and n1qn1c 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.
Top gtsummary alternatives in Analytics are ranked by recent ship velocity. Browse the "gtsummary alternatives" section above for the current picks, or visit /alternatives/gtsummary-r for the full list with editorial commentary on each.
Top n1qn1c alternatives in Analytics are ranked by recent ship velocity. Browse the "n1qn1c alternatives" section above for the current picks, or visit /alternatives/n1qn1c for the full list with editorial commentary on each.