sikuli-driver team mailing list archive

[Thom Bowden <question280712@xxxxxxxxxxxxxxxxxxxxx>]

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

Thom Bowden posted a new comment:
Hi RaiMan and dinesh

I have been looking at essentially the same issue as dinesh describes.

I too have been using the IDE tooling to gauge the score of the image
and thus ascertain whether the image would be found on the screen. As
far as I understand it;

0.0 - 0.69 would trigger a FindFailed exception. When using exists these
should return False

0.7 - 0.99 (or 1?) would return True on exists

0.95-0.99 would return true for exists, exists.exact. 0.94 and below
would return false for exact.

I use the IDE tooling to check at what sensitivity point my image starts
to be recognised, in my case it is stops finding any matches at 0.41 on
the slider. I thus conclude that the png I have captured would be no
good to use and I need to rethink the area I capture.

If I try and run the test with the image that could not be found above a
0.41 sensitivity then I expect it to return a False for exists and
exact. If I used pattern similar, it should find it at 0.40, as per the
IDE. Is this all correct ?

Unfortunately, my call is always returning a True and thus a pass for
exists and exact, regardless of when the image is different, or that it
only gets recognised by the IDE tool below 0.41

My code is the same as dinesh's example

-- 
You received this question notification because your team Sikuli Drivers
is an answer contact for Sikuli.