← Back to home
Comparison · Infra & APIs

coga vs slendr

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

coga vs slendr: at a glance

Featurecogaslendr
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesprobability-distributions, gamma-convolution, rcpp, maintenance-modepopulation-genetics, simulation, tree-sequences, python-interop
Last editorial update1h ago1h ago
WebsiteVisit →Visit →

What is coga?

A gamma-convolution density package that reached completion in 2018 and has coasted since.

coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.

Read the full coga trajectory →

What is slendr?

Population-genetic simulation in R, opened up to selection and finally easier to install.

slendr specifies spatial and non-spatial population-genetic models in R and simulates them through SLiM or msprime, returning tree sequences that tskit then analyses. Two threads dominate the current releases: keeping in step with fast-moving backends, with SLiM 5.1, pyslim 1.1.0 and Python 3.13 now required, and reducing the setup burden that its Python dependency imposes. Version 1.5.0 adds ephemeral uv-based virtual environments, so init_env(uv = TRUE) can stand in for creating a permanent environment with setup_env().

Read the full slendr trajectory →

coga vs slendr: editorial side-by-side

C
coga
INFRA · APIS
0.0

A gamma-convolution density package that reached completion in 2018 and has coasted since.

◆ Current state

coga computes densities, distribution functions and random numbers for convolutions of gamma distributions, with the numerical work in C++ through Rcpp. It has been feature-complete since 1.0.0 in 2018, and every release in the seven years since has been maintenance: a documentation alias for CRAN, a compiler warning, a maintainer email change, and an Rcpp update requiring Rf_error calls to be guarded. The one functional addition in that period, in 1.1.0, was an unexported function added explicitly for research use.

◆ Where it's heading

This is a finished package being kept alive rather than developed. The releases track external pressure exactly: CRAN documentation requirements, compiler warnings, Rcpp API changes. Its maintenance is visibly shared with smam, the same maintainer's animal-movement package, which received the same email update, the same format-security fix and the same Rcpp guard within a minute or twenty of coga each time. Neither package is being extended; both are being kept installable.

◆ Prediction

Expect nothing but CRAN and toolchain maintenance, arriving whenever Rcpp or R's check requirements change, and arriving alongside smam. There is no signal in these entries of planned functional work.

S
slendr
INFRA · APIS
0.0

Population-genetic simulation in R, opened up to selection and finally easier to install.

◆ Current state

slendr specifies spatial and non-spatial population-genetic models in R and simulates them through SLiM or msprime, returning tree sequences that tskit then analyses. Two threads dominate the current releases: keeping in step with fast-moving backends, with SLiM 5.1, pyslim 1.1.0 and Python 3.13 now required, and reducing the setup burden that its Python dependency imposes. Version 1.5.0 adds ephemeral uv-based virtual environments, so init_env(uv = TRUE) can stand in for creating a permanent environment with setup_env().

◆ Where it's heading

Since the 1.0.0 release added non-neutral simulation, the work has shifted from capability to friction. A large share of recent notes concerns Python environment handling, conda activation races on Windows, dependency pruning that made shiny optional, and argument names that misled users, as when gene_flow()'s rate argument turned out to mean total ancestry proportion rather than a rate. That is the profile of a package whose scientific surface is settled and whose remaining problems are the ones users actually hit.

◆ Prediction

Expect the uv-based environment path to move from fallback to default once it has proven itself, given the notes already describe an environment variable for making it so. The deprecated rate argument in gene_flow() is explicitly slated for removal in a future major release, which is the clearest signal here of what a 2.0 would contain.

Alternatives to coga and slendr

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 coga or slendr.

See all coga alternatives → · See all slendr alternatives →

Recent activity from coga and slendr

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

  1. 1mo agoslendrEphemeral uv Python environments remove the setup step
  2. 5mo agocogaRcpp attributes regenerated; email updated
  3. 7mo agoslendrgene_flow() separates migration rate from ancestry proportion
  4. 9mo agoslendrshiny made optional; SLiM 5.1 and Python 3.13 required
  5. 1y agoslendrconda activation reverted to a slower but reliable path
  6. 1y agoslendrBackends raised to SLiM 5.0, tskit 0.6.4 and msprime 1.3.4
  7. 1y agoslendrNon-neutral models arrive; slim() interface simplified
  8. 2y agocogaMaintainer email updated
  9. 2y agocogaCompiler format-security warning resolved
  10. 3y agocogaPackage documentation alias added for CRAN
  11. 6y agocogaUnexported density variant added for research use
  12. 8y agocoga1.0.0 declares the package complete and documented

Frequently asked questions

What is the difference between coga and slendr?

They serve adjacent needs but don't currently overlap on shipped themes. coga and slendr are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 coga better than slendr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. coga and slendr are shipping at a similar cadence (velocity 0.0 vs 0.0, 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 coga?

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

What are the best alternatives to slendr?

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