← Back to home
Comparison · Infra & APIs

campsis vs humind

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

Shared themes:breaking-changes

campsis vs humind: at a glance

Featurecampsishumind
SectorInfra & APIsInfra & APIs
Velocity score3.83.8
Sparks · 30d11
Top themespharmacometrics, clinical-trial-simulation, breaking-changes, json-interfacehumanitarian-analytics, needs-assessment, r-package, breaking-changes
Last editorial update1h ago39m 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 humind?

The MSNI humanitarian needs framework as code, rewritten and re-broken every year

humind turns household survey data into Multi-Sector Needs Index severity scores across WASH, Protection, SNFI, Food Security, Education and Health. Its version line tracks the annual MSNI framework revision — 2024.x, 2025.x, 2026.x — with narrow correctness patches between rollouts. v2026.2.0 is the current rollout and the most structural one in the visible history: water-quantity scoring moved out into a new mandatory prerequisite, food-security severity now comes from a different matrix, and the impactR4PHU runtime dependency is gone.

Read the full humind trajectory →

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

H
humind
INFRA · APIS
3.8

The MSNI humanitarian needs framework as code, rewritten and re-broken every year

◆ Current state

humind turns household survey data into Multi-Sector Needs Index severity scores across WASH, Protection, SNFI, Food Security, Education and Health. Its version line tracks the annual MSNI framework revision — 2024.x, 2025.x, 2026.x — with narrow correctness patches between rollouts. v2026.2.0 is the current rollout and the most structural one in the visible history: water-quantity scoring moved out into a new mandatory prerequisite, food-security severity now comes from a different matrix, and the impactR4PHU runtime dependency is gone.

◆ Where it's heading

Two things move together. The framework content is revised yearly — indicators added, weights corrected, instruments swapped — and the package keeps absorbing pipeline it used to delegate, most visibly by vendoring add_fcs(), add_hhs(), add_rcsi(), add_lcsi() and add_fcm_phase() locally rather than importing them. Each rollout is explicitly breaking and the release notes have grown per-function 'Action:' instructions, which reads as maintainers who expect every downstream dashboard to need rewiring on the same annual clock.

◆ Prediction

The 2025 line settled into narrow patches immediately after its rollout — 1.2, 1.3 and 1.4 fixed a separator argument, a schema rename and a shelter misclassification rather than adding indicators. Expect the 2026 line to do the same: correctness fixes against the new WASH, FCLCM and shelter-damage logic before any further framework change.

Alternatives to campsis and humind

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

See all campsis alternatives → · See all humind alternatives →

Recent activity from campsis and humind

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

  1. 15d agocampsissnake_case across the API; RxODE compatibility removed
  2. 29d agohumind2026 MSNI rollout: HWISE-4 prerequisite, FCLCM, impactR4PHU dropped
  3. 5mo agocampsisJSON arguments reach Dataset, Scenarios and Settings
  4. 7mo agocampsisMaintenance release for future package warnings
  5. 7mo agocampsisJSON import for Campsis datasets
  6. 8mo agohumindTents reclassified as inadequate shelter
  7. 10mo agohumindFix: honour the sep argument in protection score columns
  8. 10mo agohumind'Acute need' renamed to 'severe need' across every output column
  9. 1y agohumind2025 MSNI rollout: Protection revamped, WGQ dropped from Health
  10. 1y agocampsisDosing gains vectorized compartments and cycle repetition
  11. 1y agocampsisParameter uncertainty from SIR and bootstrap output
  12. 1y agohumindScoring corrections across WASH, education, health and shelter

Frequently asked questions

What is the difference between campsis and humind?

Both compete on the same themes — breaking-changes — within Infra & APIs. campsis and humind are shipping at a similar cadence (velocity 3.8 vs 3.8, 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 campsis better than humind?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. campsis and humind are shipping at a similar cadence (velocity 3.8 vs 3.8, both within Sparkpulse's "active" band). 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 humind?

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