workflow-configuration not running
EEngl52 opened this issue · 9 comments
I adapted gt-binarize-page-olena-sauvola-clip-resegment-dewarp-ocr-ocropy-tesseract.mk by renaming the input file group and exchanging the first processor olena-binarize with cis-ocropy-binarize (see attachment).
When I try to run make -r test.mk /test/data/helmstedt or -f it would just tell me that there's nothing to do in this workspace. The same holds true when using a relative path to the workspace. -s doesn't return any message.
Looking into it now.
Just 2 things ahead:
-ris wrong here. (You use that option to tellmaketo exclude its database of suffix rules.) You always need-fto select the configuration makefile.-stellsmaketo run silent (i.e. without showing the commands executed). You probably intended the opposite,-d(debugging the traversal of rules that leads up to the commands).
Okay, at that point – without your input data – I need your help. Can you please show the result of running LC_MESSAGES=C make -d -f test.mk helmstedt?
BTW, this configuration is not going to work anyway:
$(BIN): TOOL = ocrd-cis-ocropy-binarize
$(BIN): PARAMS = "level-of-operation": "line"
CLIP = $(BIN)-CLIP
$(CLIP): $(BIN)
$(CLIP): TOOL = ocrd-cis-ocropy-clip...because you cannot clip segments that already have AlternativeImage on them – this makes them incomparable. (Derived images one level above the level-of-operation are fine of course.) So your binarization needs to use PARAMS = "level-of-operation": "page".
ah, ok, thanks for your explanations
there's the output from your command. I could also zip my workspace and upload it if that helps
output.txt
Are you sure you ran with helmstedt not with the absolute path?
Sorry, I know this should be irrelevant. Just trying to understand.
Also, yes, if it's possible, please upload your workspace (the mets.xml and empty directories will sufffice though).
sorry, used the absolute path. there's the output for helmstedt
and there's my workspace. I had to delete the original images in OCR-D-IMG as they were too big to upload
just changed level of operation to page and ran it on a new workspace with just OCR-D-IMG as input. This also produced the same error message
I think I know what the issue is. This happens when you don't install (as documented by the README). However, I am thinking of a solution without installation anyway...