Concerns with Dataset construction
Comparing to common tasks like sentiment analysis, 400 may sound like a small number but we would like to emphasize the challenges of creating and evaluating scientific tasks, which reflect the value of our work, and that the data set that we evaluated is actually much larger:
1) creating and evaluating a scientific text-to-image dataset requires expertise: We tax the value of our evaluation at roughly 3,000 USD, with up to 11 annotators (STEM PhD or faculty in our case) involved for up to 7 hours each, all working for a conservative estimate of 40 USD per hour (including taxes), on average. We added these numbers to the revised version. Note that scientific tasks require expert annotators as shown in Belouadi et al. (2024a,b) as otherwise the agreements are too low.
2) reasonable numbers compared to similar scientific domain tasks: while we have only 404 prompts, we provide human ground truth of evaluation for ~3k generated images in three dimensions in our dataset (as there are several models that generate for each prompt), all evaluated by up to 11 expert annotators. This size makes it comparable to similar datasets in the community, e.g. MMVP (Tong et al., 2024) with 300 image+question pairs, CONTEXTUAL (Wadhawan et al., 2024) with 506 samples, SciBench (Wang et al, 2024) with 869 cases. So, these numbers are actually smaller than ours (others may contain reference images - but so do we for a subset of highly scored images).
3) regarding “evaluating a subset of the dataset with domain experts”: we fully agree and want to point out that our prompt dataset has been fully checked (and even constructed) by computer science PhD and faculty. Diversity and representativeness is ensured by the data construction: e.g., we focus on the three dimensions of numeric, spatial and attribute understanding and their combinations and these dimensions are adequately represented (in roughly equal proportion), by construction. Of course, one might argue to include further dimensions - and we are open to this - which could yield additional insights into other model failures, but we think that the **current dimensions already make a strong point regarding limitations of text-to-image generation models in the scientific domain**. We also want to highlight that we provide statistics over different quantities of scientific graphs in the tables (e.g., sample sizes of different prompts relating to numeric understanding, etc.).
4) lacking ground truth: we admit that we lack ground truth for some of the images (but we have them indirectly for a large subset of images which are highly scored by at least one of the models). As a benchmark, what we contribute primarily is to provide Ground Truth Evaluation Scores from Experts for ~3k generated images which will facilitate the improvement of automated evaluation metrics. In addition to this, we will release highly scored reference images for a subset of the data.
> Can you provide a detailed explanation of the rationale behind constructing the dataset solely from generated prompts based on templates? What considerations were made regarding the lack of ground truth in this dataset? Additionally, have you considered using real-world scientific data to construct the prompts, which would provide a more robust basis for evaluation?
In dataset construction, our motivation was to provide clearly specified targeted dimensions of scientific image generation where we exactly know the attributes queried. This makes the evaluation specific & targeted. This contrasts with a “real-world” evaluation where potentially long query prompts are leveraged which may contain various dimensions at the same time and, thus, model failure may be a result of multiple aspects which cannot be clearly disentangled. For example, Datikz (Belouadi et al. 2024) provides a real-world dataset - while it inspired us in selecting scientific objects, it is unspecific and mixes different understanding properties in each prompt. Our evaluation framework is inspired by the famous CheckList methodology of Ribeiro (https://aclanthology.org/2020.acl-main.442/).