Skip to content

Fix last-screenshot selection: sort trajectory images by step index#2

Open
jianganghan wants to merge 1 commit into
Mininglamp-AI:mainfrom
jianganghan:fix/naveval-screenshot-order
Open

Fix last-screenshot selection: sort trajectory images by step index#2
jianganghan wants to merge 1 commit into
Mininglamp-AI:mainfrom
jianganghan:fix/naveval-screenshot-order

Conversation

@jianganghan

Copy link
Copy Markdown

os.listdir order is filesystem-dependent; taking [-1] as the last screenshot picks a wrong step on macOS/APFS (observed 0.png, the initial page), causing systematic false FAILs in NavEval ("final screenshot shows only the homepage"). Sort by numeric step index instead — plain lexicographic sorting would also break beyond step 9 ('9.png' > '15.png').

Verified on a 10-task Protocol-III run (judge: claude-sonnet-4-5): before the fix all 6 evaluable tasks were judged FAIL (0.15); after, 3 flipped to PASS (0.95), matching manual review of the trajectories.

Fixes #1.

🤖 Generated with Claude Code

os.listdir returns entries in arbitrary order, so taking [-1] as the
"last" screenshot silently picks a wrong step on some filesystems
(observed 0.png, the initial page, on macOS/APFS), causing the judge
to fail tasks for "no visual evidence in final screenshot". Even
lexicographic order breaks past step 9 ('9.png' > '15.png'). Sort by
numeric step index instead.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.

NavEval picks wrong "last screenshot" because os.listdir order is filesystem-dependent

1 participant