microsoft / microsoft/winml-cli

[Task] image-to-text EP coverage investigation

Open
#299 2 comments 0 reactions 1 assignee View on GitHub

@ssss141414 is already working on this.

Since Apr 9, 2026.

model / task scale P2 triaged
Dominant language
Python
Stars
40
Forks
11
Avg merge
1d 8h
Merged PRs (30d)
50

Description

Overview

Image-to-text models generate textual descriptions or transcriptions from images — covering OCR (TrOCR, manga-ocr), document understanding (Donut, Nougat), and image captioning (BLIP, ViT-GPT2). 9 of 11 models pass on at least one EP.

This issue focuses on the 2 models with severe EP gaps — donut and nougat currently pass only on VitisAI and fail on both QNN and OV. These are encoder-decoder architectures with custom preprocessing, and the failure pattern is distinct from the rest of the task's models.

Agent Scenarios

  • Document parsing agent: convert scanned PDFs, receipts, or forms into structured JSON using Donut's end-to-end document understanding, without OCR preprocessing
  • Scientific paper extraction agent: use Nougat to convert academic PDFs (including LaTeX math) into structured markdown for downstream summarization or RAG ingestion
  • OCR pipeline agent: transcribe printed or handwritten text from images (TrOCR, manga-ocr) as a preprocessing step for document search and indexing

EP Coverage Status

Model QNN OV VitisAI
naver-clova-ix/donut-base FAIL FAIL PASS
facebook/nougat-base FAIL FAIL PASS

Reference: microsoft/trocr-large-printed, microsoft/trocr-base-printed, nlpconnect/vit-gpt2-image-captioning, microsoft/trocr-base-handwritten, kha-white/manga-ocr-base, microsoft/trocr-large-handwritten, Salesforce/blip-image-captioning-base already pass all 3 EPs.

Acceptance Criteria

  • naver-clova-ix/donut-base passes all 3 EPs (investigate QNN + OV failure)
  • facebook/nougat-base passes all 3 EPs (investigate QNN + OV failure)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.