Skip to content

fix(screenspot): specify normalized click coordinate units - #1761

Open
rudycelekli wants to merge 1 commit into
open-compass:mainfrom
rudycelekli:codex/vlmeval-screenspot-coordinate-instructions
Open

rudycelekli wants to merge 1 commit into
open-compass:mainfrom
rudycelekli:codex/vlmeval-screenspot-coordinate-instructions

Conversation

@rudycelekli

Copy link
Copy Markdown
Contributor

ScreenSpot default prompts ask for x/y without stating the coordinate units, while the evaluator uses fractions of image dimensions. State that x is a fraction of image width and y of image height, both between 0 and 1, in the functional and composite user templates. This addresses the explicit prompt remedy proposed in #1706.

Scoring, pixel fallback, custom-model prompts and stored predictions are unchanged. No rescoring of saved 1000-grid results or measured model-accuracy gain is claimed. Related open #1719/#1722 change weighting and parsing, not these instructions.

Frozen baseline: four prompt regressions fail and one normalized-point control passes. Candidate and independent review: seven tests pass, including two image-helper controls. Fixtures execute actual builder/conversion/parser methods with real pandas rows and a local image, while isolating the heavy dataset import. New-test lint and whitespace pass; source diagnostics decrease from six to four with none introduced. ADR included in this reviewed revision. No full-package or model execution. AI-assisted contribution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant