ZTWHHH commited on
Commit
ecebb73
·
verified ·
1 Parent(s): e0abdd1

metadata: add score_type/score_params/score_protocol (official grading protocol taxonomy); task_type is now format-only (judge_scored migrated to vqa + llm_judge). See dataset-upload skill references/metadata-json.md.

Browse files
Files changed (1) hide show
  1. metadata.json +5 -0
metadata.json CHANGED
@@ -10,6 +10,11 @@
10
  "single_image_start"
11
  ],
12
  "task_type": "vqa",
 
 
 
 
 
13
  "prompt_template": "<image>{{ question }}{% if options %}\nOptions:\n{% for k, v in options.items() %}{{ k }}. {{ v }}{% if not loop.last %}\n{% endif %}{% endfor %}{% endif %}\n",
14
  "mapping_from_source": {
15
  "media": {
 
10
  "single_image_start"
11
  ],
12
  "task_type": "vqa",
13
+ "score_type": "llm_extract",
14
+ "score_protocol": {
15
+ "reference": "VLMEvalKit@vlmeval/dataset/dynamath.py:58-109 — rule parse of the answer first (JSON 'short answer' / direct parse_answer), auxiliary LLM extraction only on parse failure, then rule compare: float abs(diff)<=0.001, MC letter equality, text containment. Official DynaMath@evaluation/gpt4o/gpt_4o_json_eval.py:98-123 uses the same JSON 'short answer' parse + abs(diff)<=0.001 rule compare.",
16
+ "note": "Official grading is rule-based over a JSON-formatted answer forced by their inference prompt; the mm-eval prompt (lmms-eval style question+Options trailer) does not force JSON, so LLM extraction fallback (VLMEvalKit protocol) is required. Official float tolerance is ABSOLUTE 0.001, not relative. Official headline metrics are average-case AND worst-case accuracy over 10 generated variants per seed question; the mm-eval copy ships 501 rows (seed variant only), so worst-case accuracy is not reproducible."
17
+ },
18
  "prompt_template": "<image>{{ question }}{% if options %}\nOptions:\n{% for k, v in options.items() %}{{ k }}. {{ v }}{% if not loop.last %}\n{% endif %}{% endfor %}{% endif %}\n",
19
  "mapping_from_source": {
20
  "media": {