4drawio

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

DrawIO 非数据图示绘制

DrawIO Non-Data Diagram Creation

本 skill 承接

3coding-visual

。它只负责论文中的非数据型图示，例如技术路线图、求解流程图、模型结构图、数据处理流程图、变量关系图、指标体系图等。

This skill follows

3coding-visual

. It is responsible only for non-data diagrams in the paper, such as technical roadmaps, solution flowcharts, model structure diagrams, data processing flowcharts, variable relationship diagrams, indicator system diagrams, and so on.

数学建模规范参考

Mathematical Modeling Standards Reference

如需领域判断，读取

../_references/math_modeling_norms.md

中的“图表与可视化”和“非数据图工具选择”小节。该文件只作为规范知识库，不要求为了凑数量生成额外图示。

If domain judgment is needed, read the “Charts and Visualization” and “Non-Data Diagram Tool Selection” sections in

../_references/math_modeling_norms.md

. This file serves only as a standards knowledge base; do not generate extra diagrams merely to increase the count.

阶段边界

Stage Boundaries

本阶段负责：DrawIO 源文件、非数据图 PDF、图示生成记录。
本阶段不负责：折线图、柱状图、散点图、热力图、箱线图、雷达图等数据图。这些由
```
3coding-visual
```
生成。
本阶段不重跑模型、不修改
```
code/
```
，不改写
```
reports/RESULTS_REPORT.md
```
的数值结论。

This stage is responsible for: DrawIO source files, non-data diagram PDFs, and diagram generation records.
This stage is not responsible for: line charts, bar charts, scatter plots, heatmaps, box plots, radar plots, and other data-driven charts. These are generated by
```
3coding-visual
```
.
This stage does not rerun models, modify
```
code/
```
, or rewrite the numerical conclusions in
```
reports/RESULTS_REPORT.md
```
.

必须产出

Required Outputs

在当前工作目录创建或更新：

text

figures/
  fig_roadmap.drawio
  fig_roadmap.pdf
  fig_flow_q1.drawio
  fig_flow_q1.pdf
  ...
reports/DRAWIO_REPORT.md

如果某类图不需要生成，在

reports/DRAWIO_REPORT.md

中说明原因。不要把技术路线图当作固定数量要求；只有它能传达真实方法关系时才生成。

读取这些文件的目的不是提取数据作图，而是理解论文方法、章节结构、子问题关系和已有图表，避免重复。

Create or update the following files in the current working directory:

text

figures/
  fig_roadmap.drawio
  fig_roadmap.pdf
  fig_flow_q1.drawio
  fig_flow_q1.pdf
  ...
reports/DRAWIO_REPORT.md

If a particular type of diagram is not needed, explain the reason in

reports/DRAWIO_REPORT.md

. Do not treat the technical roadmap as a fixed-count requirement; generate it only if it can communicate genuine methodological relationships.

The purpose of reading these files is not to extract data for charting, but to understand the paper’s methodology, chapter structure, subproblem relationships, and existing figures, thereby avoiding duplication.

工作流程

Workflow

Step 1: 盘点已有图表和需求

Step 1: Inventory Existing Figures and Requirements

先读取以下文件（存在则读取）：

reports/ANALYSIS_MODELING_REPORT.md

、

reports/RESULTS_REPORT.md

、

figures/

目录列表。

然后从前序文档提取非数据图需求，输出一个清单：

text

DRAWIO PLAN CHECKLIST:
[ ] fig_roadmap      技术路线图，放在问题重述/绪论
[ ] fig_flow_q1      问题一求解流程图
[ ] fig_flow_q2      问题二求解流程图
[ ] fig_flow_q3      问题三求解流程图
[ ] fig_pipeline     数据处理流程图
[ ] fig_model        模型结构/变量关系图

清单不是固定模板，要根据题目实际删减或增补。不要为了凑图生成无意义图示。

First read the following files if they exist:

reports/ANALYSIS_MODELING_REPORT.md

reports/RESULTS_REPORT.md

, and the

figures/

directory listing.

Then extract the non-data diagram requirements from the preceding documents and output a checklist:

text

