Use when preparing an accepted ACM CCS paper for the ACM Digital Library proceedings, covering de-anonymization, the ACM sigconf final format, ACM rights and eRights forms, badge placement from artifact evaluation, incorporation of shepherd and minor-revision requirements, disclosure-timing coordination, registration, and in-person presentation.
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
Use this after acceptance or after clearing a minor revision. Reopen the current CCS camera-ready instructions, the ACM rights form, the registration page, and the notification or shepherd email before advising authors.
sigconf final template and the ACM rights-management block; the DOI, the
conference reference string, and the copyright notice come from the ACM eRights system.| Badge earned in artifact evaluation | Where it goes | What to confirm |
|---|---|---|
| Artifacts Available | First page, with the archival DOI/URL | The archive is public and permanent before camera-ready |
| Artifacts Evaluated - Functional | First page | The committee's functional result is final |
| Artifacts Evaluated - Reusable | First page | Documentation matches the reusable claim |
| Results Reproduced | First page | The reproduced results match the camera-ready numbers |
sigconf build changes spacing; recheck
every page break, protocol figure, and wide result table after adding the author block.The shepherd asked that the adaptive-attack results move from the appendix into the main evaluation. Camera-ready move: promote the adaptive table into Section 6, add one sentence interpreting the degraded defense numbers honestly, and leave the full attack derivation in the appendix — without strengthening any claim the reviewers did not see.
[Camera-ready status] Ready / Needs fixes / Blocked
[Final package] <PDF / source / bib / ACM rights form / badges / artifacts>
[Policy checks] <format / authors / disclosure timing / registration / presentation>
[Reviewer-change map] <shepherd/revision requirement -> final edit>
[Remaining owner] <person -> task>
还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Use when packaging AAAI code, data, multimedia appendices, technical appendices, reproducibility evidence, and post-acceptance artifact releases without violating double-blind or immutable-supplement rules.
中文简介正在准备中。当前显示原文说明。
Use when drafting an AAAI author response (rebuttal) under the single short character-limited author-feedback window, the no-URL rule, no-new-results guidance, AI-generated-review handling, and the AAAI two-phase review process where Phase-2 papers receive one feedback round before SPC/AC discussion.
中文简介正在准备中。当前显示原文说明。
Use when preparing an accepted AAAI paper for camera-ready source submission to AAAI Press, including proceedings page limits, two-column template compliance, copyright transfer, purchased extra technical pages, deanonymization, registration, oral or poster presentation, and final public artifact release.
中文简介正在准备中。当前显示原文说明。
Use when designing or auditing AAAI experiments for the broad-AI program committee, including baselines, ablations, statistical significance, robustness, human evaluation, AI-for-Social-Impact and alignment/safety evidence, compute and cost reporting, and reproducibility-checklist alignment for Phase-1 survival.
中文简介正在准备中。当前显示原文说明。
Use when positioning an AAAI paper's novelty against archival work, contemporaneous arXiv or workshop papers, and AAAI/IJCAI/NeurIPS/ICML/ICLR neighbors across the broad AI scope, while staying inside AAAI's dual-submission and AI-as-source policy constraints and writing a related-work section legible to non-specialist reviewers.
中文简介正在准备中。当前显示原文说明。
Use when strengthening an AAAI paper's reproducibility checklist (placed after references), experimental traceability, seed and hyperparameter reporting, compute and cost disclosure, dataset access and licensing, code/data ZIP readiness, and the claim-to-evidence map that Phase-1 reviewers use to judge rigor across AAAI's broad AI scope.
中文简介正在准备中。当前显示原文说明。