Replies: 8 comments
|
On this one, it's probably about building the endpoints
Then those endpoints can be reused on proof addition, or for retro-processing |
0 replies
|
On Slack you mentionned a tool/workflow you used to extract barcode info for instance. We could use this issue to list available tools ? I've been thinking of ways to accelerate data collection, taking pictures of shelves, and having an image recognition tool that would return a list of product codes+prices. Then would come a step to integrate the "chosen" tool in the backend ? |
0 replies
|
0 replies
0 replies
|
Or we could cloudvision our way out of it, it's not like we'll be out of credits this year. |
0 replies
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment




Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
There is lots of interesting info in the proof images :
What if the server was able to do some image recognition, and return to the frontend all of that info ? 🤩
How ?
Using GenAI
@TTalex has built a prototype, using Google's Gemini API.
Using an external library
Our own trained model
price_tagstable to store predictions #611@raphael0202 is working on building a long-term solution based on training data.
Challenges
Price tag
Receipt
Without the product EAN or barcode, how to link to the exact product in the OFF database ?
Related discussions
Related issues
proof_predictiontable to store predictions from ML models #511price_tagstable to store predictions #611All reactions