Loading...
Loading...
Compare original and translation side by side
| Action | ✅ Correct | ❌ Wrong |
|---|---|---|
| Adding a citation | Search API → verify → fetch BibTeX | Write BibTeX from memory |
| Uncertain about a paper | Mark as | Guess the reference |
| Can't find exact paper | Note: "placeholder - verify" | Invent similar-sounding paper |
| 操作 | ✅ 正确做法 | ❌ 错误做法 |
|---|---|---|
| 添加引用 | 搜索API → 验证 → 获取BibTeX | 凭记忆编写BibTeX |
| 对某篇论文存疑 | 标记为 | 猜测参考文献 |
| 无法找到确切论文 | 标注:"placeholder - verify" | 编造名称相似的论文 |
% EXPLICIT PLACEHOLDER - requires human verification
\cite{PLACEHOLDER_author2024_verify_this} % TODO: Verify this citation exists% 明确占位符 - 需要人工验证
\cite{PLACEHOLDER_author2024_verify_this} % TODO: 确认该引用是否存在claude mcp add exa -- npx -y mcp-remote "https://mcp.exa.ai/mcp"{
"mcpServers": {
"exa": {
"type": "http",
"url": "https://mcp.exa.ai/mcp"
}
}
}claude mcp add exa -- npx -y mcp-remote "https://mcp.exa.ai/mcp"{
"mcpServers": {
"exa": {
"type": "http",
"url": "https://mcp.exa.ai/mcp"
}
}
}Project Understanding:
- [ ] Step 1: Explore the repository structure
- [ ] Step 2: Read README, existing docs, and key results
- [ ] Step 3: Identify the main contribution with the scientist
- [ ] Step 4: Find papers already cited in the codebase
- [ ] Step 5: Search for additional relevant literature
- [ ] Step 6: Outline the paper structure together
- [ ] Step 7: Draft sections iteratively with feedbackundefined项目理解步骤:
- [ ] 步骤1:探索仓库结构
- [ ] 步骤2:阅读README、现有文档和关键结果
- [ ] 步骤3:与科学家确认核心贡献
- [ ] 步骤4:查找代码库中已有的引用文献
- [ ] 步骤5:搜索额外的相关文献
- [ ] 步骤6:共同规划论文结构
- [ ] 步骤7:迭代起草各章节并获取反馈undefined
Look for:
- `README.md` - Project overview and claims
- `results/`, `outputs/`, `experiments/` - Key findings
- `configs/` - Experimental settings
- Existing `.bib` files or citation references
- Any draft documents or notes
**Step 2: Identify Existing Citations**
Check for papers already referenced in the codebase:
```bash
重点查找:
- `README.md` - 项目概述和核心论点
- `results/`、`outputs/`、`experiments/` - 关键发现
- `configs/` - 实验设置
- 现有的`.bib`文件或引用参考
- 任何草稿文档或笔记
**步骤2:识别现有引用**
检查代码库中已引用的论文:
```bash
These are high-signal starting points for Related Work—the scientist has already deemed them relevant.
**Step 3: Clarify the Contribution**
Before writing, explicitly confirm with the scientist:
> "Based on my understanding of the repo, the main contribution appears to be [X].
> The key results show [Y]. Is this the framing you want for the paper,
> or should we emphasize different aspects?"
**Never assume the narrative—always verify with the human.**
**Step 4: Search for Additional Literature**
Use web search to find relevant papers:
Then verify and retrieve BibTeX using the citation workflow below.
**Step 5: Deliver a First Draft**
**Be proactive—deliver a complete draft rather than asking permission for each section.**
If the repo provides clear results and the contribution is apparent:
1. Write the full first draft end-to-end
2. Present the complete draft for feedback
3. Iterate based on scientist's response
If genuinely uncertain about framing or major claims:
1. Draft what you can confidently
2. Flag specific uncertainties: "I framed X as the main contribution—let me know if you'd prefer to emphasize Y instead"
3. Continue with the draft rather than blocking
**Questions to include with the draft** (not before):
- "I emphasized X as the main contribution—adjust if needed"
- "I highlighted results A, B, C—let me know if others are more important"
- "Related work section includes [papers]—add any I missed"
---
这些是相关工作部分的高价值起点——科学家已认定它们与项目相关。
**步骤3:明确核心贡献**
撰写前,务必与科学家明确确认:
> "根据我对仓库的理解,核心贡献似乎是[X]。
> 关键结果显示[Y]。这是否是你希望的论文框架,
> 还是我们应该强调其他方面?"
**绝不要主观臆断叙事逻辑——务必与人工确认。**
**步骤4:搜索额外文献**
使用网络搜索查找相关论文:
然后按照下方的引用工作流验证并获取BibTeX。
**步骤5:交付初稿**
**保持主动性——交付完整草稿,而非请求撰写每个章节的许可。**
如果仓库提供了清晰的结果且核心贡献明确:
1. 从头到尾撰写完整的初稿
2. 提交完整草稿以获取反馈
3. 根据科学家的回应迭代优化
如果对框架或主要论点存在真正的不确定性:
1. 先撰写你有把握的部分
2. 标记具体的不确定点:"我将X作为核心贡献进行阐述——如果你希望强调Y,请告知"
3. 继续撰写草稿而非停滞
**随草稿一起提出问题**(而非提前):
- "我将X作为核心贡献重点阐述——如有需要可调整"
- "我突出了结果A、B、C——如果其他结果更重要,请告知"
- "相关工作部分引用了[论文]——如有遗漏请补充"
---| Confidence Level | Action |
|---|---|
| High (clear repo, obvious contribution) | Write full draft, deliver, iterate on feedback |
| Medium (some ambiguity) | Write draft with flagged uncertainties, continue |
| Low (major unknowns) | Ask 1-2 targeted questions, then draft |
| Section | Draft Autonomously | Flag With Draft |
|---|---|---|
| Abstract | Yes | "Framed contribution as X—adjust if needed" |
| Introduction | Yes | "Emphasized problem Y—correct if wrong" |
| Methods | Yes | "Included details A, B, C—add missing pieces" |
| Experiments | Yes | "Highlighted results 1, 2, 3—reorder if needed" |
| Related Work | Yes | "Cited papers X, Y, Z—add any I missed" |
| 信心水平 | 行动 |
|---|---|
| 高(仓库清晰,贡献明确) | 撰写完整草稿,交付后根据反馈迭代 |
| 中(存在一些模糊点) | 撰写草稿并标记不确定点,继续推进 |
| 低(存在重大未知) | 提出1-2个针对性问题,然后开始撰写草稿 |
| 章节 | 自主撰写 | 随草稿标记 |
|---|---|---|
| 摘要 | 是 | "将贡献框架定为X——如有需要可调整" |
| 引言 | 是 | "重点强调了问题Y——如有错误请修正" |
| 方法 | 是 | "包含了细节A、B、C——如有遗漏请补充" |
| 实验 | 是 | "突出了结果1、2、3——如有需要可重新排序" |
| 相关工作 | 是 | "引用了论文X、Y、Z——如有遗漏请补充" |
| Pillar | Description | Example |
|---|---|---|
| The What | 1-3 specific novel claims within cohesive theme | "We prove that X achieves Y under condition Z" |
| The Why | Rigorous empirical evidence supporting claims | Strong baselines, experiments distinguishing hypotheses |
| The So What | Why readers should care | Connection to recognized community problems |
| 支柱 | 描述 | 示例 |
|---|---|---|
| 是什么 | 1-3个具体的创新性论点,围绕统一主题 | "我们证明了X在条件Z下可实现Y" |
| 为什么 | 支持论点的严谨实证证据 | 强大的基线、区分假设的实验 |
| 重要性 | 读者为何需要关注 | 与社区公认问题的关联 |
Paper Writing Progress:
- [ ] Step 1: Define the one-sentence contribution (with scientist)
- [ ] Step 2: Draft Figure 1 → get feedback → revise
- [ ] Step 3: Draft abstract → get feedback → revise
- [ ] Step 4: Draft introduction → get feedback → revise
- [ ] Step 5: Draft methods → get feedback → revise
- [ ] Step 6: Draft experiments → get feedback → revise
- [ ] Step 7: Draft related work → get feedback → revise
- [ ] Step 8: Draft limitations → get feedback → revise
- [ ] Step 9: Complete paper checklist (required)
- [ ] Step 10: Final review cycle and submission"I propose framing the contribution as: '[one sentence]'. Does this capture what you see as the main takeaway? Should we adjust the emphasis?"
1. What you achieved: "We introduce...", "We prove...", "We demonstrate..."
2. Why this is hard and important
3. How you do it (with specialist keywords for discoverability)
4. What evidence you have
5. Your most remarkable number/result论文撰写进度:
- [ ] 步骤1:与科学家共同定义一句话核心贡献
- [ ] 步骤2:起草图1 → 获取反馈 → 修订
- [ ] 步骤3:撰写摘要 → 获取反馈 → 修订
- [ ] 步骤4:撰写引言 → 获取反馈 → 修订
- [ ] 步骤5:撰写方法 → 获取反馈 → 修订
- [ ] 步骤6:撰写实验 → 获取反馈 → 修订
- [ ] 步骤7:撰写相关工作 → 获取反馈 → 修订
- [ ] 步骤8:撰写局限性 → 获取反馈 → 修订
- [ ] 步骤9:完成论文检查清单(必填)
- [ ] 步骤10:最终审核和提交"我建议将贡献框架定为:'[一句话]'。这是否准确捕捉了你认为的核心结论?我们是否需要调整重点?"
1. 你的成果:"我们提出..."、"我们证明..."、"我们展示..."
2. 为什么这很困难且重要
3. 你的实现方法(使用专业术语以提升可发现性)
4. 你的证据
5. 最显著的数值/结果"A paper is a short, rigorous, evidence-based technical story with a takeaway readers care about." — Neel Nanda
"论文是一个简短、严谨、有证据支持的技术故事,包含读者关心的核心结论。" — Neel Nanda
| Source | Key Contribution | Link |
|---|---|---|
| Neel Nanda (Google DeepMind) | The Narrative Principle, What/Why/So What framework | How to Write ML Papers |
| Sebastian Farquhar (DeepMind) | 5-sentence abstract formula | How to Write ML Papers |
| Gopen & Swan | 7 principles of reader expectations | Science of Scientific Writing |
| Zachary Lipton | Word choice, eliminating hedging | Heuristics for Scientific Writing |
| Jacob Steinhardt (UC Berkeley) | Precision, consistent terminology | Writing Tips |
| Ethan Perez (Anthropic) | Micro-level clarity tips | Easy Paper Writing Tips |
| Andrej Karpathy | Single contribution focus | Various lectures |
| 来源 | 核心贡献 | 链接 |
|---|---|---|
| Neel Nanda(Google DeepMind) | 叙事原则、What/Why/So What框架 | How to Write ML Papers |
| Sebastian Farquhar(DeepMind) | 5句话摘要公式 | How to Write ML Papers |
| Gopen & Swan | 7条读者期望原则 | Science of Scientific Writing |
| Zachary Lipton | 措辞选择、消除模糊表述 | Heuristics for Scientific Writing |
| Jacob Steinhardt(UC Berkeley) | 精确性、术语一致性 | Writing Tips |
| Ethan Perez(Anthropic) | 微观层面的清晰度技巧 | Easy Paper Writing Tips |
| Andrej Karpathy | 聚焦单一贡献 | 各类讲座 |
| Principle | Rule | Example |
|---|---|---|
| Subject-verb proximity | Keep subject and verb close | ❌ "The model, which was trained on..., achieves" → ✅ "The model achieves... after training on..." |
| Stress position | Place emphasis at sentence ends | ❌ "Accuracy improves by 15% when using attention" → ✅ "When using attention, accuracy improves by 15%" |
| Topic position | Put context first, new info after | ✅ "Given these constraints, we propose..." |
| Old before new | Familiar info → unfamiliar info | Link backward, then introduce new |
| One unit, one function | Each paragraph makes one point | Split multi-point paragraphs |
| Action in verb | Use verbs, not nominalizations | ❌ "We performed an analysis" → ✅ "We analyzed" |
| Context before new | Set stage before presenting | Explain before showing equation |
| 原则 | 规则 | 示例 |
|---|---|---|
| 主语-动词靠近 | 保持主语和动词位置接近 | ❌ "The model, which was trained on..., achieves" → ✅ "The model achieves... after training on..." |
| 强调位置 | 将重点放在句末 | ❌ "Accuracy improves by 15% when using attention" → ✅ "When using attention, accuracy improves by 15%" |
| 主题位置 | 先给出上下文,再提供新信息 | ✅ "Given these constraints, we propose..." |
| 先旧后新 | 熟悉的信息→不熟悉的信息 | 先回顾已有内容,再引入新内容 |
| 一段一旨 | 每段只表达一个观点 | 拆分包含多个观点的段落 |
| 动词体现动作 | 使用动词,而非名词化形式 | ❌ "We performed an analysis" → ✅ "We analyzed" |
| 先上下文后新内容 | 先铺垫背景,再呈现内容 | 先解释,再展示公式 |
| Paper Section | % Reviewers Who Read | Implication |
|---|---|---|
| Abstract | 100% | Must be perfect |
| Introduction | 90%+ (skimmed) | Front-load contribution |
| Figures | Examined before methods | Figure 1 is critical |
| Methods | Only if interested | Don't bury the lede |
| Appendix | Rarely | Put only supplementary details |
| 论文章节 | 阅读的审稿人比例 | 启示 |
|---|---|---|
| 摘要 | 100% | 必须完美 |
| 引言 | 90%+(略读) | 前置核心贡献 |
| 图表 | 在阅读方法部分前查看 | 图1至关重要 |
| 方法 | 仅在感兴趣时阅读 | 不要将核心内容隐藏在后面 |
| 附录 | 很少阅读 | 仅放置补充细节 |
| Conference | Page Limit | Extra for Camera-Ready | Key Requirement |
|---|---|---|---|
| NeurIPS 2025 | 9 pages | +0 | Mandatory checklist, lay summary for accepted |
| ICML 2026 | 8 pages | +1 | Broader Impact Statement required |
| ICLR 2026 | 9 pages | +1 | LLM disclosure required, reciprocal reviewing |
| ACL 2025 | 8 pages (long) | varies | Limitations section mandatory |
| AAAI 2026 | 7 pages | +1 | Strict style file adherence |
| COLM 2025 | 9 pages | +1 | Focus on language models |
| 会议 | 页数限制 | 终稿额外页数 | 核心要求 |
|---|---|---|---|
| NeurIPS 2025 | 9页 | +0 | 强制检查清单,录用论文需提供通俗摘要 |
| ICML 2026 | 8页 | +1 | 需提供更广泛影响声明 |
| ICLR 2026 | 9页 | +1 | 需披露LLM使用情况,互惠审稿协议 |
| ACL 2025 | 8页(长文) | 依情况而定 | 强制包含局限性部分 |
| AAAI 2026 | 7页 | +1 | 严格遵循样式文件 |
| COLM 2025 | 9页 | +1 | 聚焦语言模型 |
Template Setup Checklist:
- [ ] Step 1: Copy entire template directory to new project
- [ ] Step 2: Verify template compiles as-is (before any changes)
- [ ] Step 3: Read the template's example content to understand structure
- [ ] Step 4: Replace example content section by section
- [ ] Step 5: Keep template comments/examples as reference until done
- [ ] Step 6: Clean up template artifacts only at the endundefined模板设置检查清单:
- [ ] 步骤1:将完整模板目录复制到新项目
- [ ] 步骤2:验证模板可直接编译(修改前)
- [ ] 步骤3:阅读模板示例内容以了解结构
- [ ] 步骤4:逐章节替换示例内容
- [ ] 步骤5:保留模板注释/示例作为参考直至完成
- [ ] 步骤6:仅在最后清理模板工件undefined
**⚠️ IMPORTANT**: Copy the ENTIRE directory, not just `main.tex`. Templates include:
- Style files (`.sty`) - required for compilation
- Bibliography styles (`.bst`) - required for references
- Example content - useful as reference
- Makefiles - for easy compilation
**Step 2: Verify Template Compiles First**
Before making ANY changes, compile the template as-is:
```bash
**⚠️ 重要提醒**:复制**整个目录**,而非仅`main.tex`。模板包含:
- 样式文件(`.sty`)- 编译必需
- 参考文献样式(`.bst`)- 引用必需
- 示例内容 - 作为参考很有用
- Makefile - 便于编译
**步骤2:先验证模板可编译**
在进行**任何**修改前,先直接编译模板:
```bash
If the unmodified template doesn't compile, fix that first. Common issues:
- Missing TeX packages → install via `tlmgr install <package>`
- Wrong TeX distribution → use TeX Live (recommended)
**Step 3: Keep Template Content as Reference**
Don't immediately delete all example content. Instead:
```latex
% KEEP template examples commented out as you write
% This shows you the expected format
% Template example (keep for reference):
% \begin{figure}[t]
% \centering
% \includegraphics[width=0.8\linewidth]{example-image}
% \caption{Template shows caption style}
% \end{figure}
% Your actual figure:
\begin{figure}[t]
\centering
\includegraphics[width=0.8\linewidth]{your-figure.pdf}
\caption{Your caption following the same style.}
\end{figure}Replacement Order:
1. Title and authors (anonymize for submission)
2. Abstract
3. Introduction
4. Methods
5. Experiments
6. Related Work
7. Conclusion
8. References (your .bib file)
9. Appendix% Common template macros to use:
\newcommand{\method}{YourMethodName} % Consistent method naming
\newcommand{\eg}{e.g.,\xspace} % Proper abbreviations
\newcommand{\ie}{i.e.,\xspace}
\newcommand{\etal}{\textit{et al.}\xspace}% BEFORE SUBMISSION - remove these:
% - Commented-out template examples
% - Unused packages
% - Template's example figures/tables
% - Lorem ipsum or placeholder text
% KEEP these:
% - All style files (.sty)
% - Bibliography style (.bst)
% - Required packages from template
% - Any custom macros you're using
如果未修改的模板无法编译,先解决此问题。常见问题:
- 缺少TeX包 → 通过`tlmgr install <package>`安装
- 错误的TeX发行版 → 使用TeX Live(推荐)
**步骤3:保留模板内容作为参考**
不要立即删除所有示例内容。相反:
```latex
% 保留模板示例作为注释供撰写时参考
% 这展示了预期格式
% 模板示例(保留参考):
% \begin{figure}[t]
% \centering
% \includegraphics[width=0.8\linewidth]{example-image}
% \caption{Template shows caption style}
% \end{figure}
% 你的实际图表:
\begin{figure}[t]
\centering
\includegraphics[width=0.8\linewidth]{your-figure.pdf}
\caption{Your caption following the same style.}
\end{figure}替换顺序:
1. 标题和作者(提交时匿名)
2. 摘要
3. 引言
4. 方法
5. 实验
6. 相关工作
7. 结论
8. 参考文献(你的.bib文件)
9. 附录% 常用模板宏:
\newcommand{\method}{YourMethodName} % 方法名称一致性
\newcommand{\eg}{e.g.,\xspace} % 正确缩写
\newcommand{\ie}{i.e.,\xspace}
\newcommand{\etal}{\textit{et al.}\xspace}% 提交前删除这些:
% - 注释掉的模板示例
% - 未使用的包
% - 模板的示例图表/表格
% - 乱数假文或占位符文本
% 保留这些:
% - 所有样式文件(.sty)
% - 参考文献样式(.bst)
% - 模板要求的包
% - 你使用的自定义宏| Pitfall | Problem | Solution |
|---|---|---|
Copying only | Missing | Copy entire directory |
Modifying | Breaks conference formatting | Never edit style files |
| Adding random packages | Conflicts, breaks template | Only add if necessary |
| Deleting template content too early | Lose formatting reference | Keep as comments until done |
| Not compiling frequently | Errors accumulate | Compile after each section |
| 陷阱 | 问题 | 解决方案 |
|---|---|---|
仅复制 | 缺少 | 复制整个目录 |
修改 | 破坏会议格式 | 永远不要编辑样式文件 |
| 添加随机包 | 冲突,破坏模板 | 仅在必要时添加 |
| 过早删除模板内容 | 失去格式参考 | 保留为注释直至完成 |
| 不频繁编译 | 错误累积 | 每完成一个章节就编译一次 |
| Conference | Main File | Key Style File | Notes |
|---|---|---|---|
| NeurIPS 2025 | | | Has Makefile |
| ICML 2026 | | | Includes algorithm packages |
| ICLR 2026 | | | Has math_commands.tex |
| ACL | | | Strict formatting |
| AAAI 2026 | | | Very strict compliance |
| COLM 2025 | | | Similar to ICLR |
| 会议 | 主文件 | 核心样式文件 | 说明 |
|---|---|---|---|
| NeurIPS 2025 | | | 包含Makefile |
| ICML 2026 | | | 包含算法包 |
| ICLR 2026 | | | 包含math_commands.tex |
| ACL | | | 严格格式要求 |
| AAAI 2026 | | | 非常严格的合规要求 |
| COLM 2025 | | | 与ICLR类似 |
Format Conversion Checklist:
- [ ] Step 1: Identify source and target template differences
- [ ] Step 2: Create new project with target template
- [ ] Step 3: Copy content sections (not preamble)
- [ ] Step 4: Adjust page limits and content
- [ ] Step 5: Update conference-specific requirements
- [ ] Step 6: Verify compilation and formatting| From → To | Page Change | Key Adjustments |
|---|---|---|
| NeurIPS → ICML | 9 → 8 pages | Cut 1 page, add Broader Impact if missing |
| ICML → ICLR | 8 → 9 pages | Can expand experiments, add LLM disclosure |
| NeurIPS → ACL | 9 → 8 pages | Restructure for NLP conventions, add Limitations |
| ICLR → AAAI | 9 → 7 pages | Significant cuts needed, strict style adherence |
| Any → COLM | varies → 9 | Reframe for language model focus |
undefined格式转换检查清单:
- [ ] 步骤1:识别源模板和目标模板的差异
- [ ] 步骤2:使用目标模板创建新项目
- [ ] 步骤3:复制内容章节(而非序言)
- [ ] 步骤4:调整页数限制和内容
- [ ] 步骤5:更新会议特定要求
- [ ] 步骤6:验证编译和格式| 源会议→目标会议 | 页数变化 | 核心调整 |
|---|---|---|
| NeurIPS → ICML | 9 → 8页 | 删减1页,如缺失则添加更广泛影响声明 |
| ICML → ICLR | 8 → 9页 | 可扩展实验部分,添加LLM披露 |
| NeurIPS → ACL | 9 → 8页 | 按NLP惯例重构,添加局限性部分 |
| ICLR → AAAI | 9 → 7页 | 需要大量删减,严格遵循样式 |
| 任意→COLM | 可变→9页 | 重新调整为聚焦语言模型 |
undefined
**Step 3: Adjusting for Page Limits**
When cutting pages (e.g., NeurIPS 9 → AAAI 7):
- Move detailed proofs to appendix
- Condense related work (cite surveys instead of individual papers)
- Combine similar experiments into unified tables
- Use smaller figure sizes with subfigures
- Tighten writing: eliminate redundancy, use active voice
When expanding (e.g., ICML 8 → ICLR 9):
- Add ablation studies reviewers requested
- Expand limitations discussion
- Include additional baselines
- Add qualitative examples
**Step 4: Conference-Specific Adjustments**
| Target Venue | Required Additions |
|--------------|-------------------|
| **ICML** | Broader Impact Statement (after conclusion) |
| **ICLR** | LLM usage disclosure, reciprocal reviewing agreement |
| **ACL/EMNLP** | Limitations section (mandatory), Ethics Statement |
| **AAAI** | Strict adherence to style file (no modifications) |
| **NeurIPS** | Paper checklist (appendix), lay summary if accepted |
**Step 5: Update References**
```latex
% Remove self-citations that reveal identity (for blind review)
% Update any "under review" citations to published versions
% Add new relevant work published since last submission\usepackage\bibliography{}
**步骤3:调整页数限制**
当需要删减页数时(如NeurIPS 9页→AAAI 7页):
- 将详细证明移至附录
- 精简相关工作(引用综述而非单篇论文)
- 将相似实验合并为统一表格
- 使用更小的图表尺寸和子图
- 精简写作:消除冗余,使用主动语态
当可以扩展页数时(如ICML 8页→ICLR 9页):
- 添加审稿人要求的消融研究
- 扩展局限性讨论
- 包含更多基线
- 添加定性示例
**步骤4:会议特定调整**
| 目标会议 | 必需添加内容 |
|--------------|-------------------|
| **ICML** | 更广泛影响声明(结论后) |
| **ICLR** | LLM使用披露,互惠审稿协议 |
| **ACL/EMNLP** | 局限性部分(强制),伦理声明 |
| **AAAI** | 严格遵循样式文件(不得修改) |
| **NeurIPS** | 论文检查清单(附录),录用后需提供通俗摘要 |
**步骤5:更新参考文献**
```latex
% 删除可能暴露身份的自引(双盲评审)
% 将任何“在审”引用更新为已发表版本
% 添加上次提交后发表的新相关工作\usepackage\bibliography{}IF you cannot programmatically fetch a citation:
→ Mark it as [CITATION NEEDED] or [PLACEHOLDER - VERIFY]
→ Tell the scientist explicitly
→ NEVER invent a plausible-sounding reference如果无法通过程序获取引用:
→ 标记为[CITATION NEEDED]或[PLACEHOLDER - VERIFY]
→ 明确告知科学家
→ 绝不要编造看似合理的参考文献Citation Verification (MANDATORY for every citation):
- [ ] Step 1: Search using Exa MCP or Semantic Scholar API
- [ ] Step 2: Verify paper exists in 2+ sources (Semantic Scholar + arXiv/CrossRef)
- [ ] Step 3: Retrieve BibTeX via DOI (programmatically, not from memory)
- [ ] Step 4: Verify the claim you're citing actually appears in the paper
- [ ] Step 5: Add verified BibTeX to bibliography
- [ ] Step 6: If ANY step fails → mark as placeholder, inform scientistSearch: "RLHF language model alignment 2023"
Search: "sparse autoencoders interpretability"
Search: "attention mechanism transformers Vaswani"from semanticscholar import SemanticScholar
sch = SemanticScholar()
results = sch.search_paper("attention mechanism transformers", limit=5)
for paper in results:
print(f"{paper.title} - {paper.paperId}")
print(f" DOI: {paper.externalIds.get('DOI', 'N/A')}")import requests
def doi_to_bibtex(doi: str) -> str:
"""Get verified BibTeX from DOI via CrossRef."""
response = requests.get(
f"https://doi.org/{doi}",
headers={"Accept": "application/x-bibtex"}
)
response.raise_for_status()
return response.text引用验证(每个引用都必须执行):
- [ ] 步骤1:使用Exa MCP或Semantic Scholar API搜索
- [ ] 步骤2:在2+来源中验证论文存在(Semantic Scholar + arXiv/CrossRef)
- [ ] 步骤3:通过DOI获取BibTeX(程序获取,而非记忆)
- [ ] 步骤4:验证你引用的论点确实出现在论文中
- [ ] 步骤5:将已验证的BibTeX添加到参考文献
- [ ] 步骤6:如果任何步骤失败→标记为占位符并告知科学家Search: "RLHF language model alignment 2023"
Search: "sparse autoencoders interpretability"
Search: "attention mechanism transformers Vaswani"from semanticscholar import SemanticScholar
sch = SemanticScholar()
results = sch.search_paper("attention mechanism transformers", limit=5)
for paper in results:
print(f"{paper.title} - {paper.paperId}")
print(f" DOI: {paper.externalIds.get('DOI', 'N/A')}")import requests
def doi_to_bibtex(doi: str) -> str:
"""通过CrossRef从DOI获取已验证的BibTeX。"""
response = requests.get(
f"https://doi.org/{doi}",
headers={"Accept": "application/x-bibtex"}
)
response.raise_for_status()
return response.text
**Step 4: Verify Claims**
Before citing for a specific claim, access the paper and confirm the attributed claim actually appears.
**Step 5: Handle Failures Explicitly**
If you cannot verify a citation at ANY step:
```latex
% Option 1: Explicit placeholder
\cite{PLACEHOLDER_smith2023_verify} % TODO: Could not verify - scientist must confirm
% Option 2: Note in text
... as shown in prior work [CITATION NEEDED - could not verify Smith et al. 2023]."I could not verify the following citations and have marked them as placeholders:
- Smith et al. 2023 on reward hacking - could not find in Semantic Scholar
- Jones 2022 on scaling laws - found similar paper but different authors Please verify these before submission."
**步骤4:验证论点**
在引用特定论点前,访问论文并确认所引用的论点确实存在。
**步骤5:处理失败情况**
如果在任何步骤无法验证引用:
```latex
% 选项1:明确占位符
\cite{PLACEHOLDER_smith2023_verify} % TODO: 无法验证 - 需科学家确认
% 选项2:在文本中注明
... as shown in prior work [CITATION NEEDED - could not verify Smith et al. 2023]."我无法验证以下引用,已将其标记为占位符:
- Smith等人2023年关于奖励黑客的论文 - 在Semantic Scholar中未找到
- Jones2022年关于缩放定律的论文 - 找到相似论文但作者不同 请在提交前验证这些引用。"
| Situation | Action |
|---|---|
| Found paper, got DOI, fetched BibTeX | ✅ Use the citation |
| Found paper, no DOI | ✅ Use arXiv BibTeX or manual entry from paper |
| Paper exists but can't fetch BibTeX | ⚠️ Mark placeholder, inform scientist |
| Uncertain if paper exists | ❌ Mark |
| "I think there's a paper about X" | ❌ NEVER cite - search first or mark placeholder |
| 情况 | 行动 |
|---|---|
| 找到论文,获取DOI,获取BibTeX | ✅ 使用该引用 |
| 找到论文,无DOI | ✅ 使用arXiv的BibTeX或从论文手动输入 |
| 论文存在但无法获取BibTeX | ⚠️ 标记为占位符并告知科学家 |
| 不确定论文是否存在 | ❌ 标记 |
| "我认为有一篇关于X的论文" | ❌ 绝不要引用 - 先搜索或标记为占位符 |
| Criterion | What Reviewers Look For |
|---|---|
| Quality | Technical soundness, well-supported claims |
| Clarity | Clear writing, reproducible by experts |
| Significance | Community impact, advances understanding |
| Originality | New insights (doesn't require new method) |
| 评估维度 | 审稿人关注要点 |
|---|---|
| 质量 | 技术严谨性,论点有充分支持 |
| 清晰度 | 写作清晰,专家可复现 |
| 重要性 | 对社区的影响,推动领域理解 |
| 原创性 | 新见解(不一定要提出新方法) |
booktabs\usepackage{booktabs}
\begin{tabular}{lcc}
\toprule
Method & Accuracy ↑ & Latency ↓ \\
\midrule
Baseline & 85.2 & 45ms \\
\textbf{Ours} & \textbf{92.1} & 38ms \\
\bottomrule
\end{tabular}booktabs\usepackage{booktabs}
\begin{tabular}{lcc}
\toprule
Method & Accuracy ↑ & Latency ↓ \\
\midrule
Baseline & 85.2 & 45ms \\
\textbf{Ours} & \textbf{92.1} & 38ms \\
\bottomrule
\end{tabular}| Document | Contents |
|---|---|
| writing-guide.md | Gopen & Swan 7 principles, Ethan Perez micro-tips, word choice |
| citation-workflow.md | Citation APIs, Python code, BibTeX management |
| checklists.md | NeurIPS 16-item, ICML, ICLR, ACL requirements |
| reviewer-guidelines.md | Evaluation criteria, scoring, rebuttals |
| sources.md | Complete bibliography of all sources |
| 文档 | 内容 |
|---|---|
| writing-guide.md | Gopen & Swan7条原则,Ethan Perez微观技巧,措辞选择 |
| citation-workflow.md | 引用API,Python代码,BibTeX管理 |
| checklists.md | NeurIPS16项检查清单,ICML、ICLR、ACL要求 |
| reviewer-guidelines.md | 评估标准,评分,回复审稿意见 |
| sources.md | 所有来源的完整参考文献 |
templates/latexmk -pdf main.texpdflatexbibtextemplates/latexmk -pdf main.texpdflatexbibtex