You have chosen to sponsor your bid up to a maximum amount of .
I am uncertain about the cost of this project, please let me know if you regard the range as unrealistic.
Some software is required for connecting to the Betfair betting exchange through the API, reading data and making bets.
C++ is the preferred programming language. It should run on 64 bit Windows 8 operating system, and ideally on earlier 32 bit Windows operating system also. There is a certain degree of flexibility in the overall architecture of the system according to your recommendation. It is proposed that some controlling software will open and close some bot sessions which will make the bets on the exchange. A simple GUI should be provided which can be used to specify a range of parameters. These preferences should be prepopulated with a parameters fie. The software should be efficient and stable and the code must be fully editable in a visual programming environment and it must be possible for someone without advanced technical expertise to set up with simple instructions you will provide. In particular, their will be a logic function that makes betting decisions, and it must be possible to add and remove parameters by editing the code and recompiling the software. The software is likely to be used in betting on horse races, but it should be possible to run it on other sports. The software must be able to place bets on the Uk and Australian exchanges, and must be able to place bets before the race and in running. API and screen scraping FTP mode must both be supported.
At the start of the day the control software should start all the bots and at the end of the day it should close them down.
The bot will need to be able to detect the length of time before each race.
The software should facilitate configuring all of the following:
• The countries from which race meetings will be selected (e.g. UK and Ireland).
• Whether one bot for all betting is required or one bot for each meeting.
• The interval of time before or after the start of the race that betting is to begin and end.
• Whether betting stops when the market is suspended or continues until it is closed.
• It should be possible to view the race meetings that have been selected and manually alter the list for the day by removing some and adding others.
• Minimum and maximum number of runners allowed.
• Minimum and maximum stake.
• Output bets information.
• Output market information.
• Make profit loss calculation.
The software will read data from the site. The variables should conform to an existing naming system, details of which I will provide you.
This information which will be passed in to a logic function that makes betting decisions. I will write this, it is not something that you need to do. Based on the data decisions to place new bets, either back or lay, and to cancel or modify existing ones will be made. You need to support these operations which I will call from the logic function.
Data structures and variable names must ideally conform to existing ones to facilitate compatibility with existing code. Ensuring this compatibility will not be your responsibility and you will not have to work with this existing code, however it would useful if you would use our names for variables to minimize changes required to the existing code.
The bot will need to output data in to two CSV files for each race that can be readily studied in a spread sheet. This should include all of the data read in one file and all of the betting decisions made in another, both should be properly indexed and include the time before the start of the race. This will be used for debugging future changes to the code.
There is some flexibility in these specifications, particularly if altering them will produce a cheaper quote.
A slightly more detailed specification is avaialbe at https://skydrive.live.com/redir?resid=6C7D6F28A7591688!2199&authkey=!AJrQZeKF8Alhb7c.
Please let me know if you have problems following this link.