DRAWIO PLAN CHECKLIST:
[ ] fig_roadmap      Technical roadmap, placed in the Problem Restatement/Introduction
[ ] fig_flow_q1      Problem 1 solution flowchart
[ ] fig_flow_q2      Problem 2 solution flowchart
[ ] fig_flow_q3      Problem 3 solution flowchart
[ ] fig_pipeline     Data processing flowchart
[ ] fig_model        Model structure/variable relationship diagram

The checklist is not a fixed template. Adjust it according to the actual problem by removing or adding items. Do not generate meaningless diagrams just to increase the count.

Step 2: 判定图类型

Step 2: Determine the Diagram Type

常见图示选择：

图类型	文件名建议	适用场景
技术路线图	`fig_roadmap`	展示整体解题路线、章节逻辑、方法串联
子问题求解流程图	`fig_flow_q1` , `fig_flow_q2`	展示单个子问题的输入、判断、算法、输出
数据处理流程图	`fig_pipeline`	展示数据清洗、特征构造、建模输入
模型结构图	`fig_model`	展示模块关系、变量关系、模型层次
指标体系图	`fig_index_system`	展示目标层、准则层、指标层
决策树/规则图	`fig_decision_tree`	展示分类规则、设备选择、策略分支

不要用 DrawIO 画这些图：

结果对比柱状图
预测误差曲线
灵敏度曲线
相关性热力图
分布图和箱线图

Common diagram choices:

Diagram Type	Suggested Filename	Use Case
Technical roadmap	`fig_roadmap`	Present the overall solution route, chapter logic, and method sequence
Subproblem solution flowchart	`fig_flow_q1` , `fig_flow_q2`	Present the inputs, decisions, algorithms, and outputs of an individual subproblem
Data processing flowchart	`fig_pipeline`	Present data cleaning, feature construction, and model inputs
Model structure diagram	`fig_model`	Present module relationships, variable relationships, and model hierarchy
Indicator system diagram	`fig_index_system`	Present the objective, criteria, and indicator layers
Decision tree/rule diagram	`fig_decision_tree`	Present classification rules, equipment selection, or strategy branches

Do not use DrawIO for the following:

Result comparison bar charts
Prediction error curves
Sensitivity curves
Correlation heatmaps
Distribution plots and box plots

Step 3: 生成 DrawIO 源文件

Step 3: Generate DrawIO Source Files

每张图一个

.drawio

文件，放在

figures/

。

DrawIO 内容要求：

文字语言与论文语言一致。
节点文字短，必要时双行，不堆长句。
同类节点样式统一。
箭头方向清晰，避免交叉。
图中不写大段解释，解释留给论文正文。
不使用装饰性阴影和过度渐变。

生成大 XML 时使用可靠的文件编辑方式分段完成并复查尾部闭合，避免截断。

Create one

.drawio

file per diagram and place it in

figures/

DrawIO content requirements:

Use the same text language as the paper.
Keep node text short, using two lines if necessary; do not stack long sentences.
Use consistent styles for nodes of the same type.
Keep arrow directions clear and avoid crossings.
Do not place lengthy explanations in the diagram; leave them in the paper’s main text.
Do not use decorative shadows or excessive gradients.

When generating a large XML file, use a reliable file-editing approach that writes it in sections and then verify that the closing tags are complete to avoid truncation.

Step 4: 导出 PDF

Step 4: Export PDFs

优先用可用的 DrawIO 命令导出 PDF：

bash

DRAWIO_BIN="$(command -v drawio 2>/dev/null || command -v draw.io 2>/dev/null || command -v draw.io.exe 2>/dev/null || true)"
if [ -n "$DRAWIO_BIN" ]; then
  "$DRAWIO_BIN" --export --format pdf --crop --output figures/fig_roadmap.pdf figures/fig_roadmap.drawio
else
  echo "DrawIO command not found; keep .drawio source and record export failure."
fi

如果无法导出 PDF，保留

.drawio

，在

reports/DRAWIO_REPORT.md

记录失败原因和建议导出命令。

Prefer an available DrawIO command to export PDFs:

bash

DRAWIO_BIN="$(command -v drawio 2>/dev/null || command -v draw.io 2>/dev/null || command -v draw.io.exe 2>/dev/null || true)"
if [ -n "$DRAWIO_BIN" ]; then
  "$DRAWIO_BIN" --export --format pdf --crop --output figures/fig_roadmap.pdf figures/fig_roadmap.drawio
else
  echo "DrawIO command not found; keep .drawio source and record export failure."
fi

If PDF export is unavailable, retain the

.drawio

file and record the failure reason and the recommended export command in

reports/DRAWIO_REPORT.md

Step 5: 自检和修复

Step 5: Self-Inspection and Repair

每张图必须检查：

```
.drawio
```
文件非空。
若导出成功，
```
.pdf
```
文件非空。
节点没有明显重叠。
箭头不穿过核心节点。
字号、颜色、边框风格一致。
文件名和图意一致。
没有与
```
3coding-visual
```
的数据图重复。

发现问题要修

.drawio

并重新导出，不要只在报告里解释。

Every diagram must be checked for the following:

The
```
.drawio
```
file is not empty.
If the export succeeds, the
```
.pdf
```
file is not empty.
Nodes do not visibly overlap.
Arrows do not pass through core nodes.
Font sizes, colors, and border styles are consistent.
The filename matches the diagram’s meaning.
The diagram does not duplicate a data chart from
```
3coding-visual
```
.

If any issue is found, fix the

.drawio

file and export it again. Do not merely explain the issue in the report.

Step 6: 写生成记录

Step 6: Write the Generation Record

创建

reports/DRAWIO_REPORT.md

，至少包含：

markdown

undefined

Create

reports/DRAWIO_REPORT.md

containing at least the following:

markdown

undefined

DrawIO 图示生成报告

DrawIO Diagram Generation Report

图示清单

Diagram Inventory

文件	类型	来源依据	用途	状态

File	Type	Source Basis	Purpose	Status

未生成图示及原因

Ungenerated Diagrams and Reasons

导出与自检记录

Export and Self-Inspection Log

给论文阶段的嵌入建议

Embedding Recommendations for the Paper Stage


CUMCM 2026 模式下，图示清单还要记录“是否含 AI 生成结构”和“人工检查状态”，并把本阶段的 AI 参与追加到 `compliance/AI_USAGE_LOG.md`。不得把未完成人工检查写成“已核验”。

嵌入建议只说明每张图适合放入哪个章节和建议 caption，不生成 `*_typst_includes.typ`。最终的图表插入代码（Typst 的 `#figure(image(...), caption: [...])` 或 LaTeX 的 `\begin{figure}...\end{figure}`）由 `5writing` 根据论文结构和所选引擎决定。


In CUMCM 2026 mode, the diagram inventory must also record whether it contains an AI-generated structure and the manual inspection status. Append this stage’s AI involvement to `compliance/AI_USAGE_LOG.md`. Do not represent an incomplete manual inspection as “verified.”

Embedding recommendations should only identify the chapter appropriate for each diagram and suggest a caption. Do not generate `*_typst_includes.typ`. The final figure insertion code, whether Typst’s `#figure(image(...), caption: [...])` or LaTeX’s `\begin{figure}...\end{figure}`, is determined by `5writing` based on the paper structure and selected engine.

质量要求

Quality Requirements

图示服务论文论证，不为装饰而画。
每张图必须能对应到
```
reports/ANALYSIS_MODELING_REPORT.md
```
中的真实方法。
数据型图表不得在本阶段重复生成。
论文阶段引用的非数据图都应有
```
.drawio
```
源文件和 PDF，或者在
```
reports/DRAWIO_REPORT.md
```
说明导出失败。

Diagrams should support the paper’s argumentation rather than serve as decoration.
Every diagram must correspond to a real method in
```
reports/ANALYSIS_MODELING_REPORT.md
```
.
Data-driven charts must not be regenerated during this stage.
Every non-data diagram cited during the paper stage must have both a
```
.drawio
```
source file and a PDF, or the export failure must be explained in
```
reports/DRAWIO_REPORT.md
```
.