Tightness-aware Evaluation Protocol for Scene Text Detection
Yuliang Liu Lianwen Jin Zecheng Xie Canjie Luo Shuaitao Zhang Lele Xie







Tightness-aware Evaluation Protocol for Scene Text Detection
    Yuliang Liu, Lianwen Jin^*, Zecheng Xie, Canjie Luo, Shuaitao Zhang, Lele Xie

College of Electronic Information Engineering, South China University of Technology 

liu.yuliang@mail.scut.edu.cn; lianwen.jin@gmail.com











    December 30, 2023
=======================================================================================================================================================================================================================================





   Evaluation protocols play key role in the developmental progress of text detection methods.
   There are strict requirements to ensure that the evaluation methods are fair, objective and reasonable. 
   However, existing metrics exhibit some obvious drawbacks: 
   1) They are not goal-oriented;
   2) they cannot recognize the tightness of detection methods;
   3) existing one-to-many and many-to-one solutions involve inherent loopholes and deficiencies. 
   Therefore, this paper proposes a novel evaluation protocol called  Tightness-aware Intersect-over-Union (TIoU) metric that could quantify completeness of ground truth, compactness of detection, and tightness of matching degree. 
   Specifically, instead of merely using the IoU value, two common detection behaviors are properly considered; meanwhile, directly using the score of TIoU to recognize the tightness. In addition, we further propose a straightforward method to address the annotation granularity issue, which can fairly evaluate word and text-line detections simultaneously.
   By adopting the detection results from published methods and general object detection frameworks, comprehensive experiments on ICDAR 2013 and ICDAR 2015 datasets are conducted to compare recent metrics and the proposed TIoU metric. The comparison demonstrated some promising new prospects, e.g., determining the methods and frameworks for which the detection is tighter and more beneficial to recognize. Our method is extremely simple; however, the novelty is none other than the proposed metric can utilize simplest but reasonable improvements to lead to many interesting and insightful prospects and solving most the issues of the previous metrics.
   
   The code is publicly available at <https://github.com/Yuliang-Liu/TIoU-metric>.





§ INTRODUCTION



Recent metrics for evaluating text detection have been adopted from the object detection Pascal VOC metric <cit.>.

 However, unlike object detection, text detection tasks require the bounding box to be tighter because the primary goal of detection is to recognize the text. Simply adopting the same IoU metric for text detection leads to the following issues:

  
  * As shown in Fig. <ref> (a), detection over a fixed IoU threshold with the ground truth (GT) may not completely recall the text (some characters are missed); however, previous metrics consider that the GT has been entirely recalled.
  
  * As shown in Figs. <ref> (b), (c), and (d), detection over a fixed IoU threshold with the GT may still contain background noise; however, previous metrics consider such detection to have 100% precision.
  
  * As shown in Fig. <ref>, previous metrics consider detections (a), (b), (c), and (d) to be equivalent perfect detections because they all have the same IoU value that is higher than a threshold. However, considering that the primary goal of detection is to recognize the text, these detections are not equivalent: 1) In (a), there is no way to recognize the characters outside the detection bounding box; 2) in (c), it is very difficult for a recognizer to distinguish which is the target GT; 3) the issues pertaining to both (a) and (c) can simultaneously occur for (d);
  4) as for (b), it is easy for a normal text recognizer to recognize the content correctly. 
  
  * Previous metrics severely rely on an IoU threshold. However, if a relatively high IoU threshold is set, some satisfactory bounding boxes may be discarded (e.g., if 0.7 is set as the threshold, the detection in Fig. <ref> (b) will be misjudged); if a low IoU threshold is set, several inexact bounding boxes would be included.


The essential reasons that cause such inequalities are: 1) The detections in Figs. <ref> (a) and (d) cut the GT region; 2) the detections in Figs. <ref> (c) and (d) both contain outlier-GT; and 3) recent metrics use binary results (0 or 100%) to represent the final recall or precision score.

To solve these issues, an intuitive solution is to penalize the exceptional detections. 
In the proposed Tightness-aware Intersection-over-Union (TIoU) metric, we use the occupation ratio of detection to GT and occupation ratio of outlier-GT to detection as penalty factors, respectively. 
In addition, we directly use the score of the TIoU as the value of recall and precision, and thus, the compact degree among different methods can be distinguished. The TIoU metric targets the following three characteristics, which are also the main contributions of this work:

  
  * Completeness. Using the TIoU metric would force methods to pay more attention to recalling every part of the GT, i.e., ensuring the completeness of GT.
  
  * Compactness. Because the detections of outlier-GT will be punished by TIoU, the compactness of the detection would receive more attention.
  
  
  * Tightness-aware. TIoU can distinguish the tightness among different detection methods, i.e., a 0.9 IoU detection would be much better than a 0.5 IoU detection in our metric.




§ RELATED WORK

Evaluation methods <cit.> have been an important research topic for several decades. For scene text detection, there are four  mainstream evaluation methods that are largely identical but have minor differences: ICDAR 2003 (IC03) <cit.>, ICDAR 2013 (IC13) <cit.>, ICDAR 2015 (IC15) <cit.>, and AP-based methods <cit.>. 



 §.§ ICDAR 2003 Evaluating Method

The early IC03 metric <cit.> is based on the notions used by the information retrieval community to calculate precision and recall, which are as follows:

    Recall(G,D) = ∑_i=1^|G|BestMatch_G(G_i)/|G|,


    Precision(G,D) = ∑_j=1^|D|BestMatch_D(D_j)/|D|,

where, BestMatch_G and BestMatch_D indicate the result of the closest match between detection and ground truth rectangles, as defined below <cit.>:

    BestMatch_G(G_i) = max_j = 1...|D|2· Area(G_i∩ D_j)/Area(G_i)+Area(D_j),


    BestMatch_D(D_j) = max_i = 1...|G|2· Area(D_j∩ G_i)/Area(D_j)+Area(G_i).

The matching mechanism involves finding the perfect-matching pairs to detect the matching value, i.e., if a rectangle is perfectly matched, the match value is unity, else the value is less than 1. The disadvantages of the IC03 metric are as follows: 1) Multiple detections can be repeatedly matched to the same GT;
2) as the authors reported in <cit.> themselves, this evaluation scheme only considers one-to-one (OO) matches, and thus one-to-many (OM) and many-to-one (MO) matches <cit.> are considered to have zero recall and precision. However, practically, word-level and text-line detections can both be conducive to recognition.



 §.§ ICDAR2013 Evaluation Method

IC13 <cit.> has three evaluation metrics: IC13, DetEval, and IoU.  The IoU metric is subsequently adopted following the IC15 <cit.> metric, which is discussed in the next subsection.



  §.§.§ ICDAR2013, DetEval

Unlike Eqs. <ref> and <ref>, the criteria of these two evaluations are based on mutual overlap rates between detection ({D_j}_j) and ground truth ({G_i}_i): 

    A(G_i∩ D_j)/A(D_j) > tp,


    A(G_i∩ D_j)/A(G_i) > tr,

where, tp and tr are the thresholds of precision and recall, respectively. The metrics evaluate the methods using three steps including OO, OM, and MO. Unlike the IC03 metric, OO guarantees that each GT can be at most matched once, and multiple matching detections are considered false positives. 

OM indicates that a GT is matched by a set of detection results, and it should satisfy two requirements: a) Sufficient detections covering the GT; b) each contributing detection is covered enough by the GT. If these conditions are satisfied, the precision value of each detection box and recall value of the GT are both set to 0.8 <cit.>. 

MO indicates that a detection is matched by a set of GT. The following two requirements must be satisfied: a) The detection must contain sufficiently overlapping GT; b) each GT must be recalled with sufficient area. If these conditions are satisfied, the recall value of each GT and the precision value of this detection are both set to 1.

Although these two matching methods can overcome the problem of inconsistency of the annotation granularity to some extent, such metrics still involve some unsatisfactory circumstances (examples are shown in Fig.  <ref>):

   
  * For MO matching, a rough detection can recall all GTs, as shown in the left image of the first row of Fig. <ref>. Such rough detection may not be proper recognized, which is relatively unfair for those methods that can granularly detect the text. 
   
  * For OM matching, many segmented detections are considered as correct results, which is unfair for singularly perfect detection. Some examples are shown in the right image of the first row of Fig. <ref>. It is worth mentioning that although 0.8 is set to penalize over-segmentation, loophole still exists. For example, if the overall precision is less than 0.8, a method that separates a perfect detection into numerous small over-segmented OM detections (e.g., 20) can make the precision close to 0.8. An example is given below:

    origin_precision = 0+1+0+0/4 = 0.25


    fake_precision = 0+0.8+...+0.8^20+0+0/23 = 0.7


   
  * For the IC13 metric, the matching order is OO, OM and MO. Because each GT and detection can only be matched once, the OO matching pairs would not be calculated during OM or MO matching, which would affect the detection results. As shown in the bottom image of Fig. <ref>, the long detections do not satisfy MO matching because the bluish detections have already OO matched with some GT in advance. Thus, the long detections are regarded as false positives and the rest of the GTs are considered to be not recalled.

   
  * For DetEval evaluation, OM and MO are evaluated in advance before OO, which may lead to unsatisfactory results. As shown in the middle image of Fig. <ref>, because OM is validated in advance, the two detection bounding boxes have already been used. Thus, the two jacinth GTs are considered not to be recalled. 






























 §.§ ICDAR 2015 IoU Metric

