Don't use sub-venv for ocrd_segment #154
Conversation
That processors don't use TensorFlow. Signed-off-by: Stefan Weil <sw@weilnetz.de>
Oh, but they do (or will in the near future): look at the |
That's bad news. Maybe we should split such projects in two, one with processors which don't need a sub-venv, one with processors which need one? Or will all processors depend on TensorFlow in the near future? Ideally we should not add new processors depending on old versions of TensorFlow ... |
If you look at the README.md (outlining the original plan/idea for this repo), the TF-based MaskRCNN segmentation was always at the core of what we wanted to do here. The other (non-TF) processors were just preliminaries and fall-off which we exposed/exported early on, because they had value in the OCR-D ecosphere independently. I am reluctant to change that, because of the interdependencies. @wrznr what do you think?
Agreed, but our MaskRCNN implementation has become unmaintained since we started using it, and it's not trivial to make the migration (there are already dozens of competing PRs targeting different TF2 versions in different ways). ocrd_anybaseocr is just one example of that effort (but they decided to just copy the source files into their own repo, so there's no point in follow them). Perhaps if I find some time to look at it, I'll merge and refine on of these PRs into my fork's master... |
|
BTW ocrd_segment's TF branch |
That processors don't use TensorFlow.
Signed-off-by: Stefan Weil sw@weilnetz.de