← Back to home
Comparison · Infra & APIs

campsis vs watcher

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

campsis vs watcher: at a glance

Featurecampsiswatcher
SectorInfra & APIsInfra & APIs
Velocity score3.80.0
Sparks · 30d10
Top themespharmacometrics, clinical-trial-simulation, breaking-changes, json-interfacefilesystem-events, r6, build-portability, c-bindings
Last editorial update2h ago6d ago
WebsiteVisit →Visit →

What is campsis?

Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.

Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.

Read the full campsis trajectory →

What is watcher?

watcher is a thin filesystem-events binding whose releases are mostly build work.

The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.

Read the full watcher trajectory →

campsis vs watcher: editorial side-by-side

C
campsis
INFRA · APIS
3.8

Campsis breaks its API on purpose: snake_case throughout, RxODE compatibility cut loose.

◆ Current state

Campsis runs clinical-trial simulations from pharmacometric models, sitting on mrgsolve and rxode2 as interchangeable engines, with the sibling package Campsismod supplying the model object layer. Version 1.9.0 is the release where the suite stops carrying its history: the whole API migrates to snake_case, backward compatibility with the old RxODE package is removed, and result processing is refactored into output functions that can be applied as a collection, with an NCA table the first substantial one. Campsismod made the same snake_case move a week earlier, so this is a suite-wide rename rather than one package's decision.

◆ Where it's heading

The 1.8 and 1.9 releases together describe a package being made drivable from outside R. JSON interfaces arrived first for models in Campsismod 1.3.0 and for datasets in Campsis 1.8.0, then extended to scenarios, settings and study replication; the output side has now been generalised the same way, from fixed result processing to a collection of output functions applied to simulated results. Renaming every function and cutting RxODE loose is the cost of that consolidation, paid in one deliberate breaking release rather than spread across several.

◆ Prediction

With the rename and the RxODE removal behind it, the next releases should restore the rxode2 engine to the test suite, which 1.9.0 removed temporarily, and continue filling out the output-function catalogue beyond NCA. The JSON surface looks like the intended entry point for driving Campsis from outside R, though the entries do not say what is meant to consume it.

W
watcher
INFRA · APIS
0.0

watcher is a thin filesystem-events binding whose releases are mostly build work.

◆ Current state

The package wraps libfswatch in an R6 Watcher class for monitoring files and directories. Seven releases over sixteen months have added a vector path argument and two accessor methods, and spent the rest of their effort on build portability — non-standard system library locations, Windows bi-arch source builds on old rtools, and most recently removing the cmake requirement so the bundled source compiles with the R toolchain alone.

◆ Where it's heading

The API is deliberately small and appears finished; the work that remains is making the C dependency install cleanly everywhere. Dropping cmake follows the same move nanonext made, which is not a coincidence — both come from the same author and both are aiming at environments where installing a build system is not an option.

◆ Prediction

With cmake gone and the bundled library current, further releases are most likely to track libfswatch upstream rather than extend the R interface.

Alternatives to campsis and watcher

Other Infra & APIs 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 campsis or watcher.

See all campsis alternatives → · See all watcher alternatives →

Recent activity from campsis and watcher

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

  1. 15d agocampsissnake_case across the API; RxODE compatibility removed
  2. 1mo agowatchercmake dropped from the bundled library build
  3. 3mo agowatcherBundled libfswatch updated to 1.20.1
  4. 5mo agocampsisJSON arguments reach Dataset, Scenarios and Settings
  5. 7mo agocampsisMaintenance release for future package warnings
  6. 7mo agocampsisJSON import for Campsis datasets
  7. 8mo agowatcherWindows CPU usage fix for sub-second latency
  8. 1y agowatcherSystem libfswatch found in non-standard locations
  9. 1y agowatcherMultiple paths per watcher, and older Windows builds fixed
  10. 1y agocampsisDosing gains vectorized compartments and cycle repetition
  11. 1y agowatcherAccessor methods replace public Watcher fields
  12. 1y agocampsisParameter uncertainty from SIR and bootstrap output

Frequently asked questions

What is the difference between campsis and watcher?

They serve adjacent needs but don't currently overlap on shipped themes. campsis is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 campsis better than watcher?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. campsis is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to campsis?

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

What are the best alternatives to watcher?

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