← Back to home
Comparison · Infra & APIs

rsofun vs surveycore

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

rsofun vs surveycore: at a glance

Featurersofunsurveycore
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesecosystem-modelling, carbon-isotopes, land-use-change, fortransurvey-statistics, variance-estimation, replicate-weights, api-stability
Last editorial update59m ago3h ago
WebsiteVisit →Visit →

What is rsofun?

An ecosystem model starts tracking carbon isotopes and land-use change.

rsofun wraps the P-model and BiomeE vegetation models in R with Fortran cores, covering photosynthesis, water balance and forest demography, plus Bayesian calibration. The 5.1.0 release is the first in the window to widen what the models simulate rather than reorganise them. Before it, the history is renaming, cost-function rewrites and output-format consistency work.

Read the full rsofun trajectory →

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.

Read the full surveycore trajectory →

rsofun vs surveycore: editorial side-by-side

R
rsofun
INFRA · APIS
0.0

An ecosystem model starts tracking carbon isotopes and land-use change.

◆ Current state

rsofun wraps the P-model and BiomeE vegetation models in R with Fortran cores, covering photosynthesis, water balance and forest demography, plus Bayesian calibration. The 5.1.0 release is the first in the window to widen what the models simulate rather than reorganise them. Before it, the history is renaming, cost-function rewrites and output-format consistency work.

◆ Where it's heading

The direction is from a calibration harness toward a model that can answer different questions: isotope fractionation now comes out of the P-model, BiomeE handles land use and land-use change, and forcing can be recycled when a simulation outruns its data. Version stamps are unreliable here, with a v5.0 tag carrying only a build fix and predating v4.4, so the arc reads better through content than through numbering.

◆ Prediction

The isotope work is explicitly unfinished, with a constant atmospheric signature standing in for daily d13c forcing, so the next likely step is accepting that as model input.

S
surveycore
INFRA · APIS
0.0

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 rsofun 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 rsofun or surveycore.

See all rsofun alternatives → · See all surveycore alternatives →

Recent activity from rsofun and surveycore

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

  1. 2mo agosurveycoreFirst stable release: all four survey design types complete
  2. 3mo agosurveycoreget_effective_n() computes effective sample size
  3. 3mo agosurveycoreCollections error on divergent grouping; .on_missing renamed
  4. 4mo agosurveycoreCRAN patch removing surveytidy from the vignette
  5. 10mo agorsofunCarbon isotope tracking and LULUC support across both models
  6. 1y agorsofunLM3-PPA renamed BiomeE; cost function and stress functions rewritten
  7. 1y agorsofunParallel make fix on the v5.0 tag
  8. 2y agorsofuncnmodel 0.1 research snapshot tag
  9. 4y agorsofunFortran crash guards and consistent P-model variable names
  10. 4y agorsofunPublic release following a code refactor

Frequently asked questions

What is the difference between rsofun and surveycore?

They serve adjacent needs but don't currently overlap on shipped themes. rsofun 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 rsofun better than surveycore?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. rsofun 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 rsofun?

Top rsofun alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "rsofun alternatives" section above for the current picks, or visit /alternatives/rsofun 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.