← Back to home
Comparison · Analytics

DoseFinding vs nanonext

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

DoseFinding vs nanonext: at a glance

FeatureDoseFindingnanonext
SectorAnalyticsAnalytics
Velocity score0.02.5
Sparks · 30d00
Top themesdose-response, mcp-mod, clinical-trials, model-averagingasync-messaging, nng, http-server, memory-safety
Last editorial update1h ago6h ago
WebsiteVisit →Visit →

What is DoseFinding?

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

Read the full DoseFinding trajectory →

What is nanonext?

nanonext keeps shrinking its build requirements while adding messaging primitives.

The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.

Read the full nanonext trajectory →

DoseFinding vs nanonext: editorial side-by-side

D
DoseFinding
ANALYTICS
0.0

New stewardship at openpharma, then two releases adding the methods MCP-Mod was missing

◆ Current state

DoseFinding implements MCP-Mod and related dose-response methodology for clinical trial design and analysis. In 2024 it changed hands — Marius Thomas took over as maintainer, Novartis was recorded as copyright holder and funder, and the package moved to the openpharma GitHub organisation with roxygen documentation and a proper NEWS file. The two releases since have added substantive methodology: model averaging for dose-response fitting in 1.3-1, and conditional and predictive power for interim analyses in 1.4-1.

◆ Where it's heading

The pattern before the handover was maintenance — R-devel compliance, a bug fix, a link. After it, each release carries a named methodological addition with an acknowledged contributor, plus documentation to match: a longitudinal analysis vignette shipped alongside the interim power work. Housekeeping continues underneath, mostly clearing deprecated ggplot2 interfaces, aes_string in one release and qplot in the next.

◆ Prediction

Given the last two releases each added one method with a supporting vignette, expect the next to follow the same shape. Both additions so far extend the package beyond fixed dose-response fitting, so adaptive and interim methodology is the more likely direction.

N
nanonext
ANALYTICS
2.5

nanonext keeps shrinking its build requirements while adding messaging primitives.

◆ Current state

The R binding to NNG ships roughly monthly. Since February the package added an HTTP server that can run synchronously or through the later event loop, a zero-copy device forwarder for building brokers and proxies, and support for pthread-enabled WebAssembly targets. Send operations now move the buffer straight into the NNG message, halving peak memory on serialized sends.

◆ Where it's heading

Two directions run in parallel. One is making the package installable anywhere — the build-time cmake dependency is gone, so compiling bundled NNG and Mbed TLS needs only a C compiler, and WebAssembly targets are supported. The other is raising the ceiling on what can be built on top: device_aio() for message forwarding, an HTTP and WebSocket server with a content map, and stream buffer control. Bug fixes in recent releases concentrate on memory safety in the bundled C sources.

◆ Prediction

Given the pace and the tight coupling declared in each release, expect the next version to track a mirai requirement and continue hardening the HTTP server paths that the last two releases have been leaking memory in.

Alternatives to DoseFinding and nanonext

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 DoseFinding or nanonext.

See all DoseFinding alternatives → · See all nanonext alternatives →

Recent activity from DoseFinding and nanonext

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

  1. 10d agonanonextMemory leaks and a TLS use-after-free fixed in the HTTP server
  2. 1mo agonanonextEvent-loop integration for HTTP and WebSocket callbacks
  3. 1mo agonanonextZero-copy message forwarding, and cmake dropped from the build
  4. 2mo agonanonextBuilds against pthread-enabled WebAssembly targets
  5. 3mo agonanonextSerialized sends drop a copy and halve peak memory
  6. 4mo agonanonextBlocking HTTP server mode and stream buffer sizing
  7. 1y agoDoseFindingConditional and predictive power for interim analyses
  8. 1y agoDoseFindingModel averaging arrives for dose-response fitting
  9. 1y agoDoseFindingPackage moves to openpharma under new maintainership
  10. 2y agoDoseFindingCompliance update for R-devel
  11. 3y agoDoseFindingpowMCTBinCount bug fix

Frequently asked questions

What is the difference between DoseFinding and nanonext?

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

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

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

What are the best alternatives to nanonext?

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