core
core copied to clipboard
OCR-D
Collection of OCR-related python tools and wrappers from @OCR-D
From https://github.com/bertsky/core/pull/13 > Did you also try to remove the hard-coded defaults for `resource_locations` and `resource.type` and `resource.parameter_usage` and `resource.path_in_archive` and `resource.version_range` to see if everything still works?
see https://github.com/OCR-D/core/blob/81c0b4c01eb1db54999c5db8feae120df2cc1a7b/src/ocrd_network/cli/client.py#L91 for ideas, see [here](https://github.com/OCR-D/core/issues/1032#issuecomment-1511482113), so in this case `ocrd network client workflow list|download|upload|run` where the latter should look like `ocrd process` (i.e. block) As an extra, we could...
@kba I saw you struggle with my #1239 changes in https://github.com/OCR-D/core/actions/workflows/docker-image.yml afterwards. I did not test the last changes locally (and Github itself could not be used). Sorry about that!...
``` docker buildx build --progress=plain --platform linux/amd64,linux/arm64/v8 --push -f Dockerfile.cuda -t ghcr.io/ocr-d/core-cuda -t docker.io/ocrd/core-cuda --target ocrd_core_base --build-arg BASE_IMAGE=ghcr.io/ocr-d docker.io/ocrd/core . ERROR: "docker buildx build" requires exactly 1 argument. See 'docker...
So the last commit ensured that Github will show our pytest and flake8 results directly. However, IMO we should modify our Makefile to make sure that `PYTEST_ARGS` is used in...
on the way to our refactoring: I think this must happen now. We had decentralised resources for a while now. No-one is using the central ones (they are either out-of-date...
This branch should be back in a state it can be worked on. I did: - base it on #1309 - merged #1315 into it (which I haven't yet pushed...
https://github.com/OCR-D/core/blob/62cf25c3406144c9eb628605431e5aa3e27e8332/src/ocrd/processor/helpers.py#L160 Now that we have the METS Server option, we should reconsider this behaviour. It gets used in both the standard processor CLI (via `ocrd_cli_wrap_processor`) and in ocrd_network (via `invoke_processor`)....