RecallGain metric
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
调研方向
The issue proposes changes to metric calculation and cross validation, but names no files, tests, or entry points. Start by locating the existing metric implementations and the calc_metrics and cross_validate APIs. Done means RecallGain works for a single reference model and multiple reference models, with the proposed per-user and cross-validation behavior.
由索引模型根据 Issue 内容生成。
描述
Feature Description
Given test interactions, we can exclude all Positives that would have been recommended by the reference model (e.g. popular model). After that we can calculate Recall as usual. Resulting metrics is interpreted as a gain to overall Recall which is achieved by the new algorithm in comparison with the reference algorithm.
Why this feature?
Useful for both candidate-generators selection and simple validation protocol in case of strong popularity bias in data (e.g. calculating RecallGain from a Popular model).
Additional context
recall_gain = RecallGain(k=10, k_ref=20)
# one metric
value = recall_gain.calc(reco=recos, ref_recos=ref_recos)
per_user = recall_gain.calc_per_user(reco=recos, ref_recos=ref_recos)
# calc_metrics
calc_metrics(
metrics = {"precision": precision, "intersecton": intersecton, "recall_gain": recall_gain},
reco=recos,
interactions=df_test,
ref_recos: Union[pd.Datafame, Dict[Hashable, pd.DataFrame]]=ref_recos
)
# here we can pass multiple models with:
ref_recos = {"one": ref_recos_one, "two": ref_recos_two}
# result dict will have `intersecton_one`, `intersecton_two`, `recall_gain_one`, `recall_gain_two` as keys
# cross_validate
cv_results = cross_validate(
dataset=dataset,
splitter=splitter,
models=models,
metrics=metrics,
k=10,
filter_viewed=True,
ref_models=["one", "two"], # just selecting keys from `models` argument
validate_ref_models=False # optionally exclude ref_models from other metrics
)
- 主要语言
- Python
- 星标
- 457
- 派生
- 55
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
MTSWebServices/RecTools 的其他 Issue
-
good first issue
难度 2/5 1-3 小时 新手友好度 78/100
MTSWebServices/RecTools#330 ·
-
Is it not possible to `load` transformer model on cpu only可能已有人在做 @maxteneff 于 22 天前认领。 未关闭bug good first issue
难度 3/5 1-2 天 新手友好度 35/100
MTSWebServices/RecTools#286 · 3 条评论 ·
-
bug good first issue
难度 2/5 1-3 小时 新手友好度 35/100
MTSWebServices/RecTools#269 · 4 条评论 ·
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
MTSWebServices/RecTools#249 ·
-
enhancement
难度 5/5 一周以上 新手友好度 25/100
MTSWebServices/RecTools#243 ·
查看 MTSWebServices/RecTools 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 83/100
-
难度 2/5 1-3 小时 新手友好度 87/100
维护者通常 7 天内回复
-
area: web priority: P1 story
难度 2/5 1-3 小时 新手友好度 76/100
nfiasco/Quant-Time-Machine#151 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
autowarefoundation/autoware_carla_scenario#2019 ·
维护者通常 1 天内回复
-
docs pydanty:is-working
难度 1/5 1-3 小时 新手友好度 85/100
pydantic/pydantic-ai#12892 ·
维护者通常 1 天内回复