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

Re-examine rules related to entering the goal zones #294

Closed
justbuchanan opened this issue Apr 23, 2015 · 3 comments
Closed

Re-examine rules related to entering the goal zones #294

justbuchanan opened this issue Apr 23, 2015 · 3 comments

Comments

@justbuchanan
Copy link
Contributor

No description provided.

@jgkamat
Copy link
Contributor

jgkamat commented Apr 27, 2015

So, I've looked at the rules again, and they say that a team cannot enter their opponent's defence area (and touch the ball). We cannot have any defenders touch the ball within our own area (other than the goalie).

See the bottom and top of page 26. The manual can't seem to decide between the spelling of 'defense' or 'defence'...

Seems like we are good to go.

@jgkamat
Copy link
Contributor

jgkamat commented Apr 27, 2015

I've noticed when messing around with my new play, if a robot is just over the edge, he will still go over the line (if the ball is on the edge) when making a pivot kick. The path planner stops the robots from going into the defence zones, but when in a play, there seems to be no restriction.

@justbuchanan
Copy link
Contributor Author

Sounds good - I guess we've got it setup now the way it needs to be. The goal zone obstacles are created in the GameplayModule's constructor and added to each robot's path planner depending on whether or not they're the goalie (for our goal zone).

The reason the robot goes over the edge is because the Capture behavior (used as the first stage of PivotKick) only uses the path planner for the course_approach state, then switches to velocity control for fine_approach. If the ball is in range of fine_approach, the velocity control kicks in and we set the robot's velocity directly, which ignores any obstacles. Eventually these will be unified and rather than setting velocity directly, we'll run that through the path planner eventually. We'll leave this for now since it's an edge case that we don't see all that often and the path-planning isn't quite to the point where we can do this the way we want to.

@jgkamat jgkamat closed this as completed Apr 27, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants