verslag.tex 12 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290
  1. \documentclass[a4paper]{article}
  2. \usepackage{hyperref}
  3. \title{Using local binary patterns to read license plates in photographs}
  4. % Paragraph indentation
  5. \setlength{\parindent}{0pt}
  6. \setlength{\parskip}{1ex plus 0.5ex minus 0.2ex}
  7. \begin{document}
  8. \maketitle
  9. \section*{Project members}
  10. Gijs van der Voort\\
  11. Richard Torenvliet\\
  12. Jayke Meijer\\
  13. Tadde\"us Kroes\\
  14. Fabi\'en Tesselaar
  15. \tableofcontents
  16. \setcounter{secnumdepth}{1}
  17. \section{Problem description}
  18. License plates are used for uniquely identifying motorized vehicles and are
  19. made to be read by humans from great distances and in all kinds of weather
  20. conditions.
  21. Reading license plates with a computer is much more difficult. Our dataset
  22. contains photographs of license plates from various angles and distances. This
  23. means that not only do we have to implement a method to read the actual
  24. characters, but also have to determine the location of the license plate and
  25. its transformation due to different angles.
  26. We will focus our research on reading the transformed characters on the
  27. license plate, of which we know where the letters are located. This is because
  28. Microsoft recently published a new and effective method to find the location of
  29. text in an image.
  30. Determining what character we are looking at will be done by using Local Binary
  31. Patterns. The main goal of our research is finding out how effective LBP's are
  32. in classifying characters on a license plate.
  33. In short our program must be able to do the following:
  34. \begin{enumerate}
  35. \item Use perspective transformation to obtain an upfront view of license
  36. plate.
  37. \item Reduce noise where possible.
  38. \item Extract each character using the location points in the info file.
  39. \item Transform character to a normal form.
  40. \item Create a local binary pattern histogram vector.
  41. \item Match the found vector with a learning set.
  42. \end{enumerate}
  43. \section{Solutions}
  44. Now that the problem is defined, the next step is stating our basic solutions.
  45. This will come in a few steps as well.
  46. \subsection{Transformation}
  47. A simple perspective transformation will be sufficient to transform and resize
  48. the plate to a normalized format. The corner positions of license plates in the
  49. dataset are supplied together with the dataset.
  50. \subsection{Reducing noise}
  51. Small amounts of noise will probably be suppressed by usage of a Gaussian
  52. filter. A real problem occurs in very dirty license plates, where branches and
  53. dirt over a letter could radically change the local binary pattern. A question
  54. we can ask ourselves here, is whether we want to concentrate ourselves on these
  55. exceptional cases. By law, license plates have to be readable. Therefore, we
  56. will first direct our attention at getting a higher score in the 'regular' test
  57. set before addressing these cases. Considered the fact that the LBP algorithm
  58. divides a letter into a lot of cells, there is a good change that a great
  59. number of cells will still match the learning set, and thus still return the
  60. correct character as a best match. Therefore, we expect the algorithm to be
  61. very robust when dealing with noisy images.
  62. \subsection{Extracting a letter}
  63. Because we are already given the locations of the characters, we only need to
  64. transform those locations using the same perspective transformation used to
  65. create a front facing license plate. The next step is to transform the
  66. characters to a normalized manner. The size of the letter W is used as a
  67. standard to normalize the width of all the characters, because W is the widest
  68. character of the alphabet. We plan to also normalize the height of characters,
  69. the best manner for this is still to be determined.
  70. \begin{enumerate}
  71. \item Crop the image in such a way that the character precisely fits the
  72. image.
  73. \item Scale the image to a standard height.
  74. \item Extend the image on either the left or right side to a certain width.
  75. \end{enumerate}
  76. The resulting image will always have the same size, the character contained
  77. will always be of the same height, and the character will alway be positioned
  78. at either the left of right side of the image.
  79. \subsection{Local binary patterns}
  80. Once we have separate digits and characters, we intent to use Local Binary
  81. Patterns to determine what character or digit we are dealing with. Local Binary
  82. Patters are a way to classify a texture based on the distribution of edge
  83. directions in the image. Since letters on a license plate consist mainly of
  84. straight lines and simple curves, LBP should be suited to identify these.
  85. To our knowledge, LBP has yet not been used in this manner before. Therefore,
  86. it will be the first thing to implement, to see if it lives up to the
  87. expectations. When the proof of concept is there, it can be used in the final
  88. program.
  89. Important to note is that due to the normalization of characters before
  90. applying LBP. Therefore, no further normalization is needed on the histograms.
  91. Given the LBP of a character, a Support Vector Machine can be used to classify
  92. the character to a character in a learning set. The SVM uses
  93. \subsection{Matching the database}
  94. Given the LBP of a character, a Support Vector Machine can be used to classify
  95. the character to a character in a learning set. The SVM uses the collection of
  96. histograms of an image as a feature vector. The SVM can be trained with a
  97. subsection of the given dataset called the ''Learning set''. Once trained, the
  98. entire classifier can be saved as a Pickle object\footnote{See
  99. \url{http://docs.python.org/library/pickle.html}} for later usage.
  100. \section{Implementation}
  101. In this section we will describe our implementations in more detail, explaining
  102. choices we made.
  103. \subsection{Licenseplate retrieval}
  104. In order to retrieve the license plate from the entire image, we need to
  105. perform a perspective transformation. However, to do this, we need to know the
  106. coordinates of the four corners of the licenseplate. For our dataset, this is
  107. stored in XML files. So, the first step is to read these XML files.\\
  108. \\
  109. \paragraph*{XML reader}
  110. \paragraph*{Perspective transformation}
  111. Once we retrieved the cornerpoints of the license plate, we feed those to a
  112. module that extracts the (warped) license plate from the original image, and
  113. creates a new image where the license plate is cut out, and is transformed to a
  114. rectangle.
  115. \subsection{Noise reduction}
  116. The image contains a lot of noise, both from camera errors due to dark noise
  117. etc., as from dirt on the license plate. In this case, noise therefore means
  118. any unwanted difference in color from the surrounding pixels.
  119. \paragraph*{Camera noise and small amounts of dirt}
  120. The dirt on the license plate can be of different sizes. We can reduce the
  121. smaller amounts of dirt in the same way as we reduce normal noise, by applying
  122. a Gaussian blur to the image. This is the next step in our program.\\
  123. \\
  124. The Gaussian filter we use comes from the \texttt{scipy.ndimage} module. We use
  125. this function instead of our own function, because the standard functions are
  126. most likely more optimized then our own implementation, and speed is an
  127. important factor in this application.
  128. \paragraph*{Larger amounts of dirt}
  129. Larger amounts of dirt are not going to be resolved by using a Gaussian filter.
  130. We rely on one of the characteristics of the Local Binary Pattern, only looking
  131. at the difference between two pixels, to take care of these problems.\\
  132. Because there will probably always be a difference between the characters and
  133. the dirt, and the fact that the characters are very black, the shape of the
  134. characters will still be conserved in the LBP, even if there is dirt
  135. surrounding the character.
  136. \subsection{Character retrieval}
  137. The retrieval of the character is done the same as the retrieval of the license
  138. plate, by using a perspective transformation. The location of the characters on
  139. the license plate is also available in de XML file, so this is parsed from that
  140. as well.
  141. \subsection{Creating Local Binary Patterns and feature vector}
  142. \subsection{Classification}
  143. \section{Finding parameters}
  144. Now that we have a functioning system, we need to tune it to work properly for
  145. license plates. This means we need to find the parameters. Throughout the
  146. program we have a number of parameters for which no standard choice is
  147. available. These parameters are:\\
  148. \\
  149. \begin{tabular}{l|l}
  150. Parameter & Description\\
  151. \hline
  152. $\sigma$ & The size of the Gaussian blur.\\
  153. \emph{cell size} & The size of a cell for which a histogram of LBPs will
  154. be generated.\\
  155. $\gamma$ & Parameter for the Radial kernel used in the SVM.\\
  156. $c$ & The soft margin of the SVM. Allows how much training
  157. errors are accepted.
  158. \end{tabular}\\
  159. \\
  160. For each of these parameters, we will describe how we searched for a good
  161. value, and what value we decided on.
  162. \subsection{Parameter $\sigma$}
  163. The first parameter to decide on, is the $\sigma$ used in the Gaussian blur. To
  164. find this parameter, we tested a few values, by checking visually what value
  165. removed most noise out of the image, while keeping the edges sharp enough to
  166. work with. By checking in the neighbourhood of the value that performed best,
  167. we where able to 'zoom in' on what we thought was the best value. It turned out
  168. that this was $\sigma = ?$.
  169. \subsection{Parameter \emph{cell size}}
  170. The cell size of the Local Binary Patterns determines over what region a
  171. histogram is made. The trade-off here is that a bigger cell size makes the
  172. classification less affected by relative movement of a character compared to
  173. those in the learning set, since the important structure will be more likely to
  174. remain in the same cell. However, if the cell size is too big, there will not
  175. be enough cells to properly describe the different areas of the character, and
  176. the feature vectors will not have enough elements.\\
  177. \\
  178. In order to find this parameter, we used a trial-and-error technique on a few
  179. basic cell sizes, being ?, 16, ?. We found that the best result was reached by
  180. using ??.
  181. \subsection{Parameters $\gamma$ \& $c$}
  182. The parameters $\gamma$ and $c$ are used for the SVM. $c$ is a standard
  183. parameter for each type of SVM, called the 'soft margin'. This indicates how
  184. exact each element in the learning set should be taken. A large soft margin
  185. means that an element in the learning set that accidentally has a completely
  186. different feature vector than expected, due to noise for example, is not taken
  187. into account. If the soft margin is very small, then almost all vectors will be
  188. taken into account, unless they differ extreme amounts.\\
  189. $\gamma$ is a variable that determines the size of the radial kernel, and as
  190. such blablabla.\\
  191. \\
  192. Since these parameters both influence the SVM, we need to find the best
  193. combination of values. To do this, we perform a so-called grid-search. A
  194. grid-search takes exponentially growing sequences for each parameter, and
  195. checks for each combination of values what the score is. The combination with
  196. the highest score is then used as our parameters, and the entire SVM will be
  197. trained using those parameters.\\
  198. \\
  199. We found that the best values for these parameters are $c=?$ and $\gamma =?$.
  200. \section{Results}
  201. The goal was to find out two things with this research: The speed of the
  202. classification and the accuracy. In this section we will show our findings.
  203. \subsection{Speed}
  204. Recognizing license plates is something that has to be done fast, since there
  205. can be a lot of cars passing a camera in a short time, especially on a highway.
  206. Therefore, we measured how well our program performed in terms of speed. We
  207. measure the time used to classify a license plate, not the training of the
  208. dataset, since that can be done offline, and speed is not a primary necessity
  209. there.\\
  210. \\
  211. The speed of a classification turned out to be blablabla.
  212. \subsection{Accuracy}
  213. Of course, it is vital that the recognition of a license plate is correct,
  214. almost correct is not good enough here. Therefore, we have to get the highest
  215. accuracy score we possibly can.\\
  216. \\ According to Wikipedia
  217. \footnote{
  218. \url{http://en.wikipedia.org/wiki/Automatic_number_plate_recognition}},
  219. commercial license plate recognition software score about $90\%$ to $94\%$,
  220. under optimal conditions and with modern equipment. Our program scores an
  221. average of blablabla.
  222. \section{Conclusion}
  223. \end{document}