协作头脑风暴
brainstorming
在实现前澄清需求、探索设计选择,并形成清晰的开发方向。
ijcai-author-response【开发与工程】Use when drafting IJCAI or IJCAI-ECAI author responses under the official one-page template, concise-response guidance, no-new-results constraints, code-link restrictions, factual-error triage, pressing-question triage, and confidential unethical-review channel.
独立 GitHub 快照 · 自动分类 · 以原作者文档为准
Use this after IJCAI reviews are released. Reopen the current Author's Response FAQ and response template before drafting; rebuttal rules are cycle-specific.
The one-page budget forces ruthless selection. The response is not a dialogue, and phase-1 summary-reject papers usually get no response, so reserve the page for decision-changing items.
| Reviewer point | Respond? | How |
|---|---|---|
| Pressing question that could flip the score | Yes | Point to the submitted location |
| Factual error driving rejection | Yes | Correct precisely; anchor to section/table/theorem |
| "Add experiment X" | No new results | Promise a camera-ready note or cite existing evidence |
| Tone, score, broad disagreement | No | Do not spend budget relitigating |
| Suspected unethical review | Confidential box | Not the public PDF |
A planning paper draws one strong review and one that wrongly claims the optimality proof assumes unit costs. That misreading could drive rejection, so it earns space: cite the assumption already stated in the submitted theorem and point to the appendix proof, without a new result. A second reviewer asks for an extra benchmark family; since no new experiments may be added, promise a camera-ready note and reference the closest existing table. The complaint about presentation tone gets no words.
[Response budget] <pages used / current limit>
[Eligible reason] pressing question / factual error / unethical review
[Draft response] <IJCAI-ready text>
[Evidence anchor] <submitted location>
[Do-not-include list] <new results, code links, broad complaints, identity leaks>