Manually/automatically re-run clustering on rejected faces
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
- 技术栈
- machine-learning, php
调研方向
先检查 clustering 是如何通过 occ 调用的，并将当前行为与 issue #951 进行比较。追踪手动分配的人脸如何成为新的 clustering 输入，然后将完成定义为：无需新照片即可对之前被拒绝的人脸重新运行 clustering。
由索引模型根据 Issue 内容生成。
描述
Describe the feature you'd like to request
Last year, I added a few thousand photos to Memories over a few days. Recognize eventually churned through most of them and did a pretty good job of recognizing faces and tagging people. However, just a few weeks ago, I discovered the Unassigned faces page and there are so many photos and faces that remain unassigned. I spent a couple of hours assigning faces to ones that Recognize had already clustered together (most of which had a name assigned to them). I then assumed that Recognize would incrementally re-run clustering on rejected faces given the new information I provided by manually assigning a few. However, this does not seem to be the case.
Describe the solution you'd like
I would like a way to have Recognize re-run clustering on rejected faces given new stimuli (such as some rejected faces being manually assigned by the user). This would help me cut down on the number of unassigned faces I have.
I did come across https://github.com/nextcloud/recognize/issues/951 which says that clustering does grab a portion of rejected faces during the clustering of new faces. However, if I am not actively adding new photos, then this does not occur.
Describe alternatives you've considered
I've tried manually running clustering using occ but, as mentioned above, this will only work with new photos that have not yet been clustered. I'm hoping for a way to make the manual assignment of faces a new stimulus for attempting to cluster previously rejected faces.
- 主要语言
- PHP
- 星标
- 698
- 派生
- 68
- 平均合并
- 18 小时 34 分钟
- 30 天内合并 PR
- 2
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
nextcloud/recognize 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
insertDeletion looks up recognize_fs_deletions by node_id alone, which no index covers — bulk removals scan the whole table per file可能已有人在做 @marcelklehr 于 8 天前认领。 未关闭bug
难度 2/5 1-3 小时 新手友好度 82/100
-
enhancement
难度 3/5 1-2 天 新手友好度 65/100
-
enhancement
难度 4/5 3-5 天 新手友好度 45/100
-
Recognize maintenance routine unnecessarily redownloads Tensorflow CPU and GPU models every time可能重新可做 @marcelklehr 于 189 天前认领，目前没有进行中的 PR。 未关闭bug
查看 nextcloud/recognize 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 69/100
PrestaShop/PrestaShop#43140 ·
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 68/100
McNamara84/ernie#1437 ·
维护者通常 1 天内回复
-
sync-en
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
sync-en
难度 2/5 1-3 小时 新手友好度 83/100
维护者通常 3 天内回复
-
needs triage
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复