2005 OSAKA ROBOCUP 3D Simulation Competition Rules
2005.1.11
Translation: Xu Yuan XYCHN15@yahoo.com.cn
Summary
This article contains the official rules of the 2005 Osaka Robocup 3D Simulation Competition. Although we tried to cover all aspects, if an accident occurred, the rule committee will seek the contestant's views and make a decision. However, once the committee makes decisions, this decision will not be discussed. About more information on this competition Access: http://www.science.uva.nl/~jellekok/robocup/rc05/
Simulation environment
*machine:
The participating team can only use the Linux operating system. Depending on the time available, each team will get one or two machines. Linux will be released by Gentoo.
*Emulator
The Server version used this game will be the latest version released two weeks before the game. Use the official profile.
2. Particile needs
An effective team must meet the following conditions:
* Any timing and tracking process attempting to ruin spades will be strictly prohibited. Your responsibility is included, but not just:
- All calls, clone, etc. must be dynamic calls. You can't use a fully static connection that can be performed unless each Agent runs in the same process or thread.
- Your code cannot change the code that is monitored.
- Any Sysv IPC or UNIX interface used by any spades is strictly prohibited.
-Agent cannot communicate with process / threads that are not tracked by Spades. In fact, your Agent cannot calculate the process and threads generated by the main thread and its sub-threads.
* Agent is not allowed to communicate via Spades / RcssServer3D.
* Everyone needs to provide your Agent to provide a spades agent database login type
If the participating team has a suspicion of violating the rules, the Committee has the right to request inspection of source code.
3. Competition structure
3.1 Overview
* All games will begin manually by the human referee.
* The game contains the upper and second half, each 5 minutes. In some cases, there will be a timefather, more information see the following part.
* You can adjust your code or replace the new code during the game. Of course, the problem that occurs is responsible for yourself. Make sure you have seen the "Agent failed" section. Note that only you can upload your code between the game.
* Win the game 3 points, draw 1 point. The abandoned team participated in the competition will be recorded in 3: 0 or recorded in the abandoned team and the results of the other team of the same team (if the score is greater than 3: 0).
* You need to provide the Spades Agent database for your Agent. Please see the example of simulation packages agedb.xml. Place it in the top of the home (example: / home / [teamdir] /agentdb.xml).
* Agent Database file will be used by different users in your user group. Your files and team execution codes must be at least group readable and executable permissions.
* If your team can't work, we won't adjust it.
3.2 game program
The competition procedures are as follows:
* The game contains three rounds.
* The first round, the committee elect the seed team according to the Robocup2004 competition. The team will be randomly packet.
* The first round, the team was divided into six groups, each group 5 teams. Two teams in front of each group entered the second round. Distinguishment, please see the relevant chapters.
* The second round, the team is divided into two groups, each team 6 teams. Two teams in each group entered the semi-final.
* In the last round, each game must have a winner. If there is no victor in the competition, the extra three and a half field will be overtime in accordance with the golden ball rules. If there is still no result, there will be a human referee to throw a coin to determine the winner.
4. Distribution of flat
At the top two rounds of flat, the number n> = 2 is determined by the following priority:
1, points
2, the results of each other
If n = 2, when and only match each other, according to each other
If N> 2, when and only a team is higher than other teams, according to the results of each other
3, all net winches of this round of competition
4, the number of net winning balls between the game in the game
5, if n> 2, all the number of spins in the game between the game
6, all the number of spins in this round
7. If n = 2, the additional three and a half field will determine the winner according to the gold ball rules. If n> 2, first sort in accordance with the statistics (number 3-6) of the game. The remaining team was randomly rejected. A separate knockout, each of the three and a half game per pair of gold balls. If there is still no result, there will be a human referee to throw a coin to determine the winner.
8, throw a coin!
Excellent in the list: the team is flat, and the team can enter the next round, some can't, the competition statistics (numbers 3-6) can not distinguish.
5. Fall
In some cases, like Kick-in, the game is interrupted. If a team can't make the ball back to Play after Kick-in, it will automatically fall after 30 seconds.
If you repeatedly appear that the team that must start the game does not move toward the ball, it can be shortened by the human referee by manual frenchy. The purpose of this is to maintain the coherence of the competition and give the team fair opportunities to play their rights.
If there is no player to move to the ball in Play-ON mode, or no one can play, the referee will fall after 30 seconds. In this case, specifically, encourage the referee to use some common sense. For example, if a team member needs a long distance to get the ball, and for more than 30 seconds, they need enough time to kick the ball before falling. I should not fall before 30 seconds. But if no one is playing, the referee will fall in a shorter time.
6. foul
The current Kick-in is automatically detected by 3D Server. However, in some cases, the foul can only be discovered by the human referee and gives a free kick. The reason for the foul includes the following but not just:
* If a team is surrounded by the ball, other teams can't touch the ball.
* If the ball is too much player blocks can't go into the ball (approximately principles: the player is blocked)
* If a team deliberately blocks the movement of the opponent
* Any behavior that violates the principles of fair competition is still referred to as fouls after the rules committee.
7. Fair competition
The purpose of the competition is to simulate in accordance with the general rules of fair principles and football and limitations to simulate through virtual 3D football simulation world. Deception will be seen as a violation of fair competition principles and strictly prohibited during the game.
Violation of fair competition, for example:
* Use the execution code of other teams
* Each Client is emulated by sending too many commanders
* Direct communication between players using other communication paths, such as inter-process communication
These are strictly prohibited.
After the Rules Committee ruling, other strategies will be discovered as a violation of fair competition principles. However, we expect a fair team. In fact, it will be seen by the emulator as a violation of fair competitive principles by other ways. If you have questions when you use some methods, please ask the rules committee before the start of the game. If the team is discovered during the game, it will immediately lose the qualification.
8. Effective game
8.1 Agent error
Because the Agent's procedural problem causes an Agent error, the following procedures apply.
* If your Agent cannot connect to the emulator within 30 seconds, there will be a chance to start three times.
* If the problem is on the side of the parameters, you can change your code in 2 minutes to change or replace the execution code. This is your last chance. After this, the Agent still does not work normally, and the game will not be disrupt. The competition continues or you lose the game with a 3: 0 score.
* If your Agent lost the connection to the emulator after 30 seconds, the game will continue, if you can't continue the game, you will lose the game with a score of 3: 0. 8.2 Server error
The referee that supports any party thinks that the emulator is wrong, and the rule committee will deliver whether to continue to play. If the committee decides to stop the game, the game will start again.
9. Remote participants
Overview: The distant participants are only in special cases.
We don't have resources to find a problem with the distant participants launching procedures. Therefore, in their own interests, the distance from the distant participants must ensure that third parties (for example: we) can easily launch your code and differ from the development platform. The platform is running smoothly. Unfortunately, if we did not successfully quickly get the code and run smoothly, we don't guarantee that the distant participants participate in the competition.
10. After the game
After the game, the team will be automatically announced. To help us publish your team, install all files in / home / [teamdir] / RC2005 / to install your team. If you can't provide an executable team, we will announce the entire home directory of that team. Moreover, it is possible to deprive the Robocup2006 competition.
