You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 8, 2022. It is now read-only.
The scanner currently can take anywhere between 10 ~ 15 minutes to complete one side of a sign in sheet.
The biggest issue that can be currently be recognized is the speed of tesseract. Over a dozen takes are done per cell, which is necessary in order to get an accurate description given.
One suggestion given was to use threading or multiprocessing to split up the tasks, increasing speed. However, tesseract has issues with the use of threading and multiprocessing as when implemented, it got results faster, but it returned significantly inaccurate results.
The choices so far look like either finding a way to make tesseract friendly to threading, or revamp the code to be more efficient in general, or find shortcuts that can be taken.
As it currently stands, no option seems feasible to where its tolerable yet.
The text was updated successfully, but these errors were encountered:
As of commit 6f2cee6c4dcb3625a5957fefc1148f220c2a3977, the program can be timed with the majority of the waiting lasting ~11 minutes. Further improvisations are on the way, so it may go faster, or I'll have to start back at the drawing board.
The scanner currently can take anywhere between 10 ~ 15 minutes to complete one side of a sign in sheet.
The biggest issue that can be currently be recognized is the speed of tesseract. Over a dozen takes are done per cell, which is necessary in order to get an accurate description given.
One suggestion given was to use threading or multiprocessing to split up the tasks, increasing speed. However, tesseract has issues with the use of threading and multiprocessing as when implemented, it got results faster, but it returned significantly inaccurate results.
The choices so far look like either finding a way to make tesseract friendly to threading, or revamp the code to be more efficient in general, or find shortcuts that can be taken.
As it currently stands, no option seems feasible to where its tolerable yet.
The text was updated successfully, but these errors were encountered: