GaviZhou commited on
Commit
7594871
·
verified ·
1 Parent(s): 60f4535

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +104 -3
README.md CHANGED
@@ -1,3 +1,104 @@
1
- ---
2
- license: apache-2.0
3
- ---
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
1
+ ---
2
+ license: apache-2.0
3
+ ---
4
+
5
+ # Omni-I2C: Image2Code_Full
6
+
7
+ ## Dataset Description
8
+
9
+ `Image2Code_Full.tsv` is the inference split of the **Omni-I2C** benchmark. It is designed to evaluate whether multimodal models can generate high-fidelity code or structured outputs from input images.
10
+
11
+ Each sample contains an image, an instruction, and metadata describing the target task. The goal is to generate code or a structured string that can reproduce the original figure as accurately as possible.
12
+
13
+ - **Number of samples:** 1,080
14
+ - **Number of subjects:** 8
15
+ - **Number of figure types:** 45
16
+ - **Number of code types:** 5
17
+
18
+ Project repository: [Omni-I2C on GitHub](https://github.com/MiliLab/Omni-I2C)
19
+
20
+ ## Data Fields
21
+
22
+ The dataset is stored as a 7-column TSV file with the following header:
23
+
24
+ ```tsv
25
+ index image question answer subject figure_type code_type
26
+ ````
27
+
28
+ | Field | Description |
29
+ | ------------- | ------------------------------------------------------------------------------- |
30
+ | `index` | Unique sample identifier. |
31
+ | `image` | Input image stored as a base64-encoded string. |
32
+ | `question` | Instruction text for the generation task. |
33
+ | `answer` | Filename of the ground-truth reference file. This is not the full code content. |
34
+ | `subject` | Subject or application domain. |
35
+ | `figure_type` | Fine-grained figure category. |
36
+ | `code_type` | Target output format or code type. |
37
+
38
+ ## Task Description
39
+
40
+ This is an **image-to-code** inference dataset. Given an input image and an instruction, the model is expected to generate an executable, renderable, or otherwise structured output that reconstructs the original figure.
41
+
42
+ The `answer` field links each sample to its corresponding ground-truth file used in evaluation.
43
+
44
+ ## Supported Code Types
45
+
46
+ ```text
47
+ python
48
+ html-css
49
+ latex-tikz
50
+ svg
51
+ smiles
52
+ ```
53
+
54
+ ### Sample Counts by Code Type
55
+
56
+ | code_type | Count | Extension |
57
+ | ------------ | ----: | --------- |
58
+ | `python` | 357 | `.py` |
59
+ | `latex-tikz` | 265 | `.tex` |
60
+ | `svg` | 192 | `.svg` |
61
+ | `html-css` | 166 | `.html` |
62
+ | `smiles` | 100 | `.smi` |
63
+
64
+ ## Subjects
65
+
66
+ ```text
67
+ Biology&Medicine
68
+ Chemistry
69
+ Computer Science
70
+ Economics
71
+ Geography
72
+ Math
73
+ Other
74
+ Physics
75
+ ```
76
+
77
+ ## Figure Types
78
+
79
+ This split includes 45 figure types, including but not limited to:
80
+
81
+ ```text
82
+ 3d-plot, Area, Contour, Density, Graph, Histogram, Phase-Diagram,
83
+ Quiver, Treemap, UML-class-diagram, Violin, analytical-geometry,
84
+ anatomy-diagram, atom-model, bar-chart, block-diagram, box-chart,
85
+ cell-structure, circuit, equations-texts, error-bar, error-point,
86
+ flow-chart, free-body-diagram, function-related, gauge-chart, graph,
87
+ heatmap, line-graph, magnetic-field-line, map, molecular-formula,
88
+ multi-graph, optics-ray-diagram, other-figures, physiological-process,
89
+ pie-chart, plane-geometry, radar-chart, relationship-diagram,
90
+ scatter-plot, schematic, solid-geometry, tables, venn-diagram
91
+ ```
92
+
93
+ ## Usage
94
+
95
+ Within the Omni-I2C project, this file is used as the inference input to the evaluation pipeline:
96
+
97
+ 1. `VLMEvalKit_infer` loads `Image2Code_Full.tsv`
98
+ 2. The model takes `image` and `question` as input
99
+ 3. Predictions are saved after inference
100
+ 4. `eval_pipeline` matches predictions with GT files for code-level and image-level evaluation
101
+
102
+ For implementation details, please refer to the project repository: [https://github.com/MiliLab/Omni-I2C](https://github.com/MiliLab/Omni-I2C)
103
+
104
+