Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Defect in foul detection #36

Open
hidehisaakiyama opened this issue Feb 10, 2020 · 0 comments
Open

Defect in foul detection #36

hidehisaakiyama opened this issue Feb 10, 2020 · 0 comments
Labels

Comments

@hidehisaakiyama
Copy link
Member

This problem is reported originally from Thomas Gabel

In the NEWS file, the definition of dangerous situations is described as follows:

  • The ball handling player exists between the tackling player and the ball.
  • The ball handling player's body angle is directed to the opposite side of the tackling player.
  • The ball handling player is performing dash command.
  • Finally, the foul is determined randomly using foul_detect_probability of each heterogeneous player type.

The third condition have not been implemented correctly.

The original definition assumes that the being-tackled player must perform a dash command at the same time t at which the tackle-performing player is executing his tackle. However, a foul is sometimes detected in time steps where the player, who was tackled, was actually performing a kick command.

This defect is caused by the order of command received by server. The current automatic referee judges a foul just after the tackle command is received. In order to solve this defect, the referee have to judge a foul at the end of cycle.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant