← Back to team overview

sikuli-driver team mailing list archive

[Bug 1040541] Re: Score in "matching preview" differs from getLastMatch() score

 

--- what can be seen from your screenshot
- you seem to experiment with a Vision parameter. But one cannot see what you are doing here (hidden)
- the image you are looking for cannot be seen clearly, because it is nearly fully hidden by the min similarity badge (but it seems to be a Skype symbol: grey with a white x (offline ?) )
One might guess, that if the Sikuli window was closed only the Skype online symbols (green with white hook) are currently on the screen, but not the grey one.But not clear.
- the match shows 27x16 as width x height and position 125, 160. so the match might be one of the green Skype symbols, which would explain the bad similarity of 0.88. The shot is bad, since it has too much background, it should only be the symbol itself (means about 16x16) and should be searched (and found ;-) with a minimum similarity as high as possible (best from 0.95 to 0.99).
A positive match of a good shot should show a score of at least 0.9, even better more than 0.95

When I face problems of this kind, I do the following steps:
-- use Region.highlight(3), to visually see what is matched
-- optimize the shot, so it concentrates on the key visuals, that should lead to good matches (as little background as possible)
-- raise the min similarity ( Pattern.similar() ) as high as possible, to avoid false positives
-- restrict the search region as much as possible for the same reason and for better performance.

-- 
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1040541

Title:
  Score in "matching preview" differs from getLastMatch() score

Status in Sikuli:
  New

Bug description:
  Sikuli X-1.0rc3 (r905)
  Linux Mint 11 - 3.0.0-12-generic 32bit / Windows XP 32bit

  Reproduce:
  1.) Look for an image with find()
  2.) print getLastMatch()
  3.) Open "matching preview" dialog of image and look/play with Similarity value
  4.) You see that the "score=" value of getLastMatch() is much higher than the value of Similarity where the image was found

  Mainly occurs if an image does not show up on the screen.

  
  On the attached screenshot you see that the image was found with a score of 0.88 but a Similarity of 76 does not lead to a match.
  A decreased Similarity value of 70 result in a match. The image we are looking for is NOT on the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/sikuli/+bug/1040541/+subscriptions


References