Change criteria for checking neighbor blocks (#39) and possibly bugfix

[davidhcefx]

Description

• Criteria for checking neighbor blocks in findGeometricMatchesForSingleResults (#39).
• Possibly bugfix:
  • There are four loops around line 184:
    https://github.com/beurtschipper/Depix/blob/f2353b6f5e2334ae61182aceda32d486eb92b9ae/depixlib/functions.py#L184-L194
  • Assume that relative to singleResult, its ABOVE_PIXEL and BELOW_PIXEL both have only one "valid match".
  • By saying "valid match" we mean that the counter totalMatches in line 214 would be increased.
  • After the loops, when it comes to the check if totalMatches == 1:, it would fail.
  • However, the two pixels have indeed been determined by this singleResult, and should be taken into account.

Modification

• dataSeen: Changed from list to set for better performance.
• Instead of a single integer counter, I used a dictionary matchCount to keep track of the counter for each pixel.
• I changed the variable name xDistanceRectangles -> xDistance, but change it back if you think that'll be better.
• I guess line 193-195 are the main source of time decrease.

Before

After