Scribd
Upload
57 views

Assign Tasks

This document assigns jobs to study different classes in the RoboCup soccer simulation code to members of a group. It describes the classes WorldModel, Object, BasicPlayer, PlayerSettings, Player, and Formations. Each member is assigned one class to study - Nham is assigned WorldModel, Huyen is assigned Object, Trieu is assigned BasicPlayer, Dung is assigned PlayerSettings and Player, and Hat is assigned Formations. The members are asked to study the source code of their assigned class, report their findings, and propose ideas to improve tactics by changing the source code. The deadline to send these reports is April 24th.

Uploaded by

api-3849862
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
57 views

Assign Tasks

This document assigns jobs to study different classes in the RoboCup soccer simulation code to members of a group. It describes the classes WorldModel, Object, BasicPlayer, PlayerSettings, Player, and Formations. Each member is assigned one class to study - Nham is assigned WorldModel, Huyen is assigned Object, Trieu is assigned BasicPlayer, Dung is assigned PlayerSettings and Player, and Hat is assigned Formations. The members are asked to study the source code of their assigned class, report their findings, and propose ideas to improve tactics by changing the source code. The deadline to send these reports is April 24th.

Uploaded by

api-3849862
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 4

Studying AI with UvA_Trilearn 2003

1. A global overview of the various classes

Object Player Formations

WorldModel BasicPlayer

SenseHandler ActHandler

Connection

SOCCERSERVER

Utility classes which are used by the classes listed above but which
are not shown in the diagram are the following:
- PlayerSettings
- Logger, Timing (in Logger.C)
- ServerSettings
- SoccerTypes, SoccerCommand, Time (in SoccerTypes.C)
- Geometry, Line, Circle, Rectangle, VecPosition (all in Geometry.C)
- Parse
2. Some classes We may study

a. WorldModel(Nhâm)
This class contains the current representation of the world as observed by the agent. This
representation includes information about all the objects on the field such as the positions
and velocities of all the players and the ball. Information concerning the current play
mode is also stored, as well as the time and the score. Furthermore, the WorldModel
contains various types of methods that deal with the world state information in different
ways:

- Retrieval methods: for directly retrieving information about objects in the world
model; these methods are defined in the file WorldModel.C; this file also contains
methods for iterating over a specific set of objects; these methods make it possible
to compare information about different objects in the same set (e.g.
OBJECT_SET_OPPONENTS).
- Update methods: for updating the world model based on new sensory
information received from the SenseHandler; these methods are defined in the file
`WorldModelUpdate.C'.
- Prediction methods: for predicting future states of the world based on past
perceptions and for predicting the effect of actions performed by the agent; these
methods are defined in the file `WorldModelPredict.C'.
- High-level methods: for deriving high-level conclusions from basic information
about the state of the world (e.g. determining the fastest teammate to the ball);
these methods are defined in the file `WorldModelHighLevel.C'.

b. Object(Huyền)
This class contains information about all the objects in the simulation. Its implementation
is spread over six separate classes which together form an object type hierarchy. These
classes are the following:

- Object: abstract superclass that contains estimates (and associated confidence


values ) for the global positions of all the objects and that defines methods for
retrieving an updating this information.
- FixedObject: subclass of the Object class that contains information about the
stationary objects on the field (flags, lines and goals); it adds no additional
attributes to those inherited from the Object superclass.
- DynamicObject: subclass of the Object class that contains information about
mobile objects; it adds velocity information to the general information provided by
the Object class.
- BallObject: subclass of the DynamicObject class which contains information
about the ball; it adds no additional attributes to those inherited from the
DynamicObject superclass.
- PlayerObject: subclass of the DynamicObject class which contains information
about a specific player on the field (either a teammate or an opponent); it adds
attributes denoting the global neck angle and global of the player to the
information provided by the DynamicObject class and it holds a Boolean attribute
which indicates whether the player is a goalkeeper or not; the agent itself is not a
member of this class.
- AgentObject: subclass of the PlayerObject class which contains information
about the agent himself. It adds attributes denoting the stamina, view angle and
view quality of the agent to the information provided by the PlayerObject class.

c. BasicPlayer(Triệu)
This class defines the various skills than an agent can perform. The way in which these
skills are executed depends on the current state of the world model.

d. PlayerSettings(Dũng)
This class contains parameters which are used in the BasicPlayer class. An example of
such a parameter is `dPassEndSpeed' which denotes the desired end speed of the ball
when it is passed to a teammate. By changing the values of the parameters in this class it
is possible to adapt the behavior of the BasicPlayer.

e. Player(Dũng)
This class is a subclass of the BasicPlayer class that contains methods for reasoning
about the best possible action in a given situation. Action selection is based on the most
recent information about the state of the world as obtained from the WorldModel and on
the role of the agent in the current team formation. For making the final decision on
whether a particular type of action should be performed, the agent uses the parameter
values which are specified in the PlayerSettings class.

f. Formations(Hạt)
This class contains information about possible team formations as well as a method for
determining a strategic position on the field. Formations are read from a configuration
file (formations.conf) and are based on those used by the Simple Portugal team. The
implementation is spread over three separate classes:
- PlayerTypeInfo: contains information about a player type in a formation.
- FormationTypeInfo: contains information about one specific formation.
- Formations: contains information about all the possible team formations and stores
the currently used formation. This class is accessible from the WorldModel class.

3. Job assignment for each member

Each member must study source of correlative files:


- Nhâm: WorldModel
- Huyền: Object
- Triệu: BasicPlayer
- Dũng: PlayerSetting and Player
- Hạt: Formations
After finish studying, every one must report about content of the files and propose
many ideas to improve or change tactics or etc… by changing the source code.
We have 3 days for studing the source code. Please send to me before 11h pm 24th April.
I will summarize and reply to every one. After that, We will deliberate what next actions
to take.
My email: [email protected]
Thanks and wishing our group every success

You might also like