Yutong01 commited on
Commit
6e151a8
·
verified ·
1 Parent(s): 3959634

Update README.md

Browse files
Files changed (1) hide show
  1. README.md +5 -2
README.md CHANGED
@@ -53,6 +53,7 @@ Unlike standard text-to-text datasets, **PhysTool-Bench** relies on a decoupled
53
  * `images/`: Directory containing all high-resolution physical scenario images.
54
  * `generation_checkpoint.json`: The input file used for model inference. It contains the image paths and `task_instruct` prompts for Task II.
55
  * `corrected_tools.json`: The ground truth file used for evaluation. It contains the refined taxonomy, required tools (`target_tools`), `target_steps` for ordered tasks, and `negative_tools` (distractors).
 
56
 
57
  ### Example: Loading the Raw Data
58
  You can easily download and explore the raw dataset using the `huggingface_hub` or standard Python tools:
@@ -88,8 +89,10 @@ Due to the complex nature of physical tool planning, **standard HuggingFace pipe
88
  ### Why use the official codebase?
89
 
90
  - **Environment Isolation:** Different MLLMs require conflicting dependency versions (e.g., PyTorch, Transformers, Accelerate). Our repo provides standalone inference scripts for major models.
91
- - **LLM-as-a-Judge Evaluation:** We do not use simple string matching. Because models often output synonyms or functionally identical tools, our evaluation pipeline (`eval_gemini.py`) utilizes the Gemini API (`gemini-3.1-pro-preview`) to perform semantic one-to-one mapping against the ground truth before calculating metrics like SR@k and Pairwise Order Accuracy (POA).
92
-
 
 
93
  **Head over to [ModalityDance/PhysTool-Bench](https://github.com/ModalityDance/PhysTool-Bench) for the complete quickstart guide, environment setups, and automated evaluation scripts.**
94
 
95
 
 
53
  * `images/`: Directory containing all high-resolution physical scenario images.
54
  * `generation_checkpoint.json`: The input file used for model inference. It contains the image paths and `task_instruct` prompts for Task II.
55
  * `corrected_tools.json`: The ground truth file used for evaluation. It contains the refined taxonomy, required tools (`target_tools`), `target_steps` for ordered tasks, and `negative_tools` (distractors).
56
+ * `final_matching_info.json`: The alignment and mapping metadata file utilized by the offline evaluation pipeline to support tool taxonomy normalization and rule-based verification.
57
 
58
  ### Example: Loading the Raw Data
59
  You can easily download and explore the raw dataset using the `huggingface_hub` or standard Python tools:
 
89
  ### Why use the official codebase?
90
 
91
  - **Environment Isolation:** Different MLLMs require conflicting dependency versions (e.g., PyTorch, Transformers, Accelerate). Our repo provides standalone inference scripts for major models.
92
+ - **Dual Evaluation Pipelines:** Simple exact string matching fails on open-ended generation due to synonyms and morphological variations. We provide two robust alternatives:
93
+ * **Offline Evaluation (`eval_offline.py`):** Fast, local rule-based matching using `final_matching_info.json` for API-free evaluation.
94
+ * **LLM-as-a-Judge (`eval_gemini.py`):** Deep semantic one-to-one mapping via the Gemini API to resolve complex synonyms and functional equivalents.
95
+ *
96
  **Head over to [ModalityDance/PhysTool-Bench](https://github.com/ModalityDance/PhysTool-Bench) for the complete quickstart guide, environment setups, and automated evaluation scripts.**
97
 
98