← Back to home
Comparison · Analytics

BORG vs SSN2

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

Shared themes:spatial-statisticsr-package

BORG vs SSN2: at a glance

FeatureBORGSSN2
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themescross-validation, spatial-statistics, model-validation, reproducibilityspatial-statistics, stream-networks, kriging, large-data
Last editorial update25m ago21m ago
WebsiteVisit →Visit →

What is BORG?

A cross-validation guard that refuses to run random CV on dependent data unless you insist

BORG detects spatial, temporal and clustered dependence in a modelling dataset and generates a cross-validation scheme that respects it — spatial blocks, temporal blocks, group folds — rather than letting random splits leak information between train and test. Its distinguishing choice is enforcement: when it finds dependence, random CV is blocked outright and needs an explicit allow_random=TRUE to proceed. The package also wraps the standard rsample and caret entry points so the guard applies inside existing workflows.

Read the full BORG trajectory →

What is SSN2?

Stream-network spatial models learning to run on data that no longer fits in memory

SSN2 fits spatial statistical models on stream networks, where covariance follows flow-connected distance along the network rather than straight-line distance. It is the maintained successor to the original SSN package, published through JOSS in 2024, and leans on spmodel for its underlying model machinery. Recent releases have concentrated on the constraint that binds this class of model hardest: the distance matrix.

Read the full SSN2 trajectory →

BORG vs SSN2: editorial side-by-side

B
BORG
ANALYTICS
0.0

A cross-validation guard that refuses to run random CV on dependent data unless you insist

◆ Current state

BORG detects spatial, temporal and clustered dependence in a modelling dataset and generates a cross-validation scheme that respects it — spatial blocks, temporal blocks, group folds — rather than letting random splits leak information between train and test. Its distinguishing choice is enforcement: when it finds dependence, random CV is blocked outright and needs an explicit allow_random=TRUE to proceed. The package also wraps the standard rsample and caret entry points so the guard applies inside existing workflows.

◆ Where it's heading

The entire visible history is a single day, and the sequence within it is coherent rather than churn: enforcement first, then the evidence layer, then framework integration, then idiomatic R polish. The evidence work matters to the pitch — borg_compare_cv() runs random against blocked CV so users see the inflation on their own data instead of taking the warning on faith, and the methods-text and certificate exports are aimed squarely at getting this into published papers. By the final release the interface has been rebuilt on standard S3 plot and summary methods.

◆ Prediction

The wrappers so far cover rsample and caret; tidymodels and mlr3 are the obvious remaining entry points if the guard is to reach the workflows it hasn't yet intercepted.

S
SSN2
ANALYTICS
0.0

Stream-network spatial models learning to run on data that no longer fits in memory

◆ Current state

SSN2 fits spatial statistical models on stream networks, where covariance follows flow-connected distance along the network rather than straight-line distance. It is the maintained successor to the original SSN package, published through JOSS in 2024, and leans on spmodel for its underlying model machinery. Recent releases have concentrated on the constraint that binds this class of model hardest: the distance matrix.

◆ Where it's heading

The first year was about establishing credibility and interoperability — a JOSS review, geopackage import support, deprecation of the SSN-to-SSN2 bridge, marginal means through emmeans. The 2025 releases turn to scale, moving distance matrices onto disk via filematrix and routing estimation and prediction through the local approximation. The 0.4.0 default change is the visible consequence: the neighbourhood size rises from 100 to 200, buying accuracy now that the surrounding machinery can afford it.

◆ Prediction

With the large-data path established and its default just retuned, the next work most likely tightens that approximation further or extends it to the model classes the local argument does not yet cover.

Alternatives to BORG and SSN2

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 BORG or SSN2.

See all BORG alternatives → · See all SSN2 alternatives →

Recent activity from BORG and SSN2

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

  1. 7mo agoBORGInterface rebuilt on standard S3 plot and summary methods
  2. 7mo agoBORGGuarded wrappers for rsample and caret splitting functions
  3. 7mo agoBORGEmpirical inflation comparison and publication-ready reporting
  4. 7mo agoBORGRandom CV blocked by default when dependence is detected
  5. 7mo agoBORGVersion bump to 0.1.1
  6. 9mo agoSSN2Local neighbourhood default doubled to 200
  7. 10mo agoSSN2partition_factor regression fixed, spmodel floor raised
  8. 0y agoSSN2On-disk distance matrices lift the large-data ceiling
  9. 1y agoSSN2Numeric stability fix for beta-family models
  10. 2y agoSSN2Geopackage import support and the JOSS review release
  11. 2y agoSSN2Snapshot tag marking JOSS acceptance

Frequently asked questions

What is the difference between BORG and SSN2?

Both compete on the same themes — spatial-statistics, r-package — within Analytics. BORG and SSN2 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 BORG better than SSN2?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. BORG and SSN2 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 Analytics products to evaluate alongside.

What are the best alternatives to BORG?

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

What are the best alternatives to SSN2?

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