Monday, October 29, 2012

JAA (online software)

It appears the issues with JAA are finally fixed - now the server is using multi-core processing. A 1500 spin analysis takes about 30 seconds instead of the server timing out or crashing. This is something like 10 billion calculations so it can't get much quicker, although the typical wheel is for only 150-300 spins per direction.
 
From the testing I've done so far, it all appears ok but report any issues to me at the player forum: http://www.genuinewinner.com/forum/index.php/topic,6406.0.html
 
I still need to do some final testing, so I suggest players don't bet for real just yet. Again I will need players to contribute so testing is done quicker.

Thursday, October 25, 2012

JAA

Programmers have stated they have fixed all issues and will be uploading the fixes to the server within 24hrs. We'll wait and see if there is any significant progress. If what they say it accurate, then this is a better option than finding other developers. As soon as changes are uploaded, I'll test assuming its not past 5pm. If it is, I'll test first thing in morning.

Tuesday, October 23, 2012

Unlock codes & support

All unlock codes are now done. I was a few days behind schedule as work piled up. If you haven't gotten an unlock yet, I haven't received your request.
Also all players need to check the knowledgebase in the forum before asking questions. And preferably use the forum first for support because often other players can answer questions for you, and more often than not the question is already answered there numerous times.

JAA

The online software is having further problems.  I don't know what the cause is this time.   I've given the programmers until Wednesday to fix them, and the other issues, or I'll hire someone else.

Monday, October 22, 2012

Shipping

Items that were supposed to be shipped last week were just shipped today. Items within Australia are sent with a battery via overnight express, although they are sent via road so they may take a day extra. I will send tracking details for international items within 24hrs.

Thursday, October 18, 2012

Seeing through cards - technology development

Years ago I acquired technology that is capable of seeing through casino cards. This would have been used to predict the next card in blackjack, and to read the dealer's cards but the problem was it emitted radiation. It is highly illegal and unsafe to blast people with radiation.
 
A technician I've been developing the technology for years with has been trying to make a version that uses ambient radiation instead. We left it alone for some time though as development couldn't proceed further. We had the design for it and had tested the concept successfully, but for years the only way to build the technology into a small and practical device was to develop components at a cost that made it impractical.
 
Now things are different and we have the components we need. Development will still be expensive but considering the potential of the technology, it will be worth it. The device will be small enough to be comfortably worn (ie in pocket or strapped to inside of leg), and uses only ambient radiation from space.
 
The part I love most is we will be using some of the hybrid roulette computer technology. The hybrid technology will track the location of:
 
a. The player's cards
b. The dealer's cards (including knowing which ones are reversed/transparent)
c. The next card that is to be dealt
 
The location of these cards is easy because the hardware will have defines card location relative to marks on the table.
 
Parts A and B will be simple. But part C is a bit trickier. Nevertheless the edge obtainable from knowing the dealer's cards is all we would need.
 
From this point development will not be difficult – nowhere near as difficult as the hybrid roulette computer. Since we've already developed robust and accurate image recognition technology with the hybrid, much of the work is done.
 
I will release more details and show a video demo at some stage – I estimate 1-2 months from now for completion of the live card video. Then perhaps 1-2 months development for the rest of it. So conservatively, I will have technology that automatically determines the cards from A,B and C (including cards turned face down), then will give the player a highly covert vibration on whether to hit or stand.
 
Certainly this is a game changer. I only sold 2 of the hybrid V3s with the rest being used only by my private teams. I expect to also only sell 2 of the x-ray card readers. When I have the prototype ready for demonstration, I will announce it. If you have an interest in purchasing one of them, please keep an eye on my blog, but again it may be 4 or so months from now.

Wednesday, October 17, 2012

Shipping

There are numerous items that were due to be shipped many weeks ago but never got shipped for various reasons, such as me being on vacation. Also there are few recent items. These are now ready and are being shipped tomorrow. Recipients will be notified of parcel tracking details.

Tuesday, October 16, 2012

Scatter analysis - method 2 training video

I've uploaded a new training video regarding method 2 of scatter analysis. The download link is in the first at http://www.genuinewinner.com/forum/index.php/topic,255.0.html

Uber minor updates and Hybrid V3

Uber: The minor updates for the Uber are complete. I did some testing last night it seemed perfect, but I'll continue testing today. As he did these updates only days after starting to actually code, the programmer is now working on some of the larger updates – in particularly one that will make play much easier because it will have better automatic peak identification. As per previous posts, peak reading is where many players fail because they don't recognize the edge from the charts alone. It is more than just peak identification but whether or not the phone has the resources to do what I want it another matter. We'll know in around a week.
 
Hybrid V3: The hybrid programmer is tidying up some code in preparation for merging the phone with the main component (the last stages). This will take him a few days so the phone programmer is doing more Uber updates while he waits. Full completion for the Hybrid including testing and all is likely just a few weeks away.

Friday, October 12, 2012

Spin data sharing and jaa mods

As I have mentioned it before, part of the future updates for the online software will enable players to share data for specific wheels. For example, as many players work with exactly the same wheels, sharing the data between players makes sense. One of the problems with this though is how do we know when a player is collecting accurate data, or just pretending to so they can have access to everyone's data?
 
JAA (online software) will eventually have a feature that allows you to partner with any number of players. You will be able to form groups where everyone in the group can access each other's data. To avoid inaccurate data , you can select the specific members you want to share data with, and reject data from members you don't know or trust.
 
There are various design issues that need to be solved to make it reality, but it has been on the to-do list for a while, and will be implemented in due course. For now we are focusing development on making auto analysis faster. So the order of matters are:
 
