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
First of all, thanks for the nice tool and its helpful tutorial.
However, I got stuck with the fact that I have an electricity meter with a double counter (normal and off peak). It is not a surprise that this won't work out of the box. I edited the config-file a bit to force the script to recognize digits from both counters (by increasing digitYAlignment), and during the 'adjust'-mode the digits are recognized. But during the OCR test-mode the digits are basically swapped from top to bottom from left to right (and of course a likely result of the config amendment).
I tried sorting the digits on its y-axis instead of the x-axis, but this did not work properly. Do you have any ideas or suggestions how to extract the digits from both counters? I must admit I am not very familiar with C++ at the moment, but I am willing to dive into it.
Kind regards.
The text was updated successfully, but these errors were encountered:
Good day,
First of all, thanks for the nice tool and its helpful tutorial.
However, I got stuck with the fact that I have an electricity meter with a double counter (normal and off peak). It is not a surprise that this won't work out of the box. I edited the config-file a bit to force the script to recognize digits from both counters (by increasing digitYAlignment), and during the 'adjust'-mode the digits are recognized. But during the OCR test-mode the digits are basically swapped from top to bottom from left to right (and of course a likely result of the config amendment).
I tried sorting the digits on its y-axis instead of the x-axis, but this did not work properly. Do you have any ideas or suggestions how to extract the digits from both counters? I must admit I am not very familiar with C++ at the moment, but I am willing to dive into it.
Kind regards.
The text was updated successfully, but these errors were encountered: