Difference between revisions of "Evaltex"
From LRDE
Line 102: | Line 102: | ||
The evaluation results are given in two forms: |
The evaluation results are given in two forms: |
||
* local evaluation ''.txt'' file for each image |
* local evaluation ''.txt'' file for each image |
||
+ | |||
+ | {| class="wikitable" |
||
+ | |- |
||
+ | |<small> |
||
+ | EvaLTex statistics - image img_1<br/> |
||
+ | General <br/> |
||
+ | Number of GTs =43<br/> |
||
+ | Number of detections = 19<br/> |
||
+ | Number of false positives =1<br/> |
||
+ | Number of true positives =18<br/> |
||
+ | |||
+ | Global results<br/> |
||
+ | Recall=0.414803<br/> |
||
+ | Recall_noSplit=0.414803<br/> |
||
+ | Precision=0.921798<br/> |
||
+ | Split=0.428571<br/> |
||
+ | FScore=0.572144<br/> |
||
+ | |||
+ | FScore_noSplit=0.572144<br/> |
||
+ | |||
+ | Quantity results<br/> |
||
+ | Recall=0.967873<br/> |
||
+ | Precision=0.947368<br/> |
||
+ | |||
+ | Quality results<br/> |
||
+ | Recall=0.428571<br/> |
||
+ | Recall_noSplit=0.967873<br/> |
||
+ | Precision=0.973009<br/> |
||
+ | Coverage histogram = {0.571429, 0, 0, 0, 0, 0, 0.0238095, 0, 0.0238095, 0.380952}<br/> |
||
+ | Accuracy histogram = {0.288977, 0.00137028, 0.00091352, 0.0022838, 0.00365408, 0.00471985, 0.00517661, 0.0103532, 0.0235993, 0.658952}<br/> |
||
+ | |||
+ | EMD results<br/> |
||
+ | Recall=0.420952<br/> |
||
+ | Recall_noSplit=0.420952<br/> |
||
+ | Precision=0.926316<br/> |
||
+ | FScore=0.578853<br/> |
||
+ | |||
+ | FScore_noSplit=0.578853<br/> |
||
+ | |||
+ | Local evaluation<br/> |
||
+ | GT object 1<br/> |
||
+ | Coverage = 1 Accuracy = 0.991792 Split = 1<br/> |
||
+ | GT object 2<br/> |
||
+ | Coverage = 0.809862 Accuracy = 0.994543 Split = 1<br/> |
||
+ | GT object 3<br/> |
||
+ | Coverage = 1 Accuracy = 0.954386 Split = 1<br/> |
||
+ | GT object 4<br/> |
||
+ | Coverage = 0.998092 Accuracy = 0.967474 Split = 1<br/> |
||
+ | GT object 5<br/> |
||
+ | Coverage = 1 Accuracy = 0.993222 Split = 1<br/> |
||
+ | GT object 6<br/> |
||
+ | Coverage = 1 Accuracy = 0.960362 Split = 1<br/> |
||
+ | GT object 7<br/> |
||
+ | Coverage = 1 Accuracy = 0.987906 Split = 1<br/> |
||
+ | GT object 8<br/> |
||
+ | Coverage = 1 Accuracy = 0.977346 Split = 1<br/> |
||
+ | GT object 9<br/> |
||
+ | Coverage = 0.99977 Accuracy = 0.999885 Split = 1<br/> |
||
+ | GT object 10<br/> |
||
+ | Coverage = 1 Accuracy = 0.986737 Split = 1<br/> |
||
+ | GT object 11<br/> |
||
+ | Coverage = 1 Accuracy = 0.977986 Split = 1<br/> |
||
+ | GT object 12<br/> |
||
+ | Coverage = 1 Accuracy = 0.944269 Split = 1<br/> |
||
+ | GT object 13<br/> |
||
+ | Coverage = 1 Accuracy = 0.991489 Split = 1<br/> |
||
+ | GT object 14<br/> |
||
+ | Coverage = 1 Accuracy = 1 Split = 1<br/> |
||
+ | GT object 15<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 16<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 17<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 18<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 19<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 20<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 21<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 22<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 23<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 24<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 25<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 26<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 27<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 28<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 29<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 30<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 31<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 32<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 33<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 34<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 35<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 36<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 37<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 38<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 39<br/> |
||
+ | Coverage = 0.977941 Accuracy = 0.998527 Split = 1<br/> |
||
+ | GT object 40<br/> |
||
+ | Coverage = 0.99478 Accuracy = 0.965439 Split = 1<br/> |
||
+ | GT object 41<br/> |
||
+ | Coverage = 0 Accuracy = 0 Split = 0<br/> |
||
+ | GT object 42<br/><br/> |
||
+ | Coverage = 0.661783 Accuracy = 1 Split = 1<br/> |
||
+ | GT object 43<br/> |
||
+ | Coverage = 0.979484 Accuracy = 0.822794 Split = 1<br/> |
||
+ | </small> |
||
+ | |} |
||
Revision as of 15:32, 7 July 2016
EvaLTex (Evaluating Text Localization) is a unified evaluation framework used to measure the performance of text detection and text segmentation algorithms. It takes as input text objects represented either by rectangle coordinates or by irregular masks. The output consists of a complex set of scores, at local and global levels, and a visual representation of the behavior of the analysed algorithm through quality histograms.
For more details on the evaluation protocol, read the scientific paper published in the Image and Vision Computing Journal. Details on the visual representation of the evaluation can be found in the article published in the Proc. of International Conference in Document Analysis and Recognition.
Please cite the IVC paper in all publications that use the EvaLTex tool and the ICDAR paper in all publications that use the histogram representation. |
Performance measurements
Local evaluation
For each matched GT object we assign two quality measures: Coverage (Cov) and Accuracy (Acc);
- Cov computes the rate of the matched area with respect to the GT object area
- Acc computes the rate of the matched area with respect to the detection area
Global evaluation
The Recall () computes the amount of detected text. We compute 3 measures: a global , a quantitative that measures the amount detected objects (regardless of the matched area) and a qualitative that corresponds to the rate of the detected text area with respect to the number of true positives ().
The Precision () computes the rate of detections that have a match in the GT. Similarly to , we compute 3 measures: a quantitative that measures the amount of valid detections (regardless of the matched area) and a qualitative that corresponds to the rate of the detected text area with respect to the number of total detections, computed as the sum of and
Input format
The framework takes as input .txt files containing the coordinates of the bounding boxes surrounding the text objects and binary images corresponding to the text object masks.
Ground truth (GT)
The GT files contains the reference to which the detection and segmentation results will be compared to. For text detection tasks using bounding boxes, a .txt file is enough. If the text objects are represented by irregular masks, then an additional labeled image will be needed.
Text detection
The GT format contains the following attributes:
- img name
- image height, image width
- text object
- ID: unique text object ID
- region ID: region ID to which the object belongs to
- "transcription": can be empty
- text reject: option that decides if a text object should be counted or not; can be set to f (default) or t (not take into account)
- x: x coordinate of the bounding box
- y: y coordinate of the bounding box
- width: width of the bounding box
- height:x height of the bounding box
e.g.
img_1 960,1280 |
Text segmentation
To evaluate text segmentation we use, in addition to the .txt file a labeled image (each character is labeled differently). Each GT object is represented by a character. Character-level GT objects cannot be grouped into regions and consequently each text object has a different region tag. The x, y, width and height will define the coordinates of the bounding box of each character.
e.g.
img_1 960,1280 |
Detection/Segmentation
The detection .txt file formats differ slightly from the GT one:
- no image size
- no region tag
- no reject option
e.g.
img_1 1,"",272,264,392,186 |
Output
The evaluation results are given in two forms:
- local evaluation .txt file for each image
EvaLTex statistics - image img_1 Global results FScore_noSplit=0.572144 Quantity results Quality results EMD results FScore_noSplit=0.578853 Local evaluation |
- global evaluation for an entire dataset
Run the evaluation
Parameters to run the tool
Datasets
ICDAR 2013
Born-digital
- ground truth .txt
- labeled images
Natural scene
- ground truth .txt
- labeled images
Downloads
Credits
EvaLTex was written by Ana Stefania CALARASANU. Please send any suggestions, comments or bug reports to calarasanu@lrde.epita.fr
Please cite the ICV paper in all publications that use the EvaLTex tool and the ICDAR paper in all publications that use the histogram representation. |