fix: improve action parser compatibility - #252
Open
Rohithmatham12 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
click>point>point>x yby normalizing it into the existing structured action flow<|box_start|>...<|box_end|>coordinate strings and comma/space separated point tagsevalusage with safe coordinate parsingscroll(start_box=..., end_box=...), which is the common mobile/emulator scroll form/v1suffixIssues
Addresses #229.
Addresses #231.
Helps clarify #122.
Helps the deployment confusion discussed in #127.
Testing
Note:
make testcould not run in my local environment becauseuvis not installed. Running the same parser unittest target directly passed; full unittest discovery additionally requires Pillow fortests/inference_test.py.