-
Notifications
You must be signed in to change notification settings - Fork 15
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
plausibilize and sanitize are too broad terms #18
Comments
I agree, these are not expressive enough, or even memorable (which is what...)
...or just
ATM all it does is remove regions fully contained by others or nearly equal to them (and fix the It's intended to become much more though, like merging or shrinking overlapping neighbouring regions, or fixing reading order via basic heuristics (e.g. no arbitrary jumps back and forth). Since this processor started out under the name Maybe |
Right, they have very common names since they are intended to do various things. Right now, they do not do very much and are not ready for productive use or even testing. I would rather keep the current names and see what the processors will become. Let us discuss about a proper name when implementation and documentation are finished. ( |
Documentation from https://ocr-d.de/en/workflows:
|
This is actually from the ocrd-tool json description of these parameters, see |
ocrd-segment-repair has the optional operations "plausibilize" and "sanitize" – I have no idea what this exactly does :) I would prefer something like this:
There seems to also be another thing ocrd-segment-repair does.
In other words: Make operations explicit.
The text was updated successfully, but these errors were encountered: