I did some more investigation, and I think I located the cause of the
error. I am importing a .sikuli file that has function definitions into
the file(s) that are experiencing the errors, and I noticed that some
images have the same name in each of those two files. Is it possible
that the
I'm a little confused by this explanation. I have tested this with
capturing images from a webpage, and used the same page in the same
browser, testing on subsequent days. I am also using the minimum image
size that I can, capturing only the relevant section (such as a menu bar
item, and capturing
Sounds really weird.
But Sikuli does not have any kind of memory,that can lead to such
things in different script runs.
BTW: how can you be sure, that Sikuli finds what you think it should
find in that failing moment?
May be it finds something similar, because the one it should see is not
yet
** Changed in: sikuli
Status: New = Opinion
--
You received this bug notification because you are a member of Sikuli
Drivers, which is subscribed to Sikuli.
https://bugs.launchpad.net/bugs/1211462
Title:
Image similarity value changes randomly
Status in Sikuli:
Opinion
Bug
I do not think, that this is a bug in Sikuli, it might be an
inconvenience though.
If the same script during another run report lower similarity values
than before, then the search operation has found, that it is so.
The reason in most cases are probe images, that contain too much
background or
5 matches
Mail list logo
