Add more skills

[MayankB11]

Skills to add :

• sDefendPoint
• sDribbleToPoint
• sDribbleTurn
• sGoalKeeping
• sGoToBall
• sGoToPoint
• sKickToGoal
• sKickToPoint
• sReceiveBall
• sTurnToAngle
• sTurnToPoint

If there is an error in any skill, discuss and correct it.
Comment here whichever skill you are working on so that two persons don't work on the same

Deadline : 16th May, 2017.
@americast @ashishkg0022 @sipah00

[americast]

@MayankB11 I would like to work on sTurnToAngle.

[ashishkg0022]

i will work on sDribbleTurn , sKickToGoal , sKickToPoint , sDefendPoint for now .

[sipah00]

I will work on sGoToBall, sGoToPoint,sTurnToPoint for now.

[MayankB11]

@americast Instead of "return getRobotCommandMessage(botID, 0, 0, omega, 0, true)" it should use the send_command method defined in the skill_node module. Take reference from the tactics that were already completed like sKick.py

[ashishkg0022]

@MayankB11 sKickToGoal has no class in skills_union.py . so how to send the power value in the send_command method ?

[annimesh2809]

@MayankB11 sKickToGoal has no class in skills_union.py . so how to send the power value in the send_command method ?

@ashishkg0022 I don't think we require sKickToGoal as sKickToPoint is more general and covers it.

[MayankB11]

Exactly, sKickToGoal just kicks to the centre of the goal with full power. So, all its parameters are pre-defined and its param can be None.

[sipah00]

@MayankB11 , in sReceiveBall.cpp ,at last line ---return getRobotCommandMessage(botID, 0, 0, 0, 0, false); here passed parameters are temp(as mentioned for Testing) ...So I want to know actual parameters that should be passed here.

[MayankB11]

@sipah00 Since the ballPos is already in state, so param passed will be None. You can use the state to predict the ball position and adjust the bot's position and angle accordingly.

[americast]

@MayankB11 I would like to work on sReceiveBall, sGoalKeeping and sDribbleToPoint.

[MayankB11]

@ashishkg0022 Check for the errors in sKickToPoint.py