← Back to home
Comparison · Infra & APIs

campsis vs multimark

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

campsis vs multimark: at a glance

Featurecampsismultimark
SectorInfra & APIsInfra & APIs
Velocity score3.80.0
Sparks · 30d10
Top themespharmacometrics, clinical-trial-simulation, breaking-changes, json-interfacecapture-recapture, mcmc, maintenance, cran
Last editorial update6h ago53m 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 multimark?

Five years of compiler and CRAN fixes on a capture-recapture package.

multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.

Read the full multimark trajectory →

campsis vs multimark: 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.

M
multimark
INFRA · APIS
0.0

Five years of compiler and CRAN fixes on a capture-recapture package.

◆ Current state

multimark fits capture-mark-recapture models for populations sampled with multiple non-invasive marks, including a spatial variant. Nothing in the visible history changes the models. Every recent release responds to something outside the package: a CRAN check, a compiler flag, or an upstream package that stopped exporting a function.

◆ Where it's heading

This is preservation rather than development. The one substantive entry, in 2021, corrected an MCMC error in multimarkClosedSCR() serious enough that the author told users to revisit past analyses; everything since has been keeping the C code compiling across platforms. Release intervals now stretch to years.

◆ Prediction

Expect the pattern to hold, with a release whenever a toolchain or upstream dependency forces one and no change to the samplers.

Alternatives to campsis and multimark

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 multimark.

See all campsis alternatives → · See all multimark alternatives →

Recent activity from campsis and multimark

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

  1. 15d agocampsissnake_case across the API; RxODE compatibility removed
  2. 5mo agocampsisJSON arguments reach Dataset, Scenarios and Settings
  3. 7mo agocampsisMaintenance release for future package warnings
  4. 7mo agocampsisJSON import for Campsis datasets
  5. 8mo agomultimarkBrobdingnag sum import dropped after upstream removal
  6. 1y agocampsisDosing gains vectorized compartments and cycle repetition
  7. 1y agocampsisParameter uncertainty from SIR and bootstrap output
  8. 3y agomultimarkr-devel error fixed at CRAN's request
  9. 3y agomultimarkLinux compilation warnings cleared
  10. 4y agomultimarkFedora build error fixed at CRAN's request
  11. 4y agomultimarkMCMC detection-probability bug fixed in multimarkClosedSCR()
  12. 4y agomultimarkUnused parallelism dependencies removed

Frequently asked questions

What is the difference between campsis and multimark?

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 multimark?

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 multimark?

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