← Back to home
Comparison · Infra & APIs

campsis vs glcdp

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

campsis vs glcdp: at a glance

Featurecampsisglcdp
SectorInfra & APIsInfra & APIs
Velocity score3.86.3
Sparks · 30d11
Top themespharmacometrics, clinical-trial-simulation, breaking-changes, json-interfacer-packages, light-logging, data-standards, shiny
Last editorial update2h ago49m 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 glcdp?

glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.

glcdp imports light-logger data packages published to the GLC standard, driven by declared schemas rather than format-specific readers. 0.9.3 added glc_explore(), a Shiny application for browsing the registry and exporting an annotated reproducible script. 1.0.0 promotes schema 3.0.2 to the default and primary stable import contract and makes schema-declared variable types and factor-level order drive the import itself.

Read the full glcdp trajectory →

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

G
glcdp
INFRA · APIS
6.3

glcdp reaches 1.0.0 with a stable schema contract behind its data explorer.

◆ Current state

glcdp imports light-logger data packages published to the GLC standard, driven by declared schemas rather than format-specific readers. 0.9.3 added glc_explore(), a Shiny application for browsing the registry and exporting an annotated reproducible script. 1.0.0 promotes schema 3.0.2 to the default and primary stable import contract and makes schema-declared variable types and factor-level order drive the import itself.

◆ Where it's heading

The package is serving two audiences from one model. Programmatic users get glc_collect(), extract_metadata() and add_metadata(), with imports that reject file groups whose factor labels or level order disagree. Interactive users get an Explorer that filters by device, wearing position, modality, role and data state, pages large inventories at 100 rows, and caches remote metadata for immutable revisions. Schemas 1.0.0 and 2.0.0 stay reachable as barebones legacy paths.

◆ Prediction

With 3.0.2 named the primary stable contract and the older schemas explicitly labelled legacy, retiring the barebones paths is the most likely next structural move. The notes give no indication of work beyond the current schema line.

Alternatives to campsis and glcdp

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

See all campsis alternatives → · See all glcdp alternatives →

Recent activity from campsis and glcdp

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

  1. 13d agoglcdpSchema 3.0.2 becomes the default import contract
  2. 15d agocampsissnake_case across the API; RxODE compatibility removed
  3. 29d agoglcdpglc_explore() adds a Shiny browser and metadata joins
  4. 1mo agoglcdpLogo and favicon refresh
  5. 5mo agocampsisJSON arguments reach Dataset, Scenarios and Settings
  6. 7mo agocampsisMaintenance release for future package warnings
  7. 7mo agocampsisJSON import for Campsis datasets
  8. 1y agocampsisDosing gains vectorized compartments and cycle repetition
  9. 1y agocampsisParameter uncertainty from SIR and bootstrap output

Frequently asked questions

What is the difference between campsis and glcdp?

They serve adjacent needs but don't currently overlap on shipped themes. glcdp is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is campsis better than glcdp?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. glcdp is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. 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 glcdp?

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