How I can test your computer to check how accurate it is

It is very easy.
For that you will need device that you want to test and few good quality video spins.

Here I will explain how to test my device but same test could be applied to any prediction device, computer or system.

If you can run video spins on DVD player. It is better then using computer because computer may create time delays in video picture, which could make test harder or inaccurate. I am using DVD player with built in hard drive where I have stored roulette spins. DVD player is handy with option to repeat one single spin continuously.
And that is what we need for start.

1 Test how accurate system can detect ball speed and predict according to that.

Run one spin and try to predict it 40 times.
Each 10 times use different diamond for clocking.

IQE6 starts calculation with loaded defaults which are average values.
Time how long it will take to adjust is proportional to how far real wheel specification is from presented values. First 4 valid spins it is fast adjustment, and probably after first spin you will be set close enough to have prediction within few numbers of accuracy.
With each spin the system settings are closer to mach parameters of particular wheel.
After 4 spins system is definitely within range and starts looking and defining differences in between one single rotation to get the best accuracy when predicting. Also system starts various controls so already learned data can not be easy disturbed by accidental bad clocking. For each additional spin system is fine tuning and monitoring what is going on with wheel then adjusting according to it.
When you start testing the test could look as this.
Clocking at diamond 1
Spin …predicted number

  1. …18 this is first spin and system learns, prediction is number 18

  2. …12

  3. …26 here system is close to adjusted

  4. …26

  5. …32 stable prediction

  6. …32 it stays mostly within 3 numbers of accuracy

  7. …26

  8. …35

  9. …26

  10. …0

    Clocking at diamond 1
    Spin …predicted number

  11. … 12 It is same here, system is seated with first 4 spins

  12. … 35; but here is fine tuning for ball speeds at that range.

  13. … 0

  14. …26

  15. …26

  16. …32

  17. …32

  18. …15

  19. …35

  20. …26
    Now we continue to do it at any spot on the wheel.
    Good computer should detect ball speed correctly, eliminate human errors in clocking and predict according to ball speed. Narrower difference in between numbers means that computer is more accurate. In this test I actually used real data from Iqe6.
    Video spins move pictures in time frames of 40ms therefore at some positions error may slightly increase. Clocking at real wheel is more accurate.

  21. The test how good computer can eliminate errors in clocking.

For this alternate clocking, first rotation clock the ball at diamond and next rotation do it 1-2 cm distanced. If you do it with single click it will produce error of about 9 numbers. But error correction should reduce it. Compare results with previous data and check if there is difference and how much. IQE 6 is getting almost same data during this test.

  1. Rotor calculation tests.

Still you can use same video spin. Up to now you already know what prediction is. Next is to check how much that prediction will change by giving to system different rotor time. So repeat spin clocking but when clocking rotor start when ball is at clocking diamond but stop it 5 -10 cm earlier or later. That way you give to computer data that rotor is faster / slower. Of course prediction should move according to data.
If your last click is earlier then system should predict further in ball direction.
This is only approximate test but change should be close enough.
IQE6 uses detected ball and rotor speed when displaying result; therefore it will not show 100% accurate result. Simulation that wheel is faster will show a bit less then real and for a slower wheel it will show more.

With this test we can have general idea about system ability to define failing point of the ball. Of course that is not final prediction.

How accurate is this failing point in relationship to final result it depends of many additional factors such as:
How far in time are we from point when the ball hits rotor
Imperfections on wheel, deformations on ball track, slight tilt may have various effects on ball traveling time, kind of ball, number of diamonds etc. Therefore with later prediction we are more accurate but we have less time to place chips.
IQE6 tested on different spins with high accuracy setting, when tested on different spins have all results within same or close to same distance from prediction.

Ball bouncing 

This part is really individual for every wheel / ball combination.
Because of that no matter how good we predict the game is still partly random.
Sometimes it works for us sometimes against and we should look for average.

Task of every advanced player is to have good way of prediction but also to search where that advantage may be the highest.

For the end, if you have opportunity to look computer in action as sellers demonstration. Never look final result it could be coincidence or video editing.
Simply compare distances from predicted number to number when ball hits rotor.
If computer is good, and prediction is zero then ball hits rotor at number 18.
Next spin, whatever prediction is the ball should hit same distance from that number as it did from zero to number 18. Sure few spins could be out of that but most of them should have same distance.

You can check computer by taking remote support by any of the software such as team viewer and many other software which are compatible with can take Support for Windows if any problem persist.