ccf-submission-checker

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

CCF Submission Checker

CCF投稿检查工具

Core Rule

核心规则

Treat submission as a build, venue-policy, page-budget, and artifact-readiness gate. Use local venue guides for expected rules, then require official-policy freshness for final decisions. Do not rewrite paper content.

将投稿视为构建、会议政策、页数预算和成果就绪的关卡。使用本地会议指南了解预期规则，最终决策需以官方政策的时效性为准。请勿重写论文内容。

Modes

模式

```
venue-format
```
: template, page limit, anonymity, author block, supplementary and camera-ready rules.
```
package-check
```
: LaTeX/PDF build, metadata, fonts, page count, file structure, and submission checklist.
```
artifact
```
: code/data/model release plan, environment, seeds, hardware, licenses, artifact README, and reproducibility appendix.
```
full
```
: venue + package + artifact.

```
venue-format
```
: 模板、页数限制、匿名性、作者栏、补充文件及终稿规则。
```
package-check
```
: LaTeX/PDF构建、元数据、字体、页数、文件结构及投稿检查清单。
```
artifact
```
: 代码/数据/模型发布计划、环境、随机种子、硬件、许可证、成果README文档及可复现性附录。
```
full
```
: 会议格式检查 + 包检查 + 成果检查。

Workflow

工作流程

Identify venue/year/track, submission mode, project directory, TeX/PDF files, supplementary/artifact files, and deadline pressure.
Read
```
ccfa.yaml
```
when available. If absent, proceed with supplied files and state that project-state tracking is unavailable.
For venue questions, read
```
../ccf-paper-writer/references/venue-guides/index.md
```
and the specific venue guide before checking official freshness.
For package checks, inspect compile status, page count, target page budget, anonymity, fonts, PDF metadata, template path, references, supplementary files, and required forms.
For artifact checks, build a reproducibility checklist: code, data, models, environment, seeds, hardware, license, access restrictions, and README.
Hand off to
```
ccf-paper-writer
```
for text/page rewrites: compression when over limit, expansion when a full manuscript is materially underfilled, and normal polishing when within budget. Hand off to
```
ccf-experiment-designer
```
for missing reproducibility experiments,
```
ccf-visual-composer
```
for figure/table float order, caption placement, font, clipping, palette, or visual readability fixes, and
```
ccf-rebuttal-writer
```
for post-review response packaging.

确定会议/年份/赛道、投稿模式、项目目录、TeX/PDF文件、补充/成果文件以及截止日期压力。
若存在
```
ccfa.yaml
```
文件则读取该文件；若不存在，则使用提供的文件进行检查，并说明无法跟踪项目状态。
针对会议相关问题，先阅读
```
../ccf-paper-writer/references/venue-guides/index.md
```
及特定会议指南，再检查官方政策的时效性。
针对包检查，核查编译状态、页数、目标页数预算、匿名性、字体、PDF元数据、模板路径、参考文献、补充文件及所需表单。
针对成果检查，制定可复现性检查清单：代码、数据、模型、环境、随机种子、硬件、许可证、访问限制及README文档。
若页数超限需压缩、页数严重不足需扩充，或在预算范围内需常规润色，将任务移交
```
ccf-paper-writer
```
处理；若缺少可复现性实验，移交
```
ccf-experiment-designer
```
；若图表浮动顺序、标题位置、字体、裁剪、调色板或视觉可读性需修正，移交
```
ccf-visual-composer
```
；若需处理审稿后回复打包，移交
```
ccf-rebuttal-writer
```
。

Output Contract

输出规范

text

Mode:
Venue and rule freshness:
Files checked:
Pass/fail checklist:
Build/package issues:
Anonymity/page/font/metadata issues:
Length budget status:
Artifact/reproducibility issues:
Required fixes:
Next CCFA owner:

text

模式：
会议及规则时效性：
已检查文件：
通过/未通过检查清单：
构建/包问题：
匿名性/页数/字体/元数据问题：
页数预算状态：
成果/可复现性问题：
所需修复项：
下一任CCFA负责人：