The IC15 metric <cit.> follows the same metric as Pascal VOC <cit.>. Under this metric, detections are assigned to ground truth objects and judged to be true or false positives by measuring the bounding box overlap. To be considered a correct detection, the value of Intersection-over-Union (IoU, defined in Eq. <ref>) must exceed 0.5.

    A(G_j∩ D_i)/A(G_j∪ D_i) > 0.5.


Detections are assigned to true positives only when they satisfy the overlap criterion and they have the top ranking confidence to the target GT. Ground truth objects with no matching detections are false negatives. Although this metric has received the most attention, it still has many drawbacks, which have been pointed out in the introduction section.



 §.§ AP-based evaluation method

To avoid finetuning the output detection confidence, dataset such as RCTW-17 <cit.> has adopted interpolated average precision as the main detection evaluation metric: For a given task and class, the precision-recall curve is computed based on the method's ranked output. Basically, this metric relies on the IoU metric to calculate the precision and recall in advance.




§ METHODOLOGY






 §.§ Tightness-aware Intersection-over-Union (TIoU) Metric

The primary goal of text detection evaluation metrics is to quantify the performance of different methods. Because the major function of detecting text regions is to recognize text, it is a strong requirement for detecting bounding boxes to preserve the completeness of text information and avoid interference with other text instances. However, previous evaluation metrics mentioned in Section 2 do not consider the impact of cutting GT regions and outlier-GT. Meanwhile, it is not easy to distinguish the tightness of detections. Hence, the merits of the detecting methods cannot be thoroughly embodied. To address these problems, our solution is derived from three basic annotating concepts: (a) Annotation does not cut the text instance; (b) annotation contains less background noise, especially outlier text instances; (c) annotations may not be perfect matching the text instance, they should be as much perfect as possible.



  §.§.§ TIoU-Recall

Intuitively, one GT rectangle G_i cut by a detection bounding box D_j may result in incorrect recognition. Although traditional IoU metrics can measure the tightness between G_i and D_j, it can not goal-oriented evaluate the cases shown in Fig. <ref> (a) and (b) (Detections in (a) and (b) have the same value of IoU (0.66) against the ground truth, while the former one do not recall a few characters of the GT). To solve this issue, the cutting behavior can be penalized by the proportion of intersection in GT.

Firstly, we define the not-recalled area of G_i as C_t:

    C_t = A(G_i)-A(D_j∩ G_i), C_t∈ [0,A(G_i)],

where A(*) means the area of the region. Then, the proportion of intersection in G_i is given by:

    f(C_t) = 1-x, x = C_t/A(G_i).

Therefore, the final TIoU-Recall is defined as follows:

    TIoU_Recall = A(G_i∩ D_j)*f(C_t)/A(G_i∪ D_j).

Equation <ref> is a simple but effective solution for managing the cutting behavior, e.g., the TIoU-Recall in Fig. <ref> (a) and (b) are 0.424 and 0.66, respectively, which implies that missing characters account for a 35.8% decline in recall.



  §.§.§ TIoU-Precision

On the other hand, one detection covers several GTs may also affect the recognition results because it is intricate for recognition methods to distinguish which text is target GT, as shown in Fig. <ref> (c). The proposed solution is to penalize such type of detections to make detection compact for avoiding outlier-GTs. Nevertheless, if the outlier-GTs are inside the target GT region, even the perfect detection bounding box cannot avoid containing these outliers. Therefore, only the outlier-GT region that is inside the detection bounding box but outside the target GT region would be penalized. The area (O_t) of the union of all eligible outlier-GTs is calculated using equation <ref>:

    O_t_ij =    A((G_1∩ D_j - G_1∩ D_j∩ G_i)∪
       ... ∪ (G_i-1∩ D_j - G_i-1∩ D_j∩ G_i)∪
        (G_i+1∩ D_j - G_i+1∩ D_j∩ G_i)∪
      ... ∪
        (G_n∩ D_j - G_n∩ D_j∩ G_i)), 
        O_t_ij∈ [0,A(D_j-D_j∩ G_i)].

