Python-based tools for document analysis and OCR
Jupyter Notebook Python Other
Permalink
Failed to load latest commit information.
.github ISSUE_TEMPLATE: git log -n1 and python version Nov 6, 2016
OLD Added noisegen script (extracting functions from ocroline). Aug 11, 2017
doc Add line-normalization.ipynb for documentation Apr 26, 2017
models Add a README.md in models directory (#194) Mar 19, 2017
ocrolib Merge pull request #133 from tmbdev/dewarp-padding2 Apr 26, 2017
tests Unit tests: Add more tests and error code May 8, 2017
.gitignore Delete .hg from .gitignore May 8, 2017
.travis.yml Add tests/run-unit to .travis.yml May 8, 2017
LICENSE Added LICENSE and files I forgot to include with las tcommit. Dec 10, 2014
PACKAGES PACKAGES: Drop python-tables requirement Nov 10, 2016
README.md added note about upcoming PyTorch recognizers Jul 25, 2017
README_OSX.md Add solution for OS X (clang) Feb 21, 2015
circle.yml create 'run-test-ci', adapt travis/circle to use it May 7, 2017
ocropus-dewarp py3k: Use print function instead of statement. Nov 15, 2016
ocropus-econf Merge branch 'master' into pr Jan 23, 2017
ocropus-errs Fix ocropus-errs --erroronly May 13, 2017
ocropus-gpageseg Move comment, add line breaks in gpageseg May 7, 2017
ocropus-gtedit py3k: Use print function instead of statement. Nov 15, 2016
ocropus-hocr Made output more compatible to the hOCR spec. Dec 2, 2016
ocropus-linegen Delete unused function bounding_box in ocropus-linegen May 13, 2017
ocropus-lpred py3k: Use new-style exceptions. Jan 23, 2017
ocropus-ltrain py3k: Use new-style exceptions. Jan 23, 2017
ocropus-nlbin Delete unused function estimate_scale in o-nlbin May 14, 2017
ocropus-rpred Merge branch 'master' into cleanup-common Jan 23, 2017
ocropus-rtrain py3k: Use print function instead of statement. Nov 15, 2016
ocropus-visualize-results py3k: Use print function instead of statement. Nov 15, 2016
requirements.txt Merge branch 'master' into cleanup-requirements Nov 10, 2016
run-coverage [run-coverage]: switch to run-test-ci, test for module May 9, 2017
run-rtrain Allow test scripts to run in any directory. Nov 16, 2016
run-test Switch to run-test-ci for coverage May 9, 2017
run-test-ci Expand run-test-ci May 10, 2017
setup.py py3k: Use print function instead of statement. Nov 15, 2016

README.md

ocropy

Build Status CircleCI license Wiki Join the chat at https://gitter.im/tmbdev/ocropy

OCRopus is a collection of document analysis programs, not a turn-key OCR system. In order to apply it to your documents, you may need to do some image preprocessing, and possibly also train new models.

In addition to the recognition scripts themselves, there are a number of scripts for ground truth editing and correction, measuring error rates, determining confusion matrices, etc. OCRopus commands will generally print a stack trace along with an error message; this is not generally indicative of a problem (in a future release, we'll suppress the stack trace by default since it seems to confuse too many users).

Installing

To install OCRopus dependencies system-wide:

$ sudo apt-get install $(cat PACKAGES)
$ wget -nd http://www.tmbdev.net/en-default.pyrnn.gz
$ mv en-default.pyrnn.gz models/
$ sudo python setup.py install

Alternatively, dependencies can be installed into a Python Virtual Environment:

$ virtualenv ocropus_venv/
$ source ocropus_venv/bin/activate
$ pip install -r requirements.txt
$ wget -nd http://www.tmbdev.net/en-default.pyrnn.gz
$ mv en-default.pyrnn.gz models/
$ python setup.py install

An additional method using Conda is also possible:

$ conda create -n ocropus_env python=2.7
$ source activate ocropus_env
$ conda install --file requirements.txt
$ wget -nd http://www.tmbdev.net/en-default.pyrnn.gz
$ mv en-default.pyrnn.gz models/
$ python setup.py install

To test the recognizer, run:

$ ./run-test

Running

To recognize pages of text, you need to run separate commands: binarization, page layout analysis, and text line recognition. The default parameters and settings of OCRopus assume 300dpi binary black-on-white images. If your images are scanned at a different resolution, the simplest thing to do is to downscale/upscale them to 300dpi. The text line recognizer is fairly robust to different resolutions, but the layout analysis is quite resolution dependent.

Here is an example for a page of Fraktur text (German); you need to download the Fraktur model from tmbdev.net/ocropy/fraktur.pyrnn.gz to run this example:

# perform binarization
./ocropus-nlbin tests/ersch.png -o book

# perform page layout analysis
./ocropus-gpageseg 'book/????.bin.png'

# perform text line recognition (on four cores, with a fraktur model)
./ocropus-rpred -Q 4 -m models/fraktur.pyrnn.gz 'book/????/??????.bin.png'

# generate HTML output
./ocropus-hocr 'book/????.bin.png' -o ersch.html

# display the output
firefox ersch.html

There are some things the currently trained models for ocropus-rpred will not handle well, largely because they are nearly absent in the current training data. That includes all-caps text, some special symbols (including "?"), typewriter fonts, and subscripts/superscripts. This will be addressed in a future release, and, of course, you are welcome to contribute new, trained models.

You can also generate training data using ocropus-linegen:

ocropus-linegen -t tests/tomsawyer.txt -f tests/DejaVuSans.ttf

This will create a directory "linegen/..." containing training data suitable for training OCRopus with synthetic data.

Roadmap


Project Announcements
The text line recognizer has been ported to C++ and is now a separate project, the CLSTM project, available here: https://github.com/tmbdev/clstm
New GPU-capable text line recognizers and deep-learning based layout analysis methods are in the works and will be published as separate projects some time in 2017.
Please welcome @zuphilip and @kba as additional project maintainers. @tmb is busy developing new DNN models for document analysis (among other things). (10/15/2016)

A lot of excellent packages have become available for deep learning, vision, and GPU computing over the last few years. At the same time, it has become feasible now to address problems like layout analysis and text line following through attentional and reinforcement learning mechanisms. I (@tmb) am planning on developing new software using these new tools and techniques for the traditional document analysis tasks. These will become available as separate projects.

Note that for text line recognition and language modeling, you can also use the CLSTM command line tools. Except for taking different command line options, they are otherwise drop-in replacements for the Python-based text line recognizer.

Contributing

OCRopy and CLSTM are both command line driven programs. The best way to contribute is to create new command line programs using the same (simple) persistent representations as the rest of OCRopus.

The biggest needs are in the following areas:

  • text/image segmentation
  • text line detection and extraction
  • output generation (hOCR and hOCR-to-* transformations)

CLSTM vs OCRopy

The CLSTM project (https://github.com/tmbdev/clstm) is a replacement for ocropus-rtrain and ocropus-rpred in C++ (it used to be a subproject of ocropy but has been moved into a separate project now). It is significantly faster than the Python versions and has minimal library dependencies, so it is suitable for embedding into C++ programs.

Python and C++ models can not be interchanged, both because the save file formats are different and because the text line normalization is slightly different. Error rates are about the same.

In addition, the C++ command line tool (clstmctc) has different command line options and currently requires loading training data into HDF5 files, instead of being trained off a list of image files directly (image file-based training will be added to clstmctc soon).

The CLSTM project also provides LSTM-based language modeling that works very well with post-processing and correcting OCR output, as well as solving a number of other OCR-related tasks, such as dehyphenation or changes in orthography (see our publications). You can train language models using clstmtext.

Generally, your best bet for CLSTM and OCRopy is to rely only on the command line tools; that makes it easy to replace different components. In addition, you should keep your OCR training data in .png/.gt.txt files so that you can easily retrain models as better recognizers become available.

After making CLSTM a full replacement for ocropus-rtrain/ocropus-rpred, the next step will be to replace the binarization, text/image segmentation, and layout analysis in OCRopus with trainable 2D LSTM models.

Solution for clang

Read README_OSX.md