True_inference_with_LayoutLMv2ForTokenClassification, add support for custom OCR #128
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
|
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
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.
Hi @NielsRogge,
Thanks for these great tutorials.
This PR to add support for custom OCR alternatives to the built-in one used in LayoutLMv2Processor.
In real world use-cases, Image quality is not good and Tesseract is not the best tool to use, using other alternatives that have better text detectors can improve inference performance (and can be used for fine-tuning). I added modularity to be able to use Tesseract for the recognition part if needed.
Popular OCR tools alternatives added in this Notebook under Inference Chapter:
Let me know if there are some changes to make
Thanks