prepare-camera-ready

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Prepare Camera-Ready

Camera-Ready终稿准备

Walk an accepted paper through the camera-ready pipeline. The rules are tribal knowledge split across two big rails (ACM: eRights → ORCID → rights/DOI block → TAPS; IEEE: PDF eXpress → file naming → eCF → registration) plus the OpenReview-direct rail used by ML venues, and they change every cycle. This skill turns the venue profile into an ordered checklist, walks each form and upload with the user, and lints the final source for the mistakes that delay or block publication — but the user does every irreversible click.

引导已录用论文完成Camera-Ready终稿流程。相关规则是分散在两大流程体系（ACM：eRights → ORCID → 版权/DOI块 → TAPS；IEEE：PDF eXpress → 文件命名 → eCF → 注册）以及机器学习会议常用的OpenReview直接流程中的行业经验，且每个周期都会变化。本工具将会议配置文件转化为有序清单，逐步指导用户完成每个表单和上传操作，并检查最终源文件中可能导致发表延迟或受阻的错误——但所有不可逆的操作均由用户自行完成。

When to use

使用场景

"My paper was accepted at SIGSPATIAL / ICDE / NeurIPS — what now?"
"Help me with the camera-ready / final version."
"What is this eRights email / TAPS link / PDF eXpress conference ID / eCF?"
"Do all my coauthors really need ORCIDs?" / "Where does the DOI block go?"
"How many pages do I get for the camera-ready?" / "How do I de-anonymize?"
After
```
write-rebuttal
```
succeeds; before
```
make-slides
```
/ talk prep.

“我的论文被SIGSPATIAL / ICDE / NeurIPS录用了——接下来该做什么？”
“帮我处理Camera-Ready终稿/最终版本。”
“这封eRights邮件/TAPS链接/PDF eXpress会议ID/eCF是什么？”
“所有合著者都必须拥有ORCID吗？” / “DOI块应该放在哪里？”
“Camera-Ready终稿允许多少页？” / “如何去除匿名化？”
在
```
write-rebuttal
```
完成后；在
```
make-slides
```
/演讲准备之前。

Inputs

输入信息

The acceptance email (ask the user to paste the camera-ready instructions from it — they override everything else).
The venue profile:
```
venues/conferences/<venue>-<year>.yml
```
(schema in
```
venues/schema.yml
```
; family files supply rail defaults). If missing, create one with
```
parse-cfp
```
first.
The final
```
.tex
```
source (the file with
```
\documentclass
```
) once editing starts; a compiled
```
.log
```
/
```
.pdf
```
next to it enables the page-count check.

录用邮件（请用户粘贴其中的Camera-Ready终稿说明——这些说明优先级最高）。
会议配置文件：
```
venues/conferences/<venue>-<year>.yml
```
（配置文件格式定义在
```
venues/schema.yml
```
；同系列会议文件提供流程默认值）。如果缺失，请先使用
```
parse-cfp
```
创建。
最终.tex源文件（包含
```
\documentclass
```
的文件），编辑开始后即可提供；若旁边有编译生成的
```
.log
```
/
```
.pdf
```
文件，可启用页数检查功能。

Process

流程步骤

Resolve the rail and generate the checklist. Find the profile, ask which track the paper was accepted to (camera-ready deadlines and page limits differ per track), then run:
```
python3 scripts/camera_ready_checklist.py venues/conferences/<venue>-<year>.yml --track "<track>"
```
It merges the family profile, resolves the rail (
```
acm-taps
```
,
```
ieee-pdfexpress
```
,
```
openreview-direct
```
, or other), and prints the ordered steps, the venue-specific requirements, the deadline, and the extra-page rule.
```
--json
```
for machine-readable output.
Re-verify against live sources — mandatory. Camera-ready instructions are issued per acceptance cycle and venues change rails (FAccT left TAPS). Before the user acts on anything: read the acceptance email's instructions, fetch the venue's camera-ready page, and re-check the profile's
```
cfp_url
```
. Confirm at minimum: the camera-ready deadline and timezone, the page limit and any +page allowance, the rail, and where final files are collected (often NOT the review system — ICDE 2026 explicitly says "do NOT upload camera-ready to CMT"). Update the profile YAML if anything differs, and say so.

Walk the rail step by step. Work through the checklist with the user, using the detailed walkthrough for their rail:

Rail	Walkthrough	Key gates
`acm-taps`	references/acm-taps-rail.md	eRights email (corresponding author, check spam), ORCID for ALL authors, rights/DOI block in the preamble, SOURCE zip to TAPS, PDF+HTML proofs — budget weeks
`ieee-pdfexpress`	references/ieee-pdfexpress-rail.md	PDF eXpress conference ID, Xplore validation certificate, file naming (e.g. `PID<n>.pdf` ), eCF with EXACT title/author match (cannot be redone), registration/no-show
`openreview-direct`	rail steps in the checklist output + the venue profile	current-year `.sty` with `[final]` , +1 page cap, OpenReview camera-ready task
anything else	venue's own instructions	generic checklist printed by the script; verify everything live

De-anonymize and apply the +page rules (blind venues). Do this BEFORE any rights form — eRights/eCF need the exact final author list and title. Work through references/deanonymize-and-extra-pages.md: restore authors/affiliations/ORCIDs, acknowledgments and funding, real artifact links, PDF metadata; then fit the paper to the camera-ready page budget (never assume an allowance — the reference lists the known rules per family).
Lint the final source. After edits, run:
```
python3 scripts/check_camera_ready.py final.tex \
    --venue venues/conferences/<venue>-<year>.yml --track "<track>"
```
It follows
```
\input
```
/
```
\include
```
and reports
```
file:line
```
findings: leftover
```
review
```
/
```
anonymous
```
/
```
submission
```
options, "Anonymous Author" placeholders,
```
anonymous.4open.science
```
links, missing author block, line numbers/todos — plus per rail: ACM rights/DOI block presence and placeholder DOI/ISBN values, CCS concepts and
```
\keywords
```
; IEEE page-number suppression and copyright-notice reminder; NeurIPS-style current-year
```
.sty
```
with
```
[final]
```
. Flags:
```
--json
```
,
```
--strict
```
,
```
--no-inputs
```
. Exit codes: 0 clean, 1 errors, 2 usage. Fix and re-run until PASS.
Close out the manual gates. The lint cannot see forms or portals. Confirm with the user, one by one: rights form completed (by the corresponding author, exact title/author match), validation certificate received (IEEE), files uploaded to the right collection site under the right name, proofs approved (ACM TAPS), author registration done before the registration deadline, and a presenting author committed (no-show = removal from the proceedings at IEEE and many ACM venues).

确定流程体系并生成清单。找到配置文件，询问用户论文被录用的赛道（不同赛道的Camera-Ready终稿截止日期和页数限制不同），然后运行：
```
python3 scripts/camera_ready_checklist.py venues/conferences/<venue>-<year>.yml --track "<track>"
```
该脚本会合并同系列会议的配置文件，确定流程体系（
```
acm-taps
```
、
```
ieee-pdfexpress
```
、
```
openreview-direct
```
或其他），并输出有序步骤、会议特定要求、截止日期和额外页数规则。添加
```
--json
```
参数可获取机器可读格式的输出。
对照实时来源重新验证——强制要求。Camera-Ready终稿说明会根据每个录用周期发布，且会议可能更换流程体系（例如FAccT不再使用TAPS）。在用户执行任何操作前：阅读录用邮件中的说明，获取会议的Camera-Ready终稿页面，重新检查配置文件中的
```
cfp_url
```
。至少确认以下内容：Camera-Ready终稿截止日期及时区、页数限制及额外页数许可、流程体系、最终文件提交地点（通常不是评审系统——ICDE 2026明确要求“请勿将Camera-Ready终稿上传至CMT”）。如果有任何不一致，请更新配置文件YAML并告知用户。

逐步完成流程。与用户一起按照清单操作，使用对应流程体系的详细指南：

流程体系	指南链接	关键节点
`acm-taps`	references/acm-taps-rail.md	eRights邮件（通讯作者需查收，注意垃圾邮件）、所有作者的ORCID、序言中的版权/DOI块、上传源文件压缩包至TAPS、PDF+HTML校样——需预留数周时间
`ieee-pdfexpress`	references/ieee-pdfexpress-rail.md	PDF eXpress会议ID、Xplore验证证书、文件命名（例如 `PID<n>.pdf` ）、eCF需精确匹配标题/作者信息（无法修改）、注册/缺席处理
`openreview-direct`	清单输出中的流程步骤 + 会议配置文件	当年版本的 `.sty` 文件需添加 `[final]` 参数、最多允许1页额外页数、OpenReview的Camera-Ready终稿任务
其他	会议自身的说明	脚本生成的通用清单；所有内容需实时验证

去除匿名化并应用额外页数规则（盲审会议）。此步骤需在任何版权表单填写前完成——eRights/eCF需要精确的最终作者列表和标题。按照references/deanonymize-and-extra-pages.md操作：恢复作者/机构/ORCID信息、致谢和资助信息、真实的成果链接、PDF元数据；然后调整论文以符合Camera-Ready终稿的页数限制（切勿默认存在额外页数许可——参考文档中列出了各系列会议的已知规则）。
检查最终源文件。编辑完成后，运行：
```
python3 scripts/check_camera_ready.py final.tex \
    --venue venues/conferences/<venue>-<year>.yml --track "<track>"
```
该脚本会追踪
```
\input
```
/
```
\include
```
命令，并以
```
file:line
```
格式报告问题：残留的
```
review
```
/
```
anonymous
```
/
```
submission
```
选项、“Anonymous Author”占位符、
```
anonymous.4open.science
```
链接、缺失的作者块、行号/待办事项——此外还会针对不同流程体系检查：ACM版权/DOI块是否存在、DOI/ISBN占位符是否替换、CCS概念和
```
\keywords
```
是否齐全；IEEE是否禁用页码、是否提醒版权声明；NeurIPS风格的当年
```
.sty
```
文件是否添加
```
[final]
```
参数。可用参数：
```
--json
```
、
```
--strict
```
、
```
--no-inputs
```
。退出码：0表示检查通过，1表示存在错误，2表示使用不当。修复问题后重新运行，直到检查通过。
完成手动节点确认。检查脚本无法查看表单或门户内容。需逐一与用户确认：版权表单已完成（由通讯作者填写，标题/作者信息精确匹配）、已收到验证证书（IEEE）、文件已上传至正确的提交站点且命名符合要求、校样已确认（ACM TAPS）、作者已在注册截止日期前完成注册、已确定演讲作者（IEEE和许多ACM会议中，缺席会导致论文被从论文集中移除）。

Output

输出结果

An ordered, venue-specific camera-ready checklist with deadline, rail, extra-page rule, and re-verification warnings (step 1).
Concrete edits to the final source (rights block, de-anonymization, metadata) applied with the user's approval.
A lint report (PASS / PASS-WITH-WARNINGS / FAIL with
```
file:line
```
) plus the list of remaining manual gates and their dates.

一份有序的、针对特定会议的Camera-Ready终稿清单，包含截止日期、流程体系、额外页数规则和重新验证警告（步骤1）。
经用户确认后，对最终源文件进行具体修改（版权块、去匿名化、元数据）。
一份检查报告（通过/带警告通过/失败，含
```
file:line
```
信息），以及剩余手动节点及其截止日期列表。

Worked example

示例操作

A paper accepted at an ACM/TAPS venue, still in its submission state: it carries

[review,anonymous]

, the acmart placeholder DOI/ISBN, an "Anonymous Author(s)" block, and an

anonymous.4open.science

link, with no rights block or CCS concepts yet. Linting the source against the venue profile:

python3 scripts/check_camera_ready.py paper.tex \
    --venue venues/conferences/sigspatial-2026.yml --track Research

ERROR final/submission-mode-option       paper.tex:1   documentclass still carries [review] — camera-ready must drop submission/review-mode options
ERROR final/submission-mode-option       paper.tex:1   documentclass still carries [anonymous] — ...
ERROR final/anonymous-placeholder        paper.tex:7   anonymization placeholder still present: '\author{Anonymous'
ERROR final/anonymized-link              paper.tex:10  anonymized artifact link still present: 'anonymous.4open.science' — swap in the real repository URL
ERROR acm/rights-block-missing                     -   \acmConference (or \acmJournal) not found — part of the eRights rights/DOI block
ERROR acm/placeholder-rights-value       paper.tex:4  \acmDOI{10.1145/nnnnnnn.nnnnnnn} looks like the acmart template placeholder — replace it with YOUR eRights value
ERROR acm/ccs-concepts-missing                     -   CCS concepts missing (CCSXML block + \ccsdesc) — generate them at https://dl.acm.org/ccs; TAPS requires them
ERROR acm/keywords-missing                         -   \keywords{...} missing — mandatory in ACM camera-ready
WARN  final/review-artifact              paper.tex:3   review-time artifact still present: '\linenumbers'

verdict: FAIL (rail=acm-taps, errors=8, warnings=1)
reminder: a clean lint covers the SOURCE only — rights forms, PDF eXpress, eCF, and registration remain manual steps.

How to present this: lead with the ERRORs as an ordered fix-list — drop

[review,anonymous]

, restore the real author block, swap the

anonymous.4open.science

URL, paste the rights/DOI block and CCS/keywords from the completed eRights form — each with its

file:line

and the one-line edit; then the

\linenumbers

WARN as a judgment call. Note the order: the rights-block and CCS errors cannot clear until the eRights form is done, so the form is the gating dependency, not the source edit. Re-run the linter after each fix until it PASSes, and remind the user the lint never sees the form, the TAPS upload, or the proofs.

一篇被ACM/TAPS会议录用的论文，仍处于提交状态：文档类带有

[review,anonymous]

