Case insensitive #675
Merged
Case insensitive #675
Conversation
This file contains 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.
Sorry, I have to fix my branch and it delete my older pull request.
Summary: I propose adding an optional feature to calculate a case-insensitive Character Error Rate (CER) for the Kraken OCR test function. This metric would ignore errors caused by uppercase and lowercase differences in the predictions.
Use Case: This feature could be useful for:
OCR projects involving historical texts, where capitalization is often inconsistent.
Scenarios where case differences are less important than the overall recognition accuracy.
How to use:
ketos test (parameters)
The report will show the CER case-insensitive