FoRecoML
The machine-learning arm of a forecast reconciliation toolkit, four months old and already sharing its sibling's plumbing.
Comparison · Infra & APIs
projoint vs SLmetrics
A side-by-side editorial comparison of projoint and SLmetrics — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r-package
projoint vs SLmetrics: at a glance
What is projoint?
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
What is SLmetrics?
A young ML metrics package rewrote its own backend twice in six months chasing speed.
SLmetrics provides supervised learning evaluation metrics for R — confusion matrices, classification and regression measures, ROC and precision-recall curves — with the computation pushed into C++. After a series of pre-releases it now runs on an Armadillo backend, supports OpenMP parallelism and LAPACK/BLAS, and reports 5-20x speedups over its earlier implementations. The API has been reshaped for extensibility, with an estimator argument replacing the fixed aggregation options.
projoint vs SLmetrics: editorial side-by-side
projoint
2.5INFRA · APIS
projoint spent a year on CRAN paperwork, then shipped a correctness fix it flagged itself.
◆ Current state
projoint is an R package for analysing conjoint survey experiments, covering Qualtrics import, reshaping, and quantity-of-interest estimation with inter-rater reliability correction. Most of its release history is CRAN admission work — citation formats, DESCRIPTION fields, \value{} tags, vignette cleanups — with four tags backfilled within ninety seconds of each other on 15 July in non-monotonic version order, so neither tag order nor timestamps in this feed track the real sequence. The substantive releases are the ones fixing data-preparation bugs that silently corrupt estimates.
◆ Where it's heading
The maintainer is hardening the path from raw Qualtrics export to estimate, which is where conjoint analysis quietly goes wrong. Three separate releases fix that path: dropped respondent-level weights in organize_data(), repeated-task reshaping in reshape_projoint(), and choice-to-profile mapping in 1.1.3. Each fix now arrives with regression tests and stricter validation rather than just a patch, and 1.1.3 adds an explicit .choice_map so the mapping is auditable instead of inferred.
◆ Prediction
Expect the validation-and-regression-test pattern to keep extending across the import path, with releases continuing to arrive in bursts around CRAN submission rather than on a cadence.
SLmetrics
0.0INFRA · APIS
A young ML metrics package rewrote its own backend twice in six months chasing speed.
◆ Current state
SLmetrics provides supervised learning evaluation metrics for R — confusion matrices, classification and regression measures, ROC and precision-recall curves — with the computation pushed into C++. After a series of pre-releases it now runs on an Armadillo backend, supports OpenMP parallelism and LAPACK/BLAS, and reports 5-20x speedups over its earlier implementations. The API has been reshaped for extensibility, with an estimator argument replacing the fixed aggregation options.
◆ Where it's heading
Every release in this timeline is about making the same metrics compute faster or compose better. The backend moved from Rcpp to plain C++, gained OpenMP, then was ported wholesale from Eigen to Armadillo with heavy templating. In parallel the author has been widening the API's joints: generic S3 signatures, an extensible estimator argument, and function signatures loose enough that wrapping packages can rename arguments. Bundled datasets and embedded formulas in the docs point at teaching and benchmarking use. The package still labels itself pre-release, which is consistent with how freely it has broken argument names along the way.
◆ Prediction
A stable non-pre-release version is the natural next step now that the backend has settled on Armadillo, though the repeated willingness to rename arguments suggests more API churn may come first.
Alternatives to projoint and SLmetrics
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 projoint or SLmetrics.
FoReco
Forecast reconciliation with a real object model, five years after it started returning bare matrices.
wooldridge
A textbook data package whose whole job is to stay installable, and whose releases prove how much work that is.
L1centrality
A graph-centrality package that spent 2026 making its existing measures usable at scale, then went quiet.
exametrika
A test-theory package that grew into a graphical-model toolkit, now spending its releases paying down the API debt that growth created.
nuggets
nuggets keeps compounding on the 2.0 rewrite — more pattern families, lighter install.
See all projoint alternatives → · See all SLmetrics alternatives →
Recent activity from projoint and SLmetrics
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 17d agoprojointExplicit .choice_map guards choice-to-profile mapping
- 1mo agoprojointCRAN submission housekeeping for DESCRIPTION and examples
- 1mo agoprojointCRAN formatting pass; minor make_projoint_data() fix
- 1mo agoprojointreshape_projoint() repeated-task bug fixed; validation tightened
- 1mo agoprojointCitation metadata updated with the CRAN DOI
- 5mo agoprojointorganize_data() no longer drops respondent-level weights
- 1y agoSLmetricsArmadillo backend brings 5-20x speedups and an extensible metrics API ⚡
- 1y agoSLmetricsConsistent S3 signatures and three bundled datasets
- 1y agoSLmetricsRegression metrics 2-10x faster with reworked OpenMP controls
- 1y agoSLmetricsOpenMP parallelism and a soft-label entropy family
- 1y agoSLmetricsCross-entropy loss and relative RMSE with three normalisations
- 1y agoSLmetricsSample weights flow through the confusion matrix
Frequently asked questions
What is the difference between projoint and SLmetrics?
Both compete on the same themes — r-package — within Infra & APIs. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 projoint better than SLmetrics?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. projoint is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to projoint?
Top projoint alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "projoint alternatives" section above for the current picks, or visit /alternatives/projoint for the full list with editorial commentary on each.
What are the best alternatives to SLmetrics?
Top SLmetrics alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "SLmetrics alternatives" section above for the current picks, or visit /alternatives/slmetrics for the full list with editorial commentary on each.