参数、acmart模板的DOI/ISBN占位符、“Anonymous Author(s)”作者块、

anonymous.4open.science

链接，且尚未添加版权块或CCS概念。针对会议配置文件检查源文件：

python3 scripts/check_camera_ready.py paper.tex \
    --venue venues/conferences/sigspatial-2026.yml --track Research

ERROR final/submission-mode-option       paper.tex:1   documentclass still carries [review] — camera-ready must drop submission/review-mode options
ERROR final/submission-mode-option       paper.tex:1   documentclass still carries [anonymous] — ...
ERROR final/anonymous-placeholder        paper.tex:7   anonymization placeholder still present: '\author{Anonymous'
ERROR final/anonymized-link              paper.tex:10  anonymized artifact link still present: 'anonymous.4open.science' — swap in the real repository URL
ERROR acm/rights-block-missing                     -   \acmConference (or \acmJournal) not found — part of the eRights rights/DOI block
ERROR acm/placeholder-rights-value       paper.tex:4  \acmDOI{10.1145/nnnnnnn.nnnnnnn} looks like the acmart template placeholder — replace it with YOUR eRights value
ERROR acm/ccs-concepts-missing                     -   CCS concepts missing (CCSXML block + \ccsdesc) — generate them at https://dl.acm.org/ccs; TAPS requires them
ERROR acm/keywords-missing                         -   \keywords{...} missing — mandatory in ACM camera-ready
WARN  final/review-artifact              paper.tex:3   review-time artifact still present: '\linenumbers'

verdict: FAIL (rail=acm-taps, errors=8, warnings=1)
reminder: a clean lint covers the SOURCE only — rights forms, PDF eXpress, eCF, and registration remain manual steps.

如何呈现此结果：首先将错误按顺序整理为修复清单——移除

[review,anonymous]

参数、恢复真实作者块、替换

anonymous.4open.science

链接、粘贴已完成的eRights表单中的版权/DOI块和CCS/关键词——每个修复项都包含

file:line

位置和单行编辑说明；然后将

\linenumbers

警告作为可自主判断的项。注意顺序：版权块和CCS错误需在完成eRights表单后才能修复，因此表单是前置依赖项，而非源文件编辑。每次修复后重新运行检查脚本，直到通过，并提醒用户检查脚本无法查看表单、TAPS上传或校样状态。

Adapt to your discipline

适配不同学科

The rails here are ACM/IEEE/ML-conference specific. For other fields, add your publisher's rail to the venue family files (e.g. Springer LNCS source upload, Elsevier/Wiley journal production systems) — the checklist script reads whatever

camera_ready.requirements

the profile provides.

此处的流程体系针对ACM/IEEE/机器学习会议。对于其他领域，可在会议系列文件中添加对应出版商的流程体系（例如Springer LNCS源文件上传、Elsevier/Wiley期刊出版系统）——清单脚本会读取配置文件中提供的任何

camera_ready.requirements

内容。

Guardrails

注意事项

Never complete eRights, eCF, TAPS, PDF eXpress, or any portal on the user's behalf, and never upload anything anywhere. Prepare, explain, lint — the user clicks.
Rights forms are one-shot in practice (eCF cannot be redone; eRights metadata overrides the source). Triple-check title and author list/order with the user BEFORE they submit a form.
Never guess deadlines, conference IDs, ISBN/price strings, or DOI values — they come from the acceptance email, the live venue page, or the completed rights form. Profiles are a starting point, never ground truth (step 2 is not optional).
Page budgets: never assume a camera-ready extra-page allowance that is not stated by the venue for this year.
New or changed citations during camera-ready edits go through
```
verify-citations
```
before they enter the .bib.
Quote at most the flagged line of the user's paper in reports; never reproduce paper text at length, and never bundle paper content into the repo.

**切勿代用户完成eRights、eCF、TAPS、PDF eXpress或任何门户操作，也切勿上传任何文件至任何平台。**仅提供准备、解释和检查服务——所有点击操作均由用户自行完成。
版权表单实际上只能提交一次（eCF无法修改；eRights元数据会覆盖源文件内容）。在用户提交表单前，需与用户反复确认标题和作者列表/顺序。
切勿猜测截止日期、会议ID、ISBN/价格字符串或DOI值——这些信息需来自录用邮件、实时会议页面或已完成的版权表单。配置文件仅作为起点，绝非权威信息（步骤2为强制要求）。
页数限制：切勿默认存在会议当年未明确说明的Camera-Ready终稿额外页数许可。
Camera-Ready终稿编辑期间新增或修改的引用，需先通过
```
verify-citations
```
检查，再加入.bib文件。
在报告中最多引用用户论文中被标记的行；切勿大量复制论文文本，也切勿将论文内容存入仓库。