← Back to team overview

sikuli-driver team mailing list archive

Re: [Question #261815]: visible recognition too slow

 

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

RaiMan proposed the following answer:
ok, understood.

I guess, even with massive parallel processing (delegate the different exists into subthreads) you will not solve this problem.
To follow faster moving objects, the find op is not adequate.
To check once for the existence of 4 possible images in this region will take up to 100 to 200 milliseconds in best case with using a sequence of exists(image, 0). 
So the duration depends on the sequence you search for the images.
With parallel searches (threading) you will save some time, but a more complex implementation.

Another option might be to use an observe solution (onAppear() + observe(background=True).
Here an option would be, to subdivide the region into the 4 squares (one per line) on let an background observe run in each of these regions (which already gives you 4 parallel threads).

Another option with observe is to try with onChange().

If you want to experiment with observe, switching to version 1.1.0 is
mandatory.

In any case, I would first try to find a perfect solution for this
search problem isolated, before packing it into a workflow.

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