cumcm-paper-writing

name

cumcm-paper-writing

description

Write, revise, typeset, and audit Chinese papers for the China Undergraduate Mathematical Contest in Modeling (CUMCM/全国大学生数学建模竞赛). Use when an AI coding agent needs to turn a CUMCM problem, data, model, code, figures, or draft into a competition-ready LaTeX paper; create a paper project from the bundled cumcmthesis template; draft the abstract, problem restatement, analysis, assumptions, notation, model construction and solution, validation, evaluation, references, or appendices; or check a manuscript against the team's teacher-specified structure, citation, page, and non-AI-sounding style rules.

CUMCM Paper Writing

Start every task

1. Identify the problem statement, competition year, available data, completed models, verified numerical results, figures, code, and requested deliverable.
2. Distinguish verified facts from planned work. Never invent data, results, citations, model performance, or sensitivity outcomes. Mark unresolved items with explicit TODO comments in drafts.
3. Read references/teacher-requirements.md before creating or restructuring a full paper.
4. Read references/writing-style.md before drafting or polishing prose.
5. Read references/latex-workflow.md when creating, compiling, or repairing a LaTeX project.

Choose the operation

• Create a new project by running python3 scripts/create_project.py OUTPUT_DIR, then edit paper.tex.
• Work inside the user's existing project when one is supplied. Preserve its class, macros, bibliography system, figures, and unrelated edits unless they conflict with an explicit requirement.
• Edit only the requested sections when the user supplies a partial draft. Check neighboring sections for terminology and symbol consistency.
• Audit a TeX draft by running python3 scripts/check_paper.py PATH_TO_TEX --competition-year YEAR. Treat errors as blockers and inspect warnings manually.

Build the paper from evidence

1. Create an evidence ledger before prose: map each requested question to inputs, assumptions, model, solver, outputs, checks, figures, tables, and citations.
2. Define one canonical name and symbol for every important quantity. Reuse them across prose, formulas, figures, tables, and code.
3. Draft Chapter 5 first because it contains the actual method and evidence. Draft the problem analysis from the completed technical route, then write the abstract last.
4. Make every result traceable to a computation, table, figure, or supplied fact. Use exact values and units when available.
5. Separate model construction, solution procedure, result, validation, and short conclusion. Do not mix future-tense planning from Chapter 2 with completed-work narration from Chapter 5.
6. Cross-reference every numbered formula, figure, and table that contributes to the argument. Explain what the reader should infer; do not merely announce that an object exists.
7. Cite sources in order of first appearance and verify each bibliographic field against a real source.

Enforce the submission form

• Start the submitted PDF on the title-and-abstract page. Use \documentclass[withoutpreface,bwprint]{cumcmthesis} and retain \maketitle. Do not generate the commitment page or numbering-information page.
• Do not add a table of contents.
• Keep the abstract on one page. The class bundled here starts the body on a new page after the abstract.
• Treat 30 pages as both the preferred target and the maximum for the main text. Count from the abstract through references and exclude appendices. Aim to end the references on page 30 when the verified evidence supports it; never exceed the current official limit.
• Reach the page target with substantive modeling, solution details, validation, sensitivity analysis, figures, tables, and discussion. Never pad the paper with blank space, repeated conclusions, inflated prose, oversized figures, or unnecessary tables.
• Put all program code in Appendix A and keep that code appendix to one or two pages. Remove boilerplate and repeated code, use concise readable listings, and retain every part needed to reproduce the reported results. Group code by problem with subsections inside Appendix A when needed. Never create separate code appendices for different problems. Reserve Appendix B and later appendices for non-code supplementary material; omit them when no such material exists.
• Use XeLaTeX, preferably latexmk -xelatex paper.tex. Compile until cross-references settle.
• Render the final PDF and inspect every page for clipping, blank pages, displaced floats, unreadable text, broken formulas, table overflow, and incorrect page numbering.

Write like a modeling team

• Prefer direct Chinese sentences that state the object, operation, basis, and result.
• Minimize prose parentheses. Reserve them for unavoidable units, symbols, citations, or brief technical definitions. Rewrite side remarks as full sentences or commas.
• Avoid generic transitions, inflated claims, symmetrical filler, repeated conclusions, and stock AI phrases. Follow the replacement patterns in the style reference.
• Use a neutral, third-person academic voice. Prefer 本文 or the actual model name when an agent must be stated; avoid repeatedly writing 我们.
• Keep uncertainty visible. State limitations, sampling constraints, assumptions, and failure conditions concretely.

Final gate

1. Run the checker and resolve every error.
2. Confirm that the abstract contains no formulas, figures, or tables and that its four to six keywords are exact mathematical terms used in the abstract.
3. Confirm that every problem has model establishment, solution, conclusion, validation or sensitivity analysis, and a short summary.
4. Confirm that all references are cited, ordered by first appearance, recent enough for the teacher's rolling five-year rule, and formatted with [D] instead of [M] when that source-type marker is required.
5. Search for prose parentheses and flagged AI-style phrases; revise them manually rather than mechanically deleting meaning.
6. Confirm that the abstract through references occupies exactly 30 pages when feasible and never exceeds 30 pages. Do not use filler to manufacture the page count.
7. Confirm that Appendix A contains all reproducible code in one or two pages and that Appendix B and later appendices contain no code.
8. Compile and visually inspect the final PDF. Report any unresolved evidence or formatting limitation instead of concealing it.