TidyDensity
A distribution catalogue that grows by one family at a time, and rarely breaks anything.
Comparison · Analytics
intsurv vs randomwalk
A side-by-side editorial comparison of intsurv and randomwalk — release velocity, themes, recent moves, and the top alternatives to consider.
intsurv vs randomwalk: at a glance
What is intsurv?
A Cox cure-rate model package woke up after four years to simplify its own interface.
intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.
What is randomwalk?
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
intsurv vs randomwalk: editorial side-by-side
intsurv
0.0ANALYTICS
A Cox cure-rate model package woke up after four years to simplify its own interface.
◆ Current state
intsurv fits Cox cure rate models for right-censored survival data where event status may be uncertain — the case where you cannot tell whether a subject experienced the event or was never susceptible to it. The core has been stable since 2019: cox_cure() and its regularized counterpart cox_cure_net(), plus a weighted concordance index and a data simulator. After more than four years without a release, version 0.3.0 arrived in September 2025 and restructured how those two functions are configured rather than adding capability.
◆ Where it's heading
The package has reached the point where the methods are settled and the remaining work is ergonomics. Moving control parameters, M-step settings and penalty specification into cox_cure.control(), cox_cure.mstep() and cox_cure_net.penalty() follows the established R convention of separating tuning from the model formula, and it arrives long after the arguments accumulated. The C++ headers were placed in inst/include as early as 2019 so other packages could link against them, which suggests the implementation was always intended to be reused.
◆ Prediction
The gap between 0.2.2 and 0.3.0 makes cadence a poor basis for prediction. What the entries do support is that the interface rework is unfinished business rather than a prelude to new methods, so consolidation around the new helper functions is the likelier next step.
randomwalk
0.0ANALYTICS
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
◆ Current state
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
◆ Where it's heading
The package is being built as a browser artifact first and an R package second: the readme, the vignettes and the release notes all point at a hosted dashboard rather than at library(). The last release completes that by making the compiled WebAssembly build installable by anyone via webr::install(), which turns the deployment work into something reusable outside this project. Version numbers are unreliable here — v0.2.0 was published two weeks after v1.0.2 — so read the dates, not the tags.
◆ Prediction
With the webR repository published, the next work most likely moves back to the simulation itself, though the entries give no direct evidence of planned features.
Alternatives to intsurv and randomwalk
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 intsurv or randomwalk.
cfbfastr
College football's open data client hit v2 — and now reports how many API calls you have left.
rnpn
The USA phenology data client rebuilt its entire stack and stopped handing users -9999 as a number.
GeneNMF
GeneNMF rebuilt how it derives meta-programs, changing every result it had produced.
rempsyc
Publication-ready psychology tables and plots, tracking APA style as closely as the software allows.
sdsfun
A spatial-statistics utility package exists to be depended on, and is built accordingly.
See all intsurv alternatives → · See all randomwalk alternatives →
Recent activity from intsurv and randomwalk
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 8mo agorandomwalkPackage published as an installable webR binary repository
- 8mo agorandomwalkTermination validation removes isolated pixels from simulations
- 8mo agorandomwalkAsync dashboard with crew workers running under WebR
- 9mo agorandomwalkBrowser dashboard working end to end
- 9mo agorandomwalkMissing plot dependency and parameter display fixed
- 9mo agorandomwalkDashboard mounts WebAssembly from GitHub releases
- 10mo agointsurvModel configuration moves into dedicated control functions
- 5y agointsurvCross-validated model selection and offset terms added
- 6y agointsurvC++ headers relocated so other packages can link them
- 7y agointsurvCox cure models for uncertain event status arrive
- 7y agointsurvParameter initialization methods added to the alpha
- 7y agointsurvAlpha cut for paper submission and simulation reproducibility
Frequently asked questions
What is the difference between intsurv and randomwalk?
They serve adjacent needs but don't currently overlap on shipped themes. intsurv and randomwalk 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 intsurv better than randomwalk?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. intsurv and randomwalk 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 intsurv?
Top intsurv alternatives in Analytics are ranked by recent ship velocity. Browse the "intsurv alternatives" section above for the current picks, or visit /alternatives/intsurv for the full list with editorial commentary on each.
What are the best alternatives to randomwalk?
Top randomwalk alternatives in Analytics are ranked by recent ship velocity. Browse the "randomwalk alternatives" section above for the current picks, or visit /alternatives/randomwalk for the full list with editorial commentary on each.