1. Make auto analysis faster (this has been going on for almost 2 months now, but appears almost done finally)
 
2. Addition for auto analysis to make it more foolproof (lets you know how profitable a wheel is, and when it is or isnt profitable. currently jaa just gives you best places to bet and when, whatever the pattern strength. and you need to use the simulation feature to test. this is ok, but it is better to have it 100% automated and quick)
 
3. Integration with the mobile phones (so players can collect data covertly at the table, and receive predictions via wireless earpiece). So there would be no need to write anything at all down.
 
4. The data sharing module as explained above.
 
5. Additional pattern type integration
 
6. Minor issues to make use more practical: ie import/export data.
 
The order may change, but this is how things are looking for now.

Wednesday, October 10, 2012

Hybrid V3 and Uber Updates

The new programmer is moving very quickly, and is understanding everything very well. He has started actual coding initially for some Uber updates (minor updates to begin). But so far he is unable to test them because the Uber software will not run on anything but the specific phone models the Uber is developed for. The Hybrid V3 uses the same phones. The software wont even run in an emulator. As the phone model is discontinued, I've shipped him phones from my stock. They'll arrive in a few days, then he'll be able to continue development.
 
Once the minor Uber update is complete, he'll begin work on the Hybrid V3 phone component. As he is proving a competent programmer, I don't expect this part of development will take more than 1-2 weeks once he focuses on it. So at this stage it looks quite certain that within 30 days, the Hybrid V3 will be fully complete and ready for actual use, including testing, all components ready and all. The testing alone will take 1-2 weeks depending on what, if any, bugs are found. Almost always there are bugs which is a normal part of development – we just do all testing and correct them when found.

Thursday, October 4, 2012

New Uber Version

I now have a new programmer for further development of the Uber roulette computer. One of the determining factors of a player's success is their ability to understand the chart data. Players tend to think they understand it, but still about 80% of players don't accurately recognize their edge – they look for wheels with glaringly obvious peaks when often you don't get this despite having a clear edge. This is partly due to the fact that visually determining an edge with mere charts is insufficient. So the Uber upgrade will give players a perfectly clear indication of whether or not there is an edge, and if so, approximately what it is. This is not as simple as highlighting peaks on a chart.
 
As I have said previously, I don't think the accuracy of the Uber can be improved further. But there is still room to make it easier to use, and this is the focus of development. In roughly 2 weeks, I will know more about when it will be available.

Wednesday, October 3, 2012

Hybrid V3

I've now hired the new programmer for the mobile phone component of the Hybrid V3. At this stage he is just reviewing various material to become familiar with the overall project and requirements. Based on what he knows so far, he estimates realistically including understanding existing code, he should be able to complete everything within 30 days. This is more a conservative estimate though and expect it wont take that long.
 

JAA

The programmers are still working on JAA, but I tested this morning with a 1500 spin profile, and it seemed to work no problems despite it taking about 2 minutes for the server to complete the analysis. The analysis did appear correct but I wont be fully checking it all until the programmers tell me they've finished tinkering with it.
 
The test this morning suggests the main bugs with the functionality are corrected, but still there are no performance enhancements as the mods were supposed to achieve. But still a 2 or so minute wait for analysis to complete is more bearable than auto analysis not working at all. Anyway I'll give more updates in time, but for now don't use auto analysis for real.

Tuesday, October 2, 2012

Hybrid V3, Induction Loops and General update

Hybrid V3: Again all that's left to do is the mobile phone programming part. But I need a new programmer for this. My focus is mostly on finding the right developers for the work. It is literally only about 1-2 weeks of coding left for it to be complete, but having to find an additional programmer takes a long time especially for this kind of work. We really need people that know what they are doing or they may waste weeks just trying to understanding the existing code. I did have a programmer set a short while ago, but he didn't like the complexity of the code despite initially assuring me it wouldn't be a problem. Nevertheless I expect to have chosen another developer by mid next week. At the very least all the difficult coding and development is already done and working better than I even hoped for.
 
Induction Loops: You may recall earlier batches were easily "blown" if you put the battery in the wrong way. It seems the newer batch still has this problem. So for anyone who needed new loops, I'll send two of the older ones which work perfectly fine, unless you put the battery in the wrong way. So don't do it, and carefully check how you put the battery in (the polarity)! Nevertheless I've ordered 100 loops with the vulnerability properly addressed.
 
General update: Most of my time is being taken up by communicating with programmers either for JAA, Hybrid V3 or other projects. So I'll be on Skype a lot, but I'll be unable to chat much to anyone but programmers. If you see me online it is ok to ask a quick question, but by quick I mean quick. I do not want to appear rude or abrupt, but when 20 people each want only 5 minutes of my time, a large chunk of the day is used. Believe me I'm prioritising tasks so issues for the most people possible are addressed.

JAA Software

The software has many issues that appear to be server resource issues. ie we need a more powerful server. Currently a few people using auto analysis at the same time with 1,000+ spins will cause a crash.  First we'll try upgrading the server. If that doesn't work, we'll need to do a complete move. I'll know more within about 24hrs.

Monday, October 1, 2012

Code Requests

Many players are incorrectly using the code request form. For example, the incorrect product or item is specified for the code submitted. Specifically a player may request unlocking of a document for product they do not have, and such requests are automatically rejected. Additionally, many players are forgetting to specify their e-mail address, so I cannot verify who has made the request. If you haven't received an unlock code for any recent request within 24 hours, your submission had some kind of error and you will need to resubmit.