Generalize the analysis stack to other games and external conversation corpora
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
- 技术栈
- python
- 领域
- data, machine-learning
调研方向
先阅读 issue #1，因为这项工作依赖于其 loader 边界和分析栈。定义用于地图、棋盘状态序列和对齐的对话轮次的公共接口，然后添加一个外部语料库 loader，并重新运行 #1 的分析，报告哪些结果得以复现，哪些没有复现。
由索引模型根据 Issue 内容生成。
描述
Deferred from the initial scoping of #1, which is D12-only. Filing so we don't lose it.
Idea
Nothing in the analysis stack is actually specific to Dominating 12. A game reduces to: a map with
a territory adjacency graph, a sequence of board states, a set of players, and timestamped
conversation turns. Any territorial negotiation game fits that shape. If the loaders are written
against that interface rather than against D12's HTML, the same metrics and models run on other
sources for free.
Why it's worth doing
- Generalization is the scientific claim. "Conversations follow stereotyped trajectories as a
function of position strength" is much stronger if it holds in two unrelated games than in one.
A single-site result is always vulnerable to "that's a quirk of D12's player base." - Insurance. If D12 data access is limited in scope or volume, an external corpus keeps the
conversation analysis alive. - More board context per message. Some corpora ship annotations (e.g. intent, deception) that
D12 chat won't have, which lets us validate our unsupervised trajectory findings against labels.
Candidate sources
- Diplomacy deception dataset (Peskov et al., ACL 2020) — real human negotiation in a
territorial conquest game, ~17k messages with board context and per-message truthfulness labels.
Closest available analogue to the D12 setting. Needs a licensing/availability check. - WebDiplomacy / Diplomacy engine logs more broadly
- Other online Risk implementations with public game archives and permissive terms
- Settlers-style trading games, if we want negotiation without territorial conquest as a contrast
Scope sketch
- Formalize the loader interface implied by #1 (map -> graph, log -> board state sequence,
chat -> turn sequence aligned to board states) as the package's public boundary - Write a second loader for one external corpus
- Re-run the #1 analyses on it and report where results replicate and where they don't
Depends on
#1 — the interface has to exist before there's anything to generalize. Ideally #1 is written with
this in mind so the loader boundary is already clean and this issue is mostly additive.
- 主要语言
- Python
- 星标
- 1
- 派生
- 0
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
ContextLab/risk-analysis 的其他 Issue
-
难度 5/5 一周以上 新手友好度 35/100
ContextLab/risk-analysis#4 · 3 条评论 ·
-
难度 5/5 一周以上 新手友好度 30/100
-
basic approach未关闭
难度 5/5 一周以上 新手友好度 20/100
查看 ContextLab/risk-analysis 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 67/100
MISP/misp-workbench#496 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
维护者通常 1 天内回复
-
难度 1/5 1-3 小时 新手友好度 88/100
fossasia/visdom-dev#69 ·
维护者通常 3 天内回复
-
[Bug] Parameters named like a property break to_xcal()可能已有人在做 @atharvasalunke1267 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
collective/icalendar#2018 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复