add ketos_ocr suite (the model training part of kraken-ocr) - #1927
Open
IvoLeist wants to merge 3 commits into
Open
add ketos_ocr suite (the model training part of kraken-ocr)#1927IvoLeist wants to merge 3 commits into
IvoLeist wants to merge 3 commits into
Conversation
- Increment kraken-ocr version to 7.0.3 - Add --linetype option - Add script which replaces the filename inside the xml (ALTO/PAGE) with input.png
…me replacement python script by yq "magic"
This file contains hidden or 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.
This PR starts the addition of the ketos_ocr suite.
Ketos is the model training part of kraken, a turn-key OCR system optimized for historical and non-Latin script material.
Here the
ketos compilecommand is wrapped. Future PRs (WIP) will add other ketos functionalities such astrain.The idea of wrapping ketos' commands individually is to allow the use of each ketos command within a galaxy workflow.
FOR CONTRIBUTOR:
There are two labels that allow to ignore specific (false positive) tool linter errors:
skip-version-check: Use it if only a subset of the tools has been updated in a suite.skip-url-check: Use it if github CI sees 403 errors, but the URLs work.Notes for reviewers:
page.xmlandarrow"since I assume that the GitHub CI is still at Galaxy 26.0.1. These errors should disappear once version 26.1 is in use.