slideagent-eval
SlideAgent: Hierarchical Agentic Framework for Multi-Page Visual Document Understanding — Jin et al. (2025) (arXiv:2510.26615, 2025)
What this evaluates
Evaluates multi-page visual document understanding and question answering. It probes a model's ability to retrieve relevant slides, perform spatial and layout reasoning, and accurately extract numeric values or generate lexical matches for open-ended answers.
Datasets
- SlideVQA — total ?; splits: test (-1)
- TechSlides — total ?; splits: test (-1)
- FinSlides — total ?; splits: test (-1)
Metrics
Num (primary) — range: percent
- Extracts numeric values from predictions and ground truth, normalizes formats (e.g., '17k' to '17000', '97%' to '0.97'), and checks for exact match.
F1 — range: [0, 1]
- Computes token-level F1 score between predicted and ground-truth answers after normalization, tokenization, and removal of stopwords and punctuation.
Overall (primary) — range: percent
- Composite headline metric aggregating performance across numeric and lexical tasks, reported as a percentage score.
Input / output format
Input: Multi-page slide images (or concatenated top-3 retrieved images for single-image models) and a natural language query. Optionally, ground-truth page indices are provided in the oracle setting.
Output: A natural language text answer.
Scoring recipe
def score(pred, gold):
if is_numeric_query(gold):
pred_norm = normalize_number(pred)
gold_norm = normalize_number(gold)
return 1.0 if pred_norm == gold_norm else 0.0
else:
pred_tokens = preprocess(pred) # remove stopwords/punct, tokenize
gold_tokens = preprocess(gold)
return f1_score(pred_tokens, gold_tokens)
Common pitfalls
- Number normalization must handle diverse formats (percentages, decimals, word-based like 'thousand') consistently before comparison.
- The 'Overall' metric is a composite score; readers should not assume it equals simple arithmetic mean of Num and F1 without checking the paper's exact weighting.
- Retrieval noise significantly impacts end-to-end scores; oracle settings (ground-truth pages provided) isolate reasoning capability and yield higher scores.
Evidence (verbatim from paper)
For questions asking about numeric values, we extract, standardize, and compare the prediction and the ground-truth in various formats, including percentages, decimals, integers, and word-based representations (e.g., “three”, “thousand”, “million”). Numbers are normalized to a unified format (e.g., ‘17k’ $
ightarrow$ ‘17000’, ‘2.5 million’ $
ightarrow$ ‘2500000’, ‘97%’ $
ightarrow$ ‘0.97). Otherwise, we use F1-score to evaluate the lexical overlap between predicted and ground-truth answers. Both answers are normalized, tokenized, and preprocessed by removing stopwords and punctuation before metric calculation.
Citation
@misc{jin2025slideagent,
title={SlideAgent: Hierarchical Agentic Framework for Multi-Page Visual Document Understanding},
author={Jin et al. (2025)},
year={2025},
note={arXiv:2510.26615}
}
1---2name: slideagent-eval3description: Evaluates multi-page visual document understanding and question answering. It probes a model's ability to retrieve relevant slides, perform spatial and layout reasoning, and accurately extract numeric values or generate lexical matches for open-ended answers. Use when the user wants to benchmark on SlideVQA, TechSlides, FinSlides, or asks about evaluating this task. Reports Num, Overall.4---56# slideagent-eval78> SlideAgent: Hierarchical Agentic Framework for Multi-Page Visual Document Understanding — Jin et al. (2025) (arXiv:2510.26615, 2025)910## What this evaluates1112Evaluates multi-page visual document understanding and question answering. It probes a model's ability to retrieve relevant slides, perform spatial and layout reasoning, and accurately extract numeric values or generate lexical matches for open-ended answers.1314## Datasets1516- **SlideVQA** — total ?; splits: test (-1)17- **TechSlides** — total ?; splits: test (-1)18- **FinSlides** — total ?; splits: test (-1)1920## Metrics2122- `Num` **(primary)** — range: percent23 - Extracts numeric values from predictions and ground truth, normalizes formats (e.g., '17k' to '17000', '97%' to '0.97'), and checks for exact match.24- `F1` — range: [0, 1]25 - Computes token-level F1 score between predicted and ground-truth answers after normalization, tokenization, and removal of stopwords and punctuation.26- `Overall` **(primary)** — range: percent27 - Composite headline metric aggregating performance across numeric and lexical tasks, reported as a percentage score.2829## Input / output format3031**Input**: Multi-page slide images (or concatenated top-3 retrieved images for single-image models) and a natural language query. Optionally, ground-truth page indices are provided in the oracle setting.3233**Output**: A natural language text answer.3435## Scoring recipe3637```python38def score(pred, gold):39 if is_numeric_query(gold):40 pred_norm = normalize_number(pred)41 gold_norm = normalize_number(gold)42 return 1.0 if pred_norm == gold_norm else 0.043 else:44 pred_tokens = preprocess(pred) # remove stopwords/punct, tokenize45 gold_tokens = preprocess(gold)46 return f1_score(pred_tokens, gold_tokens)47```4849## Common pitfalls5051- Number normalization must handle diverse formats (percentages, decimals, word-based like 'thousand') consistently before comparison.52- The 'Overall' metric is a composite score; readers should not assume it equals simple arithmetic mean of Num and F1 without checking the paper's exact weighting.53- Retrieval noise significantly impacts end-to-end scores; oracle settings (ground-truth pages provided) isolate reasoning capability and yield higher scores.5455## Evidence (verbatim from paper)5657> For questions asking about numeric values, we extract, standardize, and compare the prediction and the ground-truth in various formats, including percentages, decimals, integers, and word-based representations (e.g., “three”, “thousand”, “million”). Numbers are normalized to a unified format (e.g., ‘17k’ $
ightarrow$ ‘17000’, ‘2.5 million’ $
ightarrow$ ‘2500000’, ‘97%’ $
ightarrow$ ‘0.97). Otherwise, we use F1-score to evaluate the lexical overlap between predicted and ground-truth answers. Both answers are normalized, tokenized, and preprocessed by removing stopwords and punctuation before metric calculation.5859## Citation6061```bibtex62@misc{jin2025slideagent,63 title={SlideAgent: Hierarchical Agentic Framework for Multi-Page Visual Document Understanding},64 author={Jin et al. (2025)},65 year={2025},66 note={arXiv:2510.26615}67}68```6970- arXiv: 2510.26615