-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add image preprocessing steps #159
Comments
should now read:
Instead of introducing the term raw denoising, we could also differentiate despeckling (after binarization) and denoising (before binarization)... |
👍
IMHO "raw denoising" is clearer than distinguishing despeckling/denoising. Then again, our glossary currently defines despeckling as
And "denoise" is not introduced at all. So, we're free to define it as you proposed. @EEngl52 any objection? |
Oh, but these physical artifacts cannot be reliably removed after binarization IMHO. You need special detectors on raw colors. So if that's the term OCR-D (or the OCR community in general) has agreed upon, let's stick to that, and not project any other interpretation. In that sense I think we still have no despeckling processors yet.
Then let's define it! Let's also differentiate between raw and bilevel denoising. |
IMO we could differentiate denoising/despeckling. But then the processors should be named accordingly. I would find it quite confusing to use a processor called |
Absolutely. Since
We should open respective issues in those repos, and in the workflow guide of course.
So how about:
|
IMO there is a large, still unmet demand in OCR-D for image preprocessing tools to
Most binarization algorithms depend on this. For example, Sauvola (unless it exposes the R parameter and one can estimate a good fit from the image dynamics) assumes full dynamic range.
So how about adding the following:
fileGrp/@USE
name recommendationsOCR-D-IMG-NORM
andOCR-D-IMG-RAWDEN
AlternativeImage/@comments
classesnormalized
andraw-denoised
tool/steps
enum typespreprocessing/optimization/normalization
(which is different fromgrayscale_normalization
) andpreprocessing/optimization/raw-denoising
(which is different from binarydespeckling
)The text was updated successfully, but these errors were encountered: