← Back to home
Comparison · Infra & APIs

JointFPM vs sdcMicro

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

JointFPM vs sdcMicro: at a glance

FeatureJointFPMsdcMicro
SectorInfra & APIsInfra & APIs
Velocity score0.00.0
Sparks · 30d00
Top themessurvival-analysis, recurrent-events, parametric-models, api-stabilitydisclosure-control, anonymization, llm-assisted-workflows, k-anonymity
Last editorial update37m ago3h ago
WebsiteVisit →Visit →

What is JointFPM?

Recurrent-event modelling settles, with mean_no() promoted to stable.

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

Read the full JointFPM 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 →

JointFPM vs sdcMicro: editorial side-by-side

J
JointFPM
INFRA · APIS
0.0

Recurrent-event modelling settles, with mean_no() promoted to stable.

◆ Current state

JointFPM fits joint flexible parametric models for a recurrent event process alongside a competing terminal event, and predicts the mean number of events. The visible history runs from bug fixes on the earliest CRAN releases through standardization, integration options and a summary method, ending with mean_no() declared stable. Several changes arrived through outside pull requests.

◆ Where it's heading

The arc runs from a working estimator toward a usable one: input validation and error messages first, then control over the numerical integration, then a summary method and pass-through arguments to the underlying rstpm2 fit. The latest release adds no code so much as a stability commitment to a function users were already calling.

◆ Prediction

With mean_no() stable, the next work most likely targets the prediction and standardization paths rather than the model fit itself.

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

See all JointFPM alternatives → · See all sdcMicro alternatives →

Recent activity from JointFPM 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. 1y agoJointFPMmean_no() promoted to a stable interface
  3. 2y agoJointFPMsummary() method and control arguments passed to rstpm2
  4. 2y agoJointFPMGaussian quadrature option for the mean-events integration
  5. 2y agoJointFPMStandardized marginal estimates plus input validation
  6. 2y agoJointFPMBug fixes for differences between mean-event functions
  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 JointFPM and sdcMicro?

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

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

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