recommenderlab
Lab for Developing and Testing Recommender Algorithms
recommenderlab added hybrid recommenders, then spent five years absorbing upstream churn.
◆Recent moves
- 1y ago
recommenderlab 1.0-7 accepts tibbles, tracks an arules change
Coercion from data.frame to realRatingMatrix gains drop = TRUE so tibbles work, and sparse matrix handling distinguishes 0 from NA more carefully — a distinction that decides whether an unrated item is treated as a zero rating. The dissimilarity fix tracks an argument change in arules, continuing the pattern of upstream-driven releases.
View source ↗ - 2y ago
recommenderlab 1.0.5: interestMeasure and Matrix fixes
A parameter rename in interestMeasure(), a fix for adding a single interest measure, and another Matrix row/colSums correction. Housekeeping against moving dependencies.
View source ↗ - 3y ago
recommenderlab 1.0.4 digest: evaluationScheme filtering and speed
The substance is in the rolled-in 1.0.3 notes: evaluationScheme now drops users with too few ratings with a warning and builds faster for realRatingMatrix, and UBCF works for users with fewer than n nearest neighbors. Practical fixes for benchmarking on sparse real-world data.
View source ↗ - 3y ago
recommenderlab 1.0.2 digest: proxy cosine fix, Matrix prep
Covers 1.0.0 through 1.0.2. Notable for requiring proxy >= 0.4-26 to pick up a cosine similarity conversion fix — the same upstream correction that parallelDist responded to in its own release, showing one dependency bug rippling across unrelated packages.
View source ↗ - 5y ago
recommenderlab 0.2-7 deprecates getConfusionMatrix for getResults
Evaluation results get a clearer accessor, MovieLense gains user metadata, and a normalization bug in UBCF for binary data is fixed. The deprecation tidies an API that had grown around the evaluation workflow.
View source ↗ - 6y ago
recommenderlab 0.2-6 adds hybrid recommenders
⚡ SPARKThe last release to add a genuinely new kind of model: HYBRID composes several recommenders into one, and crucially works inside evaluate(), so combinations can be benchmarked on the same footing as individual algorithms. Everything after this release is maintenance against upstream packages.
View source ↗