pr2database
The protist reference database keeps widening past the rRNA gene it was built on.
Comparison · Infra & APIs
jSDM vs surveycore
A side-by-side editorial comparison of jSDM and surveycore — release velocity, themes, recent moves, and the top alternatives to consider.
jSDM vs surveycore: at a glance
What is jSDM?
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
jSDM fits joint species distribution models by Gibbs sampling, with the sampler written in C++ against GSL and Armadillo and exposed through binomial probit, binomial logit, Poisson log and Gaussian entry points. The 0.2 line extended it with species traits, constrained factor loadings and residual-association plots. The one entry since 2023 carries only a compare link.
What is surveycore?
surveycore declared its API stable with every survey design type covered.
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
jSDM vs surveycore: editorial side-by-side
jSDM
0.0INFRA · APIS
Joint species distribution models in Gibbs-sampled C++, quiet since 2023.
◆ Current state
jSDM fits joint species distribution models by Gibbs sampling, with the sampler written in C++ against GSL and Armadillo and exposed through binomial probit, binomial logit, Poisson log and Gaussian entry points. The 0.2 line extended it with species traits, constrained factor loadings and residual-association plots. The one entry since 2023 carries only a compare link.
◆ Where it's heading
The package built out its model family quickly and then stopped: five of the six visible entries are stamped the same day as a backfilled archive, and the only later release says nothing about its contents. The direction the 0.2 line was heading, toward trait-mediated species effects and better convergence on latent variable models, has no visible continuation.
◆ Prediction
The feed does not support a confident prediction; the latest entry publishes no notes, so whether the package is still developing or only being kept CRAN-clean cannot be read from it.
surveycore
0.0INFRA · APIS
surveycore declared its API stable with every survey design type covered.
◆ Current state
surveycore is the estimation engine of a two-package survey stack, handling design objects and variance estimation while surveytidy supplies the dplyr verbs on top. The June release marks it 1.0.0 and states the API is complete and stable across Taylor series linearization, replicate weights, two-phase and non-probability designs, with means, totals, frequencies, quantiles, ratios, correlations, regression, t-tests, ANOVA and effective sample size all in place.
◆ Where it's heading
The last months before 1.0.0 were spent making the awkward designs behave like the ordinary ones. Non-probability designs gained jackknife replicate schemes and got their bootstrap repweights routed through the replicate-weight variance estimator in survey_glm(), matching every other estimation function. The survey_collection abstraction — several surveys treated as one pseudo-data-frame — was tightened rather than extended: divergent grouping across members now errors instead of stitching a patchwork with bind_rows(), and the missing-variable argument was renamed and given a stored default on the collection itself. A documentation audit before 1.0.0 turned up six dispatch and print bugs and corrections across forty-plus files, which is the kind of thing that surfaces when an API is being frozen rather than extended.
◆ Prediction
A declared-stable API means the next releases should be additive or corrective rather than breaking, and the pre-1.0.0 pattern of breaking renames should stop. The tight version pinning between the two packages means surveytidy releases will keep following surveycore's.
Alternatives to jSDM and surveycore
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 jSDM or surveycore.
ggalign
Composable aligned layouts, rebuilt on S7 while ggplot2 4.0 lands underneath.
prioritizr
Conservation planning absorbs the literature's target-setting rules as code.
rsofun
An ecosystem model starts tracking carbon isotopes and land-use change.
usmap
Ten years in, US mapping splits its data out and finally adds Puerto Rico.
trackeR
Fitness-tracking analysis in slow maintenance, still absorbing upstream breakage.
See all jSDM alternatives → · See all surveycore alternatives →
Recent activity from jSDM and surveycore
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agosurveycoreFirst stable release: all four survey design types complete ⚡
- 3mo agosurveycoreget_effective_n() computes effective sample size
- 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
- 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
- 9mo agojSDMjSDM CRAN release v0.2.7: Joint Species Distribution Models
- 3y agojSDMSpecies traits, constrained loadings and association plots
- 3y agojSDMFirst release: C++ Gibbs sampler for joint species models ⚡
- 3y agojSDMResidual correlation functions can filter to significant values
- 3y agojSDMjSDM_gaussian() fits continuous data with overdispersion
- 3y agojSDMFour versions of CRAN check corrections
Frequently asked questions
What is the difference between jSDM and surveycore?
They serve adjacent needs but don't currently overlap on shipped themes. jSDM and surveycore 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 jSDM better than surveycore?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. jSDM and surveycore 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 jSDM?
Top jSDM alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "jSDM alternatives" section above for the current picks, or visit /alternatives/jsdm for the full list with editorial commentary on each.
What are the best alternatives to surveycore?
Top surveycore alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "surveycore alternatives" section above for the current picks, or visit /alternatives/surveycore for the full list with editorial commentary on each.