Note that for each G_n (n≠ i) that does not intersect with D_j, it can be simply ignored, which can improve computing efficiency. Then, the proportion of intersection in D_j is given by:

    f(O_t) = 1-x, x = O_t/A(D_j).

Using equation <ref>, we can define the TIoU-Precision in the same way as TIoU-Recall, as shown in equation <ref>:

    TIoU_Precision = A(D_j∩ G_i)*f(O_t)/A(D_j∪ G_i).


For intuitively understanding the performance of TIoU metrics, we show many examples in Fig. <ref>, which will be further discussed in Section 4.2. 




 §.§ Tightness-aware Metric

To calculate the final score, the harmonic mean of recall and precision is usually adopted as the primary metric:

    Hmean = 2Recall· Precision/Recall+Precision,

where recall and precision are calculated by

    Recall_ori = ∑ Match_gt_i/Num_gt,


    Precision_ori = ∑ Match_dt_j/Num_dt.

IC13 and IC15 both use a binary [0, 100%] results to determine Match_gt_i and Match_dt_j.

Binary results can not quantify the tightness of the methods, e.g., two detections D_1 and D_2 would be regarded the same event if the IoU of D_1 is 51% and that of D_2 is 100%. This is unreasonable because a good evaluation protocol should be able to reflect the discrepancy of detecting tightness.

To this end, we follow and improve IC03 method that directly uses the matching value to represent the score of each item, i.e., binary [0, 100%] results are replaced by a continuous [0-100%] index.
However, unlike IC03, TIoU guarantees that all GT can be matched only once. In addition, we use a more reasonable TIoU value as the score, instead of using Eq. <ref> and <ref>. Meanwhile, if the highest IoU is less than 0.5, the score is set to 0. Therefore, equations <ref> and <ref> become

    Recall_SIoU = ∑ IoU_i/Num_gt,


    Precision_SIoU = ∑ IoU_j/Num_dt.

Equations <ref> and <ref> are referred to as the Score Intersection-over-Union (SIoU) metric, which is now tightness-aware for evaluating detection methods. To further consider cutting and outlier intervention, we can use the score of TIoU-Recall and TIoU-Precision to calculate the results, as shown in equations <ref> and <ref>:

    Recall_TIoU = ∑ TIoU_recall/Num_gt


    Precision_TIoU = ∑ TIoU_precision/Num_dt




 §.§ The Solution of One-to-many and Many-to-one Metrics.

Based on our observation, the annotation inconsistency exists on nearly all benchmark datasets. Currently, there is no strict objective annotation protocol, and thus, such ambiguous inconsistency is hard to avoid. Detection methods cannot be fairly evaluated if the GT annotation is inconsistent. Taking the dataset of ICDAR 2015 challenge 4 as an example: This dataset adopts word-level annotation, but sometimes different words are stacked together even without obvious interval. Some examples are shown in Fig. <ref>. Mandatory labeling the text by words is practically demanding for detection methods. 



The motivation of the OM and MO metrics is to solve the inconsistency of annotation granularity because both word-level and text-line detections may appear simultaneously, and it is hard to judge which one is better for recognition.

Section 2 has already pointed out the weaknesses of the existing OM and MO methods. This section presents a very straightforward solution, i.e., the metric should be used with both word-level and text-line annotations being provided. 
However, to avoid redundant calculation of the same GT, the evaluation requires thorough consideration. Taking the IC15 dataset as an example, the evaluating steps can be outlined as follows (algorithm procedures can be found on appendix):

   
  * Creating text-line annotations based on word-level annotations. Each text-line annotation contains at least two word annotations. All the “don't cared” regions are ignored in the former. Because IC15 test set contains only 2077 GT boxes, the entire creation procedure is very fast.
   
  * The auxiliary text-line annotations are evaluated in advance with the same metric as that used for evaluating word-level annotation. If a detection is matched to a text-line GT, we can calculate the TIoU-precision according to Eq. <ref>. In the subsequent word-level evaluation stage, the matched detection is ignored. Then, we use word-level annotation and Eq. <ref> to decide whether the word-level GTs inside this text-line GT are sufficiently recalled. If a word-level GT is recalled, the text-line TIoU-Recall is given by:
   
    TIoU^*_Recall = A(G_j∩ D_i)*f(C_t)/A(G_j).

   In the next word-level evaluating stage, this GT would be considered as “don't cared”. If the GT is not sufficiently recalled, the TIoU-Recall of this GT will be calculated in word-level stage.   















