Figures index

From

DotCode Damage Testing

Kevin Berisso

Journal of Computer Sciences and Applications. 2018, 6(1), 43-47 doi:10.12691/jcsa-6-1-6
  • Figure 1. Example of the DotCode symbology. The “Barcode Scanners” app by Cognex can be used to scan DotCode using either Apple or Android devices
  • Figure 2. Symbols with the same data (“874130”), but using different masks resulting in a missing bottom row (left) which prevents the symbol from being decoded whereas the right symbol can be decoded
  • Figure 3. Samples of some common matrix symbologies, QR Code (left), Data Matrix (middle left), Maxicode (middle right) and Aztec Code (right)
  • Figure 4. (Color online) DotCode on a pack of cigarettes purchased in Greece. Picture taken by Alexandra Valtzidou
  • Figure 5. Symbols with the same data (“0242FZ5CGW0D”), encoded in a 7 row by 50 column pattern using masks 0-3 (top to bottom) showing how the masks can eliminate blank columns (masks 0 and 4). The scores for each mask are -106, 137, 325 and -15 respectively and the threshold is 175
  • Figure 6. Two symbols showing the sequence (the numbered circles) and direction in which the dots are encoded. The left pattern is 7 rows x 6 columns and the right image is 6 rows by 7 columns
  • Figure 7. (Color online) Symbols with the same data (“038451”), encoded in a 10 row by 13 column pattern using masks 0 (left) and 3 (right) showing how a symbol could inadvertently be generated that is missing multiple edges. The light red boarders indicate the edges of the grid
  • Figure 8. (Color online) Testing rig. Visit vimeo.com/229003022 for video footage of the system
  • Figure 9. (Color online) Sample symbol showing one additional dot (dark blue dot) and one erasure (red dot) within the first codeword. The use of red dots was because it was determined the scanners filtered out red, which resulted in the red dots appearing as white to the scanners while allowing the researcher to still see the deleted dot
  • Figure 10. (Color online) Average scanner decode times for each damage run. Decode times are in milliseconds
  • Figure 11. (Color online) Average decode by scanner and symbol for each damage run. Decode times are in milliseconds