← Back to home
Comparison · Infra & APIs

sdcMicro vs selection.index

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

sdcMicro vs selection.index: at a glance

FeaturesdcMicroselection.index
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themesdisclosure-control, anonymization, llm-assisted-workflows, k-anonymityplant-breeding, selection-index, genomic-selection, rcpp
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

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 →

What is selection.index?

A dormant plant-breeding package returns as a genomic selection index suite

selection.index computes selection indices for plant breeding — weighting several traits into one number breeders can rank on. After two years of silence it shipped 2.0.0 in March 2026, and the package is barely recognisable: snake_case throughout, an Rcpp and RcppEigen computational core, and index families for genomic data, marker data, multi-stage trials and constrained genetic gain sitting beside the original phenotypic ones.

Read the full selection.index trajectory →

sdcMicro vs selection.index: editorial side-by-side

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.

S
selection.index
INFRA · APIS
0.0

A dormant plant-breeding package returns as a genomic selection index suite

◆ Current state

selection.index computes selection indices for plant breeding — weighting several traits into one number breeders can rank on. After two years of silence it shipped 2.0.0 in March 2026, and the package is barely recognisable: snake_case throughout, an Rcpp and RcppEigen computational core, and index families for genomic data, marker data, multi-stage trials and constrained genetic gain sitting beside the original phenotypic ones.

◆ Where it's heading

The first version series added one function at a time — combinatorial indices, then genetic advance, then mean performance under randomised block designs — against a fixed phenotypic framing. Version 2.0.0 abandons that framing rather than extending it. Genomic and marker information become inputs the package understands, multi-cycle simulation becomes a built-in toolset, and the old combinatorial entry points are replaced by a named lpsi(). The 2.0.1 follow-up is entirely CI and numerical-stability work, which reads like a maintainer bracing a much larger surface.

◆ Prediction

A seventeen-runner CI matrix mirroring every CRAN check flavour, added days after 2.0.0, says the immediate concern is keeping a compiled multi-family package green rather than adding to it. Expect stabilisation releases before anything new.

Alternatives to sdcMicro and selection.index

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 sdcMicro or selection.index.

See all sdcMicro alternatives → · See all selection.index alternatives →

Recent activity from sdcMicro and selection.index

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. 5mo agoselection.indexCI expanded to 17 runners after the 2.0.0 rewrite
  3. 5mo agoselection.indexGenomic, marker and multi-stage selection indices on an Rcpp core
  4. 6mo agoselection.indexUnspecified general performance improvements
  5. 2y agoselection.indexMean performance for randomised block designs
  6. 3y agoselection.indexsel.index() and sel.score.rank() removed for comb.indices()
  7. 4y agosdcMicrorecordSwap() adds targeted record swapping
  8. 4y agoselection.indexGenetic advance calculation added
  9. 5y agosdcMicroTwo new information-loss measures and a run of sdcApp fixes
  10. 5y agosdcMicroCompatibility fixes for R 4.1 sorting and rsconnect deployment
  11. 8y agosdcMicroMinor release, mostly GUI work
  12. 8y agosdcMicrodUtility() corrected so IL1 and IL1s can be distinguished

Frequently asked questions

What is the difference between sdcMicro and selection.index?

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

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

What are the best alternatives to selection.index?

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