§ EXPERIMENTS

This section quantitatively and qualitatively tested the proposed TIoU metric on two most popular scene text detection datasets - IC13 <cit.> and IC15 <cit.>.



 §.§ Quantitative evaluation






Quantitative experiments have been conducted to evaluate the differences between the previous metrics and the proposed TIoU metric. To evaluate the results, several state-of-the-art methods were adopted. All the methods were selected based on three criteria: 1) The methods have been frequently referred to in the literature; 2) the authors are willing to provide their detection results for our evaluation; 3) the authors or other researchers have published the source code or test model, thus making the result easy to reproduce, such as PixelLink <cit.>. Some results of IC13 directly used the model of IC15 provided by the authors (because they did not provide IC13 model).  

In addition, we further compared the metrics by several popular general object detection frameworks on the IC13 dataset. All the training data for these general detection frameworks are strictly the same, including 1715 samples from FORU <cit.> and 229 samples from the official IC13 training set. 


To further demonstrate the effectiveness of the TIoU metric, we adopted two recognition methods (CRNN <cit.> and RARE <cit.>) to evaluate end-to-end results. The end-to-end metric assesses the localization in the same way as detection task, and then evaluate the recall, precision, and Hmean based on transcription perfect match <cit.>.

The results are shown in Table <ref> and Table <ref>, respectively.
From Table <ref>, several new prospects can be observed: 

  
  * The values of TIoU show a similar tendency as end-to-end evaluation results. For example, Faster R-CNN outperforms SSD by 5% in the original IoU metric (0.676 vs. 0.626); however, in TIoU metric, the latter surpasses the former by almost 5%, which is corresponding to End-to-end results: For F_e1 and F_e2, the latter exceeds the former by 7.8% and 6%, respectively.
  To make it clearer, we further draw a line chart which can be more intuitive to visualize the correlations, as shown in Figure <ref>. From the figure, we can find the results of the F_e1, F_e2, and F_TIoU are extremely similar whereas the results of the F_IoU are clearly different from the other three results. On the other hand, the correlation coefficients r(F_TIoU ; F_e1) and r(F_TIoU ; F_e2) are higher than r(F_IoU ; F_e1) and r(F_IoU ; F_e2), with 0.5% and 2.6%, respectively.
  
  
  
  * TIoU is tightness-aware. FEN, R2CNN, and MaskTextSpotter (MTS) are comparable under previous metrics; however, in TIoU metrics, the results are much different, with 0.751, 0.704, and 0.769, respectively for these three methods. This is mainly because the TIoU is tightness-aware: Examples are shown in Fig. <ref>, MTS is the tightest method, and next is FEN and R2CNN, which are corresponding to the TIoU ranks.

  
  * Text detection is still a challenging task. Comparing the TIoU metric and previous metrics among all detection methods, most of the results consistently decrease by more than 10%, which indicates there are still insufficiencies of text detection methods. In addition, even the best performance of TIoU Hmean is under 0.8, which further shows that designing a robust text detection method is not an easy task.


Experiments on the IC15 dataset also demonstrate the effectiveness of the proposed metrics, as shown in Table <ref>:

  
  * TIoU is also tightness-aware on multi-oriented dataset. For example, PixelLink and RRD outperform East in previous IoU metric F_i; however, the gap reduces using SIoU F_s, which indicates that the detections of East are tighter; in TIoU metric F_t, East can further surpass RRD. This is because TIoU metric can reflect the tightness of different detection methods. As some detection results shown in Fig. <ref>, although the rotated detecting rectangles of RRD satisfy the requirement of previous IoU metric, they may cut the GT regions to some extent, which is the main reason that cause the decrease of TIoU. This example also implies that tighter quadrilateral detection methods may reasonably be more benefit from TIoU metric than rectangle-based methods.
  
  * Objectively evaluated Text-line detections. Because there are many ambiguous annotation granularities on the IC15 dataset (shown in Fig. <ref>), we have added the text-line level annotations of this dataset, and using our new solution (details in Section 3.3) for OM and MO matching. The results show that the results of all methods can be increased by different degrees in both the IoU and the TIoU metrics. This is mainly because some fine text line detections are fairly evaluated instead of treating them as false positives. For example, before using our new Joint-word&text-line evaluation metric, TextBox++ outperformed PixelLink for a large margin (2.4%). However, the former is worse than the latter by 0.2% with joint text-line annotations. The variation can be explained by visualization results shown in Fig. <ref>. The quantitative and qualitative results both demonstrate that our solution can reveal the potential novelty of segmentation-based methods. 








 §.§ Qualitative evaluation

