-
Notifications
You must be signed in to change notification settings - Fork 82
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Coordinates are all over the place for local testing, but works perfectly on your gradio webapp #10
Comments
Hi |
Same here. Is there any difference deploying locally? I did the same instructions as in the guide but it outputs different results every time. Thanks |
Hi, thanks, i checked out the notion file but unfortunately at least with the 2b and 7b model, i get very poor results locally I've tried running it locally with all different frameworks and the methods but the coordinates continue to have 0% accuracy while the gradio model is very accurate. Also, i tried out many different prompts, but it definitely isn't the issue It would be great if anyone has any success running this locally. |
Have you tried converting the output coordinates using the transformation described in Coordinate Mapping Section |
Are you using Ollama? Or vLLM? |
ollama as the doc suggested, as well as transformers |
It seems that the issue might be related to the precision of the model deployed with Ollama. We are currently working on optimizing it. In the meantime, you can prioritize testing with vLLM or the cloud deployment. |
thanks |
Hi, excited to see this performance.
The gradio space has very accurate performance
https://huggingface.co/spaces/Aheader/gui_test_app
So i tried running it locally but the coordinate boxes once i scale it by the image width and height is just all over the place. I get very poor results locally.
Could you share more details about the gradio implementation?
I tried using both the prompt examples in your docs but it is awful compared to the webapp - which gives perfect results everytime
Thanks!!
The text was updated successfully, but these errors were encountered: