跳到主要内容
知仓学习社ZHICANG

hpca-author-response

Use when drafting an HPCA rebuttal and revision in the single combined window: triaging objections by what the window can fix, running a small numbe…

不碰外部(只输出文字)无严重或高危命中brycewang-stanford/Awesome-Journal-Skills

它会碰到什么

扫了多少1 个文本文件,4 KB
它会碰到什么不碰外部(只输出文字)
命中总数0 处
命中统计严重 0 · 高 0 · 中 0 · 低 0

这一栏是扫描器报的事实,不是结论。命中多不等于有毒(安全工具、规则库、示例脚本本来就会包含危险写法),命中少也不等于干净。它和你手上的凭据、文件、网络有什么关系,需要你自己看。

技能内容

HPCA Author Response

Use this during HPCA's single combined rebuttal/revision window — the one period

in which you respond to reviews and revise the paper together. The goal is not to win

an argument; it is to arm a champion at the program-committee meeting and to make the

revised paper reflect what you promise.

Triage objections by what the window can fix

Sort every review comment before writing a word:

  • Deciding objection — the methodology or novelty concern the champion must

overcome. Spend most of the window here.

  • Fixable-and-worth-it — a missing baseline, a sensitivity study, an unclear

mechanism detail the window has time to address.

  • Clarification — a misreading you can correct in a sentence and reflect in the

revision.

  • Out of scope — a request no short window can satisfy; acknowledge honestly and

scope what you can show.

| Objection type | Response move | Revision move |

|---|---|---|

| Deciding (methodology/novelty) | Direct evidence or a tight argument | Change the paper to match |

| Missing baseline / sweep | A small new experiment | Add the result, mark it |

| Mechanism unclear | One-paragraph clarification | Tighten the description |

| Misreading | Point to the text | Rephrase the ambiguous line |

| Out of scope | Acknowledge; state what is feasible | Note the limitation |

Run few, decisive new experiments

The window is short. Run a small number of new experiments that each answer a

specific objection, not a scattershot of everything a reviewer mentioned. One

well-chosen sweep that closes the deciding objection is worth more than five that

answer minor points. Pull from the staging shelf you prepared before the window

opened (see hpca-supplementary).

Write for the room and its champion

The rebuttal is read at the PC meeting, where a champion argues for the paper against

the strongest objection. Write so the champion can quote you:

  • Lead each response with the answer, then the evidence — not a wind-up.
  • Make the deciding objection's answer unmissable and self-contained.
  • Be concrete: "we added the tuned baseline; it changes the gap from X to Y" beats

"we believe our baseline is fair."

  • Stay civil and specific; a defensive or vague rebuttal loses the champion.

Revise diff-minimally so response and revision agree

Because reviewers see both your response and the revised paper, keep the revision a

minimal, faithful diff: change exactly what you promised, and no more. A response

that claims a fix the revision does not contain — or a revision that quietly rewrites

beyond the promises — undercuts trust. Track each promise to a specific edit.

Window pass

1. Triage every comment (deciding / fixable / clarification / out-of-scope)
2. Pick the few decisive experiments; pull from the staging shelf
3. Draft answer-first responses; make the deciding one unmissable
4. Apply a minimal revision that matches every promise
5. Cross-check: does the revised paper contain each claimed fix?

Output format

[Deciding objection] <one>
[New experiments] <the few, each tied to an objection>
[Response map] <objection -> answer-first reply>
[Revision diff] <promise -> exact edit>
[Champion test] can a champion win the room with this? (Y/N)

Reopen the current CFP for the exact window dates and any length limit on the

response — both are per-edition.

想直接用这个技能?

本站把开放许可(MIT / Apache 等)的技能按仓库打包整理到网盘,点一下转存到你自己的网盘,不用一个个从 GitHub 拉。许可未声明的技能只给原始仓库链接,不打包。