Fig. <ref> shows some examples of the qualitatively evaluated results. If previous IoU metrics are used, all detections and target GTs of Fig. <ref> are considered to have 100% precision and recall because the their IoUs are all higher than 0.5. Clearly, this is unreasonable because some detections significantly reduce the recognition performance, such as Detection #1 in Fig. <ref> (a) and Detection #3 in Fig. <ref> (b).


Using the TIoU metric can assist in avoid these phenomenons. As shown in Fig. <ref>, the TIoU recall and precision are associated to recognition to some extent. For example, NED of detection #1 in (a) is 0.625, which means only 37.5% of the text can be correctly recognized because of the cutting effect. In this case, the TIoU-recall is also equal to 37.5%. This coincidence doesn't imply there is a specific relationship between the TIoU and recognition performance because NED can vary depending on the recognition methods. However, in Fig. <ref>, it is intuitive that high NED cases usually have a relative strong penalizes of TIoU value. Note that, for some high IoU (but not perfect detections) such as Detection #2 in Fig. <ref> (a), the recall only decreases slightly (from 0.891 to 0.866), which still meets our subjective judgment.

 



§ CONCLUSION

In this paper, we presented a goal-oriented TIoU metric to address many drawbacks of previous metrics. The TIoU metric is simple but intuitive, which moderately consider two common detection behaviors that may significantly influence the recognition. It uses the TIoU score as a measure of recall and precision to perceive the tightness of detection methods. Quantitative experiments on ICDAR 2013 and ICDAR 2015 datasets showed that the proposed metric has a similar tendency of the end-to-end detection and recognition results among general object detection frameworks and previous state-of-the-art text detection methods. Qualitative experiments further demonstrated the reduction from previous IoU to TIoU is mainly because TIoU can perceive and quantify the tightness of detections.

In addition, because the previous one-to-many and many-to-one metrics have many drawbacks, we proposed a straightforward solution to solve these issues. The results on the ICDAR 2015 dataset show that all methods can be improved with different degrees using our new solution. This is mainly because the proposed method can reasonably evaluate the text-line detections instead of roughly regarding them as false positives.


In future, we will try to use TIoU metric to guide training because its characteristics may be benefited to provide a strong supervision. In addition, it can also be used to help incremental or semi-supervised learning because TIoU can judge whether a detection is suitable to serve as a new GT annotation.



§ ACKNOWLEDGEMENTS

This research is supported in part by GD-NSF (no. 2017A030312006), the National Key Research and Development Program of China (No. 2016YFB1001405), NSFC (Grant No.: 61673182, 61771199), and GDSTP (Grant No.:2017A010101027), GZSTP(no. 201704020134).

ieee





§ APPENDIX




Pseudo code of OM & MO solution. Algorithm <ref> summarizes the joint Word&Text-Line annotation evaluating procedure. Note that not all details are covered by <ref>, which can be found on the source code.  




Experiments on Non-Latin text. The experiments on the main paper only conducted on the word-level Latin datasets. Actually, it may be more effective for detecting long text lines. Thus we further supplemented an experiment on well-known MSRA-TD500 <cit.>. Because we cannot retrieve the others' previous detection results of this dataset, we train East <cit.> and an improved version of Mask R-CNN with additional data selected from RCTW-17 <cit.> to test the TIoU metric. The results are shown in Table <ref>, and some of the qualitative results are shown in Figure <ref>. Note that, during the evaluation, we calculate the exact value of the area of the polygon instead of using approximate area calculation in <cit.>. It can be seen from Table <ref> that the recall, precision, and Hmean all drop significantly, which are mainly because there exists many defective detections shown in Figure <ref>. TIoU metric also highlights the difference between object detection and text detection task, showing there still exists a large room for detection methods to improve.





