Please read the user's manual to get started with the contents of the source package, and basic functionalities of the simulator and the agents. The manual also contains information about the communication protocol between the simulator and the clients, and formalizes the model of the dynamics of the environment. Download the manual from:http://gridsoccer.codeplex.com/releases/view/64543Quick Start
- Build the source files. Having downloaded the source code, build the source files by opening the AllInOne2010.sln solution file and choosing build in the IDE. It is recommended that either Microsoft Visual Studio 2010, or SharpDevelop 4.0 be used.
- Run the executables. Having built the source files successfully, go the Bin folder. There you can find the executables for the simulator and the sample clients.
- Adjust the simulator configs. In the Bin folder there exists a file named GridSoccerSimulator.exe.config, which is a plain-text file containing the simulator configs formatted as XML. There you can modify various parameters of the simulator including the cycle length in milliseconds, the total number of cycles of each game, the dimensions of the field, the width of the goal, the minimum, and maximum number of players in the game, the passability and visibility radii for each player, and others. If the simulator is already running you need to restart it, in order for the changes to take effect.
- Use a script to start a game. In the Scripts folder, there exists a couple of sample scripts to demonstrate how a game and the players for the 2 teams should be started. You may want to run RandomVsHandCoded.bat to start, or modify it as you wish. If you are using Mono instead of .NET Framework, you can use Mono - RandomVsHandCoded.bat instead. Note that, in order for the latter script to work, you have to add the path to the mono executable in your system's PATH environment variable.
- Use turbo mode to increase speed of the simulation. There are times, that some experiments need days of simulation. In such cases the turbo mode can be of great help. In turbo mode, there's no time-gap between two consecutive cycles, hence the CPU usage of your system might be greatly increased. You can also turn the monitor off to further increase performance, and turn it back on whenever needed.