-
Notifications
You must be signed in to change notification settings - Fork 27
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
added a new file Goalie_2.py #59
base: fsm
Are you sure you want to change the base?
Conversation
tactics/Goalie_2.py
Outdated
#expected_y = goalie_expected_y(state, self.kub.kubs_id) | ||
if state.ballVel.x < -10: | ||
#angle = state.ballVel.y/state.ballVel.x | ||
angle = math.atan(state.awayPos[state.opp_bot_closest_to_ball].theta) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also it is better not to use state.opp_bot_closest_to_ball here as it was removed as an unwanted belief state recently by @shamin1998 . @shamin1998 do we still have opp_bot_closest_to_ball variable in BS? Is the computation reliable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd removed the variables that weren't being used at the time. But I guess we'll need opp_bot_closest_to_ball for role selector, I'll put it back in
I am concerned about opp_bot_closest to ball here. Change that, maybe you can find out the closest opponent bot, when required. Don't use the variable from belief state. |
I have removed the issues and committed the changes. |
Do we need this goalie or old goalie code is in use? |
Parth had written a goalie code. Right now that is in use. |
So no need to keep this open I think |
No description provided.