← Back to home
Comparison · Infra & APIs

campsis vs tf

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

campsis vs tf: at a glance

Featurecampsistf
SectorInfra & APIsInfra & APIs
Velocity score3.80.0
Sparks · 30d10
Top themespharmacometrics, clinical-trial-simulation, breaking-changes, json-interfacefunctional-data-analysis, vctrs, multivariate, r-packages
Last editorial update3h ago52m 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 tf?

tf gave functional data a second dimension: curves whose values are vectors.

tf supplies the vector classes underneath the tidyfun stack — tfd for raw functional observations, tfb for basis-represented ones, both built on vctrs so curves sit in a data frame column and behave like any other vector. Until July that codomain was scalar. The 0.5.0 release adds tfd_mv and tfb_mv, classes for functions whose values are vectors in R^d, and rebuilds the analysis verbs to match.

Read the full tf trajectory →

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

T
tf
INFRA · APIS
0.0

tf gave functional data a second dimension: curves whose values are vectors.

◆ Current state

tf supplies the vector classes underneath the tidyfun stack — tfd for raw functional observations, tfb for basis-represented ones, both built on vctrs so curves sit in a data frame column and behave like any other vector. Until July that codomain was scalar. The 0.5.0 release adds tfd_mv and tfb_mv, classes for functions whose values are vectors in R^d, and rebuilds the analysis verbs to match.

◆ Where it's heading

The package is widening what a functional observation can be, then porting the toolkit onto it. Registration arrived first in 0.4.0 for univariate curves and immediately gained an srvf_mv method for aligning components jointly, and tfb_mfpc() ports principal component analysis to the multivariate case with a single set of scores shared across components. Alongside that runs steady dependency shedding — mvtnorm and pracma both replaced by inlined samplers that reproduce prior draws bit-for-bit, glue dropped for cli in the previous release — and an unusually long tail of NA-handling and edge-case fixes, several caught in pre-release review of the new classes.

◆ Prediction

The new classes ship with FPCA, registration and shape alignment but the release notes describe tidyfun::tf_unnest() as the consumer of one new export, so the visible next step is the rest of the tidyfun stack catching up to vector-valued columns. Expect follow-up patches on the vctrs casting paths, which is where most of this release's late fixes clustered.

Alternatives to campsis and tf

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

See all campsis alternatives → · See all tf alternatives →

Recent activity from campsis and tf

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

  1. 15d agocampsissnake_case across the API; RxODE compatibility removed
  2. 1mo agotfVector-valued functional data becomes a first-class type
  3. 5mo agotfCurve registration, five depth measures and sub-domain splitting
  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. 1y agocampsisDosing gains vectorized compartments and cycle repetition
  8. 1y agocampsisParameter uncertainty from SIR and bootstrap output
  9. 2y agotfFix: tf_crosscov normalization

Frequently asked questions

What is the difference between campsis and tf?

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

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

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