Again another non-roulette post, but many of you asked about my foundation's research (universalsymbiosis.org). The current project is the housing, and things have moved along faster than expected. I'm in the middle of selecting a block of land for the building. We also now have a qualified builder on board.
Once the land is purchased, and will only be about $70,000 for roughly 10 acres which is cheap country land, two particular test buildings will be completed. One will be a conventional building that complies with building standards, andf the other will be a foam dome home which is what I most look forward to. Basically the company that does them inflates an enormous ball, sprays it with building foam, covers it in mesh for better support, sprays concrete on it, and basically done minus a fgew points. Very quick and much cheaper. Because domes are self-supporting, they need far less material.
The is to create the cheapest home possible without making it "cheap and nasty". ie from the inside, it will have every appeal oif a normal home. The outside can be made to be whatever we want.
It is difficult to know the timeline for progress, but soon I'll decide on the land which is the first step.
When I have more time I'll give more details, but am posting this because a few players were interested.
Friday, March 30, 2012
New secure document software
The new secure document software is ready. I'm making the service available to the public for free, despite the nearest competitor charges over $10,000 for the same kind of document security. So any document publisher will be able to use it for their own documents for free. It may upset secure document service providers, but it happens - they overcharge anyway.
The website draft is at www.freedocumentsecurity.com but it needs some finishing touches before it is launched and software made available. The software is not related to roulette in any way. Simply I didn't like the secure document software I'm currently using so had my own created which took roughly 2 months to do properly. In the coming week or so I'll transfer all documents to the new software, then the previous documents will be suspended. While I'm at it I'll update the documents. I'll send an announcement when the updated documents are ready.
The website draft is at www.freedocumentsecurity.com but it needs some finishing touches before it is launched and software made available. The software is not related to roulette in any way. Simply I didn't like the secure document software I'm currently using so had my own created which took roughly 2 months to do properly. In the coming week or so I'll transfer all documents to the new software, then the previous documents will be suspended. While I'm at it I'll update the documents. I'll send an announcement when the updated documents are ready.
Back into things
I've just about recovered from my illness. Fascinating really. More out than ever went in (sorry). Anyway I'm back into things and aim to at at least be up to date on emails by the end of today.
The new roulette computer website is online. If you wanted to have an ad published in the used computer section, let me know.
The online software programmers have finally agreed to fix the simulation bug, but after that is done I'll still change programmers.
I'm way behind on shipping but this will all be sorted this upcoming week.
Regarding the Uber, the programmer is still learning the source code. I will receive an update on his progress shortly. When he's finally past this part, he can finally make the small mod then I can resume shipping Ubers.
And finally the Hybrid, I'm expecting the latest build in the next day or so.
The new roulette computer website is online. If you wanted to have an ad published in the used computer section, let me know.
The online software programmers have finally agreed to fix the simulation bug, but after that is done I'll still change programmers.
I'm way behind on shipping but this will all be sorted this upcoming week.
Regarding the Uber, the programmer is still learning the source code. I will receive an update on his progress shortly. When he's finally past this part, he can finally make the small mod then I can resume shipping Ubers.
And finally the Hybrid, I'm expecting the latest build in the next day or so.
Wednesday, March 28, 2012
Limited responses for few days
Unfortunately I've caught a nasty bug (begins with G and isnt nice) so I'm far from running at my best. I've responded to all critical issues like code requests. I'll still attend the support forum and get some emails done, but I'm quite broken for now so please be patient and I expect to be up to date on all emails by the end of the week. I'm aware of a lot of emails in my inbox, and will get to them asap - you dont need to resend.
Thursday, March 22, 2012
V4 DVD with uber
For players testing the computers on the #4 DVD, that video is a perfect example showing:
- a good set of dominant diamonds, with bad scatter
- How variation of rotor speed affects ball bounce
- How gradual ball deceleration rate changes affect outcomes
For testing, I suggest use the basic auto target, so don't aim for specific diamond hits. Check the raw chart which shows the basic computer algorithm. Keep comparing it to the COM chart for target. With correct application you will find that the raw chart starts out with great accuracy, but after about 40 spins the accuracy turns terrible. But the accuracy is maintained on the COM chart with target. If you do it right, after the 110 or so spins, you will see the difference between almost no accuracy with basic settings, and about 80% wins covering 18 numbers.
Uber Dynamic Tuning & General Update
Many variables determine how the ball's bounce will vary betweren different rotor spins. On a set of spin dvds sent to me by a player, the ball travelled 19 pockets extra when the rotor was just 1 second faster. So if the rotor is just slightly faster, the ball will biounce completely differently. On such a wheel, it would be just about impossible to achieve any accuracy unless you used dynamic tuning, which adjusts for the different ball bounce on different rotor speeds. The lite and basic computers don't do this, same as devices from other developers. Even software used by casinos to assess wheel vunerabilities don't have this feature -= they all assume the ball will bounce the same regardless of rotor speed which is obvious nonsense. It is a feature only user by the uber and hybrid versions.
I also did further testing on the news uber modification, but this time there wasn't a significant improvement (about the same results as target). This is because of a ball and rotor combination anomaly that sometimes occurs. You cant always predict when or it it will occur though without collecting 60+ spins per direction. I'll continue work on it but again it will be months before this is fully implemented.
As for the uber and the new programmer, he's still learning the code but told me he expects to be finish about mid next week. Then he can start coding.
I also did further testing on the news uber modification, but this time there wasn't a significant improvement (about the same results as target). This is because of a ball and rotor combination anomaly that sometimes occurs. You cant always predict when or it it will occur though without collecting 60+ spins per direction. I'll continue work on it but again it will be months before this is fully implemented.
As for the uber and the new programmer, he's still learning the code but told me he expects to be finish about mid next week. Then he can start coding.
Wednesday, March 21, 2012
Calls tomorrow
I'll be taking calls tomorrow but please only call if the matter cannot be resolved via the support forum or email.
Uber and Hybrid development
I've done more research into the possible new algorithm/setting. In the last test, the results were:
Basic algorithm: near no accuracy
Target algorithm (no dynamic tuning): +122 units
New algorithm: +220 units
This was a similarly very difficult wheel. So again it showed a big improvement in the results, but it was more the data the confirmed the improvement.
Testing is one thing, but implementation to make it a practical setting is going to be very difficult. It is a lot more complicated than I expected especially when incorporating the dynamic tuning algorithms (different ball bounce on different rotor speeds).
To do it all in the optimal way will need a 3 dimensional chart using 3 dimensional areas to calculate predictions. A normal pc can do it, but I'm not yet sure if the mobile phones are capable of it. And no off-the-shelf microprocessor can do anything close to it. The phones we use have the storage, but may not have the RAM (memory). So perhaps only the hybrid will be able to do it, unless we can either do further firmware modifications or code the algorithm to use minimal resources on the phone.
Nevertheless, first for the uber we'll get the new programmer working on the firmware compatability issue so I can resume shipping. Within 2-3 weeks I will have designed the algorithm, then we can start coding it. Coding will take roughly a month so it will not be ready for perhaps 2-3 months. Only at this time I will know if it is viable for the uber, or only the hybrid.
The current uber version will do part of it when we re-enable the required menu items, but it is only a limited version of what will be possible. So users can test the improvements, but it is quite fiddly to do compared to what it will be.
Basic algorithm: near no accuracy
Target algorithm (no dynamic tuning): +122 units
New algorithm: +220 units
This was a similarly very difficult wheel. So again it showed a big improvement in the results, but it was more the data the confirmed the improvement.
Testing is one thing, but implementation to make it a practical setting is going to be very difficult. It is a lot more complicated than I expected especially when incorporating the dynamic tuning algorithms (different ball bounce on different rotor speeds).
To do it all in the optimal way will need a 3 dimensional chart using 3 dimensional areas to calculate predictions. A normal pc can do it, but I'm not yet sure if the mobile phones are capable of it. And no off-the-shelf microprocessor can do anything close to it. The phones we use have the storage, but may not have the RAM (memory). So perhaps only the hybrid will be able to do it, unless we can either do further firmware modifications or code the algorithm to use minimal resources on the phone.
Nevertheless, first for the uber we'll get the new programmer working on the firmware compatability issue so I can resume shipping. Within 2-3 weeks I will have designed the algorithm, then we can start coding it. Coding will take roughly a month so it will not be ready for perhaps 2-3 months. Only at this time I will know if it is viable for the uber, or only the hybrid.
The current uber version will do part of it when we re-enable the required menu items, but it is only a limited version of what will be possible. So users can test the improvements, but it is quite fiddly to do compared to what it will be.
Tuesday, March 20, 2012
Software bug
The online software programmers modified something and introduced a bug I only just found. It seems to affect the simulation feature. It doesn't seem to affect betting charts though. You can compare the betting charts with the simulation to see the difference. I've notified them and they'll correct it asap.
Monday, March 19, 2012
Update on schedule
Im about 2 days behind on emails but will catch up tomorrow. Please done resend emails.
Uber and Hybrid V3
I've completed testing of a new setting for the Uber and Hybrid V3. It has been run on my pc so the timings wont be as accurate as the phones, but the difference isn't overly significant. The purpose of the setting is to better deal with very difficult wheels, in particularly where the scatter is quite bad. For the testing I used a dvd where the velstone mk7 gives virtually random results when using typical roulette computer algorithms (X ball revs until drop, like VB). Of course you aim to avoid such wheels, but it isn't always possible if you are unable to travel.
The results over the same 100 spins were:
1. Basic settings only (no target etc): break even (no significant profit)
2. Target with standard tuning (not dynamic): +24 units
3. New algorithm (not dynamic tuning): +145 units
#1 was pretty much a flat-line chart with no discernable peaks. #2 had marginally clearer data. #3 was much clearer. There was an enormous difference. Keep in mind this is one of the kind of wheels you would normally not bother with because the accuracy is normally not worth your time compared to other wheels.
While this difference may not be as dramatic with different spins or a different wheel calibration, the results are certainly promising. You may know even rotation of the wheel of 20 degrees can be the difference between a wheel being very easy or very difficult to beat.
The current uber version already has part of this implemented, but the option to use it is removed from the menu system because it is too impractical to use. To make it practical requires about 8mb storage on the phone (which wont be a problem), and a bit more coding. Once the new programmer is more familiar with the software we'll get it all done, then I can test more.
How it works is basically better dynamic modelling of the relationship between the variables, in particularly detected ball speed, and the variations in ball deceleration.
Regarding uber progress, for now the new programmer is still learning what the code all does. The code is a lot more complex than when I last changed programmers so its taking longer than anticipated.
The results over the same 100 spins were:
1. Basic settings only (no target etc): break even (no significant profit)
2. Target with standard tuning (not dynamic): +24 units
3. New algorithm (not dynamic tuning): +145 units
#1 was pretty much a flat-line chart with no discernable peaks. #2 had marginally clearer data. #3 was much clearer. There was an enormous difference. Keep in mind this is one of the kind of wheels you would normally not bother with because the accuracy is normally not worth your time compared to other wheels.
While this difference may not be as dramatic with different spins or a different wheel calibration, the results are certainly promising. You may know even rotation of the wheel of 20 degrees can be the difference between a wheel being very easy or very difficult to beat.
The current uber version already has part of this implemented, but the option to use it is removed from the menu system because it is too impractical to use. To make it practical requires about 8mb storage on the phone (which wont be a problem), and a bit more coding. Once the new programmer is more familiar with the software we'll get it all done, then I can test more.
How it works is basically better dynamic modelling of the relationship between the variables, in particularly detected ball speed, and the variations in ball deceleration.
Regarding uber progress, for now the new programmer is still learning what the code all does. The code is a lot more complex than when I last changed programmers so its taking longer than anticipated.
Hybrid V3
I've just received the first hybrid v3 with all essential components put together. This includes the wheel position tracking, and the parts to track actual rotor and ball timings. This is with the camera constantly moving around to unreasonable levels.
With the basic implementation only, timings are accurate to within 60ms and are 95% reliable. This may sound inaccurate, but consider it is only basic implementation so far, and manual clicks for timings have errors at about 50ms. With the full implementation of the algorithms, the timings will be accurate to within about 10ms and with 100% reliability as per previous hybrid versions. In other works, timings for the hybrid will be roughly 5 times more accurate than any manual clicking method. I'm very happy with progress but there is still work to be done.
Also we've designed a receiver that can be used with either the uber or hybrid computers. Basically it will vibrate or pulse when the predicted number(s) pass the reference diamond. It can be implemented in a tiny microprocessor device about the size of a coin, but considering a body search would still reveal this, size means nothing (small size is only relevant if the device is physically invisible).
Instead, the device will be part of a mobile phone which is much more common. If you are physically searched, all that will be found on the bettor is a plain mobile phone - nothing else. No cables, no induction loop, not even a button for clocking. Not even software the phone manufacturer themselves could retrieve. Nothing but a phone. Not that we condone illegal application, but with such equipment, there is just no evidence to support a case against roulette computer players. Even if additional players are also caught, there is still not enough proof to establish "beyond reasonable doubt".
With the basic implementation only, timings are accurate to within 60ms and are 95% reliable. This may sound inaccurate, but consider it is only basic implementation so far, and manual clicks for timings have errors at about 50ms. With the full implementation of the algorithms, the timings will be accurate to within about 10ms and with 100% reliability as per previous hybrid versions. In other works, timings for the hybrid will be roughly 5 times more accurate than any manual clicking method. I'm very happy with progress but there is still work to be done.
Also we've designed a receiver that can be used with either the uber or hybrid computers. Basically it will vibrate or pulse when the predicted number(s) pass the reference diamond. It can be implemented in a tiny microprocessor device about the size of a coin, but considering a body search would still reveal this, size means nothing (small size is only relevant if the device is physically invisible).
Instead, the device will be part of a mobile phone which is much more common. If you are physically searched, all that will be found on the bettor is a plain mobile phone - nothing else. No cables, no induction loop, not even a button for clocking. Not even software the phone manufacturer themselves could retrieve. Nothing but a phone. Not that we condone illegal application, but with such equipment, there is just no evidence to support a case against roulette computer players. Even if additional players are also caught, there is still not enough proof to establish "beyond reasonable doubt".
Wednesday, March 14, 2012
Uber
The new programmer is still learning the source code. It usually takes new programmers about a week to have a reasonable understanding of it because of its complexity, and he's almost ready to begin coding.
Again I cannot do any shipping until a particular issue is resolved, because as it is now, the java software component is mismatched with the firmware of the new phone, so it does not run correctly. There is no point to me shipping if you can't use it. It is minor error and easily fixed, but the new programmer needs to understand the source code properly before making modifications.
Before you tell me how painful the wait it, consider it from my perspective. Like you, my hands are tied and all I can do it wait.
Again I cannot do any shipping until a particular issue is resolved, because as it is now, the java software component is mismatched with the firmware of the new phone, so it does not run correctly. There is no point to me shipping if you can't use it. It is minor error and easily fixed, but the new programmer needs to understand the source code properly before making modifications.
Before you tell me how painful the wait it, consider it from my perspective. Like you, my hands are tied and all I can do it wait.
Hybrid V3
Below is a link to a video of the latest wheel tracking algorithm for the hybrid v3. It is important to note that the green box I select uses a tracking algorithm for the wheel's location, NOT the ball. So it is used to track where the wheel actually is, and other parts of the v3 software track rotor and ball movement. But to give the wheel tracking algorithm a real challenge, I selected just the ball in this video. The result is at www.roulettesystemanalysis.com/m/balltrack.wmv
Despite it not even being designed for it, the software had no problem with ball detection and tracking - it really is military precision. When the technology is applied and optimized to track ball and rotor timings, establishing accurate timings very early in the spin (with faster ball speed) will be no problem at all.
While progress has taken much longer than originally anticipated (about 3 months behind), things are looking very, very good.
Despite it not even being designed for it, the software had no problem with ball detection and tracking - it really is military precision. When the technology is applied and optimized to track ball and rotor timings, establishing accurate timings very early in the spin (with faster ball speed) will be no problem at all.
While progress has taken much longer than originally anticipated (about 3 months behind), things are looking very, very good.
Monday, March 5, 2012
Uber Roulette computer shipping
With the exception of two purchases of the lite computer in the past few days, all new purchasers of any roulette computers are now shipped. A few previous purchasers haven't yet been sent the current version, but this will be done either tomorrow or the next day.
Any partners waiting for the latest phone models unfortunately need to wait a bit longer. This is because the actual builds are still conflicting with the firmware on the new phones. We thought this was fixed, but only part of it was fixed. It is a very minor issue, but the software simply wont work on the new phones unless it is fully resolved. But considering the lack of action from the programmer, such a small issue is a stopping me from shipping the rest, which are new phones. I've now finally passed the project to the new programmer. I have thoroughly explained to him that if he takes the project, that he needs to continue to be reliable. I've been working with him on other projects for over a year now, and he has proven very competent and reliable so I expect there wont be any issues with him.
I understand especially some partners have been waiting a long time to receive their phones back. This is not a matter of laziness or incompetence on my end. Most of the issues have been related to stock shortage, but as per previous posts, this is now sorted. There are a lot of other issues that players do not see, and I do not explain every issue at hand. Understand I am not paid unless partners make money, so I do everything possible to keep things moving. Just the christmas period alone slowed things to a crawl as the technician was away for about 3 weeks holiday while demand didnt slow, but this is only part of the picture.
Any partners waiting for the latest phone models unfortunately need to wait a bit longer. This is because the actual builds are still conflicting with the firmware on the new phones. We thought this was fixed, but only part of it was fixed. It is a very minor issue, but the software simply wont work on the new phones unless it is fully resolved. But considering the lack of action from the programmer, such a small issue is a stopping me from shipping the rest, which are new phones. I've now finally passed the project to the new programmer. I have thoroughly explained to him that if he takes the project, that he needs to continue to be reliable. I've been working with him on other projects for over a year now, and he has proven very competent and reliable so I expect there wont be any issues with him.
I understand especially some partners have been waiting a long time to receive their phones back. This is not a matter of laziness or incompetence on my end. Most of the issues have been related to stock shortage, but as per previous posts, this is now sorted. There are a lot of other issues that players do not see, and I do not explain every issue at hand. Understand I am not paid unless partners make money, so I do everything possible to keep things moving. Just the christmas period alone slowed things to a crawl as the technician was away for about 3 weeks holiday while demand didnt slow, but this is only part of the picture.
Ebook updates
My programmers are almost finished with the new secure ebook software (I had my own software created as the one I was using had some issues). We're just doing some fine-tuning then all ebooks will be updated. Especially the Uber instructions need updating, to simplify things.
Friday, March 2, 2012
Wheel evaluation instructions
I made a mistake in the initial instructions - I suggested Uber settings based on the previous version. I've corrected it and you should now download the corrected version.
Thursday, March 1, 2012
Wheel evaluation software for computer players
The wheel evaluation software for roulette computer players, and the instructions, are available from http://www.genuinewinner.com/forum/index.php/topic,339.0.html
A lot of players just try and get predictions as early as they can, without considering losses in accuracy. Understand the ball track and ball are not perfect, and every spin is different - the ball never rolls exactly the same way on different spins. Essentially this software will tell you how early you can get predictions while maintaining accuracy, especially for features like the Uber's target. So say if you want to know how early you can get a prediction and still accurately target which diamond the ball will hit and when, this software is what you need.
A lot of players just try and get predictions as early as they can, without considering losses in accuracy. Understand the ball track and ball are not perfect, and every spin is different - the ball never rolls exactly the same way on different spins. Essentially this software will tell you how early you can get predictions while maintaining accuracy, especially for features like the Uber's target. So say if you want to know how early you can get a prediction and still accurately target which diamond the ball will hit and when, this software is what you need.
Subscribe to:
Posts (Atom)