← Back to home
Comparison · Analytics

icesSAG vs tulpa

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

icesSAG vs tulpa: at a glance

FeatureicesSAGtulpa
SectorAnalyticsAnalytics
Velocity score0.07.5
Sparks · 30d02
Top themesfisheries-science, api-client, ices, data-validationbayesian-inference, cran-release, r-packages, spatial-modeling
Last editorial update4d ago8h ago
WebsiteVisit →Visit →

What is icesSAG?

The ICES stock assessment client took upload away in 2024 and spent two years giving it back.

icesSAG is the R client for the ICES Stock Assessment Graphs database, used by fisheries scientists to retrieve and publish stock assessment summaries and figures. The 1.5.0 release repointed every function at a new API, replaced token authentication with JWT via icesConnect, and dropped file upload entirely. Upload returned in 1.6.2, now routing through icesDatsu to check file format and validate data before submission.

Read the full icesSAG trajectory →

What is tulpa?

The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.

tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.

Read the full tulpa trajectory →

icesSAG vs tulpa: editorial side-by-side

I
icesSAG
ANALYTICS
0.0

The ICES stock assessment client took upload away in 2024 and spent two years giving it back.

◆ Current state

icesSAG is the R client for the ICES Stock Assessment Graphs database, used by fisheries scientists to retrieve and publish stock assessment summaries and figures. The 1.5.0 release repointed every function at a new API, replaced token authentication with JWT via icesConnect, and dropped file upload entirely. Upload returned in 1.6.2, now routing through icesDatsu to check file format and validate data before submission.

◆ Where it's heading

The package is consolidating onto the shared ices-tools stack rather than carrying its own machinery — authentication moved to icesConnect, validation to icesDatsu, and the icesVocab dependency was dropped once it was no longer needed. Alongside that, redundant graph functions were deprecated and caching was added to reduce load on the server. Releases are infrequent and driven by upstream API changes.

◆ Prediction

Expect the next release to follow whatever the ICES service or the sibling ices-tools packages change next, rather than introducing new analysis capability of its own.

T
tulpa
ANALYTICS
7.5

The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.

◆ Current state

tulpa is the C++/R Bayesian spatial inference engine sitting under gcol33's family of ecological occupancy packages, tagging 0.0.x releases several times a week. 0.1.0 is its first CRAN release, and the notes state outright that the engine surface is unchanged from 0.0.198 — the work is packaging discipline: local T bindings rebound to n_t/n_times, OpenMP teams capped under R CMD check, the pkgdown deploy narrowed, an aspell dictionary added. The window behind it splits between the S3 generics conversion and numerical-correctness work in the nested-Laplace grid.

◆ Where it's heading

Two moves in nine days point at the same destination: the generics conversion made tulpa extensible by downstream packages, and CRAN admission makes it installable by them. The current cadence — several tags a week, some existing only to record a measurement that produced no code change — does not survive CRAN's submission overhead, so the release rhythm has to slow whether or not the project intends it. The correctness work still clusters on the joint nested-Laplace driver, and 0.1.0 extends the same diagnostics habit with .NL_AXIS_SD_REASONS, a closed vocabulary for an outer axis whose grid does not contain its own posterior mode.

◆ Prediction

Expect tulpaObs to follow tulpa onto CRAN, since it is the consumer whose registrations the engine has spent this window unblocking, and expect the version line to move in larger, less frequent steps now that each one carries a submission.

Alternatives to icesSAG and tulpa

Other Analytics 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 icesSAG or tulpa.

See all icesSAG alternatives → · See all tulpa alternatives →

Recent activity from icesSAG and tulpa

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

  1. 17h agotulpaFirst CRAN release: engine surface unchanged from 0.0.198
  2. 4d agotulpatulpa_re_aghq() exposes the mode/theta cross-Hessian
  3. 8d agotulpaDense batched joint path could silently drop a grid cell
  4. 8d agotulpaCalibration and goodness-of-fit entry points become S3 generics
  5. 9d agotulpaCUDA backend had two definitions; link order decided if it ran
  6. 9d agotulpaHyperparameter bounds now flag when they leave the node range
  7. 3mo agoicesSAGStock upload restored with pre-submission validation
  8. 1y agoicesSAGEvery function repointed at a new API, with JWT auth
  9. 6y agoicesSAGlocal release 1.3-5

Frequently asked questions

What is the difference between icesSAG and tulpa?

They serve adjacent needs but don't currently overlap on shipped themes. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 icesSAG better than tulpa?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. tulpa is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to icesSAG?

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

What are the best alternatives to tulpa?

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