[robocup-small] New Referee Box Protocol

Christopher Head chead at chead.ca
Tue Dec 25 03:10:05 EST 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

On Tue, 25 Dec 2012 09:47:55 +0200
Ali Erdinç Köroğlu <erdinc at neu.edu.tr> wrote:

> Hi,
> 
> On Sat, 17 Nov 2012 01:55:55 +0100
> Michael Bleier <michael.bleier at robotics-erlangen.de> wrote:
> 
> | Hi all,
> | 
> | One thing is bugging me for years. The keeper is only allowed to be 
> | exchanged in consensus with the referee. Unfortunately the referee
> has | no way to signal this decision. Teams either can only change
> the keeper | in a timeout or they rely on auto detection like using
> the robot in the | defense area. I can come up with a couple
> scenarios when auto detection | will fail and I have seen it happen
> during RoboCup. | 
> | Should we add a keeper exchange signal to the referee box or even
> send | the active keeper id (this would also solve any arguing about
> which | robot was the actual keeper)?
> 
> Sending the active keeper id  may cause some problems, instead its
> better to have keeper exchange signal
> 

What kind of problems? I can see a lot of problems with just sending an
exchange signal (namely, you don’t tell the team which robot should be
the keeper), but what are the problems with sending the active keeper
ID?

Chris
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.19 (GNU/Linux)

iEYEAREDAAYFAlDZX2AACgkQXUF6hOTGP7d+SgCeNp0wlBdpiMvBdn+CemrObFBU
NbYAnA/GiWgX/T6DGfpRyWB9mkUTbkV1
=dbri
-----END PGP SIGNATURE-----


More information about the robocup-small mailing list