Update dataset card with task category and paper/code links
#2
by nielsr HF Staff - opened
README.md
CHANGED
|
@@ -1,12 +1,23 @@
|
|
| 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
|
| 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 |
|
|
@@ -15,7 +26,7 @@ Each sample contains an image, an instruction, and metadata describing the targe
|
|
| 15 |
- **Number of figure types:** 45
|
| 16 |
- **Number of code types:** 5
|
| 17 |
|
| 18 |
-
|
| 19 |
|
| 20 |
## Data Fields
|
| 21 |
|
|
@@ -23,7 +34,7 @@ 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 |
| ------------- | ------------------------------------------------------------------------------- |
|
|
@@ -76,7 +87,7 @@ Physics
|
|
| 76 |
|
| 77 |
## Figure Types
|
| 78 |
|
| 79 |
-
This split includes 45 figure types, including
|
| 80 |
|
| 81 |
```text
|
| 82 |
3d-plot, Area, Contour, Density, Graph, Histogram, Phase-Diagram,
|
|
@@ -94,11 +105,20 @@ scatter-plot, schematic, solid-geometry, tables, venn-diagram
|
|
| 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 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
---
|
| 2 |
license: apache-2.0
|
| 3 |
+
task_categories:
|
| 4 |
+
- image-to-text
|
| 5 |
+
language:
|
| 6 |
+
- en
|
| 7 |
+
tags:
|
| 8 |
+
- image-to-code
|
| 9 |
+
- vision-language-models
|
| 10 |
+
- code-generation
|
| 11 |
+
- benchmark
|
| 12 |
---
|
| 13 |
|
| 14 |
# Omni-I2C: Image2Code_Full
|
| 15 |
|
| 16 |
+
[**Paper**](https://huggingface.co/papers/2603.17508) | [**GitHub**](https://github.com/MiliLab/Omni-I2C)
|
| 17 |
+
|
| 18 |
## Dataset Description
|
| 19 |
|
| 20 |
+
`Image2Code_Full.tsv` is the inference split of the **Omni-I2C** benchmark. It is designed to evaluate whether Large Multimodal Models (LMMs) can generate high-fidelity code or structured outputs from input images.
|
| 21 |
|
| 22 |
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.
|
| 23 |
|
|
|
|
| 26 |
- **Number of figure types:** 45
|
| 27 |
- **Number of code types:** 5
|
| 28 |
|
| 29 |
+
Omni-I2C requires a holistic understanding where any minor perceptual hallucination or coding error leads to a complete failure in visual reconstruction.
|
| 30 |
|
| 31 |
## Data Fields
|
| 32 |
|
|
|
|
| 34 |
|
| 35 |
```tsv
|
| 36 |
index image question answer subject figure_type code_type
|
| 37 |
+
```
|
| 38 |
|
| 39 |
| Field | Description |
|
| 40 |
| ------------- | ------------------------------------------------------------------------------- |
|
|
|
|
| 87 |
|
| 88 |
## Figure Types
|
| 89 |
|
| 90 |
+
This split includes 45 figure types, including:
|
| 91 |
|
| 92 |
```text
|
| 93 |
3d-plot, Area, Contour, Density, Graph, Histogram, Phase-Diagram,
|
|
|
|
| 105 |
|
| 106 |
Within the Omni-I2C project, this file is used as the inference input to the evaluation pipeline:
|
| 107 |
|
| 108 |
+
1. `VLMEvalKit_infer` loads `Image2Code_Full.tsv`.
|
| 109 |
+
2. The model takes `image` and `question` as input.
|
| 110 |
+
3. Predictions are saved after inference.
|
| 111 |
+
4. `eval_pipeline` matches predictions with GT files for code-level and image-level evaluation.
|
| 112 |
|
| 113 |
For implementation details, please refer to the project repository: [https://github.com/MiliLab/Omni-I2C](https://github.com/MiliLab/Omni-I2C)
|
| 114 |
|
| 115 |
+
## Citation
|
| 116 |
|
| 117 |
+
```bibtex
|
| 118 |
+
@article{zhou2025omni,
|
| 119 |
+
title={Omni-I2C: A Holistic Benchmark for High-Fidelity Image-to-Code Generation},
|
| 120 |
+
author={Zhou, Jiawei and Zhang, Chi and Feng, Xiang and Zhang, Qiming and Qiu, Haibo and He, Lihuo and Ye, Dengpan and Gao, Xinbo and Zhang, Jing},
|
| 121 |
+
journal={arXiv preprint arXiv:2603.17508},
|
| 122 |
+
year={2025}
|
| 123 |
+
}
|
| 124 |
+
```
|