sikuli-driver team mailing list archive

[RaiMan <question167056@xxxxxxxxxxxxxxxxxxxxx>]

Question #167056 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/167056

RaiMan proposed the following answer:
@ shawn

--- comment #12

---  I'm going at it in a different direction and it seems to work.
This is exactly is how one is supposed to use Sikuli, if the image to check is to be compared with an expected_result image

--- it means that totally different images one being very close to the original and one being very differnt are matching at the same percent
definitely NO: if the matched region on the screen is the same image as the expected_result image, the score is always 1.0. If you allow Sikuli to search the whole screen for an expected_result image, that currently is not visible, then you either get a FindFailed or Sikuli finds an image that is similar with a score greater than the given by similar (standard 0.7) and might lead to weird results with scripts, that do not check the matches about correctness. 
If the image is visible, but has slight differences (usually in the background and at edges caused by different renderings), then you might get a match, but with a lower score. But the lower the match score, the higher the risk to get false positives.

Therefor the usual Sikuli image processing has to be called search and not compare, as long as the search region is larger than the image.
If you restrict the search region exactly to the size of the image, then you can call it a compare (which is what was requested with this question at the beginning).

--- comment #13
What are you missing in the docs?
Might be, I did not understand your comment.

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.