← Back to home
Comparison · Infra & APIs

rollupTree vs sdcMicro

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

rollupTree vs sdcMicro: at a glance

FeaturerollupTreesdcMicro
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesrecursive-computation, tree-structures, dag, engine-packagedisclosure-control, anonymization, llm-assisted-workflows, k-anonymity
Last editorial update44m ago1h ago
WebsiteVisit →Visit →

What is rollupTree?

The recursive-computation engine under massProps grows the accessors its consumer needed

rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.

Read the full rollupTree trajectory →

What is sdcMicro?

A 20-year anonymization toolbox now has a language model inside its refinement loop.

sdcMicro is the reference R implementation of statistical disclosure control — k-anonymity, local suppression, PRAM, microaggregation, record swapping — used by national statistical offices, with a Shiny GUI (sdcApp) as its second face. The feed shows a long GUI-maintenance era through 2018-2022 and then a gap, and the package that reappears in 5.8.2 has an AI_applyAnonymization() workflow and a query_llm() helper that the older entries know nothing about. The July release tunes that loop rather than introducing it.

Read the full sdcMicro trajectory →

rollupTree vs sdcMicro: editorial side-by-side

R
rollupTree
INFRA · APIS
0.0

The recursive-computation engine under massProps grows the accessors its consumer needed

◆ Current state

rollupTree performs recursive computations over tree and DAG structures — the generic engine that its author's massProps package uses to roll mass properties up an assembly breakdown. It is small and moves slowly: five releases in a year, of which two are README and vignette work. The current surface added row-level get and set accessors by key and by id at 0.4.0.

◆ Where it's heading

The package develops in response to its one visible consumer. The 0.4.0 accessors appeared in January 2026 and massProps switched to them thirteen days later; 0.4.1 then fixed missing column names in the setters, which is the kind of defect only real use surfaces. Before that, 0.3.0's default_validate_dag() extended validation past strict trees to directed acyclic graphs, widening what structures the engine will accept.

◆ Prediction

On the established pattern the next release will be whatever massProps needs next, discovered by using it. A DAG validator suggests non-tree structures are in scope, but nothing in these notes says that path is being pushed further.

S
sdcMicro
INFRA · APIS
0.0

A 20-year anonymization toolbox now has a language model inside its refinement loop.

◆ Current state

sdcMicro is the reference R implementation of statistical disclosure control — k-anonymity, local suppression, PRAM, microaggregation, record swapping — used by national statistical offices, with a Shiny GUI (sdcApp) as its second face. The feed shows a long GUI-maintenance era through 2018-2022 and then a gap, and the package that reappears in 5.8.2 has an AI_applyAnonymization() workflow and a query_llm() helper that the older entries know nothing about. The July release tunes that loop rather than introducing it.

◆ Where it's heading

Two threads run in parallel. The visible one is the LLM-assisted anonymization path maturing: 5.8.2 gives its refinement loop early stopping via tol and patience so it stops when the combined utility score plateaus instead of burning all max_iter rounds, and teaches query_llm() to drop the temperature parameter for reasoning models that reject it. The other is unglamorous statistical correctness — a distinct l-diversity computation fixed for NAs in key variables, with the C++ simplified and tests added. The release also ships reproducibility scripts for a SoftwareX paper, which suggests the AI path is being written up rather than quietly trialled.

◆ Prediction

The provider-compatibility fix is reactive — a parameter dropped because one model family rejected it — so expect more of the same as query_llm() meets other backends. Given tol and patience were added to stop wasted iterations, cost or runtime of the refinement loop is the live concern, and further controls on it are the likeliest next move.

Alternatives to rollupTree and sdcMicro

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 rollupTree or sdcMicro.

See all rollupTree alternatives → · See all sdcMicro alternatives →

Recent activity from rollupTree and sdcMicro

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

  1. 1mo agosdcMicroEarly stopping for the AI anonymization loop, plus GPT-5.x support
  2. 6mo agorollupTreeMissing column names in the new row setters
  3. 6mo agorollupTreeRow-level get and set accessors by key and by id
  4. 1y agorollupTreeMinor vignette improvements
  5. 1y agorollupTreeBadges and GitHub Actions added to the README
  6. 1y agorollupTreedefault_validate_dag() extends validation past strict trees
  7. 4y agosdcMicrorecordSwap() adds targeted record swapping
  8. 5y agosdcMicroTwo new information-loss measures and a run of sdcApp fixes
  9. 5y agosdcMicroCompatibility fixes for R 4.1 sorting and rsconnect deployment
  10. 8y agosdcMicroMinor release, mostly GUI work
  11. 8y agosdcMicrodUtility() corrected so IL1 and IL1s can be distinguished

Frequently asked questions

What is the difference between rollupTree and sdcMicro?

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

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

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

What are the best alternatives to sdcMicro?

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