FisFilter_DL_ReadCharacters

For input inImage only pixel formats are supported: 1⨯uint8, 3⨯uint8.

Read more about pixel formats in Image documentation.

This tool locates and recognizes characters. Without additional training, it is suitable for reading characters:

• horizontally oriented,
• of height between 60% and 140% of inCharHeight (in pixels) - for the FastWide, Balanced, Extended or OcrA models
• of height between 85% and 115% of inCharHeight (in pixels) - for the Fast model
• of height between 45% and 225% of inCharHeight (in pixels) - for the Scalable model
• being latin letters (upper- or lower-case), digits or one of: !#$%&()*+,-./:;<=>?@[]^_`{|}~"'\€£¥.

The pretrained models are described here.

This behavior can be configured with parameters described below.

The inRoi and inRoiAlignment inputs may be used to limit the analysed area, which, in most cases, leads to improved performance. Moreover, it may be used to adjust to text which is not horizontally oriented.

The inCharHeight should be set to the average height of characters (specifically, capital letters) in the analysed area. E.g. if image contains 2 kind of characters: one being 24 pixels high and the second being 40 pixels high, inCharHeight should be set to 32, irrespective of number of characters of each kind. Fast mode supports a more narrow range of character sizes, the character size should be between 30 and 40 pixels.

Here the top row characters are 56 pixels high, whereas the bottom row is 26 pixels. The inCharHeight parameter was set to the average value of 42:

In case of fonts with exceptionally thin or wide symbols, inWidthScale may be used to reshape them to a more "typical" aspect ratio. The analysed area will be scaled by inWidthScale in the horizontal axis. It may improve quality of results. Furthermore, it may also help in reading a text with tight spaces between subsequent characters.

In the image below illustrates how the inWidthScale parameter can be used to read an exceptionally wide font:

To limit the set of recognized characters, inCharRange may be used. This string has to be formatted according to the following rules:

• allowed characters have to be separated with commas,
• for ease of use, continuous range of letters or digits, may be written as starting_character-ending_character, e.g. A-Z or 1-6,
• comma and backslash have to be prepended with backslash.

For example, inCharRange equal to A-F,g-o,0-9,X,Y,Z,-,\\,\, will result in recognizing only ABCDEFXYZghijklmno0123456789-\, characters.

The inMinScore parameter may be used to change minimum score of a character. By default, this threshold is set to 0.5. Changing this parameter, however, may result in showing false characters. See the example image below:

The inContrastThreshold and inPolarization parameters sets a desired contrast interval of a character, which may be used to reduce amount of false positives:

• For inPolarization = Polarity::Bright, only characters with a contrast greater than inContrastThreshold will be returned.
• For inPolarization = Polarity::Dark, only characters with a contrast lower than -inContrastThreshold will be returned.
• For inPolarization = Polarity::Any, only characters with a contrast lower than -inContrastThreshold or greater than inContrastThreshold will be returned.

Example of results with different values of the inPolarization parameter:

Character which is darker than its background have a negative contrast. Opposite situation results in a positive contrast.

Using positive inCharSpacing can eliminate false detections of characters that are close to other characters. Conversely, using negative inCharSpacing can capture more characters that are located near each other. This value is set to 0 by default.

Illustration of outcomes with various values of the inCharSpacing parameter:

To filter out characters that are not fully contained within the Region of Interest (ROI), use parameter inRemoveBoundaryCharacters.

Demonstration of effects using different inRemoveBoundaryCharacters parameter values:

• It is recommended that the deep learning model is deployed with DL_ReadCharacters_Deploy first and connected through the inModelId input.
• If one decides not to use DL_ReadCharacters_Deploy, then the model will be loaded in the first iteration. It will take up to several seconds.
• In case of characters having too much differing height, it is advised to separate the analysed area (e.g. with inRoi input) to smaller parts containing symbols with a more consistent height.
• In case of poor quality results in Fast mode, check if inCharHeight is set correctly.
• False characters characters can also be removed using MergeCharactersIntoLines.
• To match the known inPattern, use grammar rules in MergeCharactersIntoLines.

This filter should not be executed along with running Deep Learning Service as it may result in degraded performance or even out-of-memory errors.

List of possible exceptions:

• DL_ReadCharacters_Deploy – Loads a deep learning model and prepares its execution on a specific target device.

• DL_LocateText – Performs text detection using a pre-trained deep learning model.

• MergeCharactersIntoLines – Converts a output of Deep Learning filter DL_ReadCharacters to lines of text.

• "Reading characters" section in Machine Vision Guide